[openstack-dev] [Quantum][LBaaS] LBaaS development plan for Havana
Vasudevan, Swaminathan (PNB Roseville)
swaminathan.vasudevan at hp.com
Thu Apr 25 19:13:29 UTC 2013
Do you have an Lbaas meeting today.
If so what is the IRC channel.
From: Eugene Nikanorov [mailto:enikanorov at mirantis.com]
Sent: Thursday, April 25, 2013 9:24 AM
To: Sumit Naiksatam
Cc: OpenStack Development Mailing List; Salvatore Orlando; Youcef Laribi
Subject: Re: [openstack-dev] [Quantum][LBaaS] LBaaS development plan for Havana
No, thanks for reminding! need to think how it will fit into the plan (at which step it would be easier to implement)
Youcef, drivers are only vendor-specific in my diagram (both plugin-side drivers or agent-side drivers).
Device Inventory or scehduling don't belong to drivers, but drivers could rely on them.
On Thu, Apr 25, 2013 at 8:09 PM, Sumit Naiksatam <sumitnaiksatam at gmail.com<mailto:sumitnaiksatam at gmail.com>> wrote:
Thanks. During the summit we discussed the notion of a logical loadbalancer/device which we later moved to calling a loadbalancer service instance (one or more tenant, as desired). Is this capture somewhere in the scheme of things?
On Thu, Apr 25, 2013 at 8:38 AM, Eugene Nikanorov <enikanorov at mirantis.com<mailto:enikanorov at mirantis.com>> wrote:
I've prepared a list of a major action items needed for futher development of multivendor and production-ready LBaaS: https://wiki.openstack.org/wiki/Quantum/LBaaS/HavanaPlan
I'd be glad to here your feedback about it.
I think we need to start discussing these items in more details.
Aside from this list I imply that vendors will create their drivers choosing whatever architecture is reasonable for their solution, while quantum provides convenient way of integrating them.
Also, as you can see, some of action items (like service insertion or device inventory) have scope beyond LBaaS so I expect folks who are interested in other services to participate in corresponding discussions.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev