Bullhorn #17

Ansible Bullhorn banner

The Bullhorn

A Newsletter for the Ansible Developer Community Issue #17, 2021-01-06 (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-01-06: community IRC meeting, 19:00 UTC
  • 2021-01-07: D&I working group meeting, 19:00 UTC
  • 2021-01-13: community IRC meeting, 19:00 UTC
  • 2021-01-18: Bullhorn #18 content deadline
  • 2021-01-18: ETA for Ansible-base 2.10.5 release
  • 2021-01-26: ETA for Ansible 2.10.6 release
  • 2021-01-27: New collections to be included in Ansible 3.0.0 must be reviewed and approved by this date.
    • Please submit your new collections for review as early as possible because we have limited reviewers. Submissions made close to the deadline may not have time to be reviewed and approved in time for inclusion.
  • 2021-02-16: ETA for Ansible 3.0.0 release

ACCEPTING NEW COLLECTIONS FOR ANSIBLE 3.0.0

The criteria for accepting new collections for Ansible 3.0.0 (scheduled for release in February) have been approved.

If you would like your collection to be included in ansible-3.0.0, please try to make your collection conform to the requirements and then submit it as a discussion.

  • When you start the discussion, please include a link to the collection on galaxy, a link to the source code repository, a link to the issue tracker, and the GitHub IDs of collection owners that we should contact if there's a problem with the collection later.
  • We will review the new collection requests that have been submitted on a first-come, first-served basis. The earlier you submit your collection, the more likely you are to get it into 3.0.0.
  • The review may turn up things that need to be fixed which would delay acceptance.
  • 2021-01-27 is the date by which new collections must be reviewed and accepted, so get your collection in as early as possible, i.e. NOW! Submitting it close to the deadline may mean that there is not enough time for us to review and approve it resulting in it not being accepted.

The procedure for getting new collections in is highly likely to change for the Ansible 4.0.0 release (including who reviews, whether it remains first-come first-served, and so forth).

ANSIBLE 2.10.5 NOW GENERALLY AVAILABLE

The Ansible Community team announced the general availability of Ansible 2.10.5 on January 5th. This update contains bug fixes and new, backwards compatible features in the contained collections. For more information on what’s new, how to get it, plus schedule for upcoming releases, read Deric Crago’s announcement to the ansible-devel mailing list.

NEW/UPDATED COMMUNITY COLLECTIONS

PROPOSAL FOR ANSIBLE NETWORKING

The Ansible Network Engineering Team is cordially welcoming comments from the Ansible Network community for the following proposal: BGP Global and AF Context Resource Model. The enablement of BGP as network resource modules for supported platforms has long been requested, and is now being scoped and planned for implementing this year. Please provide feedback in the next few weeks!

ANSIBLE COMMUNITY STATS UPDATE

For the last bit of fun in 2020, Greg re-did the 2019 bubble plot for the new world of Collections. As before, it shows the amount of contribution to the various collections, coloured by the amount of contribution from staff vs community.

DIVERSITY & INCLUSION WORKING GROUP MEETING

The first Diversity WG meetings will be this week on January 7th at 19:00 UTC in IRC channel #ansible-diversity, and take place every other week. Submit agenda items in this GitHub issue.

CONTENT FROM THE ANSIBLE COMMUNITY

ara 1.5.4 has been released: - See the changelog - The new version is already available on: PyPi, DockerHub, and Quay as well as Fedora

ANSIBLE VIRTUAL MEETUPS

The following virtual meetups 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.