The v1.1 spec is still marked as beta, yes.
The extensions code however was included in Cactus and is fully working. From
the looks of your PDF you need a top level resource with several sub-resources.
I think most of this should be supported with the existing ResourceExtension
code.
You might
It is my understanding that we would use the standard Openstack extension
mechanism, though I don't believe jorge's proposal has been officially
accepted yet.
However our plugin model will require a complex way of expressing capability
that might not be a part of jorge's proposal.
T-Mobile
On Sat, May 21, 2011 at 11:51 AM, Ram Durairaj (radurair) <
radur...@cisco.com> wrote:
> Hi Dan:
>
>
>
> As far as I remember, In Design summit, we’ve agreed to expose “extra”
> attributes for Virtual networks and any other vendor specific features using
> “API-Extensions” and possibly thru existi
Hi Dan:
As far as I remember, In Design summit, we've agreed to expose "extra"
attributes for Virtual networks and any other vendor specific features
using "API-Extensions" and possibly thru existing Openstack extension
mechanisms. Don't recall that we've concluded on Jorge's proposal.
Als
Hi Ying,
Thanks for sending this out. I think many of the capabilities you are
looking to introduce (ability to configure ACLs, QoS, packet statistics) are
definitely things we will want Quantum to expose as API extensions
(and possibly in the future, as part of the base API if they are
sufficien
Hi all,
We just posted a proposal for OpenStack Quantum Service API extension on
community wiki page at
http://wiki.openstack.org/QuantumAPIExtensions?action=AttachFile&do=view
&target=quantum_api_extension.pdf
or
http://wiki.openstack.org/QuantumAPIExtensions?action=AttachFile&do=view
&targ
6 matches
Mail list logo
