Single Server Upgrade

Warning

When running any upgrade please ensure there are no active Kasm Workspaces sessions running. On large deployments this will likely require a maintenance window.

Note

While not required, making a backup using a VM snapshot or other method of the server is recommended as a precaution to provide a recovery point if something goes wrong.

Automated Upgrade

The automated upgrade script can be used to upgrade a previous installation to 1.15.0 .

Administrators have several options to choose from when running the automated upgrade script:

Flag                                        Description
---------------------------------------------------------------------------------------------------------------
| -h|--help                     | Display this help menu                                                      |
| -L|--proxy-port               | Default Proxy Listening Port                                                |
| -s|--offline-service          | Path to the tar.gz service images offline installer                         |
| -S|--role                     | Role to Upgrade: [app|db|agent|remote_db|guac|proxy]                        |
| -p|--public-hostname          | Agent/Component <IP/Hostname> used to register with deployment.             |
| -g|--database-master-user     | Database master username required for remote DB                             |
| -G|--database-master-password | Database master password required for remote DB                             |
| -q|--db-hostname              | Database Hostname needed when upgrading agent and pulling images            |
| -T|--db-port                  | Database port needed when upgrading agent and pulling images (default 5432) |
| -Q|--db-password              | Database Password needed when upgrading agent and pulling images            |
| -b|--no-check-disk            | Do not check disk space                                                     |
| -n|--api-hostname             | Set API server hostname                                                     |
| -A|--enable-lossless          | Enable lossless streaming option (1.12 and above)                           |
| -O|--use-rolling-images       | Use rolling Service images                                                  |
| -k|--registration-token       | Register a component with an existing deployment.                           |
| --slim-images                 | Use slim alpine based service containers                                    |
---------------------------------------------------------------------------------------------------------------

In this example --proxy-port is used.

cd /tmp
curl -O https://kasm-static-content.s3.amazonaws.com/kasm_release_1.15.0.06fdc8.tar.gz
tar -xf kasm_release_1.15.0.06fdc8.tar.gz
sudo bash kasm_release/upgrade.sh --proxy-port 443

cd /tmp
curl -O https://kasm-static-content.s3.amazonaws.com/kasm_release_1.15.0.06fdc8.tar.gz
curl -O https://kasm-static-content.s3.amazonaws.com/kasm_release_service_images_amd64_1.15.0.06fdc8.tar.gz
curl -O https://kasm-static-content.s3.amazonaws.com/kasm_release_workspace_images_amd64_1.15.0.06fdc8.tar.gz
tar -xf kasm_release_1.15.0.06fdc8.tar.gz
sudo bash kasm_release/upgrade.sh --proxy-port 443 --offline-service /tmp/kasm_release_service_images_amd64_1.15.0.06fdc8.tar.gz

cd /tmp
curl -O https://kasm-static-content.s3.amazonaws.com/kasm_release_1.15.0.06fdc8.tar.gz
curl -O https://kasm-static-content.s3.amazonaws.com/kasm_release_service_images_arm64_1.15.0.06fdc8.tar.gz
curl -O https://kasm-static-content.s3.amazonaws.com/kasm_release_workspace_images_arm64_1.15.0.06fdc8.tar.gz
tar -xf kasm_release_1.15.0.06fdc8.tar.gz
sudo bash kasm_release/upgrade.sh --proxy-port 443 --offline-service /tmp/kasm_release_service_images_arm64_1.15.0.06fdc8.tar.gz

Automatic Upgrade Troubleshooting

The upgrade.sh script creates a log file as it runs, this file is removed upon completion of a successful upgrade. However, if something does go wrong the logfile will be available from the directory the upgrade.sh script was executed from in the format kasm_upgrade_${TIMESTAMP}.log. This file will be important for diagnosing the error that caused the upgrade to fail and will be requested when submitting a support ticket with Kasm Technologies.

Manual Upgrade

Kasm Tech recommends installing a separate instance of the application, migrating the data and performing a cutover of the application.

Please read through the entire process before getting started.

Warning

The Kasm Workspaces 1.15.0 upgrade will optionally install a new set of default desktop and application images. Please ensure 50GB of free space is available on the Kasm server ( or Agent role server for multi-server installations) prior to upgrading if selecting the options to seed new images.

Create a Database Backup

Backup the existing Kasm database. This can be saved for later recovery, but will also be used to migrate existing data to the latest version.

Stop existing Kasm Services

sudo /opt/kasm/bin/stop

Execute the database backup utility

sudo mkdir -p /opt/kasm/backups/
sudo bash /opt/kasm/1.14.0/bin/utils/db_backup -f /opt/kasm/backups/kasm_db_backup.tar -p /opt/kasm/1.14.0/

Verify the presence and location of the database backup

sudo ls -al /opt/kasm/backups/kasm_db_backup.tar

Note

When performing an offline upgrade please ensure that versions of docker and docker compose that meet the updated system requirements have been downloaded and installed see System Requirements for details.

Download and extract the new installation media

cd /tmp
curl -O https://kasm-static-content.s3.amazonaws.com/kasm_release_1.15.0.06fdc8.tar.gz
tar -xf kasm_release_*.tar.gz

Get the existing database password for use in the subsequent commands.

sudo grep " password" /opt/kasm/1.14.0/conf/app/api.app.config.yaml

Get the existing manager token for use in the subsequent commands.

sudo grep "token" /opt/kasm/1.14.0/conf/app/agent.app.config.yaml

Perform a clean install

Install kasm from the release media downloaded in the prior steps.
- When performing an offline update add these flags --offline-service <KASM_SERVICE_IMAGES_TAR>

sudo bash kasm_release/install.sh -D -Q <DATABASE_PASSWORD> -M <MANAGER_TOKEN>

Modify Configs

Copy the server_id and the public_hostname properties from the old agent to the new

grep server_id /opt/kasm/1.14.0/conf/app/agent.app.config.yaml
grep public_hostname /opt/kasm/1.14.0/conf/app/agent.app.config.yaml
sudo vi /opt/kasm/1.15.0/conf/app/agent.app.config.yaml

Copy manager_id and server_hostname from the old configuration into the new

grep manager_id /opt/kasm/1.14.0/conf/app/api.app.config.yaml
grep server_hostname /opt/kasm/1.14.0/conf/app/api.app.config.yaml
sudo vi /opt/kasm/1.15.0/conf/app/api.app.config.yaml

Copy the auto-generated nginx configs for any sessions that may exist on the Agent

sudo cp /opt/kasm/1.14.0/conf/nginx/containers.d/* /opt/kasm/1.15.0/conf/nginx/containers.d/

Copy the id and the token properties from the old connection_proxy to the new
- The token field of kasmguac.app.config.yaml has been renamed to auth_token in the Kasm Workspaces 1.13.0 release

grep id /opt/kasm/1.14.0/conf/app/kasmguac.app.config.yaml
grep token /opt/kasm/1.14.0/conf/app/kasmguac.app.config.yaml
sudo vi /opt/kasm/1.15.0/conf/app/kasmguac.app.config.yaml

Restoring the Database.

Restore and update the database from the prior version

Ensure all Kasm services are stopped

sudo /opt/kasm/bin/stop

Execute the database restore command

sudo /opt/kasm/1.15.0/bin/utils/db_restore -f /opt/kasm/backups/kasm_db_backup.tar -p  /opt/kasm/1.15.0

Perform an upgrade of the database schema

sudo /opt/kasm/1.15.0/bin/utils/db_upgrade -p /opt/kasm/1.15.0

(Optional) Install the Kasm 1.15.0 default images for the platform
- With Kasm Workspaces 1.13.0 and newer the Kasm team recommends using the Workspaces Registry to install Workspaces rather than seeding the images during the installation.
- Seeding workspaces is still needed when doing an offline Kasm installation as the official Kasm Workspaces Registry will be unavailable.
- If doing an offline upgrade first extract the default image seed data from the workspace images tar.
  
  For x86 (amd64) platforms:
```
tar xf <KASM_WORKSPACE_IMAGES_TAR> --strip-components=1 -C /opt/kasm/1.15.0/conf/database/seed_data/ workspace_images/default_images_amd64.yaml
```
  For ARM (arm64) platforms:
```
tar xf <KASM_WORKSPACE_IMAGES_TAR> --strip-components=1 -C /opt/kasm/1.15.0/conf/database/seed_data/ workspace_images/default_images_arm64.yaml
```

For x86 (amd64) platforms:

sudo /opt/kasm/1.15.0/bin/utils/db_init -s /opt/kasm/1.15.0/conf/database/seed_data/default_images_amd64.yaml

For ARM (arm64) platforms:

sudo /opt/kasm/1.15.0/bin/utils/db_init -s /opt/kasm/1.15.0/conf/database/seed_data/default_images_arm64.yaml

Start the Kasm services

sudo /opt/kasm/bin/start

Add Connection Proxy Settings to Database

When upgrading from a version <= 1.11.0 to >= 1.12.0 add connection proxy settings to the database:

sudo /opt/kasm/1.15.0/bin/utils/db_init -s /opt/kasm/1.15.0/conf/database/seed_data/default_connection_proxies.yaml

Start the Kasm services

sudo /opt/kasm/bin/start

Update Custom Workspaces

Each release, the Kasm Technologies team updates the default workspaces with new features and security updates. Old workspaces should be removed as they may not be compatible with new Kasm features.

Note

Kasm Workspaces 1.13.0 and newer utilize a Workspaces Registry to install new Workspaces after upgrade. Upon logging into Kasm Workspaces for the first time after the upgrade the administrator will have the opportunity to add the default Kasm Workspaces registry if the administrator has not already configured it.

Workspaces from prior releases may contain incompatible features and are not guaranteed to work. Kasm recommends that the administrator utilize the registry to add the latest compatible Workspaces for the installed version.

Kasm recommends rebuilding any custom Workspaces using the appropriately tagged Docker image (e.g : kasmweb/core-ubuntu-focal:1.15.0 ) see creating custom Kasm images for more information.

See Default and Custom Docker Images for details.

For existing Workspaces officially supported by Kasm, it is possible to edit the Workspace configuration and change the tag to the new version of Kasm Workspaces, this will preserve configuration and group settings that may already have been added. It will take a few minutes for the Kasm Agent to download the new Workspace during which time it will be unavailable.