We want to hear from you! Help us gain insights into the state of the Ansible ecosystem.
Take the Ansible Project Survey 2024

Bullhorn #12

Ansible Bullhorn banner

The Bullhorn

A Newsletter for the Ansible Developer Community
Issue #12, 2020-10-21


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 2.10.1 NOW GENERALLY AVAILABLE

The Ansible Community team announced the general availability of Ansible 2.10.1 on October 13th. This first minor release of the ansible-2.10 package should be a drop-in replacement for Ansible 2.9; the roles and playbooks that you currently use should work out of the box with ansible-2.10.1. For more information on what’s new, how to get it, plus caveats and known bugs, read Toshio Kuratomi’s announcement to the ansible-devel mailing list.
 

ANSIBLE-BASE 2.10.2 NOW GENERALLY AVAILABLE

The Ansible Base team announced the general release of Ansible 2.10.2 on October 5th. This 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. For more information on how to download, test, and report issues, read Rick Elrod’s announcement to the ansible-devel mailing list.
 

ANSIBLE 2.9.14 AND 2.8.16 RELEASED

The Ansible Core team announced the availability of Ansible 2.9.14 and Ansible 2.8.16 on October 5th, both of which are maintenance releases. Follow this link for Rick Elrod’s email to the ansible-devel mailing list, to obtain details on what’s new, installation instructions, and links to the full changelogs.
 

PROPOSALS FOR ANSIBLE COLLECTIONS

Feedback is needed from the wider Ansible community on the following:
  • Moving content from collections in Ansible 2.10 to collections currently outside, or: should we add new collections to 2.10.x? For example, should we allow Postgres modules to be migrated from community.general to a new community.postgres collection to be included in Ansible 2.10? #117
  • Should docs be included in collection and Ansible package tarballs? #120
  • Should tests be included in collection tarballs? #111
Please add your feedback via commenting on the GitHub discussions. You can see the full list of proposals here.
 

CHANGES IMPACTING COLLECTION CONTRIBUTORS

  • ansible-test sanity now validates more semantic versioning properties for collections (details)
You can stay up-to-date with the changes as they happen by subscribing to this GitHub issue.
 

NEW/UPDATED COMMUNITY COLLECTIONS

These collections have been released on September 30: community.general 1.2.0 and community.network 1.2.0.

For VMware, community.vmware 1.3.0 was released on October 2. This blog post introduces the new VMware REST collection.

The community.kubernetes collection is going to move to kubernetes.core shortly (see why). Also, the community.okd collection just got a new 0.3.0 release that is ready for testing, and soon, inclusion on Automation Hub under the name ‘redhat.openshift’.

Ansible Podman collection released 1.3.1 version on October 8, which includes bug fixes and enhancements for podman_container, podman_network, podman_volume and other modules. The dependency on PyYAML python package has finally been removed from all podman modules, so now the collection doesn't require anything but Podman installed on the host.

Several more collections were updated on October 13: community.crypto 1.2.0 (fixes CVE-2020-25646), community.mysql 1.1.0, and cloudscale_ch.cloud 1.2.0.

Last but not least, Ansible Openstack Cloud collection released the newest 1.2.0 version on October 13. Modules for management of Openstack volumes and snapshots were added: volume_snapshot_info, volume_backup, volume_backup_info.
 

ANSIBLE CONTRIBUTOR SUMMIT (OCTOBER 2020) RECAP

The third fully virtual Ansible Contributor Summit of 2020 was held on October 12th and 15th. More than 700 participants joined us over the course of the 2 days, which is 10 times the previous event in July. We are still processing the videos and recordings from the summit, and they will be made available on the Ansible Community Youtube channel, and shared with the attendees along with notes and Q&A responses.

In the meantime, you can check out the summary (Day 1, Day 2) and full logs (Day 1, Day 2) from the IRC sessions.

We would appreciate your feedback to help us improve the Contributor Experience, whether or not you were able to attend the event. Here is the Contributor Survey; please take a couple of minutes to fill this in. Thank you!
 

ANSIBLE HACKTOBERFEST 2020

We usually follow up issues discussed in the Ansible Contributor Summit with an Ansible Hackathon. Since this is also the month of Hacktoberfest, we will have an Ansible Hacktoberfest event on October 30th, 2020. Please register and join us!
 

ANSIBLE COMMUNITY STATS UPDATE

Following our Contributor Summit last week, Greg will be digging into the participation stats from Bluejeans, and results from post-event surveys as usual. A cursory glance over the data shows 707 attendees from 67 countries across the two days! We can also see some indicators that the event helped to get people contributing, and especially that the Katacoda sessions helped with this - 19 of the 23 newcomers (83%) said Katacoda was useful, and 9/10 attendees who said they didn't know how to contribute earlier now say they do.

More to come!
 

CONTENT FROM THE ANSIBLE COMMUNITY

 

ANSIBLE VIRTUAL MEETUPS

The following virtual meetups are being held in the Ansible community over the next month:

Ansible NOVA Note: For these virtual events, the links to participate will be visible once you RSVP to attend. If you’re interested in the topics presented, you can join from anywhere in the world as long as the time zone and language works for you!
 

NETDEVOPS SURVEY 2020 NOW OPEN

The NetDevOps Survey 2020 is now live, and looking for respondents! The goal of this survey is to collect information to understand how network operators and engineers are using automation to operate their network today. The survey has been designed to be vendor neutral, collaborative, and community-focused. All network professionals are welcome to participate in the survey, please complete the survey here October 23.
 

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.