[puppet][tripleo][neutron] Deprecating support for networking-ansible
Hello Currently puppet-neutron supports deploying networking-ansible[1]. However I noticed the project looks unmaintained. - No release was made since stable/victoria - Its job template has not been updated still points openstack-python3-wallaby-jobs (likely because of no release activity) - setup.cfg still indicates support for Python 2 while it does not support 3.6/7/9 Although the repo got a few patches merged 6 months ago, I've not seen any interest in maintaining the repository. Based on the above observations, I'd propose deprecating the support in Zed and removing it in the post-Zed release. TripleO also supports networking-ansible but that will be also deprecated and removed because the dependent implementation will be removed. (That's why I added the tripleo tag) If you have any concerns then please let me know. If we don't hear any concerns in a few weeks then I'll propose the deprecation. I'm adding the [neutron] tag in case anybody in the team is interested in fixing the maintenance status. IIUC networking-ansible is not part of the stadium but I'm not aware of any good alternatives... [1] https://opendev.org/x/networking-ansible Thank you, Takashi
// adding [networking-ansible] tag in case it can attract attention of the team Because we have not heard any objections for a while, I've proposed deprecation of networking-ansible support in puppet-neutron[1] and TripleO[2]. [1] https://review.opendev.org/c/openstack/puppet-neutron/+/842996 [2] https://review.opendev.org/c/openstack/tripleo-heat-templates/+/842997 If anybody has concerns about this, please let us know in the above reviews. Thank you, Takashi On Wed, May 11, 2022 at 12:10 PM Takashi Kajinami <tkajinam@redhat.com> wrote:
Hello
Currently puppet-neutron supports deploying networking-ansible[1].
However I noticed the project looks unmaintained. - No release was made since stable/victoria - Its job template has not been updated still points openstack-python3-wallaby-jobs (likely because of no release activity) - setup.cfg still indicates support for Python 2 while it does not support 3.6/7/9
Although the repo got a few patches merged 6 months ago, I've not seen any interest in maintaining the repository.
Based on the above observations, I'd propose deprecating the support in Zed and removing it in the post-Zed release. TripleO also supports networking-ansible but that will be also deprecated and removed because the dependent implementation will be removed. (That's why I added the tripleo tag)
If you have any concerns then please let me know. If we don't hear any concerns in a few weeks then I'll propose the deprecation.
I'm adding the [neutron] tag in case anybody in the team is interested in fixing the maintenance status. IIUC networking-ansible is not part of the stadium but I'm not aware of any good alternatives...
[1] https://opendev.org/x/networking-ansible
Thank you, Takashi
participants (1)
-
Takashi Kajinami