Hi Salvatore,
Just to confirm, the proposal is to keep:
POST /networks/{net_id}/ports/{port_id}/attachment
DELETE /networks/{net_id}/ports/{port_id}/attachment
GET /networks/{net_id}/ports/{port_id}/attachment
But remove:
POST /networks/{net_id}/attachments
GET /networks/{net_id}/attachments
Is that correct?
Thanks,
~Sumit.
From: openstack-bounces+snaiksat=cisco....@lists.launchpad.net
[mailto:openstack-bounces+snaiksat=cisco....@lists.launchpad.net] On
Behalf Of Salvatore Orlando
Sent: Wednesday, June 08, 2011 4:02 AM
To: <openstack@lists.launchpad.net> (openstack@lists.launchpad.net)
Subject: [Openstack] [NetStack] Proposed changes to Quantum API
Hi,
Following feedback on the proposed API specification, we are proposing a
few changes:
1) Removing operation: POST /networks/{net_id}/attachments
This is an orchestration operation (see second diagram for 'Create
Network
<http://wiki.openstack.org/QuantumAPIUseCases#Create_Network_and_Spawn_V
M> ' use case). It has been suggested that orchestration should be
avoided in low-level services in order to ensure each operation is
atomic thus limiting rollback issues.
2) Removing operation: GET /networks/{net_id}/attachments
This operation retrieves all the resources attached to a network. In
nova the 'detail' action is typically used for this purpose. It would
make more sense to change it into GET /networks/{net_id}/detail which
would list all ports with all attributes of ports (including
attachments).
I would be more than happy to receive your feedback on the proposed
changes.
Also, please feel free to use this email thread to provide further
feedback on the API or propose more changes.
Thanks,
Salvatore
_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
