1. Expand the root partition, since on 5.13.x appliance the size of the disk is only 4 GB. It must be expanded before upgrading, for docker to work, since it requires more space.
   1. Boot the virtual machine and log in to it.
   2. To find out which hard disk to expand, do df -h to see which disk partition is mounted for root file system, /dev/sdc1 or /dev/sdb1.
   3. Assuming that sdb1 is the primary hard disk, shut down the virtual machine and expand the size of the virtual machine's disk (as mentioned in step 1 above), from 4GB to minimum 16GB via editing the Virtual Machine settings.
      
      1. If /dev/sdb1is mounted, hard disk 2 needs to be expanded.
      2. If /dev/sdc1is mounted, hard disk 3 needs to be expanded.
   4. Boot the virtual machine and log in again.
   5. Verify the disk size of mounted disk by running this command:

      
      

      Code Block
      title Check disk size
      fdisk -l

      
      

   6. Once the disk is successfully expanded, resize the partition and expand the file system.

      1. Resize the partition using the command below. This will display the free space available on the disk.

         Code Block
         title Resize
         sudo cfdisk /dev/sdb

         

      2. Select the Resize menu in the bottom. Once resize is selected, it displays the disk size after resizing as 16GB (or the size that was set in step 1 above).
      3. Select the Write menu, to write the new partition table on disk.
      4. Select Quit to exit from command.
      5. Expand the file system on the root partition:

         
         

         Code Block
         title resize
         sudo resize2fs /dev/sdb1

         
         

      6. Verify the size of the disk partition:

         
         

         Code Block
         title check disk size
         df -h

         
         

2. The following ports shall be open to traffic to and from each Docker host participating on an overlay network:
   1. TCP port 2377 for cluster management communications.
   2. TCP and UDP port 7946 for communication among nodes.
   3. UDP port 4789 for overlay network traffic.
3. Copy upgradeFrom5.13.tgz to the manager node (node where administration service is running) and all worker (other) nodes. In this setup we will set and consider the administration-service node as the manager node.

   Extract the tar file:

   Code Block
   title Extract
   tar -xzf upgradeFrom5.13.tgz

    

4. Set up the docker daemon and pull images:
   1. Verify the Digital Access tag in versiontag.yml (<path to upgrade folder>/docker-compose/versiontag.yml) file. The same tag will be installed as part of the upgrade. If it is not the correct tag, update it manually.
   2. Although the upgrade script installs docker and pulls the images from repository, it is recommended to install docker and pull the images before running the upgrade. This will reduce the script run time and also the downtime of the system.

   3. Run the script pull_image.sh to pull images on all nodes.

      Note
      In case of offline upgrade, load the Digital Access docker images to the machine. Also, if you are using internal postgres, load postgres:9.6-alpine image on the manager node.

      
      

      Code Block
      title Pull images
      sudo bash upgrade/scripts/pull_image.sh

      
      

   4. Make sure there is a backup/snapshot of the machine before starting the upgrade.

1. Keep note of token, ip and port from the above steps.

2. Run the upgrade script, follow the command line options:

   Code Block
   title Get cluster join token
   sudo bash upgrade/scripts/upgrade.sh --worker --token <token value> --ip-port <ip:port>

   
   

1. Verify if all nodes are part of cluster by running this command.

   Code Block
   title Verify if all nodes are part of cluster
   sudo docker node ls

   Example:
   

2. Identify nodes ID, master and worker where the service will be distributed.

   Code Block
   title Identify nodes
   sudo docker node inspect --format '{{ .Status }}' h9u7iiifi6sr85zyszu8xo54l

   
   

3. Output from this command:

   No Format
   {ready 192.168.86.129}

   IP address will help to identify the Digital Access node.

Add new labels for each service which you want to run. Choose any name based on requirement, but make sure they are in accordance with what you have defined in the constraint section in the docker-compose.yml file.

1. Use these commands to add label for each service:

   Code Block
   title Commands to add labels
   sudo docker node update --label-add da-policy-service=true <manager node ID> sudo docker node update --label-add da-authentication-service=true <manager node ID> sudo docker node update --label-add da-administration-service=true <manager node ID> sudo docker node update --label-add da-access-point=true <manager node ID> sudo docker node update --label-add da-distribution-service=true <manager node ID> sudo docker node update --label-add da-policy-service1=true <worker node ID> sudo docker node update --label-add da-access-point1=true <worker node ID>

   
   

2. Deploy your Digital Access stack using this command. 

   Verify that the required images are available on the nodes. Then run the start-all.sh script on the manager node.

   Code Block
   title Deploy DA stack
   sudo bash /opt/nexus/scripts/start-all.sh

   
   

1. Log in to Digital Access Admin. If you use an internal database for configurations, provide the host machine IP address to connect the databases (HAG, Oath, Oauth).
   
   
2. Publish the configurations.
3. Change the internal host and port for each added service according to the docker-compose.yml and network.yml files.
   
   
4. Go to Manage System > Distribution Services and select the checkbox for “Listen on All Interfaces” in case of the ports that are to be exposed.
5. Go to Manage System >Access Points and provide the IP address instead of the service name. Also enable the "Listen on all Interfaces" option.
   
6. If you want to enable the XPI and SOAP services, the expose port ID should be 0.0.0.0 in Digital Access Admin.
   

7. Redeploy the services using this command on the manager node:

   Code Block
   title Deploy Digital Access stack
   sudo bash /opt/nexus/scripts/start-all.sh