Ce contenu n'est pas disponible dans la langue sélectionnée.
Chapter 7. Installing automation hub
With the installation of the Ansible Automation Platform operator completed, the following steps install automation hub within a Red Hat OpenShift cluster.
The resource requests and limits values are specific to this reference environment. Ensure to read the Chapter 3, Before you start section to properly calculate the values for your Red Hat OpenShift environment.
When an instance of automation hub is removed, the associated Persistent Volume Claims (PVCs) are not automatically deleted. This can cause issues during migration if the new deployment has the same name as the previous deployment. It is recommended to remove old PVCs prior to deploying a new automation hub instance in the same namespace. The steps to remove previous deployment PVCs can be found within Appendix B, Delete existing PVCs from previous AAP installations.
Automation hub requires ReadWriteMany file-based storage, Azure Blob storage or Amazon S3-compliant storage for operation to ensure multiple pods can access shared content, such as collections.
- Log in to the Red Hat OpenShift web console using your cluster credentials.
-
In the left-hand navigation menu, select Operators
Installed Operators, select Ansible Automation Platform. - Navigate to the Automation Hub tab, then click Create AutomationHub.
Within the Form view
- provide a Name, e.g. my-automation-hub
Within the Storage type, select your
ReadWriteManycompliant storage.NoteThis reference environment uses Amazon S3 as its
ReadWriteManystorage. Details to create an Amazon S3 bucket can be found in Appendix D, Create an Amazon S3 bucket.- Provide S3 storage secret. Details on how to create within Appendix E, Creating an AWS S3 Secret.
- Select the Advanced configuration to expand the additional options.
Within PostgreSQL container storage requirements (when using a managed instance)
- set storage limit to 50Gi
- set storage requests to 8Gi
Within PostgreSQL container resource requirements (when using a managed instance)
- Limits: CPU cores: 500m, Memory: 1Gi
- Requests: CPU cores: 200m, Memory: 1Gi
Within Redis deployment configuration, select Advanced configuration
Select In-memory data store resource requirements
- Limits: CPU cores: 250m, Memory: 200Mi
- Requests: CPU cores: 100m, Memory: 200Mi
Within API server configuration, select Advanced configuration
Select API server resource requirements
- Limits: CPU cores: 250m, Memory: 400Mi
- Requests: CPU cores: 150m, Memory: 400Mi
Within Content server configuration, select Advanced configuration
Select Content server resource requirements
- Limits: CPU cores: 250m, Memory: 400Mi
- Requests: CPU cores: 100m, Memory: 400Mi
Within Worker configuration, select Advanced configuration
Select Worker resource requirements
- Limits: CPU cores: 1000m, Memory: 3Gi
- Requests: CPU cores: 500m, Memory: 3Gi
- Click the Create button
