Bullhorn #24

Ansible Bullhorn banner

The Bullhorn

A Newsletter for the Ansible Developer Community Issue #24, 2021-04-15 (Past Issues)

Welcome to the Bullhorn, our newsletter for the Ansible developer community. If you have any questions or content you’d like to share, please reach out to us at the-bullhorn@redhat.com, or comment on this GitHub issue.

KEY DATES

ANSIBLE-BASE 2.10.8, ANSIBLE 2.9.20 AND 2.8.20 RELEASED

The Ansible Core team announced the maintenance releases of Ansible-Base 2.10.8, Ansible 2.9.20, and Ansible 2.8.20 on April 13th.

  • Ansible 2.9.20 is the last in the 2.9 series to receive bug fixes. All future releases will be for security fixes only.
  • Ansible 2.8 will go EOL (End Of Life) with the release of Ansible 2.8.20 (final release in the 2.8 series).
  • The ansible-base package consists of only the Ansible execution engine, related tools (e.g. ansible-galaxy, ansible-test), and a very small set of built-in plugins, and is also bundled with the larger Ansible distribution.

Follow this link for Rick Elrod’s email to the ansible-devel mailing list, to obtain details on what’s new, installation instructions, and schedule for future releases.

ANSIBLE 4.0.0 ALPHA4 RELEASED

The Ansible Community team announced the fourth alpha release of Ansible 4.0.0 on April 15th. This update is based on the ansible-core-2.11.x package which is a major update from the Ansible 3.x package (which is based on ansible-base-2.10.x). There may be backwards incompatibilities in the core playbook language. Please see the porting guide for details.

The last day for new collections to have been reviewed and approved for Ansible 4.0.0 is April 26th. We have limited volunteers to review the collections so please do not wait until the last minute to respond to any feedback on your submissions!

This is an alpha release. Therefore, there may be more backwards incompatible changes and new features added before Ansible 4.0.0 final is released. For what is included in this release, and how to get it for testing, please see Toshio Kuratomi’s email to the ansible-devel list.

Ansible 4.0.0 beta1 is scheduled for April 27th.

MAINTENANCE LIFECYCLE FOR THE ANSIBLE COMMUNITY PACKAGE

The ansible package published to PyPI aggregates a selected list of over 85 Ansible collections and pulls in ansible-core (previously ansible-base) as a dependency.

At the two previous #ansible-community meetings, we have discussed how we might maintain past major releases of the package (such as 3.x once 4.x has shipped) and we have settled on revisiting this later for the time being.

There are benefits to a longer maintenance cycle and while we are open to the idea, it is a non-negligible amount of work without even considering the implications of patching collections that do not backport bug and security fixes.

Maintaining a single major version of the ansible package for six months while providing the ability to install and update collections out-of-band leveraging ansible-core and ansible-galaxy is likely a good middle ground until the need for a longer maintenance cycle is voiced by the wider community.

Please refer to this GitHub issue if you would like to read more about this or would like to help and get involved.

NEW/UPDATED COMMUNITY COLLECTIONS

  • Ansible Community VMware Collection - community.vmware 1.9 has been released with security fixes. Please upgrade to the latest version.
  • Ansible Collection for ServiceNow ITSM - servicenow.itsm 1.0.0 is a new collection to automate ServiceNow IT Service Management ITSM. You can install the new collection with ansible-galaxy collection install servicenow.itsm. Please feel free to use and provide feedback.
  • Docker Community Collection - community.docker 1.5.0 has been released
  • Ansible Community Crypto Collection - community.crypto 1.6.1 has been released
  • Community General Collection - community.general 2.5.1 has been released
  • MySQL collection for Ansible - community.mysql 2.0.0 has been released
  • Community Network Collection - community.network 2.1.1 has been released

CHANGES IMPACTING COLLECTION OWNERS

The ansible-core repository now includes the stable-2.11 branch, and the version of the devel branch has been bumped to 2.12.0.dev0 (announcement). For collection maintainers, this means that if you have an tests/sanity/ignore-2.11.txt file in your collection, it needs to be copied to tests/sanity/ignore-2.12.txt to avoid CI crashes. See this pull request as an example.

In addition, if the collection is included in Ansible, please make sure that CI also tests against the new stable-2.11 branch. Ansible 4.0.0 will be based on ansible-core 2.11 and thus, according to the inclusion criteria, your collection must work with stable-2.11.

See the examples of related pull requests for GitHub Actions and Azure Pipelines.

We still recommend testing against the devel branch as well to be informed early about breaking changes (see the GitHub action workflow example).

UPDATE: ANSIBLE COMMUNITY IRC MEETING

Previously, all the agenda topics that needed to be discussed in the weekly Ansible Community IRC meetings were added to this GitHub issue. To track and categorize each topic separately, we've created a new "community-topics" GitHub repository. If you want to discuss an idea, suggest improvements, or submit new policy/proposals and New Collection Inclusion Requests, please create a new issue in the repo as a topic, and it’ll be discussed publicly in the weekly IRC meeting. After every meeting, the meeting minutes/summaries and meeting logs will be posted to the original issue.

MINI DOCUMENTATION PR DAY

The Ansible Documentation Working Group (aka DaWGs) will host a mini docs PR day on Tuesday, April 20th at 10am ET/14:00 UTC, lasting four hours. We will review and merge docs PRs for ansible/ansible and any collection-based docs PRs that attendees bring! So come on over to #ansible-docs on Freenode IRC.

THE ANSIBLE TEAM IS HIRING

Red Hat is hiring several roles to work on Ansible. Please check the job descriptions in the links and apply!

CONTENT FROM THE ANSIBLE COMMUNITY

Daniel published a blog post giving an overview of Ansible including tools and development in the broader ecosystem.

ara 1.5.6 has been released and features a refresh of the playbook reporting interface included with the API server. David has written a blog post about it to provide some highlights.

ANSIBLE CONTRIBUTOR SUMMIT 2021.06

The next Ansible Contributor Summit will be held on June 8, 2021. Registration info will be shared shortly, and in the meantime, please propose topics you’d like to discuss in this HackMD note.

ANSIBLE VIRTUAL MEETUPS

The following virtual meetup(s) are being held in the Ansible community over the next month:

FEEDBACK

Have any questions you’d like to ask, or issues you’d like to see covered? Please send us an email at the-bullhorn@redhat.com.