You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltacloud.apache.org by "Andrew Brady (JIRA)" <ji...@apache.org> on 2013/06/27 14:42:21 UTC
[jira] [Created] (DTACLOUD-574) Address Model should allow the use
of an actual identifier for an instance instead of just the IP
Andrew Brady created DTACLOUD-574:
-------------------------------------
Summary: Address Model should allow the use of an actual identifier for an instance instead of just the IP
Key: DTACLOUD-574
URL: https://issues.apache.org/jira/browse/DTACLOUD-574
Project: DeltaCloud
Issue Type: Bug
Components: Server
Reporter: Andrew Brady
Priority: Minor
The model for Address doesn't support setting both the address and the id. And, since it doesn't support setting the href it doesn't allow accessing an address specifically by id (which is how you would do it in OpenStack).
Even just making the "to_hash" method on Address use a ternary on href and making that attribute settable would be an acceptable solution. The only real use case is to be able to retrieve address details for an individual address.
An example from mock driver:
<address href="http://localhost:3001/api/addresses/192.168.0.4" id="192.168.0.4"><ip>192.168.0.4</ip><actions><link href="http://localhost:3001/api/addresses/192.168.0.4" method="delete" rel="destroy"/><link href="http://localhost:3001/api/addresses/192.168.0.4/associate" method="post" rel="associate"/></actions></address>
But 192.168.0.4 isn't an id, it's an IP
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira