Open Stack

Hi,

Now that neutron's stable/ocata is deleted some non-stadium project's 
stable periodic job also started to fail (on stable/ocata) [1]:

- networking-bagpipe
- networking-bgpvpn
- networking-midonet
- neutron-vpnaas

There are two options to fix this:

1. transition these projects also to ocata-eol
2. fix them by using neutron's ocata-eol tag

(I guess the 1st option is the easiest, considering that these projects 
are not among the most active ones)

Does neutron team have a plan how to continue with these?

Thanks,

Előd

[1] 
http://logstash.openstack.org/#/dashboard/file/logstash.json?query=message:%5C%22error:%20pathspec%20'stable%2Focata'%20did%20not%20match%20any%20file(s)%20known%20to%20git.%5C%22&from=86400s


On 2021. 05. 14. 22:18, Előd Illés wrote:

> Hi,
>
> The patch was merged, so the ocata-eol tags were created for neutron 
> projects. After the successful tagging I have executed the branch 
> deletion, which has the following result:
>
> Branch stable/ocata successfully deleted from openstack/networking-ovn!
> Branch stable/ocata successfully deleted from 
> openstack/neutron-dynamic-routing!
> Branch stable/ocata successfully deleted from openstack/neutron-fwaas!
> Branch stable/ocata successfully deleted from openstack/neutron-lbaas!
> Branch stable/ocata successfully deleted from openstack/neutron-lib!
> Branch stable/ocata successfully deleted from openstack/neutron!
>
> Thanks,
>
> Előd
>
>
> On 2021. 05. 12. 9:22, Slawek Kaplonski wrote:
>>
>> Hi,
>>
>>
>> Dnia środa, 5 maja 2021 20:35:48 CEST Előd Illés pisze:
>>
>> > Hi,
>>
>> >
>>
>> > Ocata is unfortunately unmaintained for a long time as some general 
>> test
>>
>> > jobs are broken there, so as a stable-maint-core member I support 
>> to tag
>>
>> > neutron's stable/ocata as End of Life. After the branch is tagged,
>>
>> > please ping me and I can arrange the deletion of the branch.
>>
>> >
>>
>> > For Pike, I volunteered at the PTG in 2020 to help with reviews 
>> there, I
>>
>> > still keep that offer, however I am clearly not enough to keep it
>>
>> > maintained, besides backports are not arriving for stable/pike in
>>
>> > neutron. Anyway, if the gate is functional there, then I say we could
>>
>> > keep it open (but as far as I see how gate situation is worsen now, as
>>
>> > more and more things go wrong, I don't expect that will take long). If
>>
>> > not, then I only ask that let's do the EOL'ing first with Ocata and 
>> when
>>
>> > it is done, then continue with neutron's stable/pike.
>>
>> >
>>
>> > For the process please follow the steps here:
>>
>> > 
>> https://docs.openstack.org/project-team-guide/stable-branches.html#end-of-life
>>
>> > (with the only exception, that in the last step, instead of infra team,
>>
>> > please turn to me/release team - patch for the documentation change is
>>
>> > on the way:
>>
>> > https://review.opendev.org/c/openstack/project-team-guide/+/789932 )
>>
>>
>> Thx. I just proposed patch 
>> https://review.opendev.org/c/openstack/releases/+/790904 
>> <https://review.opendev.org/c/openstack/releases/+/790904> to make 
>> ocata-eol in all neutron projects.
>>
>>
>> >
>>
>> > Thanks,
>>
>> >
>>
>> > Előd
>>
>> >
>>
>> > On 2021. 05. 05. 16:13, Slawek Kaplonski wrote:
>>
>> > > Hi,
>>
>> > >
>>
>> > >
>>
>> > > I checked today that stable/ocata and stable/pike branches in both
>>
>> > > Neutron and neutron stadium projects are pretty inactive since 
>> long time.
>>
>> > >
>>
>> > > * according to [1], last patch merged patch in Neutron for 
>> stable/pike
>>
>> > > was in July 2020 and in ocata October 2019,
>>
>> > >
>>
>> > > * for stadium projects, according to [2] it was September 2020.
>>
>> > >
>>
>> > >
>>
>> > > According to [3] and [4] there are no opened patches for any of those
>>
>> > > branches for Neutron and any stadium project except neutron-lbaas.
>>
>> > >
>>
>> > >
>>
>> > > So based on that info I want to propose that we will close both those
>>
>> > > branches are EOL now and before doing that, I would like to know if
>>
>> > > anyone would like to keep those branches to be open still.
>>
>> > >
>>
>> > >
>>
>> > > [1]
>>
>> > > 
>> https://review.opendev.org/q/project:%255Eopenstack/neutron+(branch:stable/ocata+OR+branch:stable/pike)+status:merged
>>
>> > > 
>> <https://review.opendev.org/q/project:%255Eopenstack/neutron+(branch:stable/ocata+OR+branch:stable/pike)+status:merged>
>>
>> > >
>>
>> > > [2]
>>
>> > > 
>> https://review.opendev.org/q/(project:openstack/ovsdbapp+OR+project:openstack/os-ken+OR+project:%255Eopenstack/neutron-.*+OR+project:%255Eopenstack/networki
>>
>> > > ng-.*)+(branch:stable/ocata+OR+branch:stable/pike)+status:merged
>>
>> > > 
>> <https://review.opendev.org/q/(project:openstack/ovsdbapp+OR+project:openstack/os-ken+OR+project:%255Eopenstack/neutron-.*+OR+project:%255Eopenstack/networ
>>
>> > > king-.*)+(branch:stable/ocata+OR+branch:stable/pike)+status:merged>
>>
>> > >
>>
>> > > [3]
>>
>> > > 
>> https://review.opendev.org/q/project:%255Eopenstack/neutron+(branch:stable/ocata+OR+branch:stable/pike)+status:open
>>
>> > > 
>> <https://review.opendev.org/q/project:%255Eopenstack/neutron+(branch:stable/ocata+OR+branch:stable/pike)+status:open>
>>
>> > >
>>
>> > > [4]
>>
>> > > 
>> https://review.opendev.org/q/(project:openstack/ovsdbapp+OR+project:openstack/os-ken+OR+project:%255Eopenstack/neutron-.*+OR+project:%255Eopenstack/networki
>>
>> > > ng-.*)+(branch:stable/ocata+OR+branch:stable/pike)+status:open
>>
>> > > 
>> <https://review.opendev.org/q/(project:openstack/ovsdbapp+OR+project:openstack/os-ken+OR+project:%255Eopenstack/neutron-.*+OR+project:%255Eopenstack/networ
>>
>> > > king-.*)+(branch:stable/ocata+OR+branch:stable/pike)+status:open>
>>
>> > >
>>
>> > >
>>
>> > > --
>>
>> > >
>>
>> > > Slawek Kaplonski
>>
>> > >
>>
>> > > Principal Software Engineer
>>
>> > >
>>
>> > > Red Hat
>>
>>
>>
>> -- 
>>
>> Slawek Kaplonski
>>
>> Principal Software Engineer
>>
>> Red Hat
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20210520/4c998145/attachment-0001.html>