Chapter 8. Migrating Red Hat Ansible Automation Platform to Red Hat Ansible Automation Platform Operator

Procedure

1. Locate the old secret keys in the inventory file you used to deploy Ansible Automation Platform in your previous installation.

2. Create a YAML file for your secret keys:

   ---
   apiVersion: v1
   kind: Secret
   metadata:
     name: <controller-resourcename>-secret-key
     namespace: <target-namespace>
   stringData:
     secret_key: <replaceme-with-controller-secret>
   type: Opaque
   ---
   apiVersion: v1
   kind: Secret
   metadata:
     name: <eda-resourcename>-secret-key
     namespace: <target-namespace>
   stringData:
     secret_key: <replaceme-with-eda-secret>
   type: Opaque
   ---
   apiVersion: v1
   kind: Secret
   metadata:
     name: <hub-resourcename>-secret-key
     namespace: <target-namespace>
   stringData:
     database_fields.symmetric.key: <replace-me-withdb-fields-encryption-key>
   type: Opaque

   Copy to Clipboard Toggle word wrap
   Note

   If admin_password_secret is not provided, the operator looks for a secret named <resourcename>-admin-password for the admin password. If it is not present, the operator generates a password and create a secret from it named <resourcename>-admin-password.

3. Apply the secret key YAML to the cluster:

   oc apply -f <yaml-file>

   Copy to Clipboard Toggle word wrap

Procedure

1. Create a yaml file for your postgresql configuration secret:

   apiVersion: v1
   kind: Secret
   metadata:
     name: <resourcename>-old-postgres-configuration
     namespace: <target namespace>
   stringData:
     host: "<external ip or url resolvable by the cluster>"
     port: "<external port, this usually defaults to 5432>"
     database: "<desired database name>"
     username: "<username to connect as>"
     password: "<password to connect with>"
   type: Opaque

   Copy to Clipboard Toggle word wrap
2. Apply the postgresql configuration yaml to the cluster:

Procedure

1. Create a yaml file to verify the connection between your new deployment and your old deployment database:

   apiVersion: v1
   kind: Pod
   metadata:
       name: dbchecker
   spec:
     containers:
       - name: dbchecker
         image: registry.redhat.io/rhel8/postgresql-13:latest
         command: ["sleep"]
         args: ["600"]

   Copy to Clipboard Toggle word wrap

2. Apply the connection checker yaml file to your new project deployment:

   oc project ansible-automation-platform
   oc apply -f connection_checker.yaml

   Copy to Clipboard Toggle word wrap

3. Verify that the connection checker pod is running:

   oc get pods

   Copy to Clipboard Toggle word wrap

4. Connect to a pod shell:

   oc rsh dbchecker

   Copy to Clipboard Toggle word wrap

5. After the shell session opens in the pod, verify that the new project can connect to your old project cluster:

   pg_isready -h <old-host-address> -p <old-port-number> -U awx

   Copy to Clipboard Toggle word wrap

   Example

   <old-host-address>:<old-port-number> - accepting connections

   Copy to Clipboard Toggle word wrap

Procedure

1. Log in to Red Hat OpenShift Container Platform.
2. Navigate to Operators Installed Operators.
3. Select the Ansible Automation Platform Operator installed on your project namespace.
4. Select the Automation Controller tab.

5. Click Create AutomationController. You can create the object through the Form view or YAML view. The following inputs are available through the Form view.

   1. Enter a name for the new deployment.

   2. In Advanced configurations:

      1. From the Secret Key list, select your secret key secret.
      2. From the Old Database Configuration Secret list, select the old postgres configuration secret.
   3. Click Create.

Procedure

1. Log in to Red Hat OpenShift Container Platform.
2. Navigate to Operators Installed Operators.
3. Select the Ansible Automation Platform Operator installed on your project namespace.
4. Select the Automation Hub tab.
5. Click Create AutomationHub.
6. Enter a name for the new deployment.
7. In Advanced configurations, select your secret key secret and postgres configuration secret.
8. Click Create.

Procedure

1. Log in to Red Hat Ansible Automation Platform as the administrator with the password you created during migration.

   Note

   Note: If you did not create an administrator password during migration, one was automatically created for you. To locate this password, go to your project, select Workloads Secrets and open controller-admin-password. From there you can copy the password and paste it into the Red Hat Ansible Automation Platform password field.

2. Select Administration Instance Groups.
3. Select all Instance Groups except controlplane and default.
4. Click Delete.

1. Log in to Red Hat OpenShift Container Platform.
2. Navigate to Operators Installed Operators.
3. Select the Ansible Automation Platform Operator installed on your project namespace.
4. Select the Automation Controller tab.
5. Click your AutomationController object. You can then view the object through the Form view or YAML view. The following inputs are available through the YAML view.
6. Locate the old_postgres_configuration_secret item within the spec section of the YAML contents.
7. Delete the line that contains this item.
8. Click Save.