Upstream Ansible is not suitable for mission-critical automation.
The upstream project is often where users start getting familiar with Ansible and grow their own competency with the project and with automation in general. It is often good for learning to automate or experimenting, but isn’t suitable for missioncritical automation.
There are additional upstream open source projects within the Ansible ecosystem, such as “AWX,” that offer a user interface (UI) and the ability to create role-based access controls (RBAC), audits and logs, advanced workflows, job scheduling, and other features. However, with all upstream Ansible projects, it’s important to remember they were not developed as a standalone software project or with the mission-critical needs of businesses in mind.
Upstream projects are not, for example, concerned with secure software supply chains, or orchestrating cross-domain workflows across multiple datacenter and cloud locations, or providing the Ansible developer with support tools needed for long-term sustainability. Upstream Ansible projects are fast-changing software projects meant for rapid experimentation for open source developers.
This is why Red Hat maintains a hardened and productized version of Ansible composed of more than 20 open source Ansible-related projects in a single, supported platform.
This enterprise platform version of Ansible requires a subscription, and it includes an array of features that serve the needs and goals of IT businesses looking for automation solutions. If upstream Ansible is primarily for individuals, Red Hat Ansible Automation Platform is primarily for organizations.
However, the 2 projects are connected.
Find the benefits of upstream innovation in a platform hardened for security.
The community Ansible project is what is known as an “upstream” project, which means that it serves as the hub and source of the core development on Ansible. Ansible Automation Platform is a downstream project, where additional development turns Ansible into a hardened version for business organizations and business-critical environments. Important development in the community version of Ansible makes its way to Ansible Automation Platform, and, occasionally, developments in Ansible Automation Platform are sent back upstream to the community Ansible project.
This collaboration with the open source community has always been Red Hat’s business model for customers, and it has resulted in the growth of Red Hat Enterprise Linux® and Red Hat OpenShift® for the most critical environments requiring stability, performance, and security.
Why is it called Ansible?
The term “ansible” refers to a device that can allow near-instant, faster-than-light communication across long distances. Originally used by Ursula K. LeGuin in her novel Rocannon’s World, it has since become a standardized term in fiction. The Ansible project took the name from that term.1