Skip to content

Installing for Testing

The following section outlines how to install the Testing mode of the CAS Manager.

Proof of Concept and Testing Only

This mode is recommended for testing and proof of concept purposes only. This mode installs all the external components such as Mongo DB and a storage Vault on the same virtual machine as CAS Manager.

  • This mode does not scale beyond a single CAS Manager instance and does not support high availability.
  • This mode is not to be used in production environments.
  • By default, CAS Manager will be installed in Testing mode. In this mode CAS Manager will use an internal Vault and MongoDB, and will generate self-signed TLS certificates to use for it's gatway.
  • CAS Manager is considered to be in Production mode when it is configured to use an external Vault and MongoDB. To deploy CAS Manager in Production mode, see Installing for Production.
  • It will take roughly 45 minutes to complete the installation in this mode.

Prerequisite Configurations

The following sections outline the process from start to finish, to install CAS Manager in Testing Mode. It includes all prerequisite steps.

Risk of Data Loss

CAS Manager does not do any data migration when updating Vault/MongoDB configuration. Any data stored when CAS Manager is used in Testing mode will not be transferred if the same CAS Manager instance is updated to run in Production mode.

System Requirements and Prerequisite Steps

Before installing CAS Manager please ensure you have read through the system requirements, and configured the necessary prerequisites outlined in the sections below. Failure to do this will result in an unsuccessful installation of CAS Manager.

1. System Requirements

For information on the minimum system requirements for installing CAS Manager in Testing mode, see System Requirements.

Installing CAS Manager

The following section outlines how to install CAS Manager in the Proof of Concept mode. These steps should be performed on the target machine by connecting via SSH or console.

System Requirements and Prerequisite Steps

Before installing CAS Manager please ensure you have read through the system requirements, and configured the necessary prerequisites outlined in the sections above. Failure to do this will result in an unsuccessful installation of CAS Manager.

3. Add CAS Manager Repository

The virtual machine you are adding the repo to must have access to the internet. If it doesn't, you will be unable to download and install the required files.

Run the following command to add the CAS Manager repository:

curl -1sLf \
  'https://dl.teradici.com/502R0tFrirxlgmRy/cas-manager/setup.rpm.sh' \
  | sudo -E distro=el codename=7 bash

3. SELinux Configuration

SELinux policies are required for persistent storage and container logging on CAS Manager. If SELinux policies are not found, data stored in CAS Manager will be lost when the CAS Manager Machine is shut down.

Once configured, and the installation has verified SELinux, all CAS Manager related data will persist when the target machine hosting CAS Manager is re-booted.

  1. To install the SELinux policies and set the basic framework for persistent database and Vault, run the following command:

    sudo yum install -y selinux-policy-base container-selinux
    
  2. To install a specific version of SELinux that has been tested for K3s, run the following command:

    sudo yum install https://github.com/k3s-io/k3s-selinux/releases/download/v0.2.stable.1/k3s-selinux-0.2-1.el7_8.noarch.rpm
    
  3. To install CAS Manager SELinux from the CAS Manager repo, run the following command:

    sudo yum install -y cas-manager-selinux
    

Non-Persistent Storage

If persistent storage is not required, set SELinux to permissive by running setenforce 0 with sudo / as root before beginning the install.

4. Install CAS Manager

Run the following command to install CAS Manager:

sudo yum install -y cas-manager
The installer will install CAS Manager, as well as all external components required. These external components are:

  • k3s
  • Mongo database
  • Secret Store (HashiCorp Vault)
  • A self-signed SSL certificate for HTTPS access

Vault Data Encryption

The Vault data that is installed as part of the CAS Manager installation, is installed on the CAS Manager virtual machine, and is encrypted at rest. It is recommended that you take appropriate measures to secure access to the filesystem. For information on this, see the Filesystem Storage Backend section of the HashiCorp Vault guide.

Installer Health Check

Towards the end of the installation, the installer will check the CAS Manager's health status. This health check is part of the installation process. This health check takes about 15 minutes to complete.

If the installation appears unhealthy you should generate a support bundle and send this to Teradici for investigation. For more information on generating a support bundle, see Support Bundle. For more information on monitoring and assessing the health status of CAS Manager, see Health Status.

Once the installation has been successful you should see the following message: Alt Text

Generated Credentials

The installer will automatically generate a password. This password is important as it will be required when accessing the Admin Console. This password can be found in the temp-creds.txt file which is located at /opt/teradici/casm/temp-creds.txt. This location will be displayed in the CLI window once the the installation has been successful, as seen in the image above.

If you are using a proxy in your network, you must ensure you have enabled the proxy settings on CAS Manager.

5. Proxy Configuration

If the proxy environment variables were not set before installing CAS Manager, please see the System Requirements section for the steps involved in setting these variables. If you have already set your proxy configuration prior to installing CAS Manager, you do not need to run the command below.

If you have installed CAS Manager and have not configured the environment variables for the proxy, follow the steps below:

  1. From the CAS Manager virtual machine set the environment variables HTTPS_PROXY, HTTP_PROXY, ALL_PROXY and NO_PROXY in the /etc/environment file.
  2. Establish a new ssh/shell session.
  3. Configure CAS Manager to use the proxy configuration by running the following command:
    sudo /usr/local/bin/cas-manager update -–enable-proxy
    

6. Access the Admin Console

The following section outlines how to access and unlock the Admin Console.

  1. Open a web browser and navigate to https://{public-or-private-ip-address-of-cas-manager}. This is the external IP address of the target machine that CAS Manager has been installed on. You will be presented with the CAS Manager login page. Alt Text
  2. Use the following credentials to begin setting up the admin user:
    • username: adminUser
    • password: The password generated by the installer. This password can be found in the temp-creds.txt file which is located at /opt/teradici/casm/temp-creds.txt. You can run the following command to view the password:
      sudo cat /opt/teradici/casm/temp-creds.txt
      
  3. Upon successful login, you will be required to immediately change this password. Alt Text After updating the password you will be able to use CAS Manager as the adminUser user.

For further information on using the Admin Console, see Admin Console.

Installing the Cloud Access Connector

Once you have installed the CAS Manager you can install Cloud Access Connector(s) by following the instructions outlined in the Installing the Cloud Access Connector section.