Bug 8217 - Unclear if agent can belong to multiple subclusters
Summary: Unclear if agent can belong to multiple subclusters
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: VSM Server (show other bugs)
Target Milestone: LowPrio
Assignee: Bugzilla mail exporter
Depends on:
Reported: 2023-08-30 15:12 CEST by Samuel Mannehed
Modified: 2023-09-05 13:11 CEST (History)
0 users

See Also:
Acceptance Criteria:


Description Samuel Mannehed cendio 2023-08-30 15:12:30 CEST
Our documentation doesn't mention whether it is allowed to configure the same agent in multiple subclusters: 


Configuring ThinLinc this way can be useful in the following scenario for example:

* Admin has limited resources and has two agent servers
* The agents are identical apart from one application which, due to cost, is only licensed for one machine
* Only a few specific users need access to the licensed application

The admin could then wish to configure the default subcluster to contain both agents. Alongside the default one, he wishes to set up a different subcluster for the agent with the licensed application, this time with specific user associations. Such a setup could guarantee that the licensed application users would always end up on the correct agent.

We print warnings in vsmserver.log when the master is configured like this:

> 2023-08-30 14:20:51 WARNING vsmserver.loadinfo: Agent 'agent01' is assigned to 2 subclusters
> 2023-08-30 14:20:51 WARNING vsmserver.loadinfo: Agent 'agent01' found in multiple subclusters: Default, SpecialSoftware

However, looking at the current logic in the code, I believe things will work.

Note You need to log in before you can comment on or make changes to this bug.