Migrating from Python virtual environments to automation execution environments in Ansible Automation Platform 2
Red Hat Ansible Tower (included in Ansible Automation Platform 1.x) used Python virtual environments to manage dependencies and implement consistent automation execution across multiple Red Hat Ansible Automation Platform instances. This method of managing dependencies came with its own set of limitations:
- Managing Python virtual environments across multiple Ansible Tower instances.
- Confirming custom dependencies across Ansible Tower instances grew in complexity as more end-users interacted with it.
- Python virtual environments were tightly coupled to the control plane, resulting in Operations teams bearing the majority of the burden to maintain them.
- There were no tools supported and maintained by Red Hat to manage custom dependencies across Ansible Automation Platform deployments.
Ansible Automation Platform 2 introduced automation execution environments. These are container images in which all automation is packaged and run, which includes components such as Ansible Core, Ansible Content Collections, a version of Python, Red Hat Enterprise Linux UBI 8, and any additional package dependencies.
Why should you upgrade?
Ansible Automation Platform 2, announced at AnsibleFest 2021, comes with a re-imagined architecture that fully decouples the automation control plane and execution plane. The new capabilities enable easier to scale automation across the globe and allow Continue reading