The ansible project has re-organized how they release and distribute ansible. This change moves Fedora in sync with those changes and retires the old 'ansible classic/2.9.x' package in favor of a 'ansible' metapackage that pulls in ansible-core (the engine) and all the collections included in upstream ansible releases.
- Email: email@example.com, firstname.lastname@example.org
- Targeted release: Fedora Linux 36
- Last updated: 2021-09-24
- FESCo issue: <will be assigned by the Wrangler>
- Tracker bug: <will be assigned by the Wrangler>
- Release notes tracker: <will be assigned by the Wrangler>
The upstream ansible project found that maintaining a single monolithic ansible package with everything included was not working well. Small changes had to wait for releases, some areas had no subject matter reviewers, it was difficult to try and handle all the issues and changes in a timely manner. So, the ansible engine was split off and then the rest of the content was moved to separate collections. These collections could then be maintained by communities that care about that area and could release at their own pace. A number of collections have agreed to release on the same cadence. These collections, along with the ansible-core engine comprise a upstream 'ansible' release.
The engine package (ansible-core) is already in Fedora 35+. Currently the 'ansible' package is 'ansible classic', ie, the 2.9.x version from before the reorginization. This version will end of life soon. A number of collections are already packaged as 'ansible-collection-X' in Fedora.
This change will modify the existing 'ansible' package to package the collections that are in upstream ansible releases as well as create a ansible meta package. This meta package will install ansible-core (the engine) and install the ansible-collections. Users can, if desired, remove the collections and install separately packaged ones or install via ansible-galaxy.
Benefit to Fedora
- On current upstream releases with bugfixes and enhancements
- Will allow users to choose to uninstall the release collections and install standalone collections or via galaxy
- More rapid improvements for Fedora users.
- Proposal owners:
'ansible' package needs to be modified for this change (work is in progress already).
- Other developers: N/A
- Release engineering: N/A
- Policies and guidelines:
Possibly policies for packaging collections?
- Trademark approval: N/A (not needed for this Change
- Alignment with Objectives: First!
On upgrade, ansible-2.9.x will be replaced by ansible-core + release collections. Ansible playbooks will continue to run as before.
How To Test
Run playbook with ansible 2.9, upgrade and re-run with ansible-core-2.11.x
Users can remove the release collections and install separately packaged collections or install from ansible-galaxy.
Might need to conflict with some seperately packaged collections.
- Contingency mechanism: Keep shipping ansible classic, but it will go EOL and updates will become much harder.
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change)
N/A (not a System Wide Change)
Ansible is now shipped as 'ansible-core' (the engine) and a set of ansible-collections. Users can use 'dnf install ansible' to install ansible-core and all the release collections from upstream ansible releases. User can also 'dnf remove ansible-collections-ansible' and install collections from standalone packages or via ansible-galaxy.