[puppet] Retiring untested and unmaintained modules (murano, rally and tacker)
Hello,
In Puppet OpenStack projects we have multiple modules to support multiple OpenStack components. However unfortunately some of these have not been attracting enough interest from developers and have been unmaintained.
During the past few cycles we retired a few incomplete modules but I'm wondering if we can retire a few unmaintained modules now, to reduce our maintenance/release effort.
I checked the modules we have currently, and I think the following three can be first candidates. - puppet-murano - puppet-rally - puppet-tacker
We haven't seen any feedback from users about these modules for a long time. Most of the changes for the past 2~3 years are proposed by me but I am not really using these components.
These modules do not have proper test coverage and it's quite difficult for us to catch any breakage and honestly I'm not quite sure these modules can work properly with the latest code. Actually we've often caught up with the latest requirements several years after the change was made in the software side, and I'm afraid these are not well-maintained.
eg. - support for tacker-conductor was added 4 years after the service was added - we didn't noticed that the openstack plugin was split out from the core rally package for several years
If anybody has concerns with retiring these modules, then please let us know. If we don't hear any objections for a while, then I'll start proposing changes for project retirement.
Thank you, Takashi
+1 to retiring unmaintained modules mentioned to relief maintenance burden.
Thanks Takashi!
Best regards Tobias
On 25 Jan 2023, at 09:34, Takashi Kajinami tkajinam@redhat.com wrote:
Hello,
In Puppet OpenStack projects we have multiple modules to support multiple OpenStack components. However unfortunately some of these have not been attracting enough interest from developers and have been unmaintained.
During the past few cycles we retired a few incomplete modules but I'm wondering if we can retire a few unmaintained modules now, to reduce our maintenance/release effort.
I checked the modules we have currently, and I think the following three can be first candidates. - puppet-murano - puppet-rally - puppet-tacker
We haven't seen any feedback from users about these modules for a long time. Most of the changes for the past 2~3 years are proposed by me but I am not really using these components.
These modules do not have proper test coverage and it's quite difficult for us to catch any breakage and honestly I'm not quite sure these modules can work properly with the latest code. Actually we've often caught up with the latest requirements several years after the change was made in the software side, and I'm afraid these are not well-maintained.
eg. - support for tacker-conductor was added 4 years after the service was added - we didn't noticed that the openstack plugin was split out from the core rally package for several years
If anybody has concerns with retiring these modules, then please let us know. If we don't hear any objections for a while, then I'll start proposing changes for project retirement.
Thank you, Takashi -- ---------- Takashi Kajinami
Hi Takashi,
I'd like you to wait for dropping puppet-tacker for a while.
- support for tacker-conductor was added 4 years after the service was
added Unfortunately, we don't know anything about this support in current tacker team because no one didn't join the team yet. I'd like to confirm anyone in our users still want the module to be supported.
Thanks, Yasufumi
On 2023/01/25 17:34, Takashi Kajinami wrote:
Hello,
In Puppet OpenStack projects we have multiple modules to support multiple OpenStack components. However unfortunately some of these have not been attracting enough interest from developers and have been unmaintained.
During the past few cycles we retired a few incomplete modules but I'm wondering if we can retire a few unmaintained modules now, to reduce our maintenance/release effort.
I checked the modules we have currently, and I think the following three can be first candidates.
- puppet-murano
- puppet-rally
- puppet-tacker
We haven't seen any feedback from users about these modules for a long time. Most of the changes for the past 2~3 years are proposed by me but I am not really using these components.
These modules do not have proper test coverage and it's quite difficult for us to catch any breakage and honestly I'm not quite sure these modules can work properly with the latest code. Actually we've often caught up with the latest requirements several years after the change was made in the software side, and I'm afraid these are not well-maintained.
eg.
- support for tacker-conductor was added 4 years after the service was
added
- we didn't noticed that the openstack plugin was split out from the core
rally package for several years
If anybody has concerns with retiring these modules, then please let us know. If we don't hear any objections for a while, then I'll start proposing changes for project retirement.
Thank you, Takashi
Hi Yasufumi,
We'll wait for any feedback regarding puppet-tacker.
Please note, we need to add proper functional test coverage, fixing any critical feature gap and working on CI failures related to Tacker to maintain the module properly. We'd still need to discuss how we address these points and probably look for actual volunteers, in case we aim to keep the module.
Thank you, Takashi
On Mon, Jan 30, 2023 at 5:49 PM Yasufumi Ogawa yasufum.o@gmail.com wrote:
Hi Takashi,
I'd like you to wait for dropping puppet-tacker for a while.
- support for tacker-conductor was added 4 years after the service was
added Unfortunately, we don't know anything about this support in current tacker team because no one didn't join the team yet. I'd like to confirm anyone in our users still want the module to be supported.
Thanks, Yasufumi
On 2023/01/25 17:34, Takashi Kajinami wrote:
Hello,
In Puppet OpenStack projects we have multiple modules to support multiple OpenStack components. However unfortunately some of these have not been attracting enough interest from developers and have been unmaintained.
During the past few cycles we retired a few incomplete modules but I'm wondering if we can retire a few unmaintained modules now, to reduce our maintenance/release effort.
I checked the modules we have currently, and I think the following three can be first candidates.
- puppet-murano
- puppet-rally
- puppet-tacker
We haven't seen any feedback from users about these modules for a long time. Most of the changes for the past 2~3 years are proposed by me but I am not really using these components.
These modules do not have proper test coverage and it's quite difficult
for
us to catch any breakage and honestly I'm not quite sure these modules can work properly with the
latest
code. Actually we've often caught up with the latest requirements several years after the change was made in the software side, and I'm afraid these are not well-maintained.
eg.
- support for tacker-conductor was added 4 years after the service was
added
- we didn't noticed that the openstack plugin was split out from the
core
rally package for several years
If anybody has concerns with retiring these modules, then please let us know. If we don't hear any objections for a while, then I'll start proposing changes for project retirement.
Thank you, Takashi
Hi Takashi,
We're still using puppet-murano. If there's any specific issues, I'd be happy to look into them, but it's working OK for us currently.
cheers, Andy
On Wed, 25 Jan 2023 at 19:36, Takashi Kajinami tkajinam@redhat.com wrote:
Hello,
In Puppet OpenStack projects we have multiple modules to support multiple OpenStack components. However unfortunately some of these have not been attracting enough interest from developers and have been unmaintained.
During the past few cycles we retired a few incomplete modules but I'm wondering if we can retire a few unmaintained modules now, to reduce our maintenance/release effort.
I checked the modules we have currently, and I think the following three can be first candidates.
- puppet-murano
- puppet-rally
- puppet-tacker
We haven't seen any feedback from users about these modules for a long time. Most of the changes for the past 2~3 years are proposed by me but I am not really using these components.
These modules do not have proper test coverage and it's quite difficult for us to catch any breakage and honestly I'm not quite sure these modules can work properly with the latest code. Actually we've often caught up with the latest requirements several years after the change was made in the software side, and I'm afraid these are not well-maintained.
eg.
- support for tacker-conductor was added 4 years after the service was added
- we didn't noticed that the openstack plugin was split out from the core rally package for several years
If anybody has concerns with retiring these modules, then please let us know. If we don't hear any objections for a while, then I'll start proposing changes for project retirement.
Thank you, Takashi
--
Takashi Kajinami
Hi Andy,
Thank you for the response. May I know which version you are currently using ?
We can keep puppet-murano for now as there is a user(or some users, hopefully) using the module. However please note there is no functional test coverage(integration tests/acceptance tests) to test actual deployments in our CI. We probably better try enabling a few tests to test actual deployments. I'll look into it when I get time, and might ask for your help in case I face any problems.
Thank you, Takashi
On Mon, Jan 30, 2023 at 6:12 PM Andy Botting andy@andybotting.com wrote:
Hi Takashi,
We're still using puppet-murano. If there's any specific issues, I'd be happy to look into them, but it's working OK for us currently.
cheers, Andy
On Wed, 25 Jan 2023 at 19:36, Takashi Kajinami tkajinam@redhat.com wrote:
Hello,
In Puppet OpenStack projects we have multiple modules to support
multiple OpenStack components.
However unfortunately some of these have not been attracting enough
interest from developers and
have been unmaintained.
During the past few cycles we retired a few incomplete modules but I'm
wondering if we can retire
a few unmaintained modules now, to reduce our maintenance/release effort.
I checked the modules we have currently, and I think the following three
can be first candidates.
- puppet-murano
- puppet-rally
- puppet-tacker
We haven't seen any feedback from users about these modules for a long
time. Most of the changes
for the past 2~3 years are proposed by me but I am not really using
these components.
These modules do not have proper test coverage and it's quite difficult
for us to catch any breakage and
honestly I'm not quite sure these modules can work properly with the
latest code. Actually we've often
caught up with the latest requirements several years after the change
was made in the software side,
and I'm afraid these are not well-maintained.
eg.
- support for tacker-conductor was added 4 years after the service was
added
- we didn't noticed that the openstack plugin was split out from the
core rally package for several years
If anybody has concerns with retiring these modules, then please let us
know. If we don't hear any objections
for a while, then I'll start proposing changes for project retirement.
Thank you, Takashi
--
Takashi Kajinami
Hi Takashi,
We're currently using Wallaby, but looking to move to Zed soon.
Please reach out to me if I can give you a hand with this.
cheers, Andy
On Mon, 30 Jan 2023 at 20:32, Takashi Kajinami tkajinam@redhat.com wrote:
Hi Andy,
Thank you for the response. May I know which version you are currently using ?
We can keep puppet-murano for now as there is a user(or some users, hopefully) using the module. However please note there is no functional test coverage(integration tests/acceptance tests) to test actual deployments in our CI. We probably better try enabling a few tests to test actual deployments. I'll look into it when I get time, and might ask for your help in case I face any problems.
Thank you, Takashi
On Mon, Jan 30, 2023 at 6:12 PM Andy Botting andy@andybotting.com wrote:
Hi Takashi,
We're still using puppet-murano. If there's any specific issues, I'd be happy to look into them, but it's working OK for us currently.
cheers, Andy
On Wed, 25 Jan 2023 at 19:36, Takashi Kajinami tkajinam@redhat.com wrote:
Hello,
In Puppet OpenStack projects we have multiple modules to support multiple OpenStack components. However unfortunately some of these have not been attracting enough interest from developers and have been unmaintained.
During the past few cycles we retired a few incomplete modules but I'm wondering if we can retire a few unmaintained modules now, to reduce our maintenance/release effort.
I checked the modules we have currently, and I think the following three can be first candidates.
- puppet-murano
- puppet-rally
- puppet-tacker
We haven't seen any feedback from users about these modules for a long time. Most of the changes for the past 2~3 years are proposed by me but I am not really using these components.
These modules do not have proper test coverage and it's quite difficult for us to catch any breakage and honestly I'm not quite sure these modules can work properly with the latest code. Actually we've often caught up with the latest requirements several years after the change was made in the software side, and I'm afraid these are not well-maintained.
eg.
- support for tacker-conductor was added 4 years after the service was added
- we didn't noticed that the openstack plugin was split out from the core rally package for several years
If anybody has concerns with retiring these modules, then please let us know. If we don't hear any objections for a while, then I'll start proposing changes for project retirement.
Thank you, Takashi
--
Takashi Kajinami
Hello,
I've not heard any additional feedback so far, so I'd like to decide the next steps about the three modules.
1. puppet-murano We'll continue maintaining this module based on the response by Andy. I've managed to restore acceptance tests for puppet-murano[1] which would allow us to catch quite essential deployment problems. We might need to address the remaining two problems but we don't have capacity to address these two immediately so I'll leave these two as future TODO. It'd be nice if anyone interested can help us with these items. - acceptance tests in Ubuntu are still broken - no functional tests are enabled (murano is still disabled in integration tests)
[1] https://review.opendev.org/c/openstack/puppet-murano/+/872102
2. puppet-rally I've proposed a few critical bug fixes [2] during this cycle and I think we should create a release containing these fixes. So I'll retire this module after the Antelope release.
[2] example https://review.opendev.org/c/openstack/puppet-rally/+/869628
3. puppet-tacker We haven't heard any actual objection to retiring this module and we don't see any critical fixes/features merged during this cycle so I'll retire this module immediately. @Yasufumi Ogawa yasufum.o@gmail.com Do you have any update about the confirmation ?
In case anyone has additional concerns, then please let me know.
Thank you, Takashi Kajinami
On Wed, Jan 25, 2023 at 5:34 PM Takashi Kajinami tkajinam@redhat.com wrote:
Hello,
In Puppet OpenStack projects we have multiple modules to support multiple OpenStack components. However unfortunately some of these have not been attracting enough interest from developers and have been unmaintained.
During the past few cycles we retired a few incomplete modules but I'm wondering if we can retire a few unmaintained modules now, to reduce our maintenance/release effort.
I checked the modules we have currently, and I think the following three can be first candidates.
- puppet-murano
- puppet-rally
- puppet-tacker
We haven't seen any feedback from users about these modules for a long time. Most of the changes for the past 2~3 years are proposed by me but I am not really using these components.
These modules do not have proper test coverage and it's quite difficult for us to catch any breakage and honestly I'm not quite sure these modules can work properly with the latest code. Actually we've often caught up with the latest requirements several years after the change was made in the software side, and I'm afraid these are not well-maintained.
eg.
- support for tacker-conductor was added 4 years after the service was
added
- we didn't noticed that the openstack plugin was split out from the core
rally package for several years
If anybody has concerns with retiring these modules, then please let us know. If we don't hear any objections for a while, then I'll start proposing changes for project retirement.
Thank you, Takashi
--
Takashi Kajinami
Hi Takashi,
- puppet-murano
We'll continue maintaining this module based on the response by Andy. I've managed to restore acceptance tests for puppet-murano[1] which would allow us to catch quite essential deployment problems. We might need to address the remaining two problems but we don't have capacity to address these two immediately so I'll leave these two as future TODO. It'd be nice if anyone interested can help us with these items.
- acceptance tests in Ubuntu are still broken
- no functional tests are enabled (murano is still disabled in integration tests)
[1] https://review.opendev.org/c/openstack/puppet-murano/+/872102
Thanks for this. I'll try and look into sorting these out for Murano.
cheers, Andy
On Thu, Feb 16, 2023 at 10:48 PM Takashi Kajinami tkajinam@redhat.com wrote:
Hello,
I've not heard any additional feedback so far, so I'd like to decide the next steps about the three modules.
- puppet-murano
We'll continue maintaining this module based on the response by Andy. I've managed to restore acceptance tests for puppet-murano[1] which would allow us to catch quite essential deployment problems. We might need to address the remaining two problems but we don't have capacity to address these two immediately so I'll leave these two as future TODO. It'd be nice if anyone interested can help us with these items.
- acceptance tests in Ubuntu are still broken
- no functional tests are enabled (murano is still disabled in
integration tests)
[1] https://review.opendev.org/c/openstack/puppet-murano/+/872102
- puppet-rally
I've proposed a few critical bug fixes [2] during this cycle and I think we should create a release containing these fixes. So I'll retire this module after the Antelope release.
[2] example https://review.opendev.org/c/openstack/puppet-rally/+/869628
- puppet-tacker
We haven't heard any actual objection to retiring this module and we don't see any critical fixes/features merged during this cycle so I'll retire this module immediately. @Yasufumi Ogawa yasufum.o@gmail.com Do you have any update about the confirmation ?
In case anyone has additional concerns, then please let me know.
Because I've not heard any objections for almost 1 month, I've submitted the changes to retire puppet-tacker and will get these merged before the Antelope release. In case you have any concerns then please let me know in this thread or in these reviewers.
https://review.opendev.org/q/topic:retire-puppet-tacker
Thank you, Takashi Kajinami
On Wed, Jan 25, 2023 at 5:34 PM Takashi Kajinami tkajinam@redhat.com wrote:
Hello,
In Puppet OpenStack projects we have multiple modules to support multiple OpenStack components. However unfortunately some of these have not been attracting enough interest from developers and have been unmaintained.
During the past few cycles we retired a few incomplete modules but I'm wondering if we can retire a few unmaintained modules now, to reduce our maintenance/release effort.
I checked the modules we have currently, and I think the following three can be first candidates.
- puppet-murano
- puppet-rally
- puppet-tacker
We haven't seen any feedback from users about these modules for a long time. Most of the changes for the past 2~3 years are proposed by me but I am not really using these components.
These modules do not have proper test coverage and it's quite difficult for us to catch any breakage and honestly I'm not quite sure these modules can work properly with the latest code. Actually we've often caught up with the latest requirements several years after the change was made in the software side, and I'm afraid these are not well-maintained.
eg.
- support for tacker-conductor was added 4 years after the service was
added
- we didn't noticed that the openstack plugin was split out from the
core rally package for several years
If anybody has concerns with retiring these modules, then please let us know. If we don't hear any objections for a while, then I'll start proposing changes for project retirement.
Thank you, Takashi
--
Takashi Kajinami
participants (4)
-
Andy Botting
-
Takashi Kajinami
-
Tobias Urdin
-
Yasufumi Ogawa