Open Stack

Ocata and Pike should already be EOL as far as I am aware. It should have
been done a while ago. Thanks for pointing out this error!

Here is the patch to correct this: https://review.opendev.org/719097


The discussion at hand is marking the Queens release as EOL, followed
shortly by Rocky. Testing on these branches is becoming less and less
stable, and is leeching time from an already overly taxed pool of
developers. Even if we wanted to merge more backported fixes to these
repos, it would be difficult to do with any level of confidence. There are
no outstanding patches for stable/queens as of this moment.

Barring any further comment, we will proceed with this EOL at the end of
next week (targeting Friday, April 17th).

Comments for Queens should be left on the following patch:
https://review.opendev.org/719099

Thanks,
    Adam Harwell (Octavia PTL)

On Mon, Apr 6, 2020, 03:27 Előd Illés <elod.illes at est.tech> wrote:

> Hi,
>
> First of all, sorry for the late response. I've checked what is the
> current state of Octavia according to *openstack/releases* repository and
> it seems even Ocata is not yet EOL'd. As far as I see from the discussion,
> the Team wants to move Queens and Pike to EOL. I suggest to do it branch by
> branch, so as a first step please EOL Ocata with the steps described in
> Stable Branches page [1]. If that is ready, then do the same for Pike, and
> then Queens. If you have any question feel free to ping me on IRC (elod @
> #openstack-stable or #openstack-releases) and I'll try to help you.
>
> Note: Extended Maintenance helps operators / interested parties with
> having a common place where they can cooperate and push (backport) bugfixes
> to ease everyone's work. As long as there are someone (in best case: more
> people) who comes and fixes bugs and maintains the CI, the "EM" branches
> can be kept open. (To keep the CI functional, it is usually easier if it is
> done regularly with small fixes, when something failure comes in). Of
> course, if there are no volunteer, who fixes the gate failures and a branch
> becomes "Unmaintained" for ~6 months, then it should be EOL'd. Sorry if
> this was obvious, just wanted to have it here :)
>
> Thanks,
>
> Előd
>
> [1]
> https://docs.openstack.org/project-team-guide/stable-branches.html#end-of-life
>
>
> On 2020. 04. 05. 13:19, Carlos Goncalves wrote:
>
> Hey folks,
>
> Apologies for my late response in this thread.
>
> This topic was also discussed on IRC #openstack-lbaas on March 19 [1]. I
> had some initial reservations that were clarified as we discussed the topic
> further. I am supportive now of declaring the Queens release EOL.
>
> Carlos
>
> [1]
> http://eavesdrop.openstack.org/irclogs/%23openstack-lbaas/%23openstack-lbaas.2020-03-19.log.html
>
> On Fri, Mar 20, 2020 at 2:44 AM Michael Johnson <johnsomor at gmail.com>
> wrote:
>
>> Hi Erik,
>>
>> The Queens branch entered Extended Maintenance (EM) on August 25th,
>> 2019 (later extended to October 25th, 2019 to accommodate release team
>> resources[1]) and was tagged EM on November 6th, 2019.
>>
>> This proposal is to exit Extended Maintenance and mark the Queens
>> release as End-of-Life(EOL). This is following the guidelines for
>> stable branch releases[2].
>>
>> Currently the Octavia team is maintaining five branches and supporting
>> queens is becoming more difficult as the test jobs are still based on
>> the Ubuntu Xenial release (released April 21. 2016). The python 2.7
>> end-of-life combined with the older OS version has made it hard to
>> keep reliable test jobs[3]. Backporting patches is also becoming more
>> difficult as the Octavia code base has rapidly evolved in the two
>> years since it was released.
>>
>> If you or others are willing to help us with fixing the queens jobs
>> and backporting patches, that would be great and we may be able to
>> leave the queens branch in Extended Maintenance. If not, Adam is
>> proposing we move it into EOL.
>>
>> Personally, I agree with Adam that it is time to mark the Queens
>> release as EOL. Since you can run newer releases of Octavia on older
>> clouds (as many do), the branch cannot release under EM, and patches
>> on that branch are few.
>>
>> Michael
>>
>> [1]
>> https://github.com/openstack/releases/commit/be797b61677b1eafc0162bd664f09db54287ac81#diff-8fa0a5ef8165646609d2f3d50646c597
>> [2]
>> https://docs.openstack.org/project-team-guide/stable-branches.html#end-of-life
>> [3]
>> https://zuul.openstack.org/builds?project=openstack%2Foctavia&branch=stable%2Fqueens&pipeline=check&job_name=octavia-v2-dsvm-scenario
>>
>> On Thu, Mar 19, 2020 at 11:40 AM Erik McCormick
>> <emccormick at cirrusseven.com> wrote:
>> >
>> >
>> > On Thu, Mar 19, 2020, 11:57 AM Adam Harwell <flux.adam at gmail.com>
>> wrote:
>> >>
>> >> I'm officially proposing dropping support for the queens stable branch
>> of Octavia.
>> >> Given a quorum of cores, we will move forward with marking it EOL and
>> all that entails.
>> >
>> >
>> > Adam,
>> >
>> > Why can't it go into EM Instead of EOL?
>> >
>> > Thanks
>> > Erik
>> >
>> >>
>> >> Thanks,
>> >>    --Adam
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20200410/8ebaf961/attachment-0001.html>