Chapter 3. Standalone upgrade

Procedure

1. Enter the following command to scale down the Red Hat Quay container:

   $ sudo podman stop <quay_container_name>

2. Optional. If you are using Clair, enter the following command to stop the Clair container:

   $ sudo podman stop <clair_container_id>

3. Run the Podman process from SCLOrg’s Data Migration procedure, which allows for data migration from a remote PostgreSQL server:

   $ sudo podman run -d --name <migration_postgresql_database> 1
     -e POSTGRESQL_MIGRATION_REMOTE_HOST=172.17.0.2 \ 2
     -e POSTGRESQL_MIGRATION_ADMIN_PASSWORD=remoteAdminP@ssword \
     -v </host/data/directory:/var/lib/pgsql/data:Z> 3
     [ OPTIONAL_CONFIGURATION_VARIABLES ]
     rhel8/postgresql-13

   1

   The name of your PostgreSQL 13 migration database.

   2

   Your current Red Hat Quay PostgreSQL 13 database container IP address. Can obtained by running the following command: sudo podman inspect -f "{{.NetworkSettings.IPAddress}}" postgresql-quay.

   3

   You must specify a different volume mount point than the one from your initial PostgreSQL 10 deployment, and modify the access control lists for said directory. For example:

   $ mkdir -p /host/data/directory

   $ setfacl -m u:26:-wx /host/data/directory

   This prevents data from being overwritten by the new container.

4. Optional. If you are using Clair, repeat the previous step for the Clair PostgreSQL database container.

5. Stop the PostgreSQL 10 container:

   $ sudo podman stop <postgresql_container_name>

6. After completing the PostgreSQL migration, run the PostgreSQL 13 container, using the new data volume mount from Step 3, for example, </host/data/directory:/var/lib/postgresql/data>:

   $ sudo podman run -d --rm --name postgresql-quay \
     -e POSTGRESQL_USER=<username> \
     -e POSTGRESQL_PASSWORD=<password> \
    	-e POSTGRESQL_DATABASE=<quay_database_name> \
     -e POSTGRESQL_ADMIN_PASSWORD=<admin_password> \
     -p 5432:5432 \
     -v </host/data/directory:/var/lib/pgsql/data:Z> \
       registry.redhat.io/rhel8/postgresql-13:1-109

7. Optional. If you are using Clair, repeat the previous step for the Clair PostgreSQL database container.

8. Start the Red Hat Quay container:

   $ sudo podman run -d --rm -p 80:8080 -p 443:8443 --name=quay \
   -v /home/<quay_user>/quay-poc/config:/conf/stack:Z \
   -v /home/<quay_user>/quay-poc/storage:/datastorage:Z \
   {productrepo}/{quayimage}:{productminv}

9. Optional. Restart the Clair container, for example:

   $ sudo podman run -d --name clairv4 \
   -p 8081:8081 -p 8088:8088 \
   -e CLAIR_CONF=/clair/config.yaml \
   -e CLAIR_MODE=combo \
   registry.redhat.io/quay/clair-rhel8:v3.9.0

1. Take all hosts in the Red Hat Quay cluster out of service.

2. Generate some random data to use as a database secret key. For example:

   $ openssl rand -hex 48
   2d023adb9c477305348490aa0fd9c

3. Add a new DATABASE_SECRET_KEY field to your config.yaml file. For example:

   DATABASE_SECRET_KEY: "2d023adb9c477305348490aa0fd9c"

   Note

   For an OpenShift installation, the config.yaml file is stored as a secret.

4. Bring up one Quay container to complete the migration to 3.2.2.
5. Once the migration is done, make sure the same config.yaml is available on all nodes and bring up the new quay 3.2.2 service on those nodes.
6. Start 3.0.z versions of quay-builder and Clair to replace any instances of those containers you want to return to your cluster.

1. Obtain a list of all Red Hat Quay instances on each system running a Red Hat Quay instance.

   1. Enter the following command on System A to reveal the Red Hat Quay instances:

      $ sudo podman ps

      Example output

      CONTAINER ID  IMAGE                                      COMMAND         CREATED        STATUS            PORTS                                        NAMES
      ec16ece208c0  registry.redhat.io/quay/quay-rhel8:v3.7.0  registry        6 minutes ago  Up 6 minutes ago  0.0.0.0:80->8080/tcp, 0.0.0.0:443->8443/tcp  quay01

   2. Enter the following command on System B to reveal the Red Hat Quay instances:

      $ sudo podman ps

      Example output

      CONTAINER ID  IMAGE                                      COMMAND         CREATED        STATUS            PORTS                                        NAMES
      7ae0c9a8b37d  registry.redhat.io/quay/quay-rhel8:v3.7.0  registry        5 minutes ago   Up 2 seconds ago   0.0.0.0:82->8080/tcp, 0.0.0.0:445->8443/tcp  quay02

   3. Enter the following command on System C to reveal the Red Hat Quay instances:

      $ sudo podman ps

      Example output

      CONTAINER ID  IMAGE                                      COMMAND         CREATED        STATUS            PORTS                                        NAMES
      e75c4aebfee9  registry.redhat.io/quay/quay-rhel8:v3.7.0  registry        4 seconds ago   Up 4 seconds ago   0.0.0.0:84->8080/tcp, 0.0.0.0:447->8443/tcp  quay03

2. Temporarily shut down all Red Hat Quay instances on each system.

   1. Enter the following command on System A to shut down the Red Hat Quay instance:

      $ sudo podman stop ec16ece208c0

   2. Enter the following command on System B to shut down the Red Hat Quay instance:

      $ sudo podman stop 7ae0c9a8b37d

   3. Enter the following command on System C to shut down the Red Hat Quay instance:

      $ sudo podman stop e75c4aebfee9

3. Obtain the latest Red Hat Quay version, for example, Red Hat Quay 3.9, on each system.

   1. Enter the following command on System A to obtain the latest Red Hat Quay version:

      $ sudo podman pull registry.redhat.io/quay/quay-rhel8:v3.8.0

   2. Enter the following command on System B to obtain the latest Red Hat Quay version:

      $ sudo podman pull registry.redhat.io/quay/quay-rhel8:v3.8.0

   3. Enter the following command on System C to obtain the latest Red Hat Quay version:

      $ sudo podman pull registry.redhat.io/quay/quay-rhel8:v3.8.0

4. On System A of your highly available Red Hat Quay deployment, run the new image version, for example, Red Hat Quay 3.9:

   # sudo podman run --restart=always -p 443:8443 -p 80:8080 \
      --sysctl net.core.somaxconn=4096 \
      --name=quay01 \
      -v /mnt/quay/config:/conf/stack:Z \
      -v /mnt/quay/storage:/datastorage:Z \
      -d registry.redhat.io/quay/quay-rhel8:v3.8.0

5. Wait for the new Red Hat Quay container to become fully operational on System A. You can check the status of the container by entering the following command:

   $ sudo podman ps

   Example output

   CONTAINER ID  IMAGE                                      COMMAND         CREATED        STATUS            PORTS                                        NAMES
   70b9f38c3fb4  registry.redhat.io/quay/quay-rhel8:v3.8.0  registry        2 seconds ago   Up 2 seconds ago   0.0.0.0:82->8080/tcp, 0.0.0.0:445->8443/tcp  quay01

6. Optional: Ensure that Red Hat Quay is fully operation by navigating to the Red Hat Quay UI.

7. After ensuring that Red Hat Quay on System A is fully operational, run the new image versions on System B and on System C.

   1. On System B of your highly available Red Hat Quay deployment, run the new image version, for example, Red Hat Quay 3.9:

      # sudo podman run --restart=always -p 443:8443 -p 80:8080 \
         --sysctl net.core.somaxconn=4096 \
         --name=quay02 \
         -v /mnt/quay/config:/conf/stack:Z \
         -v /mnt/quay/storage:/datastorage:Z \
         -d registry.redhat.io/quay/quay-rhel8:v3.8.0

   2. On System C of your highly available Red Hat Quay deployment, run the new image version, for example, Red Hat Quay 3.9:

      # sudo podman run --restart=always -p 443:8443 -p 80:8080 \
         --sysctl net.core.somaxconn=4096 \
         --name=quay03 \
         -v /mnt/quay/config:/conf/stack:Z \
         -v /mnt/quay/storage:/datastorage:Z \
         -d registry.redhat.io/quay/quay-rhel8:v3.8.0

8. You can check the status of the containers on System B and on System C by entering the following command:

   $ sudo podman ps