Chapter 2. System requirements

Procedure

1. Connect to a PostgreSQL compliant database server with superuser privileges.

   # psql -h <db.example.com> -U superuser -p 5432 -d postgres <Password for user superuser>:

   Copy to Clipboard Toggle word wrap

2. Where the default value for <hostname> is hostname:

   -h hostname
   --host=hostname

   Copy to Clipboard Toggle word wrap

3. Specify the hostname of the machine on which the server is running. If the value begins with a slash, it is used as the directory for the UNIX-domain socket.

   -d dbname
   --dbname=dbname

   Copy to Clipboard Toggle word wrap

4. Specify the name of the database to connect to. This is equal to specifying dbname as the first non-option argument on the command line. The dbname can be a connection string. If so, connection string parameters override any conflicting command line options.

   -U username
   --username=username

   Copy to Clipboard Toggle word wrap
5. Connect to the database as the user username instead of the default (you must have permission to do so).
6. Create the user, database, and password with the createDB or administrator role assigned to the user. For further information, see Database Roles.
7. Run the installation program. If you are using a PostgreSQL database, the database is owned by the connecting user and must have a createDB or administrator role assigned to it.
8. Check that you can connect to the created database with the credentials provided in the inventory file.
9. Check the permission of the user. The user should have the createDB or administrator role.

10. After you create the PostgreSQL users and databases for each component, add the database credentials and host details in the inventory file under the [all:vars] group.

    # Automation controller
    pg_host=data.example.com
    pg_database=<database name>
    pg_port=<port_number>
    pg_username=<set your own>
    pg_password=<set your own>
    
    # Platform gateway
    automationgateway_pg_host=aap.example.org
    automationgateway_pg_database=<set your own>
    automationgateway_pg_port=<port_number>
    automationgateway_pg_username=<set your own>
    automationgateway_pg_password=<set your own>
    
    # Automation hub
    automationhub_pg_host=data.example.com
    automationhub_pg_database=<database_name>
    automationhub_pg_port=<port_number>
    automationhub_pg_username=<username>
    automationhub_pg_password=<password>
    
    # Event-Driven Ansible
    automationedacontroller_pg_host=data.example.com
    automationedacontroller_pg_database=<database_name>
    automationedacontroller_pg_port=<port_number>
    automationedacontroller_pg_username=<username>
    automationedacontroller_pg_password=<password>

    Copy to Clipboard Toggle word wrap

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'"

   Copy to Clipboard Toggle word wrap

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)

   Copy to Clipboard Toggle word wrap

   Example output with hstore not available:

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

   Copy to Clipboard Toggle word wrap

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

   Copy to Clipboard Toggle word wrap

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

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

   Copy to Clipboard Toggle word wrap

   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)

   Copy to Clipboard Toggle word wrap

Procedure

1. Run a random write test:

   $ fio --name=write_iops --directory=/tmp --numjobs=3 --size=10G \
   --time_based --runtime=60s --ramp_time=2s --ioengine=libaio --direct=1 \
   --verify=0 --bs=4K --iodepth=64 --rw=randwrite \
   --group_reporting=1 > /tmp/fio_benchmark_write_iops.log \
   2>> /tmp/fio_write_iops_error.log

   Copy to Clipboard Toggle word wrap

2. Run a random read test:

   $ fio --name=read_iops --directory=/tmp \
   --numjobs=3 --size=10G --time_based --runtime=60s --ramp_time=2s \
   --ioengine=libaio --direct=1 --verify=0 --bs=4K --iodepth=64 --rw=randread \
   --group_reporting=1 > /tmp/fio_benchmark_read_iops.log \
   2>> /tmp/fio_read_iops_error.log

   Copy to Clipboard Toggle word wrap

3. Review the results:

   In the log files written by the benchmark commands, search for the line beginning with iops. This line shows the minimum, maximum, and average values for the test.

   The following example shows the line in the log file for the random read test:

   $ cat /tmp/fio_benchmark_read_iops.log
   read_iops: (g=0): rw=randread, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 4096B-4096B, ioengine=libaio, iodepth=64
   […]
      iops        : min=50879, max=61603, avg=56221.33, stdev=679.97, samples=360
   […]

   Copy to Clipboard Toggle word wrap
   Note

   The above is a baseline to help evaluate the best case performance on your systems. Systems can and will change and performance may vary depending on what else is happening on your systems, storage or network at the time of testing. You must review, monitor, and revisit the log files according to your own business requirements, application workloads, and new demands.