Unmaintained collection: Removal from the Ansible Community Package

[mariolenz]

It looks like this collection is effectively unmaintained. According to the current Ansible Community Package Collections Removal Process, we will consider removing it in a future version of the Ansible Community Package. Please see Unmaintained collection: ovirt.ovirt for more information.

At least one month after this announcement appears here and on Bullhorn, the Ansible Community Steering Committee will vote on whether this collection is considered unmaintained and will be removed, or whether it will be kept. If it will be removed, this will happen earliest in Ansible 13. Please note that people can still manually install the collection with ansible-galaxy collection install ovirt.ovirt even when it has been removed from the Ansible Community Package.

[mariolenz]

@mnecas you've done the last releases and @shubhaOracle you've done the last commit as far as I can see. So maybe you might be interested in this.

[dupondje]

Hi @mariolenz

Thanks for the notifications here.
You are correct that the ansible collection (and big parts of the rest of oVirt) is a bit unmaintained.

But, we will contribute more and more to oVirt, and will also keep this ansible collection maintained.
I think we just need a bit more time to get everything up and running, pipelines on our end etc.

So yes it's a bit unmaintained atm, but it will change. Just need some weeks/months to get our workforce in place!
I would therefor like to keep oVirt in the Ansible collection.

Is there anything urgent that needs to be picked up to avoid the removal? Then I can have a look to resolve those bits at least.

[mariolenz]

@dupondje I don't see anything urgent ATM. Anyway, the fact that you've answered this so fast is a sign that we shouldn't remove the package in the near future. I guess I'll keep this on my list of possibly unmaintained collections, but will not proceed with the removal process for now.

I'll have another look at the collection in some weeks/months, though ;-)

[mariolenz]

@dupondje

You are correct that the ansible collection (and big parts of the rest of oVirt) is a bit unmaintained.

But, we will contribute more and more to oVirt, and will also keep this ansible collection maintained. I think we just need a bit more time to get everything up and running, pipelines on our end etc.

Any news? I don't see that there is any work done on this collection. There hasn't been any commit since you've said that you will "contribute more and more to oVirt, and will also keep this ansible collection maintained".

Anyway, removing the collection from the Ansible Community Package doesn't mean that the collection will be removed from the ansible universe at all. People can still manually install the collection with ansible-galaxy collection install ovirt.ovirt, and you can also push new versions of the collection to galaxy. The collection simply wouldn't come automatically anymore when people install ansible / ACP.

If you're really committed to work on this collection, I wonder why I don't see any activity here...

[dupondje]

@mariolenz : You are right, no much action yet here indeed.
But the goal is still to commit to this and have it up-to-date again.
Currently we are mainly focusing on the ovirt-engine part (https://github.com/oVirt/ovirt-engine).

I started on this (see for example #757).
But the pain here is that the project was quite dead for almost 2 years, so more things are broken in the background. Which takes all time to fix, but doesn't show a direct change.

Next to that, I also think most of our users install Ansible via their OS packages.
That means they lose ovirt collection except if we either package it via a separate package or they fetch it from the collection.