Menu

Manager 8.1.5 to 8.4.4 Load Balancing Upgrade Guide for Docker

Before you begin 

  • If you are using qTest Manager older than 8.1.5, you will need to use qTest Docker Deployment version 3.0 to upgrade your qTest to 8.1.5 followingthese instructions. Then use qTest Docker Deployment version 4.0 to upgrade your qTest Manager to 8.4.4

Example: Image below tries to demonstrate how to configure qTest Manager with load balancer for 4 machines: 

  • Machine 1: considered as a cluster, hosts qTest Manager's prerequisite apps: redis, rabbitmq, postgres, poseidon
  • Machine 2: hosts qTest Manager 8.4 (qtest)
  • Machine 3: hosts qTest Manager 8.4 (qtest)
  • Machine 4: hosts qTest Manager's load balancer (qtestlb)

NOTE

  • cluster machine has to open 2 ports: 53 and 6783

op_diagrams1_docker.jpg

 

Upgrade Machine 1

1. Shutdown Machine 1

Access to the directory where you've extracted the docker deployment package of qTest Manager 8.1.5 (docker-deployment-3.0), shut it down and create a backup.

$ ./shutdown
$ ./backup

2. Download docker-deployment-4.0 package 

This package supports the upgrade of qTest Manager from version 8.1.5 qTest version 8.4

 $ wget https://qtest-storage.s3.amazonaws.com/docker/deployment/docker-deployment-4.0.tar.gz

3. Extract the package 

 $ tar -zxf docker-deployment-4.0.tar.gz 

4. Access to docker-deployment-4.0 directory

 $ cd docker-deployment-4.0

5. Configure

Choose either way:

  • To keep all applications in your previous deployment being upgraded, override the /profiles directory of docker-deployment-4.0 with that directory of docker-deployment-3.0
 $ cp -r /<path to your docker-deployment-3.0 package>/docker-deployment-3.0/profiles/ .
  • OR use configure command if you want to specify each application to be upgraded (for HTTP)
 $ ./configure --apps "redis rabbitmq postgres poseidon" 

6. Migrate DB from Postgres 9.4 to Postgres 9.5

 $ ./migrateDBFrom9.4To9.5

7. After the upgrading process finishes, start the deployment process 

 $ ./startup

Upgrade Machine 2, 3

Please repeat all steps on Machine 2 and 3 that you have installed qTest Manager 8.1.5 (qtest). No change needed to make on Machine 4 (qtestlb) server.

1. Shutdown your current deployment

Access to the directory where you've extracted the docker deployment package of qTest Manager 8.1.5 (docker-deployment-3.0), shut it down and create a backup.

$ ./shutdown
$ ./backup

2. Download docker-deloyment-4.0 package 

This package supports the upgrade of qTest Manager from version 8.1.5 qTest version 8.4

 $ wget https://qtest-storage.s3.amazonaws.com/docker/deployment/docker-deployment-4.0.tar.gz

3. Extract the package 

 $ tar -zxf docker-deployment-4.0.tar.gz 

4. Access to docker-deployment-4.0 directory

 $ cd docker-deployment-4.0

5. Configure

Choose either way:

  • To keep all applications in your previous deployment being upgraded, override the /profiles directory of docker-deployment-4.0 with that directory of docker-deployment-3.0
 $ cp -r /<path to your docker-deployment-3.0 package>/docker-deployment-3.0/profiles/ .
  • OR use configure command if you want to specify each application to be upgraded (for HTTP)
 $ ./configure --qtest-url "http://<IP of current machine>:<qtest port>" --qtest-http "<qtest port>"
  • OR use configure command if you want to specify each application to be upgraded (for HTTPS)
 $ ./configure --ssl-key "<SSL Key>" --ssl-cert "<SSL Cert>" --ssl-ca "<SSL Ca>" --qtest-url "https://<IP of current machine>:<qtest https port>" --qtest-https "<qtest https port>"

6. Upgrade

Upgrading will keep all current data of upgraded applications.

 $ ./upgrade

7. After the upgrading process finishes, start the deployment process 

 $ ./startup
 

The script will download the application images and qTest components to the Docker. It may take couple of hours depending on your network connection.

Restart Machine 4

Access to the directory where you've extracted the docker deployment package of qTest Manager 8.1.5 (docker-deployment-3.0), shut it down and start it up.

$ ./shutdown
$ ./startup
Subscribe To Our Blog
Powered by Zendesk