Skip to content

Upgrading CAS Manager

To upgrade CAS Manager, you must either install CAS Manager on a new VM and configure it to connect to the same external database and Vault, or reinstall CAS Manager in the same VM. The steps involved in both options are outlined below.

Applicable for Production Mode Only

These upgrade methods are only supported if CAS Manager is in production mode. In this mode, no data will be lost as the data is stored in external Vault and MongoDB. If CAS Manager is running in PoC mode, all of the data will be lost when the instance is removed.

Install CAS Manager on a new VM

The following steps outline how to install CAS Manager on a new VM, and configure it to connect to the same external database and Vault:

  1. Follow the installation steps outlined here to install a new instance of CAS Manager in a new VM to replace the existing one. You must configure it to be identical to the old CAS Manager. It needs to connect to the same MongoDB and Vault, and have the same certificate and network configurations.
  2. Change your DNS to point to the new CAS Manager instance.
  3. Reconfigure your Cloud Access Connector to connect to the new CAS Manager:
    • If you installed your Cloud Access Connector with --cam-url=FQDN of CAS-M then change your DNS for the latest CAS Manager to also point to the same FQDN.
    • If you installed your Cloud Access Connector with --cam-url=https://ip-address-of-cas-manager then update your Cloud Access Connector to use the latest CAS Manager's IP address. Log into the Cloud Access Connector VM and run the following command to update the CAS Manager IP:
      sudo usr/sbin/cloud-access-connector update --cam-url https://<New CAS-Manager IP>
      
  4. In the Cloud Access Connector, ping the FQDN to verify it can find the new CAS Manager instance.
  5. Remove the old CAS Manager VM.

Re-Install CAS Manager on the same VM

Potential Down-Time

Re-installing CAS Manager on the same VM will introduce down-time if this is the only CAS Manager instance. To minimize this down-time, install in a new VM or have high availability CAS Manager instances available using a load balancer.

The following steps outline how to remove and re-install CAS Manager, and reconfigure the new CAS Manager instance to be identical to the current instance on the same VM:

  1. Save the configuration files used in the current version of CAS Manager. For example, save them as a all-configurations.json file. If the current CAS Manager has proxy configured, save all the proxy environment variables also.
  2. Run the following commands to remove the K3s and CAS Manager:
    sudo yum remove -y cas-manager
    sudo yum remove -y cas-manager-k3s # to cleanup CAS-Manager containers.
    sudo rm -rf /opt/teradici     # Remove the cas-manager files
    
  3. Re-install CAS Manager:
    sudo yum install -y cas-manager
    
  4. Update the new CAS Manager instance to use the configurations that were used by the old CAS Manager instance. You saved these configurations in step 1:
    sudo /usr/local/bin/cas-manager update --config-file all-configurations.json
    
  5. If proxy is used, enable proxy by running the following command:
    sudo /usr/local/bin/cas-manager update --enable-proxy