Bullhorn #22
The Bullhorn
A Newsletter for the Ansible Developer Community Issue #22, 2021-03-18 (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
- 2021-03-24: Collection Inclusion review day, 13:00 UTC
- 2021-03-24: community IRC meeting, 19:00 UTC
- 2021-03-30: ETA for Ansible 3.2.0 release
- 2021-03-30: Bullhorn #23 content deadline
- 2021-03-31: community IRC meeting, 19:00 UTC
- 2021-04-01: D&I working group meeting, 19:00 UTC
- 2021-04-13: Last day for new collections to be submitted for inclusion in Ansible 4. Note that collections MUST be reviewed and approved before being included.
- 2021-04-26: ETA for ansible-core 2.11 release
- 2021-05-18: ETA for Ansible 4.0.0 release
ANSIBLE 3.1.0 RELEASED
The Ansible Community team announced the general availability of Ansible 3.1.0 on March 11th. This update contains bugfixes and new, backwards compatible features in the contained collections. If you would like to learn about how and why we got to version 3.0.0, we invite you to visit our blog for the background as well as a Q&A. For what's new in the release and how to install it, please see Toshio Kuratomi's email to the ansible-announce list.
ANSIBLE 4.0.0 ALPHA1 RELEASED
The Ansible Community team announced the first alpha release of Ansible 4.0.0 on March 16th. 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.
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.
UPCOMING ANSIBLE 2.8, ANSIBLE 2.9, ANSIBLE-BASE, ANSIBLE-CORE SCHEDULE
The Ansible Core team shared the plan for Ansible releases prior to 2.10, and the next few ansible-base and ansible-core releases.
On 26 April 2021, several things are slated to happen: * ansible-core 2.11.0 will see a general availability release * ansible 2.8.z will be considered End Of Life and will no longer see updates * ansible 2.9.z will drop to security-only releases
For more detailed dates of specific releases, please take a look at Rick Elrod's email to the ansible-devel mailing list.
NEW/UPDATED COMMUNITY COLLECTIONS
- Kubernetes Collection for Ansible - kubernetes.core 1.2.0 is now out. This release introduces a
helm_template
module, dependent deletions and more reliable idempotency checks in addition to logic to handle the breaking changes in the Kubernetes client version 12 library and other incremental fixes and improvements. - Ansible Community Crypto Collection - community.crypto 1.5.0 has been released (new features and bugfixes).
- Docker Community Collection - community.docker 1.4.0 has been released (new features, modules, and bugfixes).
- Community Sops Collection - community.sops 1.0.5 has been released (bugfixes).
- Ansible POSIX Collection - ansible.posix 1.2.0 has been released (minor changes and bugfixes).
- MySQL collection for Ansible - community.mysql 1.3.0 has been released (minor changes, important deprecation announcements, and bugfixes).
- Icinga Director Collection for Ansible - t_systems_mms.icinga_director 1.16.0 has been released with a new module (usergroup) and various other improvements.
INTRODUCING ANSIBLE COMMUNITY STEERING COMMITTEE
- Last week, at the Ansible Contributor Summit, we introduced the Ansible Community Steering Committee.
- From next week's Ansible Community meeting (2021-03-24), we will officially kick start the Steering Committee.
- For further information about the Steering Committee, see "Ansible Community Steering Committee".
ANSIBLE CONTRIBUTOR SUMMIT 2021.03 RECAP AND SURVEY
Ansible Contributor Summit 2021.03 was held last Tuesday (March 9, 2021). Here is a Contributor Survey that we have put together. If you missed the event or want to recap parts from it, the logs, presentations, and recordings are available in the Ansible Community wiki.
Please take a couple of minutes to fill in the survey, whether you have attended all/part/none of the event. Feedback is really important to us so we can keep on improving the Contributor Experience for our wonderful Ansible Community.
Daniel Schier from the community did a great write-up of the event. Thanks!
ANSIBLE DOCSITE SPLIT COMPLETED
With the release of Ansible 3, we had a need to track two different releases, Ansible and ansible-core. To achieve this, we now have:
- Ansible Documentation - This docsite now tracks Ansible (the package).
- Ansible Core Documentation - This docsite now tracks ansible-core (and ansible-base).
To clarify, Ansible Documentation includes everything, with the exception of core porting guides (which are included in the Ansible core porting guides) and core roadmaps.
The Ansible Core Documentation includes only core features. Scenario guides, network guides, and Ansible porting guides/roadmaps are not on ansible-core.
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! * Manager, Ansible Cloud Engineering * Technical Marketing Manager - Red Hat Ansible Automation Platform
CONNECT WITH THE ANSIBLE COMMUNITY
The Ansible community is growing and there are new ways for you to stay in touch, the Ansible Discord server is a passionate community of Ansible users ready to help you troubleshoot your Ansible projects via text, voice or screen-sharing.
Come join us on the Ansible Discord server.
ANSIBLE VIRTUAL MEETUPS
The following virtual meetup(s) are being held in the Ansible community over the next month:
- Thu, Mar 25 · 4:00 PM EDT - Ansible NOVA - From Ansible to Anchore: With Ansible founder, Saïd Ziouani
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.