红帽全球峰会2.2. Installing automation controller with an external managed database
You can use these instructions to install a standalone automation controller server on a single machine configured to communicate with a remote PostgreSQL instance as its database. This remote PostgreSQL can be a server you manage, or can be provided by a cloud service such as Amazon RDS.
2.2.1. Prerequisites
- You chose and obtained a platform installer
- You are installing on a machine that meets base system requirements.
You can use the Red Hat Ansible Automation Platform installer inventory file to specify your installation scenario.
- Using external databases: ensure the database sections of your inventory file are properly setup.
-
Add automation hub information in the
[automationhub]group - automation hub and automation controller cannot be installed on the same node.
- automation controller will not configure replication or failover for the database that it uses. automation controller should work with any replication you have.
- The database server should be on the same network or in the same data center as the automation controller server for performance reasons.
- For upgrading an existing cluster: When upgrading a cluster, you may decide that you want to also reconfigure your cluster to omit existing instances or instance groups. Omitting the instance or the instance group from the inventory file will not be enough to remove them from the cluster. In addition to omitting instances or instance groups from the inventory file, you must also deprovision instances or instance groups before starting the upgrade. Otherwise, omitted instances or instance groups will continue to communicate with the cluster, which can cause issues with tower services during the upgrade.
-
For clustered installations: If you are creating a clustered setup, you must replace
localhostwith the hostname or IP address of all instances. All nodes/instances must be able to reach any others using this hostname or address. In other words, you cannot use thelocalhost ansible_connection=localon one of the nodes AND all of the nodes should use the same format for the host names.
- Root access to remote machines is required. With Ansible, this can be achieved in different ways:
-
ansible_user=root ansible_ssh_pass=”your_password_here”inventory host or group variables -
ansible_user=root ansible_ssh_private_key_file=”path_to_your_keyfile.pem”inventory host or group variables -
ANSIBLE_BECOME_METHOD=’sudo’ ANSIBLE_BECOME=True ./setup.sh
For more information on become plugins, see Understanding privilege escalation.
Procedure
Navigate to the installer
[bundled installer]
$ cd ansible-automation-platform-setup-bundle-<latest-version>[online installer]
$ cd ansible-automation-platform-setup-<latest-version>
-
Open the
inventoryfile with a text editor. -
Edit
inventoryfile parameters to specify your installation scenario. Follow the example below.
This example describes how you can populate the inventory file to deploy an installation of automation controller with an external database.
Do not use special characters for pg_password. It may cause the setup to fail.
[automationcontroller]
127.0.0.1 ansible_connection=local
[database]
database.example.com
[all:vars]
admin_password='password'
pg_password='password'
pg_host='database.example.com'
pg_port='5432'
pg_database='awx'
pg_username='awx'2.2.4. Flags and extra vars
You can pass flags and extra variables when installing automation controller.
:
| Argument | Description |
|---|---|
|
| Show this help message and exit |
|
|
Path to Ansible inventory file (default: |
|
| Set additional Ansible variables as key=value or YAML/JSON |
|
| Perform a database backup in lieu of installing |
|
| Perform a database restore in lieu of installing |
|
| Generate and dsitribute a SECRET_KEY |
Use the -- separator to add any Ansible arguments you wish to apply. For example: ./setup.sh -i my_awesome_inventory.yml -e matburt_is_country_gold=True — -K.
When passing
-rto perform a database restore default restore path is used unless EXTRA_VARS are provided with a non-default path. See the example below that passed an EXTRA_VAR specifying the restore path:./setup.sh -e 'restore_backup_file=/path/to/nondefault/location' -rYou can force an online installation by passing
-e bundle_install=false:$ ./setup.sh -e bundle_install=false
| Variable | Description | Default |
|---|---|---|
|
| When installing automation controller make sure Ansible is also up to date |
|
|
| When installing Tower also create the Demo Org, project, credential, Job Template, etc. |
|
|
| When installing from a bundle where to put the bundled repos |
|
|
| Disable HTTPS traffic through nginx, this is useful if offloading HTTPS to a load balancer |
|
|
| Disable HSTS web-security policy mechanism |
|
|
| Port to configure nginx to listen to for HTTP |
|
|
| Port to configure nginx to listen to for HTTPS |
|
|
| A temp location to use when backing up |
|
|
| Specify an alternative backup file to restore from | None |
|
| The minimum RAM required to install Tower (should only be changed for test installation) |
|
|
| The minimum open file descriptions (should only be changed for test installations) | None |
|
|
Ignore preflight checks, useful when installing into a template or other non-system image (overrides |
|
Examples
- To upgrade core:
./setup.sh -e upgrade_ansible_with_tower=1- To disable https handling at nginx:
./setup.sh -e nginx_disable_https=true- To specify a non-default path when restoring from a backup file:
./setup.sh -e 'restore_backup_file=/path/to/nondefault/location' -r*
To override an inventory file used by passing it as an argument to the setup script:
You can run the setup script once you finish updating the inventory file with required parameters for installing your Private Automation Hub.
Procedure
Run the
setup.shscript$ ./setup.sh
The installation will begin.
2.2.6. Verifying automation controller installation
Once the installation completes, you can verify your automation controller has been installed successfully by logging in with the admin credentials you inserted into the inventory file.
Procedure
-
Navigate to the IP address specified for the automation controller node in the
inventoryfile. -
Log in with the Admin credentials you set in the
inventoryfile.
The automation controller server is accessible from port 80 (https://<TOWER_SERVER_NAME>/) but will redirect to port 443 so 443 needs to be available also.
If the installation fails and you are a customer who has purchased a valid license for Red Hat Ansible Automation Platform, please contact Ansible via the Red Hat Customer portal at https://access.redhat.com/.
Your automation controller is now ready for initial configuration.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}