This features are supported by default in Octavia. So like keeping HAProxy namespace driver up and running is really loosing the whole value added which Octavia delivers. You can still work on NLBaaS v2 project but you need to remember that by default octavia will be used in cloud as LBaaS and NLBaaS will be deprecated starting with P release - right now we’re merging API into Octavia to provide backward compatibility - and in this project just bugs will be fixed. Michael any thoughts about what I just said?
Regards, Lubosz Kosnik Cloud Software Engineer OSIC [email protected]<mailto:[email protected]> On Dec 13, 2016, at 9:47 AM, Bartek Żurawski <[email protected]<mailto:[email protected]>> wrote: Hello, Just to be sure about adding new feature to lbaas, should we still proposing new features like this proposed by Zhi to neutron/lbaas or already to Octavia ? @Zhi, yep I like those two extensions it will be very helpful for LB. Have you already do something with that, or for now you just asking for opinion ? Bartek On 8 December 2016 at 05:33, Brandon Logan <[email protected]<mailto:[email protected]>> wrote: On Wed, 2016-12-07 at 06:50 -0800, Michael Johnson wrote: > Lubosz, > > I would word that very differently. We are not dropping LBaaSv2 > support. It is not going away. I don't want there to be confusion > on > this point. > > We are however, moving/merging the API from neutron into Octavia. > So, during this work the code will be transitioning repositories and > you will need to carefully synchronize and/or manage the changes in > both places. > Currently the API changes have patchsets up in the Octavia > repository. > However, the old namespace driver has not yet been migrated over. I know I've talked about using the namespace driver as a guinea pig for the nlbaas to octavia shim driver layer, but I didn't know it would be fully supported in octavia. This will require a bit more work because of the callbacks the agent expects to be able to call. > > Michael > > > On Tue, Dec 6, 2016 at 8:46 AM, Kosnik, Lubosz > <[email protected]<mailto:[email protected]> > om> wrote: > > Hello Zhi, > > So currently we’re working on dropping LBasSv2 support. > > Octavia is a big-tent project providing lbass in OpenStack and > > after merging > > LBasS v2 API in Octavia we will deprecate that project and in next > > 2 > > releases we’re planning to completely wipe out that code > > repository. If you > > would like to help with LBasS in OpenStack you’re more than welcome > > to start > > working with us on Octavia. > > > > Cheers, > > Lubosz Kosnik > > Cloud Software Engineer OSIC > > > > On Dec 6, 2016, at 6:04 AM, Gary Kotton > > <[email protected]<mailto:[email protected]>> wrote: > > > > Hi, > > I think that there is a move to Octavia. I suggest reaching out to > > that > > community and see how these changes can be added. Sounds like a > > nice > > addition > > Thanks > > Gary > > > > From: zhi <[email protected]<mailto:[email protected]>> > > Reply-To: OpenStack List > > <[email protected]<mailto:[email protected]>> > > Date: Tuesday, December 6, 2016 at 11:06 AM > > To: OpenStack List > > <[email protected]<mailto:[email protected]>> > > Subject: [openstack-dev] [neutron][lbaas] New extensions for > > HAProxy driver > > based LBaaSv2 > > > > Hi, all > > > > I am considering add some new extensions for HAProxy driver based > > Neutron > > LBaaSv2. > > > > Extension 1, multi subprocesses supported. By following this > > document[1], I > > think we can let our HAProxy based LBaaSv2 support this feature. By > > adding > > this feature, we can enhance loadbalancers performance. > > > > Extension 2, http keep-alive supported. By following this > > document[2], we > > can make our loadbalancers more effective. > > > > > > Any comments are welcome! > > > > Thanks > > Zhi Chang > > > > > > [1]: http://cbonte.github.io/haproxy-dconv/1.6/configuration.html#c > > pu-map > > [2]: > > http://cbonte.github.io/haproxy-dconv/1.6/configuration.html#option > > %20http-keep-alive > > ___________________________________________________________________ > > _______ > > OpenStack Development Mailing List (not for usage questions) > > Unsubscribe: > > [email protected]?subject:unsu<http://[email protected]/?subject:unsu> > > bscribe > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > > > > ___________________________________________________________________ > > _______ > > OpenStack Development Mailing List (not for usage questions) > > Unsubscribe: > > [email protected]?subject:unsu<http://[email protected]/?subject:unsu> > > bscribe > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > _____________________________________________________________________ > _____ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: > [email protected]?subject:unsubs<http://[email protected]/?subject:unsubs> > cribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe<http://[email protected]/?subject:unsubscribe> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]<mailto:[email protected]>?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
