Prepare to migrate to Managed Ansible Automation Platform

Prepare and migrate your source environment to a Managed Ansible Automation Platform deployment, and reconcile the target environment post-migration.

Migrate to Managed Ansible Automation Platform

Submit a support ticket on the Red Hat Customer Portal to request a migration to Managed Ansible Automation Platform.

Before you begin

  • You have a migration artifact from your source environment.
  • Your source deployment is on the same major version as the Managed Ansible Automation Platform offering and on the latest async/patch release of that version.

    For example, if Managed Ansible Automation Platform is running 2.7, your source must be on Ansible Automation Platform 2.7.x (latest patch).

    Check the current Managed Ansible Automation Platform version 2.7 This content is not included.Release notes

Procedure

  1. Submit a This content is not included.support ticket on the Red Hat Customer Portal requesting a migration to Managed Ansible Automation Platform.

    The support ticket should include:

    • Source installation type (RPM, Containerized, OpenShift)
    • Managed Ansible Automation Platform URL or deployment name
    • Source version (installation program or Operator version)
  2. The Ansible Site Reliability Engineering (SRE) team provides instructions in the support ticket on how to upload the resulting migration artifact to secure storage for processing.
  3. The Ansible SRE team imports the migration artifact into the identified target instance and notifies the customer through the support ticket.
  4. The Ansible SRE team notifies customers of successful migration.

Reconcile the target environment post-migration

Update necessary configurations after migrating to Managed Ansible Automation Platform.

Procedure

  1. Log in to the Managed Ansible Automation Platform instance by using the local administrator account to confirm that data was imported.
  2. Perform the following actions based on the configuration of the source deployment:
    1. Reconfigure Single Sign-On (SSO) authenticators and mappings to reflect the new URLs.
    2. Update private automation hub content to reflect the new URLs.
      1. Run the following command to update the automation hub repositories: 
        curl -d '{\"verify_checksums\": true }' -X POST -k https://<platform url>/api/galaxy/pulp/api/v3/repair/ -u <admin_user>:<admin_password>
      2. Perform a sync on any repositories configured in automation hub.
      3. Push any custom execution environments from the source automation hub to the target automation hub.
    3. Reconfigure automation mesh.
  3. After migration, you can request standard Site Reliability Engineering (SRE) tasks through support tickets, such as configuration of custom certificates, a custom domain, or connectivity through private endpoints.