Removing unsupported, inactive or otherwise unmaintained collections from the community package

[dmsimard]

Summary

As part of the Ansible 6.0.0 roadmap, I would like to consider removing unsupported, inactive or otherwise unmaintained collections from the community package.

The following are known to be superseded by supported or otherwise maintained variants:

• community.azure -> azure.azcollection
• community.google -> google.cloud (note: google.cloud's last release, 1.0.2, was 2019-09-11)
• servicenow.servicenow -> servicenow.itsm
• community.kubernetes -> kubernetes.core

In addition to the above, the following collections have not had a new release tagged since ansible 4.0.0:

• cisco.nso (1.0.3, 2020-10-26)
• community.fortios (1.0.0, 2021-01-14)
• community.kubevirt (1.0.0, 2020-11-25)
  • Note: depends on community.kubernetes which should be removed in favor of kubernetes.core
• community.skydive (1.0.0, 2020-08-18)
• cyberark.conjur (1.1.0, 2020-05-11)
• dellemc.os10 (1.1.1, 2020-07-21) (1.2.0 release pending?)
• dellemc.os6 (1.0.7, 2020-08-03)
• dellemc.os9 (1.0.4, 2020-08-03)
• frr.frr (1.0.4-dev1, 2020-02-27)
• ibm.qradar (1.0.3, 2019-09-05)
• mellanox.onyx (1.0.0, 2020-06-30)
• ngine_io.exoscale (1.0.0, 2020-06-16)
• ngine_io.vultr (1.1.0, 2020-04-12)
• splunk.es (1.0.2, 2020-06-16)

The removed collections could still be installed manually from galaxy if need be and they would be welcome back into the package if there is traction and interest via the normal inclusion process.

[Andersson007]

#34

[gundalow]

Whatever we end up doing, we should over-communicate well in advance any removals

• Reddit
• Twitter
• Bullhorn
• Can we add something to the Collection docs on docs.ansible.com

[jillr]

kubernetes.core 1.0.0 is the exact same code as community.kubernetes 1.0.0. It should be a seamless replacement for community.kubevirt.

[felixfontein]

After the discussion at today's meeting, I've created a WIP PR with two processes we can adjust and tweak and hopefully vote on soon: ansible-collections/overview#201

These have been modelled on community.kubevirt and community.google, and might also apply to some more collections listed here. The aim wasn't to cover everything, but to have a first start we can finalize before adding more cases :)

[felixfontein]

Also referencing an earlier discussion on community.kubernetes: #22 (I completely forgot about that one...)

[felixfontein]

community.kubevirt is currently broken because it depends on community.kubernetes < 2.0.0 while we include community.kubernetes >= 2.0.0. Folks have been working on getting it to work with >= 2.0.0 (resp. kubernetes.core >= 2.0.0 directly), but that effort stagnated half a year ago.

[felixfontein]

I just found another case we should think of: collections which screw something up, and fail to fix it: cisco.ucs has been including tarballs of previous releases in their release tarball. We reported that back to them almost a year ago (CiscoDevNet/ansible-ucs#25), and I just noticed that they still do that. In fact their release tarball is growing exponentially from release to release since every new tarball includes all previous tarballs directly, and all tarballs since 1.5.0 also contain the tarballs before them recursively.

I tried to ping them again. But if they don't fix this, we should really remove them. Let's discuss this next week or so.

(Edit: it's now fixed.)

[felixfontein]

I started votes for community.kubevirt and community.kubernetes in #92 resp. #93.

[Andersson007]

fyi Dell folks were notified about pending release 1.2.0 of dellemc.os10 a couple of months ago.
there were some movement in the email thread but no action has been done.
I've reminded them a couple of times but it hasn't helped.
So imo dellemc.os10 should be returned to the removal candidates (i've just removed strikeout markdown from the list item in the description)

[felixfontein]

community.kubevirt (ansible-community/ansible-build-data#115) and community.kubernetes (ansible-community/ansible-build-data#116) are gone.

[felixfontein]

community.azure 2.0.0 has been released as an empty shell. It will be included in Ansible 7, and I guess we can completely remove it from Ansible 8 or 9.

[gotmax23]

The policy change was approved. The process of identifying collections that should be removed continues in #128.