Yes, stable/stein is the last release of neutron-lbaas, and the latest stable branch that will remain. On Mon, May 13, 2019 at 2:07 AM Lajos Katona <lajos.katona@ericsson.com> wrote:

Hi,

This means that stable/stein is the last where these projects can include neutron-lbaas?

Thanks for the heads up.

Regards Lajos

On 2019. 05. 13. 10:34, Adam Harwell wrote:

As you are hopefully already aware, the Neutron-LBaaS project is being retired this cycle (and a lot of the patches to accomplish this will land in the next few days). From a quick code search, it seems the following projects still include neutron-lbaas in their zuul job configs:

networking-odl networking-midonet senlin vmware-nsx zaqar

For projects on this list, the retirement of neutron-lbaas *will* cause your zuul jobs to fail. *Please take action to remove this requirement!* It is possible that it is simply an extra unused requirement, but if your project is actually using neutron-lbaas to create loadbalancers, it will be necessary to convert to Octavia.

If you need assistance with this change or have any questions, don't hesitate to stop by #openstack-lbaas on IRC and we can help!

--Adam Harwell

If you are using the CLI, there is a tutorial on how to use most of the functionality of Octavia here: https://docs.openstack.org/octavia/latest/user/guides/basic-cookbook.html If you are using the API directly, then the only action would be to include Octavia in your projects list (if it isn't already) and change your endpoint from neutron to octavia. The Octavia API is fully compatible with the Neutron-LBaaS v2 API spec. If you are using the python client, you will need to switch to python-octaviaclient or to the openstack SDK, and I am unfortunately not aware of a guide to do that. However, it is a remarkably similar service (object model and API are 100% compatible), so making the transition should hopefully not be very difficult, and we are happy to help in #openstack-lbaas on IRC if you need specific assistance. --Adam On Mon, May 13, 2019 at 2:13 AM Takashi Yamamoto <yamamoto@midokura.com> wrote:

On Mon, May 13, 2019 at 5:42 PM Adam Harwell <flux.adam@gmail.com> wrote:

...

As you are hopefully already aware, the Neutron-LBaaS project is being

...

From a quick code search, it seems the following projects still include neutron-lbaas in their zuul job configs:

networking-odl networking-midonet senlin vmware-nsx zaqar

For projects on this list, the retirement of neutron-lbaas *will* cause your zuul jobs to fail. Please take action to remove this requirement! It is possible that it is simply an extra unused requirement, but if your

retired this cycle (and a lot of the patches to accomplish this will land in the next few days). project is actually using neutron-lbaas to create loadbalancers, it will be necessary to convert to Octavia.

is there a guide for the conversion?

...

If you need assistance with this change or have any questions, don't

hesitate to stop by #openstack-lbaas on IRC and we can help!

...

--Adam Harwell

No, unfortunately we did not end up with a model that easily allowed for a "shim" system to allow use of older drivers. We've been trying to work with the vendors to get their drivers prepared, but I don't know how many of them actually finished the work. That said, stable/stein should be usable for the time being with no real change -- we simply will not be maintaining the service any longer (except possibly extreme cases like major security patches) or providing any further releases. If you need to adjust your code to continue to use the stein release instead of master, that is a perfectly valid option. --Adam On Mon, May 13, 2019 at 8:01 PM Takashi Yamamoto <yamamoto@midokura.com> wrote:

i'm more interested in the backend side. i've heard a plan to introduce some glue code to allow octavia to use lbaas v2 backend drivers with no or minimal modifications before deprecation/removal. (i guess it was during atlanta ptg but i might be wrong) did it happen?

On Tue, May 14, 2019 at 8:41 AM Adam Harwell <flux.adam@gmail.com> wrote:

...

If you are using the CLI, there is a tutorial on how to use most of the

functionality of Octavia here:

...

https://docs.openstack.org/octavia/latest/user/guides/basic-cookbook.html

...

If you are using the API directly, then the only action would be to

include Octavia in your projects list (if it isn't already) and change your endpoint from neutron to octavia. The Octavia API is fully compatible with the Neutron-LBaaS v2 API spec.

...

If you are using the python client, you will need to switch to

python-octaviaclient or to the openstack SDK, and I am unfortunately not aware of a guide to do that. However, it is a remarkably similar service (object model and API are 100% compatible), so making the transition should hopefully not be very difficult, and we are happy to help in #openstack-lbaas on IRC if you need specific assistance.

...

--Adam

On Mon, May 13, 2019 at 2:13 AM Takashi Yamamoto <yamamoto@midokura.com>

wrote:

...

...

On Mon, May 13, 2019 at 5:42 PM Adam Harwell <flux.adam@gmail.com>

wrote:

...

...

As you are hopefully already aware, the Neutron-LBaaS project is

being retired this cycle (and a lot of the patches to accomplish this will land in the next few days).

...

From a quick code search, it seems the following projects still include neutron-lbaas in their zuul job configs:

networking-odl networking-midonet senlin vmware-nsx zaqar

For projects on this list, the retirement of neutron-lbaas *will* cause your zuul jobs to fail. Please take action to remove this requirement! It is possible that it is simply an extra unused requirement, but if your project is actually using neutron-lbaas to create loadbalancers, it will be necessary to convert to Octavia.

is there a guide for the conversion?

...

If you need assistance with this change or have any questions, don't

hesitate to stop by #openstack-lbaas on IRC and we can help!

...

--Adam Harwell