Bullhorn #19
The Bullhorn
A Newsletter for the Ansible Developer Community Issue #19, 2021-02-04 (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-02-09: ETA for Ansible 3.0.0 release candidate
- 2021-02-10: community IRC meeting, 19:00 UTC
- 2021-02-15: ETA for Ansible-base 2.10.6 release
- 2021-02-16: ETA for Ansible 3.0.0 general release
- 2021-02-16: Bullhorn #20 content deadline
- 2021-02-17: community IRC meeting, 19:00 UTC
- 2021-02-18: D&I working group meeting, 19:00 UTC
ANSIBLE 2.10.6 NOW GENERALLY AVAILABLE
The Ansible Community team announced the general availability of Ansible 2.10.6 on January 26th. This update contains bug fixes and new, backwards compatible features in the contained collections. Important notes:
- This release fixes CVE-2021-20178 and CVE-2021-20180 in the
community.general.bitbucket_pipeline_variable
andcommunity.general.snmp_facts
modules. - There will be one more 2.10 release, ansible-2.10.7, on February 9, 2021. Ansible-3.0.0, is planned for February 16, 2021.
For the full release announcement including what’s new, how to get it, plus schedule for upcoming releases, read Toshio Kuratomi’s email to the ansible-devel mailing list.
ANSIBLE 3.0.0 BETA1 RELEASED
The Ansible Community team announced the first beta release of Ansible 3.0.0 on February 2nd, now available for testing. You can get it via pip: pip install --user ansible==3.0.0b1
- The Ansible package has moved to semantic versioning
Unless blockers are discovered, Ansible 3.0.0 final will be out on February 16th. For the full announcement including changelogs, please see Toshio Kuratomi’s email to the ansible-devel mailing list or David Moreau Simard's Reddit post and discussion.
NEW COLLECTION CRITERIA
A new collection criteria has been added: Collections are only allowed to use specific directories in the plugins/
directory which correspond to recognized plugin types.
NEW/UPDATED COMMUNITY COLLECTIONS
- The Community General Collection community.general 1.3.5 and 2.0.0 have been released. Changelog for 2.0.0 (with all changes since 1.0.0).
- The Community Network Collection community.network 1.3.1 and 2.0.0 have been released. Changelog for 2.0.0 (with all changes since 1.0.0).
- The Docker Community Collection community.docker 1.2.1 has been released with some improvements and fixes for
docker_container
,docker_image
and thedocker
connection plugin. - The Community Crypto Collection community.crypto 1.4.0 has been released with some improvements for the
luks_device
,openssl_csr*
andopenssl_pkcs12
modules. - The Sensu Go Ansible Collection sensu.sensu_go was updated to 1.8.0. For more information about its releases, head over to release notes.
- The Internal Test Tools Collection community.internal_test_tools 0.3.0 has been released (changelog). This collection is not for end-users, but for collection maintainers. It contains frameworks for testing
open_url
andfetch_url
based modules and plugins, modules for testing files and directories for changes (useful for integration tests), and some tools for running extra sanity tests and for helping withmeta/runtime.yml
redirects, in particular for collections using flatmapping.
MODULE COMPAT FOR PYTHON 3.8+ CONTROLLER
If you use Ansible's selinux support in any of the core file modules, or the yum/dnf/apt package managers, we'd love for you to try out module compat for py3.8+ controller. As part of the ansible-core 2.11 project to bump controller Python requirements to 3.8+, this pull request provides a couple of new module compatibility APIs, and changes to the core modules that need those APIs to continue functioning under Python 3.8+.
You can pip install the PR to a Python 3.8+ environment from source via pip install https://github.com/nitzmahone/ansible/tarball/module_respawn
, or clone the PR locally and run directly from the source in the usual way (assuming you've already got an environment set up to run Ansible from source).
Try out the package management and file module(s) with selinux that you use under localhost
with Ansible installed on Python 3.8/3.9, or by forcing ansible_python_interpreter
to any target-side supported Python version (2.6-3.9). The modules should now work transparently with no manual installation of dependencies required (including the oft-dreaded libselinux-python
!).
REQUEST FOR COMMENTS - KUBERNETES COLLECTION
The Kubernetes inventory plugin is being refactored to improve overall operation. We would like your comments on how this plugin is being used. Does the refactoring make sense? What is the impact, if any, of the changes? Are there other improvements to be made to help users? Please add your feedback to this GitHub issue.
THE ANSIBLE TEAM IS HIRING
The Ansible Product Marketing team has 3 jobs available as Technical Marketing Managers (individual contributors, managing content, not people) that will focus on Red Hat Ansible Automation Platform:
- Technical Marketing Manager
- Senior Technical Marketing Manager
- Principal Technical Marketing Manager
In addition, we're looking for a Manager of Technical Marketing to manage the technical marketing strategy and team, as well as 2 Product Marketing Managers. Please check the job descriptions in the links and apply!
CONTENT FROM THE ANSIBLE COMMUNITY
David Moreau Simard wrote a blog post on "Benchmarking Ansible and python versions for fun and science".
ANSIBLE CONTRIBUTOR SUMMIT 2021.03
The next Ansible Contributor Summit will be held on March 9, 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 meetups are being held in the Ansible community over the next month:
- Wed, Feb 17 · 5:00 PM GMT+1 - Ansible in DevOps Torun-Bydgoszcz - AiDO Meetup #13 Rekrutacja w IT + Ulga IP BOX
- Thu, Feb 18 · 6:00 PM GMT+1 - Ansible Meetup Dresden - Meetup 02.2021
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.