Upgrading Anyware Manager (Online Upgrade)
When upgrading Anyware Manager there are two options available.
- In-place upgrade within the maintenance window: You can run an in-place upgrade through dnf for Anyware Manager. Depending on the configuration you implemented, this will mean a period of downtime which can range from a few seconds to a few minutes.
- Zero downtime upgrade via a new VM. The second option involves installing Anyware Manager on a new virtual machine, and configuring it to connect to the same external database and secret storage. If done correctly this can result in zero downtime.
The steps involved in both options are outlined below.
Which Option Should I Choose?¶
The upgrade option you choose depends on the amount of downtime you are willing to experience and how your Anyware Manager instance has been deployed and setup. The following are some use cases that outline which option to use:
- If you have a single Anyware Manager server connecting to external database and secret storage, it is recommended to install Anyware Manager on a new virtual machine. If you don't have a new virtual machine then run the in-place upgrade on the existing virtual machine with the understanding that there will be some downtime during this upgrade.
- If you have multiple Anyware Manager servers connecting to the same external database and secret storage, it is recommended to run an in-place upgrade on each Anyware Manager server, one at a time. There should not be any downtime as long as one Anyware Manager server is up and running.
- If the database and secret storage is on the same virtual machine as Anyware Manager, you must run an in-place upgrade. This is to ensure that the data persists after the upgrade has been completed. There will be some downtime during this upgrade.
Running an In-Place Upgrade¶
Anyware Manager Downtime
The Anyware Manager virtual machine that is undergoing an in-place upgrade will not be available during the upgrade. This can take anywhere from a few seconds to a few minutes, depending on the number of services that need to be upgraded and the speed of download when retrieving new versions from the repo. If this is the only Anyware Manager server you have, the new connections will not be established until the upgrade is completed successfully.
Anyware Manager Repositories
The new repository
teradici-anyware-manager is introduced. If you currently have
teradici-cas-manager repository, you must remove it. See Repository Management to remove them. Once the unwanted repos are removed, you can proceed with the update process.
1. Add Anyware Manager dnf Repository¶
- SSH to the Anyware Manager virtual machine.
Remove the existing dnf repo for previous CAS Manager with the following command.
sudo rm /etc/yum.repos.d/teradici-cas-manager.repo
Check that the repos are removed
dnf repolist --enabled teradici-cas-manager*
To access the scripts and to configure and add the RHEL and Rocky Linux repository, select the Downloads and scripts option from the Anyware Manager support site.
If you see a login button instead, click it to log into the site and then proceed.
Accept the End User License Agreement, then click Set Up Repository.
The window will expand and show the setup scripts for each supported operating system. Copy the command for your system to the clipboard.
Paste command on the target machine where you wish to install Anyware Manager and press
The command fetches a configuration script from our servers and runs it locally, setting up and configuring the repository on the local machine.
Run the following command to confirm
teradici-anyware-manager repos were added into dnf repo.
dnf repolist --enabled teradici-anyware-manager*
The output from this command should list the repo id, names as outlined in the example below:
repo id repo name teradici-anyware-manager-beta teradici-anyware-manager-beta teradici-anyware-manager-beta-noarch teradici-anyware-manager-beta-noarch teradici-anyware-manager-beta-source teradici-anyware-manager-beta-source
2. Upgrade Anyware Manager via dnf¶
To upgrade CAS Manager 22.04 or prior to Anyware Manager, transitional steps are required so that Anyware Manager can recognize CAS Manager as the predecessor instead of thinking Anyware Manager is in conflict. Otherwise, you would see an error message as shown below:
Please follow the steps below to upgrade from CAS Manager 22.04 or prior versions:
Upgrade CAS Manager 22.04 RPM or prior to CAS Manager 22.07.0 RPM, which is the transitional version, by running the following command:
sudo dnf install cas-manager-22.07.0
Install latest version of Anyware Manager RPM by running the following command:
sudo dnf install anyware-manager
Upgrade to Anyware Manager by running the following command:
sudo /usr/local/bin/anyware-manager upgrade
If you want to use a different manifest than the default one, please add
--manifest and the path to your manifest.
sudo /usr/local/bin/anyware-manager upgrade --manifest path-to-manifest.tar.gz
Installing Anyware Manager on a new Virtual Machine¶
The following steps outline how to install Anyware Manager on a new virtual machine, and configure it to connect to the same external database and secret storage application:
- Before performing an upgrade you should backup the database and secret storage application you used when installing Anyware Manager. If you intend to install Anyware Manager on a new virtual machine, backup the configuration file so that it can be used on the Anyware Manager instance.
- Follow the installation steps outlined here to install a new instance of Anyware Manager in a new virtual machine to replace the existing one. You must configure it to be identical to the old Anyware Manager instance. It needs to connect to the same MongoDB, and secret storage application, as well as having the same certificate and network configurations.
- Change your DNS to point to the new Anyware Manager instance.
Reconfigure your Connector to connect to the new Anyware Manager if necessary:
If you installed your Connector with
- Change your DNS entry for the FQDN to point to the new Anyware Manager's static IP.
In the Connector virtual machine, flush the DNS cache to use the latest DNS. This ensures that there will be zero downtime as the Connector will be able to connect to the new Anyware Manager instance:
sudo systemd-resolve --flush-caches
If you installed your Connector with
- Update your Connector to use the latest Anyware Manager's IP address.
Log into the Connector virtual machine and run the following command to update the Anyware Manager IP:
sudo usr/sbin/cloud-access-connector update --manager-url https://<New Anyware-Manager IP>
In the Connector, ping the FQDN to verify it can find the new Anyware Manager instance.
- Remove the old Anyware Manager virtual machine.
Removing the Anyware Manager Virtual Machine¶
The following steps outline how to remove the Anyware Manager virtual machine:
- Save the configuration setting files used in the current version of Anyware Manager. For example, save them as a all-configurations.json file. If the current Anyware Manager has proxy configured, save all the proxy environment variables also.
Run the following commands to remove the Anyware Manager.
sudo dnf remove -y anyware-manager-selinux anyware-manager sudo rm -rf /opt/teradici/casm # Remove the cas-manager files
Delete the Anyware Manager VM.