The agent is responsible for provisioning instances of end user containers – Kasms when requested via the web application. The Agent reports the available system resources to the manager. These Agents are represented in the Servers tab in the Administration tab of the web application. This service automatically downloads all Kasm Images defined within the application so they are available to provision new Kasms on demand.
The Kasm server uses a Postgres Database to keep track of application data. The Docker container kasm_db holds this database.
(container: kasmweb/desktop) The default base desktop configuration based on ubuntu 16.04. This base image contains all the necessary configurations to allow this container to function within the Kasm ecosystem. All additional images are based off this base image
- Desktop Deluxe
(container: kasmweb/desktop-deluxe) Kasm image that is based off of the desktop container. An example custom configuration that provides additional productivity software.
- Deployment Zone
For large or complex installations, multiple sets of Agents and Managers may be deployed in different logical or geographically areas, or “Zones”.
Docker is the platform from which we create and receive containers. More information can be found at Docker’s Homepage
(container: kasmweb/firefox) Kasm image that is based off of the desktop container. An example of hosting a single application. In this example the popular Firefox browser is used.
Any number of Images can be registered via the web application and can be customized by the administrator to add additional software and configurations. The administrator can also configure the CPU, memory and network resources available to each Image via the Image Settings.
By default several Images are installed and registered. See Default Images for a list.
- Installation ID
The Installation ID is the key generated by the specific Server installation. It is used for licensing the Kasm Server. It can be found in the System Info tab on the navigation menu.
End users request to create Kasms that are on-demand instances of Images registered in the application. These instances are provisioned by and on the Agent These containers house the desktop or application presented to the end user via the web application.
This container, based on nginx, is used to forward traffic to the correct service container. The Docker container kasm_proxy holds the nginx configuration.
The Kasm server uses a Redis database to synchronize the share chat functionality.
- Web Application
This is the user interface for the kasm server. It is usually hosted on the selected domain on port 443 for https traffic. It contains all of the tabs needed for use and administration of the server