Hi Dan, I 101% agree we need to add filtering on Quantum API. This is already on the roadmap for the v1.1 API blueprint I'm preparing.
Netstack people: please let me know if there's something else you'd like to add to Quantum API v1.1! Other items on my roadmap (in a nutshell): - ATOM links (so that clients can navigate responses) - Pagination for lists - Rate Limiting - Concept of "operational state" for resources - Extending the core API by bringing in some of the current extensions Salvatore From: netstack-bounces+salvatore.orlando=eu.citrix....@lists.launchpad.net [mailto:netstack-bounces+salvatore.orlando=eu.citrix....@lists.launchpad.net] On Behalf Of Dan Wendlandt Sent: 06 September 2011 03:06 To: netstack@lists.launchpad.net Subject: [Netstack] API querying As far as next steps for the API (yes, its time to think about next steps already!) one area that I'd like to push on is support for querying in the API. The use case that really jumped out when doing the QuantumManager work was to be able to search to find the port-id + network-id associated with a particular interface-id. This save the "interface service" from having to duplicate quantum state in its own data store in order to efficiently perform operations on the port (e.g., delete the port when a VM is deallocated). Thoughts? Dan -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dan Wendlandt Nicira Networks, Inc. www.nicira.com<http://www.nicira.com> | www.openvswitch.org<http://www.openvswitch.org> Sr. Product Manager cell: 650-906-2650 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- Mailing list: https://launchpad.net/~netstack Post to : netstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~netstack More help : https://help.launchpad.net/ListHelp
