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
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
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.
Completely true Michael,
It’s like my mind is already in state that this project will loose support in
next few releases. 2 are the standard for OpenStack. So like personally I don’t
like to work and contribute to something what will be lost in future. And not
like years future but near future
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
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
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
Reply-To: OpenStack List
Date: Tuesday, December 6, 2016 at