[openstack-dev] [neutron][lbaas] Querries Regarding Blueprint for LBaaS API and Object Model improvement
dougw at a10networks.com
Wed Dec 17 05:42:35 UTC 2014
Adding tags for [neutron][lbaas]
Juno lbaas (v1) has pool as the root model, with VIP.
Kilo lbaas (v2), you are correct, vip is splitting into loadbalancer and listener, and loadbalancer is the root object. And yes, the new objects get new URIs.
Both v1 and v2 plugins will be available in Kilo.
From: Shreshtha Joshi <shreshtha.joshi at tcs.com<mailto:shreshtha.joshi at tcs.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Tuesday, December 16, 2014 at 9:36 PM
To: "openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Cc: Partha Datta <partha.datta at tcs.com<mailto:partha.datta at tcs.com>>, Deepankar Gupta <deepankar.gupta at tcs.com<mailto:deepankar.gupta at tcs.com>>, "johnbrandonlogan at gmail.com<mailto:johnbrandonlogan at gmail.com>" <johnbrandonlogan at gmail.com<mailto:johnbrandonlogan at gmail.com>>
Subject: [openstack-dev] Querries Regarding Blueprint for LBaaS API and Object Model improvement
I wanted to know the approach has been followed for LBaaS implementation in Openstack (juno) out of the following in the link<https://etherpad.openstack.org/p/neutron-lbaas-api-proposals>(https://etherpad.openstack.org/p/neutron-lbaas-api-proposals). Is it-
1. Existing Core Resource Model
2. LoadBalancer Instance Model
3. Vip-Centric Model
Currently I find Pool as the root object that has a VIP associated with it rather than Listeners and LoadBalancers in various openstack documents.
But while investigating the same, I came across a blueprint<https://blueprints.launchpad.net/neutron/+spec/lbaas-api-and-objmodel-improvement> (https://blueprints.launchpad.net/neutron/+spec/lbaas-api-and-objmodel-improvement) for LBaaS Api and object model improvement. It talks about moving the current VIP object to Listener and Listener will be linked to a LoadBalancer in the upcoming releases,
I wanted to know the current approach followed for openstack-juno and if in the upcoming releases(Kilo)-
* Are we planning to have new APIs for /Listener and /Loader and there will be no VIP object and its corresponding API.
* Or we will be having VIP object and its corresponding API, creation of which will result in creation of Loadbalancer and /Listener at the backend itself.
If you find the above investigation incorrect, please feel free to point to the right direction.
Thanks & Regards
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev