Skip to content

System Requirements

The following section outlines how the system requirements for installing CAS Manager in Production and Testing modes.

System Requirements for Production Mode

There are certain prerequisite steps and processes that need to be undertaken and system requirements that need to be met, before installing the CAS Manager in Production mode:

  1. Prepare the target virtual machine that CAS Manager will be installed on.

    • System Requirements

      • You need to prepare a virtual machine that has the following requirements:
        • Operating System: CentOS 8 or RHEL 8
        • Minimum 8 GB RAM
        • 4 CPU
        • 60 GB Storage: If you are using LVM and /var is mounted on a separate volume, that volume must have 30GB or more in order for the installation to succeed and for CAS Manager to function properly.
    • Firewall Configuration

      • Ensure port 443 is enabled in the firewall rules for the VM that CAS Manager is running on.
      • Configure the firewall for the virtual network CAS Manager is running on within the virtual machine by following the commands below:

        • Check and confirm if firewalld is active by running the following command:
          sudo systemctl status firewalld
          
        • If firewalld is active, follow the steps outlined below for firewall configuration. If firewalld is inactive, and your organization does not require firewall on the CAS Manager VM, then skip the firewall configuration steps below and proceed to the remaining steps.
        • Run the following commands to configure the firewall:
          sudo firewall-cmd --permanent --add-port=6443/tcp # virtual network flannel
          sudo firewall-cmd --permanent --zone=trusted --add-source=10.42.0.0/16 # This subnet is for the pods
          sudo firewall-cmd --permanent --zone=trusted --add-source=10.43.0.0/16 # This subnet is for the services
          sudo firewall-cmd --reload
          
    • Proxy Configuration

      • If HTTP/HTTPS proxy is used, then HTTP_PROXY, HTTPS_PROXY and NO_PROXY must be set. For NO_PROXY, specific IP addresses or domain names of service that are internal must be added. IP address ranges like "10.0.0.0/8" will not work; exact IP addresses or domain names must be used for NO_PROXY for the traffic to be routed through the proxy to work properly. The outlined variables need to be set in the /etc/environment file. The following steps outline how to modify this file to add these variables.

      • Run the following command to display the /etc/environment/ file in the editor:

        sudo vi /etc/environment
        

      • Update the file to include the following environment variables:
        • HTTPS_PROXY=”http://hostname_of_proxy:[port]”
        • HTTP_PROXY=”http://hostname_of_proxy:[port]”
        • NO_PROXY= [list of all host names that should not go through the proxy, such as: localhost, 127.0.0.1, 0.0.0.0, ip_address_of_mongo]
        • ALL_PROXY=”http://hostname_of_proxy:[port]”
        • https_proxy=”http:// hostname_of_proxy:[port]”
        • http_proxy=”http:// hostname_of_proxy:[port]”
        • no_proxy=”= [list of all host names that should not go through the proxy, such as: localhost, 127.0.0.1, 0.0.0.0, ip_address_of_mongo]
        • all_proxy=”http:// hostname_of_proxy:[port]”
      • Save the file. In order for these changes to take effect, a new ssh/shell terminal needs to be established. From this new terminal, proceed with the installation steps. The proxy configuration will be implemented when CAS Manager is installed.
  2. A Cloud Access Software registration code: Once you have a Cloud Access Software subscription Teradici will email a registration code to you.

  3. A MongoDB instance that will be used for CAS Manager data storage. For best practices and guidelines around deploying a MongoDB with CAS Manager, see Installing for Production. Teradici provides configuration template files and parameters that can be generated and used when configuring CAS Manager to use your MongoDB, see Configuration Template Files and Parameters. CAS Manager cannot currently connect to an external MongoDB from behind a proxy.
  4. You need to have an external Vault installed and set-up. For information on how to set-up a production Vault deployment with CAS Manager, see Installing for Production. Teradici provides configuration template files and parameters that can be generated and used when configuring your Vault server, see Configuration Template Files and Parameters.

Installing CAS Manager in AWS

If you are installing CAS Manager in AWS, and if your /var is mounted on a different virtual machine with less than 30GB of disk space, you must ensure that you have increased the /var. For information on how to do this with Ubuntu, see Resize OS Disk - Ubuntu.

System Requirements for Testing Mode

There are certain prerequisite steps and processes that need to be undertaken and system requirements that need to be met, before installing the CAS Manager in Testing mode:

  1. Prepare the target virtual machine that CAS Manager will be installed on.

    • System Requirements

      • You need to prepare a virtual machine that has the following requirements:
        • Operating System: CentOS 8 or RHEL 8
        • Minimum 8 GB RAM
        • 4 CPU
        • 60 GB Storage: If you are using LVM and /var is mounted on a separate volume, that volume must have 30GB or more in order for the installation to succeed and for CAS Manager to function properly.
    • Firewall Configuration

      • Ensure port 443 is enabled in the firewall rules for the VM that CAS Manager is running on.
      • Configure the firewall for the virtual network CAS Manager is running on within the virtual machine by following the commands below:

        • Check and confirm if firewalld is active by running the following command:
          sudo systemctl status firewalld
          
        • If firewalld is active, follow the steps outlined below for firewall configuration. If firewalld is inactive, and your organization does not require firewall on the CAS Manager VM, then skip the firewall configuration steps below and proceed to the remaining steps.
        • Run the following commands to configure the firewall:
          sudo firewall-cmd --permanent --add-port=6443/tcp # virtual network flannel
          sudo firewall-cmd --permanent --zone=trusted --add-source=10.42.0.0/16 # This subnet is for the pods
          sudo firewall-cmd --permanent --zone=trusted --add-source=10.43.0.0/16 # This subnet is for the services
          sudo firewall-cmd --reload
          
    • Proxy Configuration

      • If HTTP/HTTPS proxy is used, then HTTP_PROXY, HTTPS_PROXY and NO_PROXY must be set. For NO_PROXY, specific IP addresses or domain names of service that are internal must be added. IP address ranges like "10.0.0.0/8" will not work; exact IP addresses or domain names must be used for NO_PROXY for the traffic to be routed through the proxy to work properly. The outlined variables need to be set in the /etc/environment file. The following steps outline how to modify this file to add these variables.

      • Run the following command to display the /etc/environment/ file in the editor:

        sudo vi /etc/environment
        

      • Update the file to include the following environment variables:
        • HTTPS_PROXY=”http://hostname_of_proxy:[port]”
        • HTTP_PROXY=”http://hostname_of_proxy:[port]”
        • NO_PROXY= [list of all host names that should not go through the proxy, such as: localhost, 127.0.0.1, 0.0.0.0, ip_address_of_mongo]
        • ALL_PROXY=”http://hostname_of_proxy:[port]”
        • https_proxy=”http:// hostname_of_proxy:[port]”
        • http_proxy=”http:// hostname_of_proxy:[port]”
        • no_proxy=”= [list of all host names that should not go through the proxy, such as: localhost, 127.0.0.1, 0.0.0.0, ip_address_of_mongo]
        • all_proxy=”http:// hostname_of_proxy:[port]”
      • Save the file. Once you install CAS Manager you can configure it to use the proxy configuration. From this new terminal, proceed with the installation steps. The proxy configuration will be implemented when CAS Manager is installed.
  2. A Cloud Access Software registration code: Once you have a Cloud Access Software subscription Teradici will email a registration code to you.

Installing CAS Manager in AWS

If you are installing CAS Manager in AWS, and if your /var is mounted on a different virtual machine with less than 30GB of disk space, you must ensure that you have increased the /var. For information on how to do this with Ubuntu, see Resize OS Disk - Ubuntu.