Upgrading Automation Node Tiers for AAP on Azure
A guide for transitioning Managed Applications to higher node counting tiers.
Overview
This document outlines the mandatory process for migrating an existing Red Hat Ansible Automation Platform (AAP) on Microsoft Azure deployment to a higher node tier. Due to architectural constraints, this requires a new instance deployment rather than an in-place upgrade. This guide details the collaboration between the Customer and Site Reliability Engineering (SRE) to ensure successful data migration within a 48-hour window.
CRITICAL ARCHITECTURE NOTICE
In-Place Upgrades Are Not Possible
Due to the platform's architectural reliance on single-instance billing models, you cannot perform an in-place upgrade. Transitioning to a different tier requires the deployment of a new, separate instance of the managed application.
1. Prerequisites & Planning
Complete the following planning steps before initiating deployment.
-
Private Offer Acceptance
The Account Team must issue a private offer for the desired tier. You must accept this offer prior to deployment. -
Plan a 48-Hour Transition Window
Schedule a 48-hour window to deploy, migrate data, and test.- Note: This timeframe is critical. You will hold licenses for both environments during this time; completing the transition quickly prevents extended simultaneous billing charges.
-
Security Access
Ensure a local administrator user account is configured in your current (source) environment to facilitate SRE access during the migration. -
Halt Operations
To prevent data inconsistency, stop any automation currently running on the existing (source) site before the migration begins.
Network Architecture Strategy
Determine the networking requirements for the new deployment. You may choose to keep the original network settings (CIDR ranges, etc.) to minimize configuration issues.
Warning: Network Configuration Immutability
Network configurations (such as CIDR ranges) cannot be changed after the deployment is complete. Verify these parameters carefully before deploying.
2. Step-by-Step Migration Process
The following table outlines the sequential actions required.
| Seq | Owner | Action Item |
|---|---|---|
| 01 | Customer | Deploy New Instance At the start of the planned 48-hour window, deploy the new AAP on Azure instance ensuring the correct tier plan is selected. |
| 02 | Customer | Initiate Migration Ticket Submit a support request (ticket) to the SRE team formally requesting migration assistance. (See Template in Section 3). |
| 03 | Customer | Confirm Readiness Customers are responsible for initiating the communication by updating the support ticket they opened in Sequence 3. This message confirms that the newly deployed target environment is active and configured with all necessary Azure dependencies. The SRE Team must then respond to the ticket to acknowledge this confirmation. |
| 04 | SRE Team | Migrate Content The SRE team will proceed with migrating content from the old site to the new site. |
| 05 | SRE Team | Confirm Completion The SRE team will notify you via the ticket that the content migration is complete. |
| 06 | Customer | Update DNS Reconfigure custom DNS settings (if applicable) to point to the new deployment. |
| 07 | Customer | Validate Environment Test the configuration of the new site to validate successful migration and operational functionality. |
| 08 | Customer | Configure Azure Dependencies Configure network peering, route tables (including managed application route tables), and other Azure dependencies for the new environment using the planned networking values. |
| 09 | Customer | Reconfigure SSO If applicable, reconfigure Single Sign-On (SSO). Update your Identity Provider (IdP) with the new environment's URL. |
| 10 | Customer | Decommission Once the new environment is fully validated and operational, remove/delete the old environment to cease billing for the previous tier. |
3. Support Ticket Template
Please use the following template when submitting your request (Step 02).
Severity: 2
Subject: Request for AAP on Azure Tier Upgrade Migration
Dear SRE Team,
This ticket serves as a request to initiate the data migration process as part of our
Red Hat Ansible Automation Platform (AAP) on Microsoft Azure managed application tier upgrade.
We have completed the initial deployment and configuration steps and require your
assistance for content migration.
Migration Details:
Source Environment: [Insert Current AAP on Azure URL/Name]
Target Environment: [Insert New AAP on Azure URL/Name]
Target Tier: [Specify the new, higher node tier]
Maintenance Window: [Start Date/Time] to [End Date/Time] (Planned 48-hour window)