Bullhorn #62

Ansible Bullhorn banner

A Newsletter for the Ansible Developer Community Issue #62, 2022-06-10 (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, you're welcome to chat with us in the Ansible Social room on Matrix, and mention newsbot to have your news item tagged for review for the next weekly issue!


cybette said


andersson007_ contributed

We are happy to announce that the Collection inclusion policy has been recently relaxed by the Ansible Community Steering Committee!

Before the change, for a collection to get included in the ansible community package, it required reviews and approvals made by two Steering Committee members.

Now, one Steering Committee member and one Community (non-Steering Committee) member review and approval will be enough!

This change: * Should speed up the ansible community package enhancement by involving the broader Community. * Opens a great contribution opportunity for non-Steering Committee persons. * Allows community members (especially collection developers & maintainers) to learn a lot by checking together with the Steering Committee members if other's collections satisfy the Collection requirements.

Regular community reviewers will be offered to join the Steering Committee.

Inclusion requests to review: * ibm.spectrum_virtualize * purestorage.fusion * vultr.cloud * check_point.gaia * inspur.ispim

How? Copy the Review checklist into a discussion and go through it. See the complete example.

They are waiting for your reviews!

Thank you!

samccann contributed

Need help writing or editing your collection docs? We have community writers ready to help review docs PRs and provide basic help using the Edit on GitHub feature. These writers can provide grammar and readability advice for your collection docs or other Ansible community project docs. Ping us in the #docs matrix/irc channels to get details on how we can help, and see the project tracking board here.


Antsibull 🐂

Tooling for building the Ansible package and collection documentation.

felixfontein shared

antsibull 0.47.0 has been released with a feature that adds a CLI program ansible-community --version that allows to print the Ansible version to Ansible 6.0.0rc1 and later releases.

Ansible 📦️

The Ansible package includes ansible-core and is a batteries-included package that provides a curated set of Ansible collections. See the Ansible roadmaps for future release plans.

ompragash said

🚨 Ansible 5.9.0 which includes ansible-core 2.12.6 has been released and is available to download from pypi🎉. https://groups.google.com/g/ansible-devel/c/Xb6n9irkar0

ompragash contributed

We are excited to announce the release of Ansible 6.0.0rc1 (First Release Candidate)!🎉 🔗 https://groups.google.com/g/ansible-announce/c/cn2lofbqaGY

You can install it by running the following command or download it directly from pypi:

pip install ansible==6.0.0rc1 --user

Oh and don't miss out on the all new ansible-community command-line utility added in Ansible 6 that prints the version of the Ansible Community package:

$ ansible-community --version Ansible community version 6.0.0rc1


felixfontein shared

community.dns 2.2.0 (changelog) has been released with new features and an updated Public Suffix List.

felixfontein shared

community.general 5.1.0 (changelog) has been released with several new features and a new module.

Qalthos shared

Two more networking collection announcements: * cisco.iosxr 3.1.0 has been released with new features (changelog) * junipernetworks.junos 3.0.1 has been released with bugfixes (changelog)

felixfontein contributed

community.hrobot 1.4.0 (changelog) has been released with a new feature.


Gwmngilfen said

I've just published a blog post detailing the data we have on the usage of IRC & Matrix over the last 6 months. The TL;DR is that in terms of users-per-day IRC is flat, and Matrix is growing - check out the post for all the juicy plots!


gundalow said

Principal Software Engineer (Controller)

We are looking for a Principal Software Engineer to work on Controller, which is the downstream of AWX. This is the main component of what was previously called Ansible Tower.

In this role, you’ll be part of the Controller team whose work powers the Red Hat Ansible Automation Platform and enables customers to centralize and control their IT infrastructure with a visual dashboard, role-based access control, and more. As a Principal Software Engineer, you’ll be working with engineers at a variety of experience levels, developing each other’s skills, trusting in each other’s strengths, and supporting one another as you deliver on team commitments.

  • Write and maintain high quality code as a member of a team, leading best practice usage by example
  • Lead engineers in building implementations of new designs
  • Develop and mature habits in following engineering best practices
  • Work closely with lead architects and product managers to ensure features and fixes meet desired use-cases
  • Write unit and integration tests as well as understand debugging software
  • Actively participate in code reviews with the team
  • Work with the Quality Engineering (QE) team to ensure that builds are tested correctly
  • Submit patches for bug fixes to the Red Hat Ansible Automation Platform as well as the open source community; review patches from other community members
  • Mentor other engineers; lead them in delivering quality software

If this sounds like you, please apply via jobs.redhat.com.


Have any questions you’d like to ask, or issues you’d like to see covered? Please ask in #social:ansible.com! See you next time!