Not sure if you're in IRC, but I'm curious what:
DELETE /os-networks/{id}/association
does still. It looks like it just calls DB's network_disassociate() method which updates the project_id and host of the network to None. If we're following other OpenStack APIs I think a:
POST /os-networks/{id}/actions
with a body of:
{ "disassociate": null }
might be the most compliant. It seems like this lines up with our server "actions" (http://docs.openstack.org/cactus/openstack-compute/developer/openstack-compute-api-1.1/content/Server_Actions-d1e3229.html)
That being said this is a pretty big switch from what you have so I'm open for talking more about the best approach! Other than that I think:
Delete networks: DELETE /os-networks/{id}
List all networks: GET /os-networks/
Get specific network: GET /os-networks/{id}
Looks great.
« Back to merge proposal
Not sure if you're in IRC, but I'm curious what:
DELETE /os-networks/ {id}/associatio n
does still. It looks like it just calls DB's network_ disassociate( ) method which updates the project_id and host of the network to None. If we're following other OpenStack APIs I think a:
POST /os-networks/ {id}/actions
with a body of:
{
"disassociate": null
}
might be the most compliant. It seems like this lines up with our server "actions" (http:// docs.openstack. org/cactus/ openstack- compute/ developer/ openstack- compute- api-1.1/ content/ Server_ Actions- d1e3229. html)
That being said this is a pretty big switch from what you have so I'm open for talking more about the best approach! Other than that I think:
Delete networks:
DELETE /os-networks/{id}
List all networks:
GET /os-networks/
Get specific network:
GET /os-networks/{id}
Looks great.