Container growth topology

The container-based growth topology provides a smaller footprint deployment without redundancy for organizations getting started with Ansible Automation Platform.

Included are the tested infrastructure topology, system requirements, network port configurations, and an example inventory file for installation.

Infrastructure topology
Copy link

The Red Hat tested infrastructure topology for this deployment model:

Figure 1. Infrastructure topology diagram

Container growth topology diagram

Red Hat tests a single VM with these requirements:

Expand
Table 1. Virtual machine requirements
Requirement Minimum requirement

RAM
  • 16 GB
  • 32 GB required for growth topology bundled installations with hub_seed_collections=true. Seeding the collections can take 45 or more minutes.

CPUs

4

Local disk
  • Total available disk space: 60 GB
  • Installation directory: 15 GB (if on a dedicated partition)
  • /var/tmp for online installations: 1 GB
  • /var/tmp for offline or bundled installations: 3 GB
  • Temporary directory (defaults to /tmp) for offline or bundled installations: 10GB

Disk IOPS

3000
Expand
Table 2. Infrastructure topology components
Purpose Example group names

All Ansible Automation Platform components
  • automationgateway
  • automationcontroller
  • automationhub
  • automationeda
  • database

Tested system configurations
Copy link

Red Hat has tested these configurations to install and run Red Hat Ansible Automation Platform:

Expand
Table 3. System configuration
Type Description Notes

Subscription
  • Valid Red Hat Ansible Automation Platform subscription
  • Valid Red Hat Enterprise Linux subscription (to consume the BaseOS and AppStream repositories)

Operating system
  • Red Hat Enterprise Linux 9.4 or later minor versions of Red Hat Enterprise Linux 9.
  • Red Hat Enterprise Linux 10 or later minor versions of Red Hat Enterprise Linux 10.

CPU architecture

x86_64, AArch64, s390x (IBM Z), ppc64le (IBM Power)

ansible-core

  • RHEL 9: installation program usesansible-core 2.14, Ansible Automation Platform operation uses ansible-core 2.16
  • RHEL 10: installation program usesansible-core 2.16, Ansible Automation Platform operation uses ansible-core 2.16
  • The installation program uses the ansible-core package from the RHEL AppStream repository.
  • Ansible Automation Platform bundles ansible-core 2.16 for operation, so you do not need to install it manually.

Browser

A currently supported version of Mozilla Firefox or Google Chrome.

Database
  • For Ansible Automation Platform managed databases: PostgreSQL 15.
  • For customer provided (external) databases: PostgreSQL 15, 16, or 17.
  • External (customer supported) databases require International Components for Unicode (ICU) support.
  • External databases using PostgreSQL 16 or 17 must rely on external backup and restore processes. Backup and restore functionality is dependent on utilities provided with PostgreSQL 15.

IP version

IPv4, IPv6 (single-stack and dual-stack)

Network ports
Copy link

Red Hat Ansible Automation Platform uses several ports to communicate with its services. These ports must be open and available for Red Hat Ansible Automation Platform to work. Ensure that these ports are available and are not blocked by a firewall.

Expand
Table 4. Network ports and protocols
Port number Protocol Service Source Destination Description

80/443

TCP

HTTP/HTTPS

Event-Driven Ansible

Automation hub

Pull container decision environments

80/443

TCP

HTTP/HTTPS

Event-Driven Ansible

Automation controller

Launch automation controller jobs

80/443

TCP

HTTP/HTTPS

Automation controller

Automation hub

Pull collections and execution environment images

80/443

TCP

HTTP/HTTPS

Platform gateway

Automation controller

Platform gateway to automation controller communication

80/443

TCP

HTTP/HTTPS

Platform gateway

Automation hub

Platform gateway to automation hub communication

80/443

TCP

HTTP/HTTPS

Platform gateway

Event-Driven Ansible

Platform gateway to Event-Driven Ansible communication

5432

TCP

PostgreSQL

Event-Driven Ansible

Database

Event-Driven Ansible database access

5432

TCP

PostgreSQL

Platform gateway

Database

Platform gateway database access

5432

TCP

PostgreSQL

Automation hub

Database

Automation hub database access

5432

TCP

PostgreSQL

Automation controller

Database

Automation controller database access

6379

TCP

Redis

Event-Driven Ansible

Redis container

Job launching and data storage for Event-Driven Ansible

6379

TCP

Redis

Platform gateway

Redis container

Data storage and retrieval for platform gateway services

8443

TCP

HTTPS

Platform gateway

Platform gateway

Internal gateway NGINX communication

27199

TCP

Receptor

Automation controller

Execution container

Mesh nodes connect directly to controllers. Allows two-way communication for job distribution.

8080/8443

TCP

HTTP/HTTPS

Platform gateway

Automation controller

Automation controller NGINX ports. You can configure these ports with the following inventory variables: controller_nginx_http_port, controller_nginx_https_port.

8081/8444

TCP

HTTP/HTTPS

Platform gateway

Automation hub

Automation hub NGINX ports. You can configure these ports with the following inventory variables: hub_nginx_http_port, hub_nginx_https_port.

8082/8445

TCP

HTTP/HTTPS

Platform gateway

Event-Driven Ansible

Event-Driven Ansible NGINX ports. You can configure these ports with the following inventory variables: eda_nginx_http_port, eda_nginx_https_port.

8083/8446

TCP

HTTP/HTTPS

Platform gateway

Platform gateway

Platform gateway NGINX ports. You can configure these ports with the following inventory variables: gateway_nginx_http_port, gateway_nginx_https_port.
Note

If you change any port values by using inventory variables, refer to Inventory file variables to review all default port values and ensure there are no port conflicts.

Example inventory file
Copy link

Use the example inventory file to perform an installation:

# This is the Ansible Automation Platform installer inventory file intended for the container growth deployment topology.
# This inventory file expects to be run from the host where Ansible Automation Platform will be installed.
# Consult the Ansible Automation Platform product documentation about this topology's tested hardware configuration.
# https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.6/plan-ref_installation_deployment_models
#
# Consult the docs if you are unsure what to add
# For all optional variables consult the included README.md
# or the Ansible Automation Platform documentation:
# https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.6/install-con_aap_containerized_installation_intro

# This section is for your platform gateway hosts
# -----------------------------------------------------
[automationgateway]
aap.example.org

# This section is for your automation controller hosts
# -----------------------------------------------------
[automationcontroller]
aap.example.org

# This section is for your automation hub hosts
# -----------------------------------------------------
[automationhub]
aap.example.org

# This section is for your Event-Driven Ansible controller hosts
# -----------------------------------------------------
[automationeda]
aap.example.org

# This section is for the Ansible Automation Platform database
# -----------------------------------------------------
[database]
aap.example.org

[all:vars]
# Ansible
ansible_connection=local

# Common variables
# https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.6/install-ref_general_inventory_variables
# -----------------------------------------------------
postgresql_admin_username=postgres
postgresql_admin_password=<set your own>

registry_username=<your RHN username>
registry_password=<your RHN password>

redis_mode=standalone

# Platform gateway
# https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.6/install-ref_gateway_variables
# -----------------------------------------------------
gateway_admin_password=<set your own>
gateway_pg_host=aap.example.org
gateway_pg_password=<set your own>

# Automation controller
# https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.6/install-ref_controller_variables
# -----------------------------------------------------
controller_admin_password=<set your own>
controller_pg_host=aap.example.org
controller_pg_password=<set your own>
controller_percent_memory_capacity=0.5

# Automation hub
# https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.6/install-ref_hub_variables
# -----------------------------------------------------
hub_admin_password=<set your own>
hub_pg_host=aap.example.org
hub_pg_password=<set your own>
hub_seed_collections=false

# Event-Driven Ansible controller
# https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.6/install-ref_eda_controller_variables
# -----------------------------------------------------
eda_admin_password=<set your own>
eda_pg_host=aap.example.org
eda_pg_password=<set your own>

SSH keys are only required when installing on remote hosts. If doing a self contained local VM based installation, you can use ansible_connection=local.