Installing Ansible Automation Platform self-service technology preview

Open your Ansible Automation Platform instance in a browser and log in.

Navigate to Access Management › OAuth Applications.

Click Create OAuth Application.

Complete the fields in the form.

Click Create OAuth application.

Copy the clientId and clientSecret values and save them.

Log in to your instance of Ansible Automation Platform as the admin user.

Navigate to Access Management › Users.

Select the admin user.

Select the Tokens tab

Click Create Token.

Select your OAuth application. In the Scope menu, select Write.

Click Create Token to generate the token.

Save the new token.

You have created a project for self-service technology preview in OpenShift.

You have created a plugin registry in your project.

You have set up secrets for Ansible Automation Platform authentication and SCM authentication.

In a browser, navigate to your OpenShift project for self-service technology preview that you created earlier.

Select the Developer view.

Click the Helm option in the OpenShift sidebar.

In the Helm page, click Create and select Helm Release.

Search for AAP in the Helm Charts filter, and select the AAP Technical Preview: Self-service automation chart.

In the modal dialog on the chart page, click Create.

Select the YAML view in the Create Helm Release page.

Locate the clusterRouterBase key in the YAML file and replace the placeholder value with the base URL of your OpenShift instance.

  redhat-developer-hub
    global:
      clusterRouterBase: apps.example.com

The Helm chart is set up for the Default Ansible Automation Platform organization.

Click Create to launch the deployment.

In a browser, log in to your OpenShift instance.

In the Developer view, navigate to the Topology view for the namespace where you deployed the Helm chart.

Check the Helm release status:

$ helm list -n ${MY_NAMESPACE}

Monitor the pods in your namespace to ensure they are running:

$ oc get pods -n ${MY_NAMESPACE}

Check for ImagePullBackOff or other errors in pod events:

$ oc describe pod <pod_name> -n ${MY_NAMESPACE}

If the chart uses routes to expose services, verify that the routes are created and accessible:

$ oc get route -n ${MY_NAMESPACE}

In a browser, log in to your OpenShift instance.

In the Developer view, navigate to the Topology view for the namespace where you deployed the Helm chart.

The deployment appears: the label on the icon is D.

Click the icon representing the deployment.

The Details pane for the deployment opens.

Select the Resources tab.

Click View logs for the deployment pod in the Pods section:

Select the Logs tab in the Pod details page.

To view the install messages, select the install-dynamic-plugins container from the INIT CONTAINERS section of the dropdown list of containers:

 ======= Installing dynamic plugin http://plugin-registry:8080/ansible-backstage-plugin-catalog-backend-module-rhaap-dynamic-0.1.0.tgz
 *=> Grabbing package archive through pm pack'
 •=› Vertfying package Integrity
 •*> Extracting package archtve /dynamtc-plugtns-root/anstble-backstage-plugtn-catalog-backend-nodule-rhaap-dynamic-0.1.0.tgz
 •*› Removing package archive /dynamic-plugins-root/ansible-backstage-plugin-catalog-backend-module-rhaap-dynamic-0.1.0. tgz
 -> Successfully installed dynamic plugin http://plugin-registry:8080/ansible-backstage-plugin-catalog-backend-module-rhaap-dynamic-0.1.0.tgz

Select the Environment tab in the Pod details page to view the environment variables for the containers. If you set additional environment variables in your Helm chart, check that they are listed here.

In a browser, open the project for your self-service technology preview in your OpenShift instance.

In the Developer view, select ConfigMaps in the navigation pane.

Select the <installation-name>-backstage-app-config ConfigMap, for example my-aap-self-service-tech-preview-backstage-app-config.

Verify that the ConfigMap conforms with the values you updated in the Helm chart.

Return to the list of ConfigMaps and select the <installation-name>-dynamic-plugins ConfigMap, for example my-aap-self-service-tech-preview-dynamic-plugins.

Verify that the ConfigMap conforms with the expected plugin values.

Determine the Redirect URI from your OpenShift deployment:

Update the Redirect URIs field in the OAuth application in Ansible Automation Platform:

You have configured an OAuth application in Ansible Automation Platform for self-service technology preview.

You have configured a user account in Ansible Automation Platform.

In a browser, navigate to the URL for self-service technology preview to open the sign-in page.

Click Sign In.

The sign-in page for Ansible Automation Platform appears:

Enter your Ansible Automation Platform credentials and click Log in.

The self-service technology preview UI opens.

Click Templates to open a landing page where tiles are displayed, representing templates. When the page is populated with templates, the layout resembles the following screenshot:

Log in to the OpenShift Container Platform console and open the project for self-service technology preview in the Developer perspective.

Navigate to Helm.

Click the More actions ⋮ icon for your self-service technology preview Helm chart and select Upgrade.

Select YAML view.

Locate the redhat-developer-hub.global.dynamic.plugins section of the Helm chart.

To disable telemetry data collection, add the following lines to the redhat-developer-hub.global.dynamic.plugins section.

redhat-developer-hub:
  global:
    ....
    dynamic:
      plugins:
        - disabled: true
          package: >-
            ./dynamic-plugins/dist/backstage-community-plugin-analytics-provider-segment

Click Upgrade to apply the changes to the Helm chart and restart the pod.