Using Event-Driven Ansible 2.5 with Ansible Automation Platform 2.4
Configure the latest Event-Driven Ansible to work with an existing 2.4 automation controller
Abstract
Preface
You can configure a new installation of Event-Driven Ansible controller 1.1 with automation controller 4.4 or 4.5, which is considered a general availability release fully supported by Red Hat. Automation controller 4.4 and 4.5 were released as part of Ansible Automation Platform 2.4.
Upgrading to Event-Driven Ansible controller 1.1 from an earlier release is unsupported at this time.
This means that you can install a new Event-Driven Ansible controller 2.5 server and configure rulebook activations to execute job templates on an Ansible Automation Platform 2.4 automation controller. With this interoperability support you can retain your existing Ansible Automation Platform 2.4 clusters and add Event-Driven Ansible controller 2.5 to them. This gives you the option to upgrade your Ansible Automation Platform 2.4 cluster to Ansible Automation Platform 2.5 at a date that suits you, whilst giving you all the benefits of Event-Driven Ansible 2.5.
The installs are still two separate installs, in that you manage the Ansible Automation Platform 2.4 cluster with the Ansible Automation Platform 2.4 installer. The Event-Driven Ansible 2.5 server is managed with the Ansible Automation Platform 2.5 installer.
This guide shows you how to install and configure Event-Driven Ansible 1.1 to work with automation controller 4.4 or 4.5 for a Red Hat Package Manager (RPM)-based installation.
Providing feedback on Red Hat documentation
If you have a suggestion to improve this documentation, or find an error, you can contact technical support at https://access.redhat.com to open a request.
Chapter 1. Red Hat Package Manager-based installation
If you have an existing Ansible Automation Platform 2.4 Red Hat Package Manager (RPM)-based installation of automation controller (4.4 or 4.5), you can perform a new installation of Ansible Automation Platform 2.5, which has Event-Driven Ansible controller 1.1, and configure the two installations to work together.
If you do not have an existing Ansible Automation Platform 2.4 RPM-based installation of automation controller, see the Red Hat Ansible Automation Platform installation guide, ensuring that you use an Ansible Automation Platform 2.4 installer.
1.1. Installing Event-Driven Ansible controller 1.1 and configuring automation controller 4.4 or 4.5
Perform a new Ansible Automation Platform 2.5 RPM-based installation of Event-Driven Ansible controller 1.1 and configure it to work with an existing Ansible Automation Platform 2.4 installation of automation controller 4.4 or 4.5.
Prerequisites
- An existing RPM-based installation of Ansible Automation Platform 2.4 with automation controller version 4.4 or 4.5.
Procedure
- Follow the steps provided in Installing on virtual machines until the section Installing Red Hat Ansible Automation Platform and ensure you download the Ansible Automation Platform 2.5 version of the RPM-based installer.
Use the following example to populate the inventory file to deploy a new single instance of Event-Driven Ansible controller 1.1:
# This is the enterprise installer inventory file # Please consult the docs if you are unsure what to add # For all optional variables please consult the Red Hat documentation: # https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.5/html/rpm_installation # This section is for your platform gateway hosts # ----------------------------------------------------- [automationgateway] gateway1.example.org gateway2.example.org # This section is for your Event-Driven Ansible controller hosts # ----------------------------------------------------- [automationedacontroller] eda1.example.org eda2.example.org [all:vars] # Common variables # https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.5/html/rpm_installation/appendix-inventory-files-vars#ref-general-inventory-variables # ----------------------------------------------------- registry_username=<your RHN username> registry_password=<your RHN password> # Platform gateway # https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.5/html/rpm_installation/appendix-inventory-files-vars#ref-gateway-variables # ----------------------------------------------------- automationgateway_admin_password=<set your own> automationgateway_pg_host=<set your own> automationgateway_pg_database=<set your own> automationgateway_pg_username=<set your own> automationgateway_pg_password=<set your own> # Event-Driven Ansible controller # https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.5/html/rpm_installation/appendix-inventory-files-vars#event-driven-ansible-controller # ----------------------------------------------------- automationedacontroller_admin_password=<set your own> automationedacontroller_pg_host=<set your own> automationedacontroller_pg_database=<set your own> automationedacontroller_pg_username=<set your own> automationedacontroller_pg_password=<set your own>
NoteKeep controller out of the inventory file. Ensure that
[automationcontroller]
is an empty group. Only add an Event-Driven Ansible 2.5 server. Do not add an Event-Driven Ansible 2.4 server since there is no upgrade option available- Continue with the steps in Installing Red Hat Ansible Automation Platform.
1.2. Post installation steps for RPM-based install
You must complete post-install steps for setting up Ansible Automation Platform 2.5 with Event-Driven Ansible controller 1.1 and Ansible Automation Platform 2.4 with automation hub 4.9. The installation program does not handle the creation of decision environments and credentials in this scenario. See the following steps to complete the installation:
Upload the 2.5 de-supported decision environment to automation hub. For more information, see Pushing a container image to private automation hub.
NoteIf you are doing a bundle install, the image is included in the setup bundle .tar file.
- Create an automation hub container registry credential in Event-Driven Ansible. For more information, see Setting up credentials.
Chapter 2. Post installation configuration
After completing your installation you need to connect Automation Decisions (Event-Driven Ansible controller) to Automation Execution (automation controller) to run rulebook activations successfully.
To do this for a RPM-based install, follow the steps provided in Setting up a Red Hat Ansible Automation Platform credential.