Hi Salvatore,
Thanks for bring up this discussion. Regarding to Quantum API v1.1, we could add some improvements on the API extensions. Here are something we can add: 1. Having mechanism to verify and enforce vendor's ID used by API extension. 2. Under the extension/ directory, each vendor's extensions are grouped in one single directory with vendor's ID. This needs to be enabled and enforced by the framework. 3. Framework allows fine granularity check. Eg. checking the existence of an individual action from a particular plugin. Best, Ying From: netstack-bounces+yinliu2=cisco....@lists.launchpad.net [mailto:netstack-bounces+yinliu2=cisco....@lists.launchpad.net] On Behalf Of Salvatore Orlando Sent: Monday, September 19, 2011 7:49 AM To: netstack@lists.launchpad.net Subject: [Netstack] Proposing sessions for Openstack design summitq Hello fellow NetStackers, The list of proposed session at http://summit.openstack.org/sessions is filling up, and I think it is time we start proposing our own sessions as well. Actually, there are already two accepted sessions for NetStack: 1. Donabe/API models: http://summit.openstack.org/sessions/view/29 2. Continuous integration planning: http://summit.openstack.org/sessions/view/35 On top of these two, I would also consider having the following sessions (in order of importance): 1. Higher layer network services (L4/L7), e.g.: Firewall, NAT, VPN 2. Improved authorization framework for Quantum, with a full RBAC model. 3. Quantum API v1.1 a. Synchronous vs Asynchronous behaviour and concept of "Operational Status" b. Improvements such as Filtering, Rate Limiting, Resource Links, pagination 4. Cloud Bridging APIs in Quantum What's your opinion? Cheers, Salvatore
-- Mailing list: https://launchpad.net/~netstack Post to : netstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~netstack More help : https://help.launchpad.net/ListHelp
