So, I'm wondering if we should have some kind of (at least semi-)coordinated plan for updating ansible collections in EPEL?
My initial thought is we would sort of piggy back on to what the "ansible" community collection bundles on top of the ansible-core package provided by RedHat. So, currently in EL8.7 we have:
ansible-core-2.13.3
and EPEL ships:
ansible-6.3.0 - which corresponds to the ansible community package that ships with ansible-2.13.3.
Then we would endeavor to ship the individual package collection versions that are contained in that package, .e.g: (taken from the MANIFEST.json files):
ansible.posix 1.4.0 ansible.utils 2.6.1 chocolatey.chocolatey 1.3.0 community.docker 2.7.1 community.general 5.5.0 community.libvirt 1.2.0 community.mysql 3.4.0 community.rabbitmq 1.2.2 containers.podman 1.9.4 netbox.netbox 3.7.1
For reference, currently in epel we have:
ansible-collection-ansible-posix.noarch 1.4.0-1.el8 epel
ansible-collection-ansible-utils.noarch 2.6.1-1.el8 epel
ansible-collection-chocolatey-chocolatey.noarch 1.4.0-1.el8 epel
ansible-collection-community-docker.noarch 2.6.0-1.el8 epel
ansible-collection-community-general.noarch 3.8.9-1.el8 epel
ansible-collection-community-libvirt.noarch 1.1.0-3.el8 epel
ansible-collection-community-mysql.noarch 3.5.1-1.el8 epel
ansible-collection-community-rabbitmq.noarch 1.2.3-1.el8 epel
ansible-collection-containers-podman.noarch 1.10.1-1.el8 epel
ansible-collection-netbox-netbox.noarch 3.7.1-1.el8 epel
However, it's hard for me to resist the allure of the shiny and new, so I've updated chocolatey. Similarly some others have been updated to later versions.
The other interesting case here is community.general - ansible has it at 5.5.0, but it looks like Maxwell G has taken the generally preferred course for EPEL of sticking with the stable release track of 3.X. Although I suspect very few collections maintain multiple release tracks (no idea).
I don't really have a particular agenda here, just trying to solicit people's thoughts. Personally I like minimal installs so I have been only using ansible-core + collections on the systems I maintain and would like to continue to see them be usable together.
On Mon, 30 Jan 2023 21:13:11 -0700 Orion Poplawski orion@nwra.com wrote:
So, I'm wondering if we should have some kind of (at least semi-)coordinated plan for updating ansible collections in EPEL?
My initial thought is we would sort of piggy back on to what the "ansible" community collection bundles on top of the ansible-core package provided by RedHat. So, currently in EL8.7 we have:
ansible-core-2.13.3
and EPEL ships:
ansible-6.3.0 - which corresponds to the ansible community package that ships with ansible-2.13.3.
Then we would endeavor to ship the individual package collection versions that are contained in that package, .e.g: (taken from the MANIFEST.json files):
ansible.posix 1.4.0 ansible.utils 2.6.1 chocolatey.chocolatey 1.3.0 community.docker 2.7.1 community.general 5.5.0 community.libvirt 1.2.0 community.mysql 3.4.0 community.rabbitmq 1.2.2 containers.podman 1.9.4 netbox.netbox 3.7.1
Sounds like a reasonable plan to me.
For reference, currently in epel we have:
...
ansible-collection-community-libvirt.noarch 1.1.0-3.el8 epel
I updated ansible-collection-community-libvirt to 1.2.0: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-98b1fc46a5
I don't really have a particular agenda here, just trying to solicit people's thoughts. Personally I like minimal installs so I have been only using ansible-core + collections on the systems I maintain and would like to continue to see them be usable together.
I too just use ansible-core + collections on the systems I maintain.
Regards, Paul.
epel-devel@lists.fedoraproject.org