For the octavia API to truly be standalone, it needs to have capability parity with Neutron LBaaS’s API. Neutron LBaaS has the luxury of piggy-backing off of Neutron’s API. This gives Neutron LBaaS’s API resources many capabilities for free. This document is meant to enumerate those capabilities that the octavia API does not possess at the time of this writing.
Complete the tasks enumerated in the Work Items section
There will be some minor data model changes to octavia in support of this change.
This change will have significant impact to the octavia API.
This change will improve octavia security by adding keystone authentication.
No expected change.
Users will be able to use the new octavia API endpoint for LBaaS.
This change may slightly improve performance by reducing the number of software layers requests will traverse before responding to the request.
Over time the neutron-lbaas package will be deprecated and deployers will only require octavia for LBaaS.
This will simplify LBaaS development by reducing the number of databases as well as repositories that require updating for LBaaS enhancements.
blogan diltram johnsom rm_you dougwig
Implement the following API Capabilities:
Implement the following additional features that n-lbaas maintains:
Other Features to be Considered:
None
Api tests from neutron-lbaas will be used to validate the new octavia API.
The octavia api reference will need to be updated.
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.