Cluster module

The cluster module contains information about the ThinLinc cluster, and allows managing of subclusters and agents.

  • Subclusters allows viewing, adding, modifying or deleting subclusters.

  • Agents allows adjusting agent settings for the cluster.

Subclusters

On this page, the configured subclusters of the ThinLinc master can be found. Subclusters are groups of agents that can be associated with users or groups. Adding, modifying or deleting existing subclusters is possible. A restart of the vsmserver service is required after changes to subcluster configuration in order for the changes to take effect. A toast will be shown after saving, facilitating a service restart.

The page will present a list of currently configured subclusters. This should be something like the example in Fig. 25. To edit a subcluster, click on its name in the list.

_images/tlwebadm-subcluster-list.svg

Fig. 25 Subclusters

Fig. 25 shows a system with a total of two subclusters. The subcluster called default is configured with two agent servers and US_cluster is configured with one agent.

To add a new subcluster to the list, press the Add new subcluster button. This will bring up an empty subcluster edit pop-up. See figure Fig. 26 for an example.

_images/tlwebadm-subcluster-new.svg

Fig. 26 New subcluster pop-up

There are five editable fields in this view: Subcluster, Agents, Users, Groups and Limit sessions. The first field controls the name of the subcluster. The rest are described in Parameters in /subclusters/. To save changes, press the Save button.

Agents

On this page, it is possible to configure the weight of agents, and the draining of sessions on agents. The weights allow adjusting the distribution of users across agents in the cluster. Enabling draining for an agent prevents new sessions from being created on that agent.

A restart of the vsmserver service is required after changes to weight or draining configuration in order for the changes to take effect. A toast will be shown after saving, facilitating a service restart.

The page will present two lists as shown in Fig. 27. The first consists of currently configured agents along with its weight. The details on how the weight works is described in Parameters in /agents/. The second list consists of configured agents along with toggles for enabling draining of each agent. See Stopping new session creation on select agents in a cluster for details on draining agents.

_images/tlwebadm-subcluster-agents.svg

Fig. 27 Agent configuration