[tc][networking-l2gw] Finish the retirement for networking-l2gw and networking-l2gw-tempest-plugin
Hello Everyone, networking-l2gw and networking-l2gw-tempest-plugin projects were retired in Ocata[1] but their retirement was not completed. I have started the retirement completion as discussed in TC and neutron team. - https://review.opendev.org/#/q/topic:complete-retirement-networking-l2gw+(st...) Please let me know any injection to that. Their development can be continued under opendev as mentioned in this doc - https://governance.openstack.org/tc/reference/dropping-projects.html#continu... [1] https://review.opendev.org/#/c/392010/2 -gmann
Hi, Development of networking-l2gw continues after its retirement from TC governance. We have open pending patches and released it for Ussuri. I hope the creation of the new repository happens before the retirement patch is merged and README refers to the new repository so that existing users are not confused. Does any coordination already happen, or does TC just want to retire it? --amotoki On Thu, Jun 25, 2020 at 11:31 PM Ghanshyam Mann <gmann@ghanshyammann.com> wrote:
Hello Everyone,
networking-l2gw and networking-l2gw-tempest-plugin projects were retired in Ocata[1] but their retirement was not completed. I have started the retirement completion as discussed in TC and neutron team.
- https://review.opendev.org/#/q/topic:complete-retirement-networking-l2gw+(st...)
Please let me know any injection to that. Their development can be continued under opendev as mentioned in this doc - https://governance.openstack.org/tc/reference/dropping-projects.html#continu...
[1] https://review.opendev.org/#/c/392010/2
-gmann
On 26.06.20 07:06, Akihiro Motoki wrote:
Hi,
Development of networking-l2gw continues after its retirement from TC governance. We have open pending patches and released it for Ussuri. I hope the creation of the new repository happens before the retirement patch is merged and README refers to the new repository so that existing users are not confused.
Sure, that should happen, so make it clear what's the new location is.
Does any coordination already happen, or does TC just want to retire it? The new repository creation can AFAIK happen directly, somebody from the l2gw team should propose that.
Looking at the changes that need to be done, here's my proposal: - create networking-l2gw in new namespace, see https://docs.opendev.org/opendev/infra-manual/latest/creators.html - Stop merging any changes to openstack/networking-l2gw - change repos that use it to use the new repo in their jobs - Close openstack/networking-l2gw, including abandoning of all open reviews Andreas -- Andreas Jaeger aj@suse.com Twitter: jaegerandi SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D 90409 Nürnberg (HRB 36809, AG Nürnberg) GF: Felix Imendörffer GPG fingerprint = EF18 1673 38C4 A372 86B1 E699 5294 24A3 FF91 2ACB
Hi, I think in the last few years I was the only maintainer of networking-l2gw. The project is still used and there are bugs and fixes for it. It is not as active as core projects, but not totally dead. The new namespace would be x/networking-l2gw (and x/networking-l2gw-tempest-plugin) I suppose, am I right? Regards Lajos Katona Andreas Jaeger <aj@suse.com> ezt írta (időpont: 2020. jún. 26., P, 14:00):
On 26.06.20 07:06, Akihiro Motoki wrote:
Hi,
Development of networking-l2gw continues after its retirement from TC governance. We have open pending patches and released it for Ussuri. I hope the creation of the new repository happens before the retirement patch is merged and README refers to the new repository so that existing users are not confused.
Sure, that should happen, so make it clear what's the new location is.
Does any coordination already happen, or does TC just want to retire it? The new repository creation can AFAIK happen directly, somebody from the l2gw team should propose that.
Looking at the changes that need to be done, here's my proposal: - create networking-l2gw in new namespace, see https://docs.opendev.org/opendev/infra-manual/latest/creators.html - Stop merging any changes to openstack/networking-l2gw - change repos that use it to use the new repo in their jobs - Close openstack/networking-l2gw, including abandoning of all open reviews
Andreas -- Andreas Jaeger aj@suse.com Twitter: jaegerandi SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D 90409 Nürnberg (HRB 36809, AG Nürnberg) GF: Felix Imendörffer GPG fingerprint = EF18 1673 38C4 A372 86B1 E699 5294 24A3 FF91 2ACB
On 26.06.20 14:24, Lajos Katona wrote:
Hi, I think in the last few years I was the only maintainer of networking-l2gw. The project is still used and there are bugs and fixes for it. It is not as active as core projects, but not totally dead. The new namespace would be x/networking-l2gw (and x/networking-l2gw-tempest-plugin) I suppose, am I right?
From https://docs.opendev.org/opendev/infra-manual/latest/creators.html#decide-st... "If your project does not fit into one of the existing namespaces, you may create a new one, or use the catch-all x namespace if you cannot decide." So, your call ;) Andreas -- Andreas Jaeger aj@suse.com Twitter: jaegerandi SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D 90409 Nürnberg (HRB 36809, AG Nürnberg) GF: Felix Imendörffer GPG fingerprint = EF18 1673 38C4 A372 86B1 E699 5294 24A3 FF91 2ACB
---- On Fri, 26 Jun 2020 07:24:21 -0500 Lajos Katona <katonalala@gmail.com> wrote ----
Hi,I think in the last few years I was the only maintainer of networking-l2gw.The project is still used and there are bugs and fixes for it. It is not as active as core projects, but not totally dead.The new namespace would be x/networking-l2gw (and x/networking-l2gw-tempest-plugin) I suppose, am I right?
Right, you can continue the development under any namespace in opendev other than 'openstack/', we have documented the process in TC document also[1] Also if you get more maintainers then you can re-apply to be under OpenStack governance as per the new application criteria which is documented in this section[2]. And as Andreas mentioned, once we have the new location of repos then we can update the README file also, please ping me or any TC members which have the right to edit the retired repo. Also, we can update the OpenStack projects which have code dependencies on networking-l2gw like networking-midonet and networking-old to point to new location of repo. We might need to do these for few other retired repo also which we are clearing now - https://etherpad.opendev.org/p/tc-retirement-cleanup Thanks for your response and for taking care of forking the new repo. [1] https://governance.openstack.org/tc/reference/dropping-projects.html#continu... [2] https://governance.openstack.org/tc/reference/dropping-projects.html#re-beco... -gmann
RegardsLajos Katona Andreas Jaeger <aj@suse.com> ezt írta (időpont: 2020. jún. 26., P, 14:00): On 26.06.20 07:06, Akihiro Motoki wrote:
Hi,
Development of networking-l2gw continues after its retirement from TC governance. We have open pending patches and released it for Ussuri. I hope the creation of the new repository happens before the retirement patch is merged and README refers to the new repository so that existing users are not confused.
Sure, that should happen, so make it clear what's the new location is.
Does any coordination already happen, or does TC just want to retire it? The new repository creation can AFAIK happen directly, somebody from the l2gw team should propose that.
Looking at the changes that need to be done, here's my proposal: - create networking-l2gw in new namespace, see https://docs.opendev.org/opendev/infra-manual/latest/creators.html - Stop merging any changes to openstack/networking-l2gw - change repos that use it to use the new repo in their jobs - Close openstack/networking-l2gw, including abandoning of all open reviews
Andreas -- Andreas Jaeger aj@suse.com Twitter: jaegerandi SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D 90409 Nürnberg (HRB 36809, AG Nürnberg) GF: Felix Imendörffer GPG fingerprint = EF18 1673 38C4 A372 86B1 E699 5294 24A3 FF91 2ACB
On 26.06.20 13:57, Andreas Jaeger wrote:
On 26.06.20 07:06, Akihiro Motoki wrote:
Hi,
Development of networking-l2gw continues after its retirement from TC governance. We have open pending patches and released it for Ussuri. I hope the creation of the new repository happens before the retirement patch is merged and README refers to the new repository so that existing users are not confused.
Sure, that should happen, so make it clear what's the new location is.
Does any coordination already happen, or does TC just want to retire it? The new repository creation can AFAIK happen directly, somebody from the l2gw team should propose that.
Looking at the changes that need to be done, here's my proposal: - create networking-l2gw in new namespace, see https://docs.opendev.org/opendev/infra-manual/latest/creators.html - Stop merging any changes to openstack/networking-l2gw - change repos that use it to use the new repo in their jobs - Close openstack/networking-l2gw, including abandoning of all open reviews
The order might not work since we do not allow import of repos with local zuul config files. So, let's retire, import from the retired state and revert the retire change as first change... Andreas -- Andreas Jaeger aj@suse.com Twitter: jaegerandi SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D 90409 Nürnberg (HRB 36809, AG Nürnberg) GF: Felix Imendörffer GPG fingerprint = EF18 1673 38C4 A372 86B1 E699 5294 24A3 FF91 2ACB
---- On Fri, 26 Jun 2020 00:05:34 -0500 Akihiro Motoki <amotoki@gmail.com> wrote ----
Hi,
Development of networking-l2gw continues after its retirement from TC governance. We have open pending patches and released it for Ussuri. I hope the creation of the new repository happens before the retirement patch is merged and README refers to the new repository so that existing users are not confused. Does any coordination already happen, or does TC just want to retire it?
Yeah, that is where the confusion was and we did not complete the retirement during namespace change time. Sorry about that and that is why we end up a situation like this. Now TC is finishing all the un-completed retirements for many projects/repo, you can find all the list in below etherpad - https://etherpad.opendev.org/p/tc-retirement-cleanup And below repos are left with code under 'openstack/' namespace which was main confusion. "dragonflow networking-l2gw networking-l2gw-tempest-plugin networking-onos openstack-ux python-dracclient solum-infra-guestagent transparency-policy " We are doing proper retirement for all those repos now. Also if there is active team for any of these repo and they create the new repo location under x/ or any other namespace in opendev then TC can update the README.rst to point to new location. I agree this is not the best way but we do not have any other option than taking this step. -gmann
--amotoki
On Thu, Jun 25, 2020 at 11:31 PM Ghanshyam Mann <gmann@ghanshyammann.com> wrote:
Hello Everyone,
networking-l2gw and networking-l2gw-tempest-plugin projects were retired in Ocata[1] but their retirement was not completed. I have started the retirement completion as discussed in TC and neutron team.
- https://review.opendev.org/#/q/topic:complete-retirement-networking-l2gw+(st...)
Please let me know any injection to that. Their development can be continued under opendev as mentioned in this doc - https://governance.openstack.org/tc/reference/dropping-projects.html#continu...
[1] https://review.opendev.org/#/c/392010/2
-gmann
On 26.06.20 16:21, Ghanshyam Mann wrote:
---- On Fri, 26 Jun 2020 00:05:34 -0500 Akihiro Motoki <amotoki@gmail.com> wrote ----
Hi,
Development of networking-l2gw continues after its retirement from TC governance. We have open pending patches and released it for Ussuri. I hope the creation of the new repository happens before the retirement patch is merged and README refers to the new repository so that existing users are not confused. Does any coordination already happen, or does TC just want to retire it?
Yeah, that is where the confusion was and we did not complete the retirement during namespace change time. Sorry about that and that is why we end up a situation like this.
Now TC is finishing all the un-completed retirements for many projects/repo, you can find all the list in below etherpad - https://etherpad.opendev.org/p/tc-retirement-cleanup
And below repos are left with code under 'openstack/' namespace which was main confusion. "dragonflow networking-l2gw networking-l2gw-tempest-plugin networking-onos openstack-ux python-dracclient solum-infra-guestagent transparency-policy "
transparency-policy is fine, it's mentioned in governance/reference/foundation-board-repos.yaml, so does not need retirement. Andreas
We are doing proper retirement for all those repos now.
Also if there is active team for any of these repo and they create the new repo location under x/ or any other namespace in opendev then TC can update the README.rst to point to new location.
I agree this is not the best way but we do not have any other option than taking this step.
-- Andreas Jaeger aj@suse.com Twitter: jaegerandi SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D 90409 Nürnberg (HRB 36809, AG Nürnberg) GF: Felix Imendörffer GPG fingerprint = EF18 1673 38C4 A372 86B1 E699 5294 24A3 FF91 2ACB
On 2020-06-26 16:52:10 +0200 (+0200), Andreas Jaeger wrote: [...]
transparency-policy is fine, it's mentioned in governance/reference/foundation-board-repos.yaml, so does not need retirement. [...]
However, we should probably consider moving it to the "osf/" namespace like we did with the Interop WG repos, and then we can drop that foundation-board-repos.yaml file once the OpenStack project and OpenStack Foundation no longer need to share the namespace. -- Jeremy Stanley
participants (5)
-
Akihiro Motoki
-
Andreas Jaeger
-
Ghanshyam Mann
-
Jeremy Stanley
-
Lajos Katona