Preparing for upgrade

Upgrading TrueSight Automation Console requires you to complete these pre-upgrade tasks. You can download the installation files from the BMC Electronic Product Distribution (EPD) site. 

To set up your upgrade environment

Complete the following tasks to set up your environment:

• Back up the database.
• Back up the installation directories of the database and the application. 
  
• Back up any trusted certificates that you may be using in your environment by performing the following steps:

  1. On a host where the TrueSight Automation Console application is installed, run the following command to copy exiting certificates:

     cp <install_dir>/application/common/certs/tsvmSslCertificate.crt /opt/<backup_directory>
     cp <install_dir>/application/common/certs/tsvmSslCertificate.key /opt/<backup_directory>

  2. After successfully upgrading the application, run the following command to replace the new certificates (created during the upgrade) with the custom certificates copied earlier. 

     cp /opt/<backup_directory>/tsvmSslCertificate.crt <install_dir>/application/common/certs/
     cp /opt/<backup_directory>/tsvmSslCertificate.key <install_dir>/application/common/certs/
• Ensure that you remove the local registry container and its mapped location on the host that contains the Docker images for the previous release. 
• Ensure that the target computers meet the System-requirements.
• Download the installation files.

• Download Docker compose.

  sudo curl -L https://github.com/docker/compose/releases/download/v2.23.0/docker-compose-linux-x86_64 -o /usr/local/bin/docker-compose

  Important

  After you download Docker compose, ensure that /usr/local/bin/ is added to the PATH variable.

• Grant the required permissions to Docker compose.

  sudo chmod +x /usr/local/bin/docker-compose

To prepare to upgrade TrueSight Automation Console

You first extract the latest images and then recreate a local registry with the latest Docker images. You can choose to delete the old registry (that contains the previous version) mapped location from the host either before you upgrade or after the upgrade is complete. 

To recreate the repository on a CentOS computer

1. To remove the local registry container, if it exists, run the following commands:

   Stop the registry container

   docker stop registry

   Remove the registry container

   docker rm registry
2. To recreate a local Docker registry, do these steps:
   
   1. Download the TSAC<versionNo>-IMAGES-LIN64.zip file from the BMC Electronic Products Distribution (EPD).
   2. If the registry image is not available on the host, run the following command to load the registry from <image>.zip:
      docker load -i <installer unzip location>/registry/registryv2.tar
   3. Create a directory on the Docker host and extract the TSAC<versionNo>-IMAGES-LIN64.zip into the directory.
   4. BMC recommends that you use version numbers while creating a directory to identify mapped locations for different versions.  
      For example, /opt/tsac_24_2/dockerrepo

   5. Run the following command to create the local Docker registry.
      In the following command, replace <Directory> with the directory and its complete path that you created in step b. If there are multiple hosts, repeat this step on all the Docker hosts.

      docker run -d \
       -p 5000:5000 \
       --restart=always \
       --name registry \
       -v <Directory>:/var/lib/registry \
        registry:2 

      For example,

      docker run -d \
        -p 5000:5000 \
        --restart=always \
        --name registry \
        -v /opt/tsac_<version>/dockerrepo:/var/lib/registry \
        registry:2

      This command creates a local Docker registry on port 5000.

   6. Run the following command to verify whether the registry contains the images:

      curl http://localhost:5000/v2/_catalog 

      You can also use the http://localhost:5000/v2/_catalog URL to verify using a browser. 

To recreate the repository on an RHEL computer

1. To remove the local registry, if it exists, run the following commands:

   Stop the registry container

   docker stop registry

   Remove the registry container

   docker rm registry

2. Create a local Docker registry to manage Docker images, as follows:

   1. Download the TSAC<versionNo>-IMAGES-LIN64.zip file from the BMC Electronic Products Distribution (EPD).
   2. If the registry image is not available on the host, run the following command to load the registry from <image>.zip:
      docker load -i <installer unzip location>/registry/registryv2.tar
   3. Create a directory on the Docker host (for example, /opt/tsac_<version>/dockerrepo) and extract the TSAC<versionNo>-IMAGES-LIN64.zip into the directory.

   4. Run the following command to create the local Docker registry. Replace <Directory> with the complete path of the directory that you created in step b. If there are multiple Docker hosts, repeat this step on all hosts.

      docker run -d \
       -p 5000:5000 \
       --restart=always \
       --name registry \
       -v <Directory>:/var/lib/registry \
        registry:2

      For example,

      docker run -d \
        -p 5000:5000 \
        --restart=always \
        --name registry \
        -v /opt/tsac_<version>/dockerrepo:/var/lib/registry \
        registry:2

      This command creates a local Docker registry on port 5000.

   5. Run the following command to verify whether the registry contains the images:

      curl http://localhost:5000/v2/_catalog 

      You can also use the http://localhost:5000/v2/_catalog URL to verify using a browser. 

Where to go from here?

After completing the pre-upgrade tasks, you can now start Performing-the-upgrade.