Infrastructure changes for RPM deployments
The following sections describe the tested infrastructure changes for RPM-based deployments.
- 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. - 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. - 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. - 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. - 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. - 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.