Skip to content

Latest commit

 

History

History
200 lines (148 loc) · 7.33 KB

README.md

File metadata and controls

200 lines (148 loc) · 7.33 KB
Raw

setup_pemserver

This Ansible Galaxy Role Installs and configure PEM server.

Not all Distribution or versions are supported on all the operating systems available.

For more details refer to the: Database engines supported section.

Note: The role does not configure EDB Postgres Advanced Server or PostgreSQL for replication it only installs Postgres Enterprise Manager (PEM) and configures any node to be a PEM server.

The ansible playbook must be executed under an account that has full privileges.

Requirements

The requirements for this ansible galaxy role are:

  1. Ansible >= 2.9
  2. community.general
  3. edb_devops.edb_postgres -> setup_repo - for installing the EPAS/PG repository
  4. edb_devops.edb_postgres -> install_dbserver - for installing the EPAS/PG binaries
  5. edb_devops.edb_postgres -> init_dbserver - for initializing the EPAS/PG data directory and configuring a primary node.

Role variables

When executing the role via ansible there these are the required variables:

  • pg_version

Postgres Versions supported are: 10, 11, 12, 13, 14 and 15

  • pg_type

Database Engine supported are: PG and EPAS

  • repo_username

Username for the EDB public package repository.

  • repo_password

Password for the EDB public package repository v1 (if you have a repo token, use repo_token instead).

  • repo_token

Token for EDB public package repository.

  • pg_pem_admin_password

Password for the pemadmin user in order to log into PEM.

The rest of the variables can be configured and are available in the:

Example Playbook

Inventory file content

Content of the inventory.yml file:

---
all:
  children:
    pemserver:
      hosts:
        pemserver1:
          ansible_host: xxx.xxx.xxx.xxx
          private_ip: xxx.xxx.xxx.xxx
    primary:
      hosts:
        primary1:
          ansible_host: xxx.xxx.xxx.xxx
          private_ip: xxx.xxx.xxx.xxx
          pem_agent: true
          pem_server_private_ip: xxx.xxx.xxx.xxx

How to include the setup_pemserver role in your Playbook

Below is an example of how to include the setup_pemserver role:

---
- hosts: pemserver
  name: Setup PEM server
  become: yes
  gather_facts: yes
  any_errors_fatal: true

  collections:
    - edb_devops.edb_postgres

  pre_tasks:
    - name: Initialize the user defined variables
      set_fact:
        pg_version: 14
        pg_type: "PG"
        repo_username: "REPO_USERNAME"
        repo_password: "REPO_PASSWORD"
        repo_token: "REPO_TOKEN"
        pg_pem_admin_password: "CHANGEME"

  roles:
    - setup_repo
    - install_dbserver
    - init_dbserver
    - setup_pemserver

Defining and adding variables is done in the set_fact of the pre_tasks.

All the variables are available at:

Database engines supported

Community PostgreSQL and PEM

PostgreSQL

Distribution 10 11 12 13 14 15
CentOS 7 ✅ ✅ ✅ ✅ ✅ ✅
Red Hat Linux 7 ✅ ✅ ✅ ✅ ✅ ✅
RockyLinux 8 ✅ ✅ ✅ ✅ ✅ ✅
Red Hat Linux 8 ✅ ✅ ✅ ✅ ✅ ✅
AlmaLinux8 ✅ ✅ ✅ ✅ ✅ ✅
Ubuntu 20.04 LTS (Focal) - x86_64 ✅ ✅ ✅ ✅ ✅ ✅
Debian 9 (Stretch) - x86_64 ✅ ✅ ✅ ✅ ✅ ✅
Debian 10 (Buster) - x86_64 ✅ ✅ ✅ ✅ ✅ ✅

EnterpriseDB Postgres Advanced Server

Distribution 10 11 12 13 14 15
CentOS 7 ✅ ✅ ✅ ✅ ✅ ✅
Red Hat Linux 7 ✅ ✅ ✅ ✅ ✅ ✅
RockyLinux 8 ❌ ❌ ✅ ✅ ✅ ✅
Red Hat Linux 8 ❌ ❌ ✅ ✅ ✅ ✅
AlmaLinux8 ❌ ❌ ✅ ✅ ✅ ✅
Ubuntu 20.04 LTS (Focal) - x86_64 ❌ ❌ ❌ ✅ ✅ ✅
Debian 9 (Stretch) - x86_64 ❌ ✅ ✅ ✅ ✅ ✅
Debian 10 (Buster) - x86_64 ❌ ❌ ✅ ✅ ✅ ✅
  • ✅ - Tested and supported
  • ❌ - Not supported

Playbook execution examples

# To deploy community Postgres version 13 with the user centos
$ ansible-playbook playbook.yml \
  -u centos \
  -i inventory.yml \
  --private-key <key.pem> \
  --extra-vars="pg_version=13 pg_type=PG"
# To deploy EPAS version 12 with the user ec2-user
$ ansible-playbook playbook.yml \
  -u ec2-user \
  -i inventory.yml \
  --private-key <key.pem> \
  --extra-vars="pg_version=12 pg_type=EPAS"

Notes

Log into PEM at https://<pemserver1.ansible_host>/pem

License

BSD

Author information

Author: