Red Hat SummitChapter 4. Infrastructure changes by deployment type
You can review the infrastructure changes required when upgrading to Ansible Automation Platform 2.6. The infrastructure changes vary depending on your current version, deployment method, and target topology.
- RPM and Operator-based deployments: Upgrade directly from version 2.4 or 2.5 to 2.6
- Container-based deployments: Upgrade from version 2.5 to 2.6 (upgrades from 2.4 are not supported)
Each deployment type section includes topology diagrams, infrastructure requirements, and configuration examples to help you plan your upgrade.
4.1. RPM-based deployments
The following sections describe the tested infrastructure changes for RPM-based deployments. For step-by-step upgrade instructions, see RPM upgrade.
4.1.1. Upgrading a 2.4 single automation controller node deployment to a 2.6 growth topology
Successfully upgrade your single automation controller node deployment (version 2.4) to a 2.6 growth topology. Use the provided infrastructure changes, requirements, and example inventory file to plan your upgrade.
4.1.1.1. 2.4 infrastructure topology diagram
This diagram outlines the 2.4 infrastructure topology for this deployment model.
Figure 4.1. 2.4 infrastructure topology diagram
4.1.1.2. 2.6 infrastructure topology diagram
This diagram outlines the 2.6 infrastructure topology that Red Hat has tested with this deployment model.
Figure 4.2. 2.6 infrastructure topology diagram
4.1.1.3. Requirements for upgrading a single automation controller node deployment
The following table highlights the requirements for upgrading from Ansible Automation Platform version 2.4 to 2.6.
| Existing 2.4 topology | Tested 2.6 topology | Requirements for each VM |
|---|---|---|
| Non-redundant automation controller-only deployment:
| Growth topology:
| See the RPM growth topology section of the Tested deployment models guide. |
4.1.1.4. Example inventory file
The following inventory file has been updated with the necessary changes to upgrade to the 2.6 growth topology.
# This is the RPM-based Ansible Automation Platform installer inventory file intended for upgrading from a 2.4 single automation controller deployment to a 2.6 growth deployment.
# Consult the Ansible Automation Platform product documentation about this topology's tested hardware configuration.
# https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.6/html/tested_deployment_models/rpm-topologies
# For all optional variables consult the Ansible Automation Platform documentation:
# https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.6/html/rpm_installation
# This section is for your platform gateway hosts - NEW for 2.6 growth topology
# -----------------------------------------------------
[automationgateway]
gateway.example.org
# This section is for your automation controller hosts from your 2.4 inventory
# -----------------------------------------------------
[automationcontroller]
controller.example.org
[automationcontroller:vars]
peers=execution_nodes
# This section is for your execution hosts - NEW for 2.6 growth topology
# -----------------------------------------------------
[execution_nodes]
exec.example.org
# This section is for your automation hub hosts - NEW for 2.6 growth topology
# -----------------------------------------------------
[automationhub]
hub.example.org
# This section is for your Event-Driven Ansible hosts - NEW for 2.6 growth topology
# -----------------------------------------------------
[automationedacontroller]
eda.example.org
# This section is for the Ansible Automation Platform database from your 2.4 inventory file
# -----------------------------------------------------
[database]
db.example.org
[all:vars]
# Common variables from your 2.4 inventory file
# https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.6/html/rpm_installation/appendix-inventory-files-vars#general-variables
# -----------------------------------------------------
registry_username=<your RHN username>
registry_password=<your RHN password>
# Common variables - NEW for 2.6 growth topology
# https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.6/html/rpm_installation/appendix-inventory-files-vars#general-variables
# -----------------------------------------------------
redis_mode=standalone
# Platform gateway - NEW for 2.6 growth topology
# https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.6/html/rpm_installation/appendix-inventory-files-vars#platform-gateway-variables
# -----------------------------------------------------
automationgateway_admin_password=<set your own>
automationgateway_pg_host=db.example.org
automationgateway_pg_password=<set your own>
# Automation controller variables from your 2.4 inventory file
# https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.6/html/rpm_installation/appendix-inventory-files-vars#controller-variables
# -----------------------------------------------------
admin_password=<set your own>
pg_host=db.example.org
pg_password=<set your own>
# Automation hub - NEW for 2.6 growth topology
# https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.6/html/rpm_installation/appendix-inventory-files-vars#hub-variables
# -----------------------------------------------------
automationhub_admin_password=<set your own>
automationhub_pg_host=db.example.org
automationhub_pg_password=<set your own>
# Event-Driven Ansible - NEW for 2.6 growth topology
# https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.6/html/rpm_installation/appendix-inventory-files-vars#event-driven-ansible-variables
# -----------------------------------------------------
automationedacontroller_admin_password=<set your own>
automationedacontroller_pg_host=db.example.org
automationedacontroller_pg_password=<set your own>4.1.2. Upgrading a 2.4 single node automation controller and automation hub deployment to a 2.6 growth topology
Upgrade your 2.4 single-node deployment (automation controller and automation hub) to a 2.6 growth topology. Review the infrastructure changes and requirements needed to successfully plan your upgrade.
4.1.2.1. 2.4 infrastructure topology diagram
This diagram outlines the 2.4 infrastructure topology for this deployment model.
Figure 4.3. 2.4 infrastructure topology diagram
4.1.2.2. 2.6 infrastructure topology diagram
This diagram outlines the 2.6 infrastructure topology that Red Hat has tested with this deployment model.
Figure 4.4. 2.6 infrastructure topology diagram
4.1.2.3. Requirements for upgrading a single automation controller node and automation hub deployment
The following table highlights the requirements for upgrading from Ansible Automation Platform version 2.4 to 2.6.
| Existing 2.4 topology | Tested 2.6 topology | Requirements for each VM |
|---|---|---|
| Non-redundant deployment with automation controller and automation hub:
| Growth topology:
| See the RPM growth topology section of the Tested deployment models guide. |
4.1.2.4. Example inventory file
The following inventory file has been updated with the necessary changes to upgrade to the 2.6 growth topology.
# This is the RPM-based Ansible Automation Platform installer inventory file intended for upgrading from a 2.4 single automation controller and automation hub deployment to a 2.6 growth deployment.
# Consult the Ansible Automation Platform product documentation about this topology's tested hardware configuration.
# https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.6/html/tested_deployment_models/rpm-topologies
# For all optional variables consult the Ansible Automation Platform documentation:
# https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.6/html/rpm_installation
# This section is for your platform gateway hosts - NEW for 2.6 growth topology
# -----------------------------------------------------
[automationgateway]
gateway.example.org
# This section is for your automation controller hosts from your 2.4 inventory
# -----------------------------------------------------
[automationcontroller]
controller.example.org
[automationcontroller:vars]
peers=execution_nodes
# This section is for your execution hosts - NEW for 2.6 growth topology
# -----------------------------------------------------
[execution_nodes]
exec.example.org
# This section is for your automation hub hosts from your 2.4 inventory
# -----------------------------------------------------
[automationhub]
hub.example.org
# This section is for your Event-Driven Ansible hosts - NEW for 2.6 growth topology
# -----------------------------------------------------
[automationedacontroller]
eda.example.org
# This section is for the Ansible Automation Platform database from your 2.4 inventory file
# -----------------------------------------------------
[database]
db.example.org
[all:vars]
# Common variables from your 2.4 inventory file
# https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.6/html/rpm_installation/appendix-inventory-files-vars#general-variables
# -----------------------------------------------------
registry_username=<your RHN username>
registry_password=<your RHN password>
# Common variables - NEW for 2.6 growth topology
# https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.6/html/rpm_installation/appendix-inventory-files-vars#general-variables
# -----------------------------------------------------
redis_mode=standalone
# Platform gateway - NEW for 2.6 growth topology
# https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.6/html/rpm_installation/appendix-inventory-files-vars#platform-gateway-variables
# -----------------------------------------------------
automationgateway_admin_password=<set your own>
automationgateway_pg_host=db.example.org
automationgateway_pg_password=<set your own>
# Automation controller variables from your 2.4 inventory file
# https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.6/html/rpm_installation/appendix-inventory-files-vars#controller-variables
# -----------------------------------------------------
admin_password=<set your own>
pg_host=db.example.org
pg_password=<set your own>
# Automation hub - NEW for 2.6 growth topology
# https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.6/html/rpm_installation/appendix-inventory-files-vars#hub-variables
# -----------------------------------------------------
automationhub_admin_password=<set your own>
automationhub_pg_host=db.example.org
automationhub_pg_password=<set your own>
# Event-Driven Ansible - NEW for 2.6 growth topology
# https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.6/html/rpm_installation/appendix-inventory-files-vars#event-driven-ansible-variables
# -----------------------------------------------------
automationedacontroller_admin_password=<set your own>
automationedacontroller_pg_host=db.example.org
automationedacontroller_pg_password=<set your own>4.1.3. Upgrading a 2.4 multi node automation controller deployment to a 2.6 enterprise topology
Upgrade your 2.4 multi-node automation controller setup to a 2.6 enterprise topology. Review the required infrastructure changes and requirements needed to successfully plan the upgrade.
4.1.3.1. 2.4 infrastructure topology diagram
This diagram outlines the 2.4 infrastructure topology for this deployment model.
Figure 4.5. 2.4 infrastructure topology diagram
4.1.3.2. 2.6 infrastructure topology diagram
This diagram outlines the 2.6 infrastructure topology that Red Hat has tested with this deployment model.
Figure 4.6. 2.6 infrastructure topology diagram
4.1.3.3. Requirements for upgrading a multi automation controller node deployment
The following table highlights the requirements for upgrading from Ansible Automation Platform version 2.4 to 2.6.
| Existing 2.4 topology | Tested 2.6 topology | Requirements for each VM |
|---|---|---|
| Redundant automation controller-only deployment:
| Enterprise topology:
Note: Redis high availability requires 6 VMs. Redis can be colocated with automation hub, platform gateway, or Event-Driven Ansible components, but it cannot be colocated with automation controller, execution nodes, or the PostgreSQL database. | See the RPM enterprise topology section of the Tested deployment models guide. |
4.1.3.4. Example inventory file
The following inventory file has been updated with the necessary changes to upgrade to the 2.6 enterprise topology.
# This is the RPM-based Ansible Automation Platform installer inventory file intended for upgrading from a 2.4 multi node automation controller deployment to a 2.6 enterprise deployment.
# For all optional variables consult the Red Hat documentation:
# https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.6/html/rpm_installation
# This section is for your platform gateway hosts - NEW for 2.6 enterprise topology
# -----------------------------------------------------
[automationgateway]
gateway1.example.org
gateway2.example.org
# This section is for your automation controller hosts from your 2.4 inventory
# -----------------------------------------------------
[automationcontroller]
controller1.example.org
controller2.example.org
[automationcontroller:vars]
peers=execution_nodes
# This section is for your execution hosts from your 2.4 inventory
# -----------------------------------------------------
[execution_nodes]
hop1.example.org node_type='hop'
exec1.example.org
exec2.example.org
# This section is for your automation hub hosts - NEW for 2.6 enterprise topology
# -----------------------------------------------------
[automationhub]
hub1.example.org
hub2.example.org
# This section is for your Event-Driven Ansible hosts - NEW for 2.6 enterprise topology
# -----------------------------------------------------
[automationedacontroller]
eda1.example.org
eda2.example.org
# This section is for your Redis hosts - NEW for 2.6 enterprise topology
# -----------------------------------------------------
[redis]
gateway1.example.org
gateway2.example.org
hub1.example.org
hub2.example.org
eda1.example.org
eda2.example.org
[all:vars]
# Common variables from your 2.4 inventory
# https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.6/html/rpm_installation/appendix-inventory-files-vars#general-variables
# -----------------------------------------------------
registry_username=<your RHN username>
registry_password=<your RHN password>
# Platform gateway - NEW for 2.6 enterprise topology
# https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.6/html/rpm_installation/appendix-inventory-files-vars#platform-gateway-variables
# -----------------------------------------------------
automationgateway_admin_password=<set your own>
automationgateway_main_url=<set your own> #Set to the URL of the load balancer
automationgateway_pg_host=<set your own>
automationgateway_pg_database=<set your own>
automationgateway_pg_username=<set your own>
automationgateway_pg_password=<set your own>
# Automation controller variables from your 2.4 inventory
# https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.6/html/rpm_installation/appendix-inventory-files-vars#controller-variables
# -----------------------------------------------------
admin_password=<set your own>
pg_host=<set your own>
pg_database=<set your own>
pg_username=<set your own>
pg_password=<set your own>
# Automation hub - NEW for 2.6 enterprise topology
# https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.6/html/rpm_installation/appendix-inventory-files-vars#hub-variables
# -----------------------------------------------------
automationhub_admin_password=<set your own>
automationhub_pg_host=<set your own>
automationhub_pg_database=<set your own>
automationhub_pg_username=<set your own>
automationhub_pg_password=<set your own>
# Event-Driven Ansible - NEW for 2.6 enterprise topology
# https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.6/html/rpm_installation/appendix-inventory-files-vars#event-driven-ansible-variables
# -----------------------------------------------------
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>4.1.4. Upgrading a 2.4 multi node automation controller and automation hub deployment to a 2.6 enterprise topology
You can upgrade your 2.4 multi node automation controller and automation hub deployment to a 2.6 enterprise topology. This section outlines the infrastructure changes, requirements, and an example inventory for upgrading.
4.1.4.1. 2.4 infrastructure topology diagram
This diagram outlines the 2.4 infrastructure topology that Red Hat has tested with this deployment model.
Figure 4.7. 2.4 infrastructure topology diagram
4.1.4.2. 2.6 infrastructure topology diagram
This diagram outlines the 2.6 infrastructure topology that Red Hat has tested with this deployment model.
Figure 4.8. 2.6 infrastructure topology diagram
4.1.4.3. Requirements for upgrading a multi automation controller node and automation hub deployment
The following table highlights the requirements for upgrading from Ansible Automation Platform version 2.4 to 2.6.
| Existing 2.4 topology | Tested 2.6 topology | Requirements for each VM |
|---|---|---|
| Redundant deployment with automation controller and automation hub:
| Enterprise topology:
Note: Redis high availability requires 6 VMs. Redis can be colocated with automation hub, platform gateway, or Event-Driven Ansible components, but it cannot be colocated with automation controller, execution nodes, or the PostgreSQL database. | See the RPM enterprise topology section of the Tested deployment models guide. |
4.1.4.4. Example inventory file
The following inventory file has been updated with the necessary changes to upgrade to the 2.6 enterprise topology.
If your 2.4 inventory file uses automationhub_main_url for a load balancer, you must remove this variable from your 2.6 inventory file. The load balancer is now expected to be configured in front of platform gateway (automationgateway_main_url).
# This is the RPM-based Ansible Automation Platform installer inventory file intended for upgrading from a 2.4 multi node automation controller and automation hub deployment to a 2.6 enterprise deployment.
# For all optional variables consult the Red Hat documentation:
# https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.6/html/rpm_installation
# This section is for your platform gateway hosts - NEW for 2.6 enterprise topology
# -----------------------------------------------------
[automationgateway]
gateway1.example.org
gateway2.example.org
# This section is for your automation controller hosts from your 2.4 inventory
# -----------------------------------------------------
[automationcontroller]
controller1.example.org
controller2.example.org
[automationcontroller:vars]
peers=execution_nodes
# This section is for your execution hosts from your 2.4 inventory
# -----------------------------------------------------
[execution_nodes]
hop1.example.org node_type='hop'
exec1.example.org
exec2.example.org
# This section is for your automation hub hosts from your 2.4 inventory
# -----------------------------------------------------
[automationhub]
hub1.example.org
hub2.example.org
# This section is for your Event-Driven Ansible hosts - NEW for 2.6 enterprise topology
# -----------------------------------------------------
[automationedacontroller]
eda1.example.org
eda2.example.org
# This section is for your Redis hosts - NEW for 2.6 enterprise topology
# -----------------------------------------------------
[redis]
gateway1.example.org
gateway2.example.org
hub1.example.org
hub2.example.org
eda1.example.org
eda2.example.org
[all:vars]
# Common variables from your 2.4 inventory
# https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.6/html/rpm_installation/appendix-inventory-files-vars#general-variables
# -----------------------------------------------------
registry_username=<your RHN username>
registry_password=<your RHN password>
# Platform gateway - NEW for 2.6 enterprise topology
# https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.6/html/rpm_installation/appendix-inventory-files-vars#platform-gateway-variables
# -----------------------------------------------------
automationgateway_admin_password=<set your own>
automationgateway_main_url=<set your own> #Set to the URL of the load balancer
automationgateway_pg_host=<set your own>
automationgateway_pg_database=<set your own>
automationgateway_pg_username=<set your own>
automationgateway_pg_password=<set your own>
# Automation controller variables from your 2.4 inventory
# https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.6/html/rpm_installation/appendix-inventory-files-vars#controller-variables
# -----------------------------------------------------
admin_password=<set your own>
pg_host=<set your own>
pg_database=<set your own>
pg_username=<set your own>
pg_password=<set your own>
# Automation hub variables from your 2.4 inventory
# https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.6/html/rpm_installation/appendix-inventory-files-vars#hub-variables
# -----------------------------------------------------
automationhub_admin_password=<set your own>
automationhub_pg_host=<set your own>
automationhub_pg_database=<set your own>
automationhub_pg_username=<set your own>
automationhub_pg_password=<set your own>
# This variable is no longer used for load balancer configuration in 2.6:
# automationhub_main_url=<set your own>
# Event-Driven Ansible - NEW for 2.6 enterprise topology
# https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.6/html/rpm_installation/appendix-inventory-files-vars#event-driven-ansible-variables
# -----------------------------------------------------
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>4.1.5. Upgrading a 2.5 growth topology to a 2.6 growth topology
You can upgrade your 2.5 RPM-based growth topology to a 2.6 RPM-based growth topology. The topologies are the same between Ansible Automation Platform 2.5 and 2.6.
For more information about the growth topology infrastructure requirements and configuration details, see the RPM growth topology section of Tested deployment models.
4.1.6. Upgrading a 2.5 enterprise topology to a 2.6 enterprise topology
You can upgrade your 2.5 RPM-based enterprise topology to a 2.6 RPM-based enterprise topology. The topologies are the same between Ansible Automation Platform 2.5 and 2.6.
For more information about the enterprise topology infrastructure requirements and configuration details, see the RPM enterprise topology section of Tested deployment models.
4.2. Container-based deployments
Container-based deployments require specific infrastructure changes during upgrade. For step-by-step upgrade instructions, see Upgrading containerized Ansible Automation Platform.
Upgrades from Containerized Ansible Automation Platform 2.4 to 2.6 are not supported.
4.2.1. Upgrading a 2.5 growth topology to a 2.6 growth topology
You can upgrade your 2.5 container-based growth topology to a 2.6 container-based growth topology. The topologies are the same between Ansible Automation Platform 2.5 and 2.6.
For more information about the growth topology infrastructure requirements and configuration details, see the Container growth topology section of Tested deployment models.
4.2.2. Upgrading a 2.5 enterprise topology to a 2.6 enterprise topology
You can upgrade your 2.5 container-based enterprise topology to a 2.6 container-based enterprise topology. The topologies are the same between Ansible Automation Platform 2.5 and 2.6.
For more information about the enterprise topology infrastructure requirements and configuration details, see the Container enterprise topology section of Tested deployment models.
4.3. Operator-based deployments
The following sections describe the tested infrastructure changes for Operator-based deployments. For step-by-step upgrade instructions, see Upgrading Red Hat Ansible Automation Platform Operator on Red Hat OpenShift Container Platform.
4.3.1. Upgrading a 2.4 single automation controller node deployment to a 2.6 growth topology
Plan your upgrade from a 2.4 single automation controller node setup to a 2.6 growth topology. Review the required infrastructure changes and requirements for a successful upgrade.
4.3.1.1. 2.4 infrastructure topology diagram
This diagram outlines the 2.4 infrastructure topology for this deployment model.
Figure 4.9. 2.4 infrastructure topology diagram
4.3.1.2. 2.6 infrastructure topology diagram
This diagram outlines the 2.6 infrastructure topology that Red Hat has tested with this deployment model.
Figure 4.10. 2.6 infrastructure topology diagram
4.3.1.3. Requirements for upgrading a single automation controller node deployment
The following table highlights the requirements for upgrading from Ansible Automation Platform 2.4 to 2.6.
| Existing 2.4 topology | Tested 2.6 topology | Requirements for each pod |
|---|---|---|
| Non-redundant automation controller-only deployment:
| Growth topology:
| See the Operator growth topology section of the Tested deployment models guide. |
4.3.2. Upgrading a 2.4 single automation controller and automation hub deployment to a 2.6 growth topology
Upgrade your 2.4 single-node deployment (automation controller and automation hub) to a 2.6 growth topology. Review the infrastructure changes and requirements needed to successfully plan your upgrade.
4.3.2.1. 2.4 infrastructure topology diagram
This diagram outlines the 2.4 infrastructure topology for this deployment model.
Figure 4.11. 2.4 infrastructure topology diagram
4.3.2.2. 2.6 infrastructure topology diagram
This diagram outlines the 2.6 infrastructure topology that Red Hat has tested with this deployment model.
Figure 4.12. 2.6 infrastructure topology diagram
4.3.2.3. Requirements for upgrading a single automation controller and automation hub deployment
The following table highlights the requirements for upgrading from Ansible Automation Platform 2.4 to 2.6.
| Existing 2.4 topology | Tested 2.6 topology | Requirements for each pod |
|---|---|---|
| Non-redundant automation controller and automation hub deployment:
| Growth topology:
| See the Operator growth topology section of the Tested deployment models guide. |
4.3.3. Upgrading a 2.4 multi node automation controller deployment to a 2.6 enterprise topology
Upgrade your 2.4 multi-node automation controller setup to a 2.6 enterprise topology. Review the required infrastructure changes and requirements needed to successfully plan the upgrade.
4.3.3.1. 2.4 infrastructure topology diagram
This diagram outlines the 2.4 infrastructure topology for this deployment model.
Figure 4.13. 2.4 infrastructure topology diagram
4.3.3.2. 2.6 infrastructure topology diagram
This diagram outlines the 2.6 infrastructure topology that Red Hat has tested with this deployment model.
Figure 4.14. 2.6 infrastructure topology diagram
4.3.3.3. Requirements for upgrading a multi node automation controller deployment on OpenShift Container Platform
The following table highlights the requirements for upgrading from Ansible Automation Platform 2.4 to 2.6.
| Existing 2.4 topology | Tested 2.6 topology | Requirements for each pod |
|---|---|---|
| Redundant automation controller-only deployment:
| Enterprise topology:
| See the Operator enterprise topology section of the Tested deployment models guide. |
4.3.4. Upgrading a 2.4 multi node automation controller and automation hub deployment to a 2.6 enterprise topology
Upgrade your 2.4 multi-node deployment (automation controller and automation hub) to a 2.6 enterprise topology. Review the infrastructure changes and requirements needed to successfully plan your upgrade.
4.3.4.1. 2.4 infrastructure topology diagram
This diagram outlines the 2.4 infrastructure topology for this deployment model.
Figure 4.15. 2.4 infrastructure topology diagram
4.3.4.2. 2.6 infrastructure topology diagram
This diagram outlines the 2.6 infrastructure topology that Red Hat has tested with this deployment model.
Figure 4.16. 2.6 infrastructure topology diagram
4.3.4.3. Requirements for upgrading a multi node automation controller and automation hub deployment
The following table highlights the requirements for upgrading from Ansible Automation Platform 2.4 to 2.6.
| Existing 2.4 topology | Tested 2.6 topology | Requirements for each pod |
|---|---|---|
| Redundant deployment with automation controller and automation hub:
| Enterprise topology:
| See the Operator enterprise topology section of the Tested deployment models guide. |
4.3.5. Upgrading a 2.5 growth topology to a 2.6 growth topology
You can upgrade your 2.5 growth topology to a 2.6 growth topology on OpenShift Container Platform. The topologies are the same between Ansible Automation Platform 2.5 and 2.6.
For more information about the growth topology infrastructure requirements and configuration details, see the Operator growth topology section of Tested deployment models.
4.3.6. Upgrading a 2.5 enterprise topology to a 2.6 enterprise topology
You can upgrade your 2.5 enterprise topology to a 2.6 enterprise topology on OpenShift Container Platform. The topologies are the same between Ansible Automation Platform 2.5 and 2.6.
For more information about the enterprise topology infrastructure requirements and configuration details, see the Operator enterprise topology section of Tested deployment models.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}