[octavia][lbaas][neutron-lbaas] Octavia v1 API and neutron-lbaas retirement
Hi Octavia folks, This email is to announce that we are currently in the process of retiring both neutron-lbaas and the Octavia v1 API. We said this would happen in September 2019 or the OpenStack "U" release, whichever came first. Because September of 2019 occurs during the Train release cycle, there will be no Train release of neutron-lbaas. We will therefore be retiring the neutron-lbaas repository and the Octavia v1 API effective immediately, as there is no reason to continue to maintain them if no release is forthcoming. Reminder: The Octavia v1 API was used by the neutron-lbaas Octavia provider driver and was not an end-user API. The Octavia v1 API is a proprietary API and is not compatible with the LBaaS v2 API specification or any other LBaaS API specification. If you have questions about this deprecation cycle please see the FAQ wiki: https://wiki.openstack.org/wiki/Neutron/LBaaS/Deprecation If you have questions or concerns not covered by the FAQ, please reach out to the Octavia team either by using the "[octavia]" subject prefix on this mailing list or in our IRC channel #openstack-lbaas. We look forward to working with you moving forward with Octavia LBaaS! --Adam
Are you going to retire the complete repo with all branches including the maintained ones? That means no bug fixes can merge for these anymore, Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Mary Higgins, Sri Rasiah HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
The intent is for stable branches to remain. If there's something special I need to do in the retirement prices to guarantee this works, I'd appreciate a pointer in the right direction. So far the myriad of interdependent patches required across all the different repos involved has been a bit confusing, so all help is welcome. --Adam On Sat, May 11, 2019, 03:51 Andreas Jaeger <aj@suse.com> wrote:
Are you going to retire the complete repo with all branches including the maintained ones? That means no bug fixes can merge for these anymore,
Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany <https://maps.google.com/?q=Maxfeldstr.+5,+90409+N%C3%BCrnberg,+Germany&entry=gmail&source=g> GF: Felix Imendörffer, Mary Higgins, Sri Rasiah HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On 11/05/2019 13.56, Adam Harwell wrote:
The intent is for stable branches to remain. If there's something special I need to do in the retirement prices to guarantee this works, I'd appreciate a pointer in the right direction. So far the myriad of interdependent patches required across all the different repos involved has been a bit confusing, so all help is welcome.
Ah, that is more complicated ;) I'll review accordingly and give advise on the changes. Basically, jobs running master can remove lbaas now (and some must since an enable_plugin neutron-lbaas will fail (I assume)) but jobs running on stable should not change, Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Mary Higgins, Sri Rasiah HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
participants (2)
-
Adam Harwell
-
Andreas Jaeger