Chapter 5. Advanced containerized deployment

Procedure

1. Ensure your AWS S3 bucket exists before proceeding with the installation.

2. Add the following variables to your inventory file under the [all:vars] group to configure S3 storage:

   [all:vars]
   hub_storage_backend=s3
   hub_s3_access_key=<access_key>
   hub_s3_secret_key=<secret_key>
   hub_s3_bucket_name=<bucket_name>

3. Optional: You can pass extra parameters to the AWS S3 storage backend by using the hub_s3_extra_settings variable. For example:

   hub_s3_extra_settings={'AWS_S3_REGION_NAME': 'eu-south-1', 'AWS_S3_ENDPOINT_URL': 'https://endpoint'}

Procedure

1. Ensure your Azure container exists before proceeding with the installation.

2. Add the following variables to your inventory file under the [all:vars] group to configure Azure Blob storage:

   [all:vars]
   hub_storage_backend=azure
   hub_azure_account_key=<account_key>
   hub_azure_account_name=<account_name>
   hub_azure_container=<container_name>

3. Optional: You can pass extra parameters to the Azure Blob storage backend by using the hub_azure_extra_settings variable. For example:

   hub_azure_extra_settings={'AZURE_LOCATION': 'foo', 'AZURE_SSL': True, 'AZURE_URL_EXPIRATION_SECS': 60}

Procedure

1. To configure shared storage for automation hub, set the hub_shared_data_path variable in your inventory file:

   hub_shared_data_path=<path_to_nfs_share>

   The value must match the format host:dir, for example nfs-server.example.com:/exports/hub.

2. (Optional) To change the mount options for your NFS share, use the hub_shared_data_mount_opts variable. The default value is rw,sync,hard.

Procedure

1. Connect to a PostgreSQL compliant database server with a user that has SUPERUSER privileges.

   # psql -h <hostname> -U <username> -p <port_number>

   For example:

   # psql -h db.example.com -U superuser -p 5432

2. Create the user with a password and ensure the CREATEDB role is assigned to the user. For more information, see Database Roles.

   CREATE USER <username> WITH PASSWORD <password> CREATEDB;

3. Create the database and add the user you created as the owner.

   CREATE DATABASE <database_name> OWNER <username>;

4. When you have created the PostgreSQL users and databases for each component, you can supply them in the inventory file under the [all:vars] group.

   # Platform gateway
   gateway_pg_host=aap.example.org
   gateway_pg_database=<set your own>
   gateway_pg_username=<set your own>
   gateway_pg_password=<set your own>
   
   # Automation controller
   controller_pg_host=aap.example.org
   controller_pg_database=<set your own>
   controller_pg_username=<set your own>
   controller_pg_password=<set your own>
   
   # Automation hub
   hub_pg_host=aap.example.org
   hub_pg_database=<set your own>
   hub_pg_username=<set your own>
   hub_pg_password=<set your own>
   
   # Event-Driven Ansible
   eda_pg_host=aap.example.org
   eda_pg_database=<set your own>
   eda_pg_username=<set your own>
   eda_pg_password=<set your own>

Procedure

1. Check if the extension is available on the PostgreSQL server (automation hub database).

   $ psql -d <automation hub database> -c "SELECT * FROM pg_available_extensions WHERE name='hstore'"

2. Where the default value for <automation hub database> is automationhub.

   Example output with hstore available:

   name  | default_version | installed_version |comment
   ------+-----------------+-------------------+---------------------------------------------------
    hstore | 1.7           |                   | data type for storing sets of (key, value) pairs
   (1 row)

   Example output with hstore not available:

    name | default_version | installed_version | comment
   ------+-----------------+-------------------+---------
   (0 rows)

3. On a RHEL based server, the hstore extension is included in the postgresql-contrib RPM package, which is not installed automatically when installing the PostgreSQL server RPM package.

   To install the RPM package, use the following command:

   dnf install postgresql-contrib

4. Load the hstore PostgreSQL extension into the automation hub database with the following command:

   $ psql -d <automation hub database> -c "CREATE EXTENSION hstore;"

   In the following output, the installed_version field lists the hstore extension used, indicating that hstore is enabled.

   name | default_version | installed_version | comment
   -----+-----------------+-------------------+------------------------------------------------------
   hstore  |     1.7      |       1.7         | data type for storing sets of (key, value) pairs
   (1 row)