Difference between revisions of "QuantumAPIExtensions"
| Line 3: | Line 3: | ||
This extension mechanism should strive to be inline with the standard [[ http://wiki.openstack.org/JorgeWilliams?action=AttachFile&do=get&target=Extensions.pdf | OpenStack plans for extensions ]] | This extension mechanism should strive to be inline with the standard [[ http://wiki.openstack.org/JorgeWilliams?action=AttachFile&do=get&target=Extensions.pdf | OpenStack plans for extensions ]] | ||
| + | |||
| + | During the summit, we discussed that the set of extensions supported must be queriable. This will be the way that a tenant can detect if a provider supports a certain functionality that is not part of the "Base API". | ||
| + | |||
| + | Examples of functionality to be exposed via extensions include (but are not limited to): | ||
| + | * QoS properties | ||
| + | * ACLs | ||
Revision as of 21:23, 6 May 2011
Quantum Plugins can expose additional functionality beyond basic L2 connectivity using Extensions.
This extension mechanism should strive to be inline with the standard OpenStack plans for extensions
During the summit, we discussed that the set of extensions supported must be queriable. This will be the way that a tenant can detect if a provider supports a certain functionality that is not part of the "Base API".
Examples of functionality to be exposed via extensions include (but are not limited to):
- QoS properties
- ACLs
