Red Hat Summit Red Hat SummitSupportKonsoleEntwicklerDemo startenKontakt

Dieser Inhalt ist in der von Ihnen ausgewählten Sprache nicht verfügbar.

Chapter 2. Prerequisites

The installation of this highly available Ansible Automation Platform 2.1 reference environment uses the following on each site:

  • Three control plane nodes
  • One control plane database node
  • Two execution nodes
  • Three automation hub nodes
  • One automation hub database node
  • Shared filesystem for automation hub installation (/var/lib/pulp)
Note

These nodes are not required to be physical servers.

2.1. Node requirements
Link kopieren

Expand
Table 2.1. execution nodes

Execution nodes

Required

Notes

RAM

16Gb

 

CPUs

4

  • Runs automation. Increase memory and CPU to increase capacity for running more forks
Expand
Table 2.2. automation controller nodes

Control nodes

Required

Notes

RAM

16Gb

 

CPUs

4

  • Processes events and runs cluster jobs including project updates and cleanup jobs. Increasing CPU and memory can help with job event processing.

Disk: service node

40Gb dedicated hard disk space

  • controller: dedicate a minimum of 20 GB to /var/ for file and working directory storage
  • Storage volume should be rated for a minimum baseline of 1500 IOPS.
  • Projects are stored on control and hybrid, and for the duration of jobs, also on execution nodes. If the cluster has many large projects, consider having twice the GB in /var/lib/awx/projects, to avoid disk space errors.

Disk: database node

20Gb dedicated hard disk space

  • 150 GB+ recommended
  • Storage volume should be rated for a high baseline IOPS (1500 or more).

Browser

A currently supported version of Mozilla FireFox or Google Chrome

 

Database

PostgreSQL version 12

 
Expand
Table 2.3. automation hub nodes

automation hub nodes

Required

Notes

RAM

8Gb minimum

  • 8 GB RAM (minimum and recommended for Vagrant trial installations)
  • 8 GB RAM (minimum for external standalone PostgreSQL databases)
  • For capacity based on forks in your configuration, see additional resources

CPUs

2 minimum

  • For capacity based on forks in your configuration, see additional resources

Disk: service node

40Gb dedicated hard disk space

  • Storage volume should be rated for a minimum baseline of 1500 IOPS.

Disk: database node

20Gb dedicated hard disk space

  • 150 GB+ recommended
  • Storage volume should be rated for a high baseline IOPS (1500 or more).

Browser

A currently supported version of Mozilla FireFox or Google Chrome

 

Database

PostgreSQL version 12

 
Expand
Table 2.4. database nodes

database nodes

Required

Notes

RAM

16GB

 

CPUs

4

 

Disk

20Gb dedicated hard disk space

  • Minimum decidcated disk space 20Gb
  • 150 GB+ recommended
  • Storage volume should be rated for a high baseline IOPS (1500 or more)
Note

All automation controller data is stored in the PostgreSQL database. Database storage increases with the number of hosts managed, number of jobs run, number of facts stored in the fact cache, and number of tasks in any individual job. For example, a playbook run every hour (24 times a day) across 250, hosts, with 20 tasks will store over 800,000 events in the database every week.

If not enough space is reserved in the database, old job runs and facts will need cleaned on a regular basis. Refer to Management Jobs in the Automation Controller Administration Guide for more information

2.2. Network Requirements
Link kopieren

Ansible Automation Platform 2.1 requires at least one network across all nodes within the Ansible Automation Platform cluster.

In order to access the Ansible Automation Platform dashboard, a browser that can access the network that the control plane nodes reside on is required. If you wish to access the Ansible Automation Platform dashboard externally, ensure to add a public IP address to your control plane nodes.

It is recommended that network administrators setup a static DHCP address for all nodes and an appropriate DNS record. This ensures each node’s IP address remains constant in the absence of a DHCP server. To use static IP addresses, reserve the IP addresses with an infinite lease.

For the purposes of this reference architecture, setup of a DHCP server, setting up DNS records and setting up a load balancer is out of scope.

A network administrator should reserve at least the following number of IP addresses, including:

  1. One IP address for each control plane node.
  2. One IP address for each execution node.
  3. One IP address for each automation hub node.
  4. One IP address for the control plane database.
  5. One IP address for the automation hub database.
  6. One IP address for the load balancer automation controller cluster address for Ansible Automation Platform Site 1.
  7. One IP address for the load balancer automation controller cluster address for Ansible Automation Platform Site 2.
  8. One IP address for the load balancer private automation hub cluster address for Ansible Automation Platform Site 1.
  9. One IP address for the load balancer private automation hub cluster address for Ansible Automation Platform Site 2.

This reference environment reserves 12 IP addresses per site.

The following table provides an example of Ansible Site 1 of the reference environment.

Expand

Usage

Host Name

IP

Control Plane 1

controlplane-1.site1.example.com

192.168.0.10

Control Plane 2

controlplane-2.site1.example.com

192.168.0.11

Control Plane 3

controlplane-3.site1.example.com

192.168.0.12

Control Plane Database

controlplane-db.site1.example.com

192.168.0.13

Control Plane Cluster address

controlplane-cluster.site1.example.com

192.168.0.14

Execution Node 1

executionnode-1.site1.example.com

192.168.0.15

Execution Node 2

executionnode-2.site1.example.com

192.168.0.16

Automation Hub Node 1

automationhub-1.site1.example.com

192.168.0.17

Automation Hub Node 2

automationhub-2.site1.example.com

192.168.0.18

Automation Hub Node 3

automationhub-3.site1.example.com

192.168.0.19

Automation Hub Database

automationhub-db.site1.example.com

192.168.0.20

Automation Hub Cluster

automationhub-cluster.site1.example.com

192.168.0.21

2.3. Validation checklist for nodes
Link kopieren

The following is a summary of all the requirements:

  • ❏ 16 GB of RAM for controller nodes and execution nodes
  • ❏ 8 GB of RAM for private automation hub nodes
  • ❏ 4 CPUs for controller nodes and execution nodes
  • ❏ 2 CPUs for private automation hub nodes
  • ❏ 20 GB+ disk space for database node
  • ❏ 40 GB+ disk space for non database nodes
  • ❏ DHCP reservations use infinite leases to deploy the cluster with static IP addresses.
  • ❏ DNS records for all nodes
  • ❏ Red Hat Enterprise Linux 8.4 or later 64-bit (x86) installed for all nodes
  • ❏ Chrony configurationed for all nodes
  • ❏ ansible-core version 2.11 or later installed for all nodes
Nach oben
Red Hat logoGithubredditYoutubeTwitter

Lernen

Testen, kaufen und verkaufen

Communitys

Über Red Hat Dokumentation

Wir helfen Red Hat Benutzern, mit unseren Produkten und Diensten innovativ zu sein und ihre Ziele zu erreichen – mit Inhalten, denen sie vertrauen können. Entdecken Sie unsere neuesten Updates.

Mehr Inklusion in Open Source

Red Hat hat sich verpflichtet, problematische Sprache in unserem Code, unserer Dokumentation und unseren Web-Eigenschaften zu ersetzen. Weitere Einzelheiten finden Sie in Red Hat Blog.

Über Red Hat

Wir liefern gehärtete Lösungen, die es Unternehmen leichter machen, plattform- und umgebungsübergreifend zu arbeiten, vom zentralen Rechenzentrum bis zum Netzwerkrand.

Theme

© 2025 Red Hat