Red Hat Training

A Red Hat training course is available for Red Hat Virtualization

Chapter 7. Upgrading a Remote Database Environment from 4.1 to Red Hat Virtualization 4.2

Upgrading your environment from 4.1 to 4.2 involves the following steps:

  1. Upgrade the database from PostgreSQL 9.2 to 9.5
  2. Update the 4.1 Manager to the latest version of 4.1
  3. Upgrade the Manager from 4.1 to 4.2
  4. Upgrade the hosts
  5. Update the compatibility version of the clusters
  6. Update the compatibility version of the data centers
  7. Replace SHA-1 certificates with SHA-256 certificates
  8. If you installed the technology preview version of Open Virtual Network (OVN) in 4.1, update the OVN provider’s networking plugin

7.1. Upgrading Remote Databases from PG 9.2 to 9.5

Red Hat Virtualization 4.2 uses PostgreSQL 9.5 instead of PostgreSQL 9.2. If your databases are installed locally, the upgrade script will automatically upgrade them from version 9.2 to 9.5, and you can skip this section and proceed to the next step. However, if either of your databases (Manager or Data Warehouse) is installed on a separate machine, you must perform the following procedure on each remote database before upgrading the Manager.

  1. Stop the service running on the machine:

    • Stop the ovirt-engine service on the Manager machine: 

      # systemctl stop ovirt-engine

    • Stop the ovirt-engine-dwh service on the Data Warehouse machine: 

      # systemctl stop ovirt-engine-dwhd

  2. Enable the required repository to receive the PostgreSQL 9.5 package:

    Enable either the Red Hat Virtualization Manager repository: 

    # subscription-manager repos --enable=rhel-7-server-rhv-4.2-manager-rpms

    or the SCL repository: 

    # subscription-manager repos --enable rhel-server-rhscl-7-rpms

  3. Install the PostgreSQL 9.5 packages: 

    # yum install rh-postgresql95 rh-postgresql95-postgresql-contrib

  4. Stop and disable the PostgreSQL 9.2 service: 

    # systemctl stop postgresql
# systemctl disable postgresql

  5. Upgrade the PostgreSQL 9.2 database to PostgreSQL 9.5: 

    # scl enable rh-postgresql95 -- postgresql-setup upgrade

  6. Start and enable the rh-postgresql95-postgresql.service and check that it is running: 

    # systemctl start rh-postgresql95-postgresql.service
# systemctl enable rh-postgresql95-postgresql.service
# systemctl status rh-postgresql95-postgresql.service

    Ensure that you see an output similar to the following: 

    rh-postgresql95-postgresql.service - PostgreSQL database server
   Loaded: loaded (/usr/lib/systemd/system/rh-postgresql95-postgresql.service;
enabled; vendor preset: disabled)
   Active: active (running) since Mon 2018-05-07 08:48:27 CEST; 1h 59min ago

  7. Log in to the database and enable the uuid-ossp extension: 

    # su - postgres -c "scl enable rh-postgresql95 -- psql -d database-name"

  8. Execute the following SQL commands: 

    # database-name=# DROP FUNCTION IF EXISTS uuid_generate_v1();
# database-name=# CREATE EXTENSION "uuid-ossp";

  9. Copy the pg_hba.conf client configuration file from the 9.2 environment to your 9.5 environment: 

    # cp -p /var/lib/pgsql/data/pg_hba.conf  /var/opt/rh/rh-postgresql95/lib/pgsql/data/pg_hba.conf

  10. Update the following parameters in the postgresql.conf file: 

    # vi /var/opt/rh/rh-postgresql95/lib/pgsql/data/postgresql.conf

listen_addresses='*'
autovacuum_vacuum_scale_factor='0.01'
autovacuum_analyze_scale_factor='0.075'
autovacuum_max_workers='6'
maintenance_work_mem='65536'
max_connections='150'
work_mem = '8192'

  11. Restart the PostgreSQL 9.5 service to apply the configuration changes: 

    # systemctl restart rh-postgresql95-postgresql.service

    The remote databases have been upgraded.