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

Bullhorn #63

Source

Ansible Bullhorn banner

A Newsletter for the Ansible Developer Community Issue #63, 2022-06-17 (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!

KEY DATES ⏱️

cybette contributed

GENERAL NEWS UPDATES 🔈️

Don Naro shared

New Ansible Getting Started guide

We've made the first iteration of the new Ansible Getting Started guide available.

The goal of this content is reducing the barrier to entry for new Ansible users and simplifying the journey for anyone who wants to ramp up on the basics, start writing playbooks, and gain a solid foundation to build Ansible skills.

The Getting Started guide incorporates a lot of great suggestions from the Ansible community via PRs, chat messages, and Reddit.

We hope you find it useful and look forward to getting more feedback to improve the content.

Gwmngilfen said

Room visibility changes on Matrix

As our adoption of Matrix continues, we've been taking a look at the expectations of Matrix users. It's common on modern chat platforms to be able to see the history when you join a room (or even before you join a room), which helps make sure you have the right room, set your expectations, understand the usage patterns, posting frequency, and so on. Today, that's not the case for most of our rooms, as they inherited the IRC-bridged-default of hiding room history from new joiners.

So, following a long discussion (6 months!) we're happy to announce that the Community and the Steering Committee have approved changing the history visibility on our Matrix rooms to match those expectations. This is a minor, but positive, change for the experience of our Matrix users - but it is also a change in expectations for our IRC users (although in reality, IRC is logged in many places already), so we will be adding ChanServ notices to our rooms to flag this to our IRC folks. Of course, we will be staging this rollout slowly - all rooms will get a ChanServ notice for joining, we'll notify the room manually a few days before the change, and we will only do a few rooms per week. Thanks!

COLLECTION UPDATES 🪄

andersson007_ said

Collection Inclusion Requests

The following collection inclusion requests are waiting for your review: * vultr.cloud * check_point.gaia * purestorage.fusion

See the review process description to learn how to do it.

Please help the community extend the package!

mariolenz contributed

Collection removal

It looks like the google.cloud collection is effectively unmaintained. According to the current community guidelines for collections, we consider removing it in a future version of the Ansible community package. Please see Unmaintained collection: google.cloud for more information or to announce that you're interested in taking over the maintenance of (a fork of) google.cloud.

At least one month after this announcement appears here and in the collection's issue tracker, the Ansible Community Steering Committee will vote on whether this collection is considered unmaintained and will be removed, or whether it will be kept. If it will be removed, this will happen earliest in Ansible 8.0.0. Please note that you can still manually install the collection with ansible-galaxy collection install google.cloud even when it has been removed from Ansible.

COMMUNITY UPDATES 👂️

gotmax (He/Him) shared

Ansible packages in Fedora Copr

There is now a COPR repo, gotmax23/ansible-6, available for Fedora that provides RPM packages for the latest version of ansible (currently 6.0.0rc1) and ansible-core (currently 2.13.0), as well as the latest versions of our packaged standalone collections for the Fedora releases where they are outdated. This enables ansible early adopters to utilize the newest ansible packages that cannot be published in the default repos for stable versions due to major version bumps being prohibited.

This also allows the maintainers to test our ansible packaging before we publish it in the default repos. Fedora Rawhide will update to Ansible 6 after the 6.0.0 final release, but I plan to continue publishing the latest versions in this COPR for the currently supported stable releases (35 and 36). Feel free to leave feedback in the COPR's associated Fedora Discussion post or join us in #packaging:ansible.com (#ansible-packaging on libera.chat)!

EVENTS AND MEETUPS 📅

cybette shared

AnsibleFest and Ansible Contributor Summit

AnsibleFest 2022 will be in Chicago, IL (USA) this year, on October 18 & 19. The call for proposals is now open until July 15, 2022.

Content topics can include: * Getting Started * Automating Red Hat products * Use Case / Domain-focused (e.g. Network, Security, Cloud) * Audience-focused (e.g. Developers, Operations) * Thought Leadership * Community and Culture

There will be an Ansible Contributor Summit the day before AnsibleFest on October 17, 2022, where participants will be able to join both in-person (in Chicago) and online. More details about this event will be shared as we confirm them!

THE ANSIBLE TEAM IS HIRING 💰️

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.

THAT'S ALL FOR NOW!

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!

Powered by