We are thrilled to announce the general availability of Red Hat Ansible Automation Platform 2.1. This is the follow-on to the Ansible Automation Platform 2.0 Early Access released this summer, and announced at AnsibleFest 2021. Red Ansible Automation Platform 2.1 introduces major features that allow customers to onboard more easily with even more flexible automation architectures and use cases. Ansible Automation Platform 2.1 is the culmination of many years of reimagining how enterprise automators automate for today and tomorrow.
You can download the latest version directly from the Red Hat Customer Portal, or sign up for a free trial at red.ht/try_ansible. Ansible Automation Platform is the Ansible you know and love, designed for the enterprise. I am going to summarize Andrius Benokraitis’ blog post from September, when Ansible Automation Platform 2 was announced, and expand on some key developments from 2.0 to 2.1.
First, some general information:
- The Ansible Automation Platform life cycle page has been updated.
- Moving forward, every Ansible Automation Platform minor release will now have its own unique Red Hat Subscription Management repo, which requires an Ansible Automation Platform subscription.
subscription-manager repos –enable=ansible-automation-platform-2.1-for-rhel-8-x86_64-rpms
Now, some official product documentation updates:
- The following are the new guides developed and released in 2.1:
- The following are the existing guides with major additions:
- All Documentation updates can also be found online, including the updated release notes.
New to Ansible Automation Platform 2.1: automation mesh
Automation mesh (documentation): This is the newest addition to Ansible Automation Platform, and replaces the isolated nodes feature in 1.2. By combining automation execution environments in version 2.0 with automation mesh in version 2.1, the automation control plane and execution plane are fully decoupled, making it easier to scale automation across the globe. You can now run your automation as close to the source as possible, without being bound to running automation in a single data center. With automation mesh, you can create execution nodes right next to the source (for example, a branch office in Johannesburg, South Africa) while execution is deployed on our automation controller in Durham, NC.
Automation mesh adds:
- Dynamic cluster capacity. You can increase the amount of execution capacity as you need it.
- Global scalability. The execution plane is now resilient to network latency and connection interruptions and improves communications.
- Secure automation. Bi-directional communication between execution nodes and control nodes that include full TLS authentication and end-to-end encryption.
Check out this automation mesh demo by Shane McDonald and Craig Brandt performed at AnsibleFest 2021 (skip to 22:38). Also, stay tuned for a forthcoming blog that will explore automation mesh in greater depth.
Updated automation execution environments
Recently, automation execution environments replaced Ansible Engine in 1.2 in a much more portable and flexible package.
In Ansible Automation Platform 2.1, there is an updated set of prebuilt, supported automation execution environments now available in the Red Hat container registry. These images can be used in different capacities in your environment and are provided as part of the Ansible Automation Platform subscription. All supported automation execution environments are hosted in a parent repository called ansible-automation-platform-2. For convenience, all three automation execution environments are now included as part of the bundled 2.1 installer.
The following pre-built environments have been updated:
- Minimal (ee-minimal-rhel8) – Contains Ansible Core 2.12 built on top of UBI8 and python-3.8. This image doesn’t contain any Collections; you can use this as the base image to build additional automation execution environments with your custom Collections or the Red Hat Ansible Certified Content Collections available on Ansible automation hub.
- Supported (ee-supported-rhel8) – This is the default image available with the automation controller. It is built on top of the minimal image and contains all updated Ansible Content Collections officially supported by Red Hat.
- Ansible 2.9 (ee-29-rhel8) – Contains Ansible-2.9 and all the required Ansible dependencies. This image is best for customers who are planning to migrate to Ansible Automation Platform 2.1 from Ansible Automation Platform 1.2.
Updated for disconnected environments
With the Ansible Automation Platform 2.1 release, installation in a disconnected environment now supports the Red Hat Ansible Automation Platform Operator for Red Hat OpenShift. For more information on this, please refer to the official product documentation.
Added central authentication functionality
With any enterprise software solution, the need for single sign-on (SSO) becomes increasingly important. As Ansible Automation Platform 2 continues to release additional related components, so is the need to easily authenticate between them in a standardized way. The first of many components to leverage SSO is private automation hub, including the Red Hat Ansible Automation Platform Operator. This enhancement lays the groundwork for additional parts of Ansible Automation Platform to also be SSO-enabled in future releases.
A recap: Ansible Automation Platform 2 component overview
Ansible Automation Platform 2 introduced an entire suite of tools and components that enables enterprises to scale automation across their organizations. Ansible Automation Platform is no longer just an upstream command line Ansible package with support, nor is the platform simply just a graphical user interface for Ansible. Let’s look at a high level diagram that details the different components available:
There are a lot of components besides just the well known “ansible-*” binary command line tools. Red Hat has developed multiple components to help customers create, manage and scale their automation. Let’s break these down and highlight what has been released!
Execution environment builder (documentation): This is a command line tool that helps automation creators quickly package together their automation into containerized images calltested automation execution environments .
Ansible content tools: This refers to fully supported components that help people create automation content. For example, the command line tool “ansible-test” helps IT automators test their automation content (documentation). We’re working towards adding full support for the Ansible VS code extension, as well as other creator tools.
Ansible Content Collections: With Ansible Automation Platform 2, we have disaggregated automation content (roles, playbooks, modules, plugins, etc.) from the execution component ansible-core (e.g. ansible-playbook, etc). A good analogy for this is that I don’t have to upgrade my phone to grab the newest version of my favorite mobile game. By disaggregating automation content, it allows us to asynchronously release Ansible Content Collection updates and continually improve automation. If you need help on understanding what a Collection is, check out this YouTube video. We have continually added new automation content for multiple domains, including:
- Infrastructure (Red Hat, Windows)
- Cloud Native (Kubernetes and Red Hat OpenShift)
- Public Cloud (AWS, Azure, GCP)
- Private Cloud (VMware)
- Network Automation (Arista, Cisco, Juniper, Vyos)
- Security Automation (Checkpoint, Cisco, IBM)
You can check out all the certified and fully supported Collections on Ansible automation hub on console.redhat.com.
Automation content navigator (documentation): A new command-line component for automation creators that includes an interactive text-based user interface (TUI). Automation content navigator (ansible-navigator) allows Ansible experts to easily reuse their operational knowledge of traditional Ansible commands and methodologies (e.g. ansible-playbook) with support for automation execution environments. Automation content navigator also allows the ability to quickly zoom in and out of plays and filter output on the fly, enhancing the play recap experience that automation engineers have come to know and love. I also highly recommend watching my colleague’s YouTube video Authoring content quickly using ansible-navigator.
Automation controller (documentation): the Web User Interface (webUI) and API (Application Programming Interface) for Ansible Automation Platform. This replaces the component formerly known as Red Hat Ansible Tower. However, it goes above and beyond the old architecture by decoupling the control plane and execution plane so the execution capacity is no longer tied to the same node as the graphical interface. For more information on this architectural change, I recommend reading Craig Brandt’s blog post, What’s new in Ansible Automation Platform 2: automation controller.
Automation execution environments (documentation): Simply put, these are container images that can be utilized as Ansible control nodes. They contain the Python package dependencies (e.g. boto3 for Amazon Web Services), system level dependencies (e.g. Linux packages gcc, jq) and Ansible Content Collections bundled with a version of ansible-core to create a self-contained runtime environment for your Ansible Playbooks. Both command-line ansible-navigator and the WebUI/API driven automation controller can perform execution environments, making it easier to go from creating and testing your automation playbooks to operatilizing and putting them into production quicker and more effortlessly. For more information on automation execution environments, please check out the blog post, What’s new in Ansible Automation Platform 2: automation execution environments.
Private automation hub (documentation): Allows automation creators to collaborate and publish their own automation content and streamline Ansible code within their own organizations. Organizations can now manage and control the lifecycle of their Ansible content as their needs scale across the hybrid cloud. This component is completely self-hosted and can service both Ansible Content Collections and execution environments to automation creators and operators. I encourage you to read my blog on private automation hub for a deep dive.
Automation hub (console): This is the counterpart to private automation hub. This is a publicly hosted and curated automation content repository on console.redhat.com for all the fully supported and certified Ansible Content Collections. IT Operators can sync specific Collections from Ansible automation hub to their on-premises private automation hub and control which content they want to use.
Red Hat Insights for Ansible Automation Platform (console and product page): This optional hosted service is available on console.redhat.com. It allows automation architects to aggregate data from multiple Ansible Automation Platform clusters to a single visual dashboard, so architects can analyze and discover trends across multiple automation initiatives. Red Hat Insights for Ansible Automation Platform is a hosted service constantly adding new features and abilities asynchronous from Ansible Automation Platform. However, there is a new feature coinciding with 2.1, called reports. Reports offer analytical data and downloadable PDFs for consumption. For example, you can see which hosts were changed by which job template over time, hosts broken down by organizations, jobs and tasks broken out by organization, and more.
Automation services catalog (console): Another hosted service on console.redhat.com included in your Ansible Automation Platform subscription. Automation services catalog acts as a lightweight IT service management, where automation consumers can order automation as catalog items. Automation services catalog allows you to aggregate multiple automation controllers into a single push-button WebUI abstracting any site-specific complexity. This allows new personas to adopt automation in a consumable turn-key fashion across your organization. It also has approvals and checkout systems, adding a level of governance to your enterprise automation.
Ansible Automation Platform Operator (documentation): A native and fully supported Operator for Red Hat OpenShift, allowing easy installation of Ansible components onto Red Hat OpenShift through Operator Hub. Both automation controller and private automation hub are included in a single consumable operator. Watch this in action in our light hearted series, Automated Live, Episode 03 (skip to 5:29).
What can I do next?
Whether you are beginning your automation journey or a seasoned veteran, there are a variety of resources to enhance your automation knowledge:
- Self-paced exercises – We have interactive in-browser exercises to learn and dive into Ansible Automation Platform.
- Trial subscription – Are you ready to install on-premises? Get your own trial subscription for unlimited access to all the components of Ansible Automation Platform.
- Developer license – Did you know that you can get a free developer license to learn in your home lab? Register and get access to all the latest tools, technologies and community that Red Hat has to offer.
- Subscribe to the Red Hat Ansible Automation Platform YouTube channel . Be sure to check out our new web series, Automated Live hosted by Colin McNaughton
- Follow Red Hat Ansible Automation Platform on Twitter – Do you have questions or an automation project you want to show off? Tweet at us!
Originally posted on Ansible Blog