From Fedora Project Wiki
(Fill out other sections (TODO: proofread))
(Proofread)
Line 43: Line 43:
Ansible 9, the last release that supports Python 2.7 and Python 3.6 target nodes, will go EOL upstream in November 2024, so we must update to the latest Ansible to continue receiving upstream support.
Ansible 9, the last release that supports Python 2.7 and Python 3.6 target nodes, will go EOL upstream in November 2024, so we must update to the latest Ansible to continue receiving upstream support.


Other than the Python changes, the collections included in Ansible 11 package will receive the usual updates to their latest major versions. Ansible Core 2.18 also includes miscellaneous to the core playbook runtime that are listed in the [https://docs.ansible.com/ansible/devel/roadmap/ROADMAP_2_18.html Ansible Core roadmap].
The collections included in the Ansible 11 package will also receive the usual updates to their latest respective major versions. See the upstream roadmaps in the Documentation section for more details about other more minor Ansible Core changes and the release schedules for both Ansible and Ansible Core.


== Feedback ==
== Feedback ==


== Benefit to Fedora ==
== Benefit to Fedora ==
Line 72: Line 71:


== User Experience ==
== User Experience ==
<!-- If this change proposal is noticeable by users, how will their experiences change as a result?


This section partially overlaps with the Benefit to Fedora section above. This section should be primarily about the User Experience, written in a way that does not assume deep technical knowledge. More detailed technical description should be left for the Benefit to Fedora section.
Users will have the latest version of Ansible and Ansible Core.
 
Describe what Users will see or notice, for example:
  - Packages are compressed more efficiently, making downloads and upgrades faster by 10%.
  - Kerberos tickets can be renewed automatically. Users will now have to authenticate less and become more productive. Credential management improvements mean a user can start their work day with a single sign on and not have to pause for reauthentication during their entire day.
- Libreoffice is one of the most commonly installed applications on Fedora and it is now available by default to help users "hit the ground running".
- Green has been scientifically proven to be the most relaxing color. The move to a default background color of green with green text will result in Fedora users being the most relaxed users of any operating system.
-->


== Dependencies ==
== Dependencies ==
Line 95: Line 86:
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
* Blocks release? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Blocks release? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->


== Documentation ==
== Documentation ==
Line 101: Line 91:
* [https://docs.ansible.com/ansible/devel/roadmap/ROADMAP_2_18.html Ansible Core 2.18 Roadmap]
* [https://docs.ansible.com/ansible/devel/roadmap/ROADMAP_2_18.html Ansible Core 2.18 Roadmap]
* [https://docs.ansible.com/ansible/devel/roadmap/COLLECTIONS_11.html Ansible 11 Roadmap]
* [https://docs.ansible.com/ansible/devel/roadmap/COLLECTIONS_11.html Ansible 11 Roadmap]


== Release Notes ==
== Release Notes ==
<!-- The Fedora Release Notes inform end-users about what is new in the release.  Examples of past release notes are at https://docs.fedoraproject.org/en-US/fedora/latest/release-notes/ -->
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this change, indicate them here.  A link to upstream documentation will often satisfy this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release.
Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze.
-->


Update to Ansible 11 and Ansible Core 2.18, which no longer supports Python 2.7 and Python 3.6 target nodes, including EL 7 and EL 8 hosts.
Update to Ansible 11 and Ansible Core 2.18, which no longer supports Python 2.7 and Python 3.6 target nodes, including EL 7 and EL 8 hosts.

Revision as of 02:29, 15 September 2024

Ansible 11

This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee.

Summary

Update to Ansible 11 and Ansible Core 2.18, which no longer supports Python 2.7 and Python 3.6 target nodes, including EL 7 and EL 8 hosts.

Owner

Current status

  • Targeted release: Fedora Linux 42
  • Last updated: 2024-09-15
  • [Announced]
  • [<will be assigned by the Wrangler> Discussion thread]
  • 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>

Detailed Description

The premise of the change proposal is simple — a major version update from Ansible 9 (ansible) / Ansible Core 2.16 (ansible-core) to Ansible 11 / Ansible Core 2.18. This is being filed as a Change proposal instead of a standard update due to major breaking changes.

Ansible Core 2.18's minimum supported Python version on target nodes is Python 3.8 - 3.13. This means that Ansible will no longer be able to interact with RHEL 8 hosts (Python 3.6) or RHEL 7 hosts (Python 2.7). Ansible Core upstream plans to be more aggressive with dropping support for older Python versions on target nodes in the feature.

Ansible 9, the last release that supports Python 2.7 and Python 3.6 target nodes, will go EOL upstream in November 2024, so we must update to the latest Ansible to continue receiving upstream support.

The collections included in the Ansible 11 package will also receive the usual updates to their latest respective major versions. See the upstream roadmaps in the Documentation section for more details about other more minor Ansible Core changes and the release schedules for both Ansible and Ansible Core.

Feedback

Benefit to Fedora

Fedora will have the latest version of Ansible and continue receiving upstream support.

Scope

  • Proposal owners:
    • Update the ansible and ansible-core packages
    • Ensure Ansible Collections packages in Fedora are up to date and compatible with the latest Ansible version.
  • Other developers:
    • Ensure Ansible Collections packages in Fedora that are not maintained by the Change owners are up to date and compatible with the latest Ansible version.

Upgrade/compatibility impact

Ansible Core 2.18's minimum supported Python version on target nodes is Python 3.8 - 3.13. This means that Ansible will no longer be able to interact with RHEL 8 hosts (Python 3.6) or RHEL 7 hosts (Python 2.7).


How To Test

Install the latest ansible/ansible-core packages once they arrive in the Fedora repos and ensure that your existing playbooks and installed collections and roles continue to function as they did before.


User Experience

Users will have the latest version of Ansible and Ansible Core.

Dependencies

Ansible Collection packages in Fedora should be tested against the new ansible-core release.

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? N/A (not a System Wide Change), Yes/No

Documentation

Release Notes

Update to Ansible 11 and Ansible Core 2.18, which no longer supports Python 2.7 and Python 3.6 target nodes, including EL 7 and EL 8 hosts.

Retrieved from "https://fedoraproject.org/w/index.php?title=Changes/Ansible11&oldid=720078"