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 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