Hi, On Wed, 2010-12-08 at 13:34 +0100, [email protected] wrote: > * PUT /api/addresses/:id/associate > Get 'instance_id' parameter (means it will associate given IP > address > with given instance) > * POST /api/addresses/:id/release > 'Disassociate' IP address from the instance.
FWIW, in the RHEV-M API we modelled association operations like this as: POST /api/instances/inst1/addresses HTTP/1.1 Content-type: application/xml <address id="123456"/> HTTP/1.1 201 Created Location: http://{host}/api/instances/inst1/addresses/123456 Content-Type: application/xml <address id="123456" href="/api/instances/inst1/addresses/123456"> <visibility>PUBLIC</visibility> <instance id="inst1" href="/api/instances/inst1"/> </address> DELETE /api/instances/inst1/addresses/123456 HTTP/1.1 HTTP/1.1 204 No Content i.e. managing the association of address with instances would be done using an addresses sub-collection under each instance Cheers, Mark.
