Bug 4952 - agent hostname translation prevents having same config on entire cluster
Summary: agent hostname translation prevents having same config on entire cluster
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: VSM Server (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: LowPrio
Assignee: Peter Åstrand
Depends on:
Reported: 2014-01-07 13:31 CET by Pierre Ossman
Modified: 2022-06-08 10:05 CEST (History)
0 users

See Also:
Acceptance Criteria:


Description Pierre Ossman cendio 2014-01-07 13:31:36 CET
Because of issue with NAT, multihoming, and such things, we have a translation system from the name in /vsmserver/terminalservers to the name the client actually tries to connect to. Right now that translation is stored as /vsmagent/agent_hostname on each agent.

This system has the effect that vsmagent.hconf cannot be synced across a cluster. It also means more information needs to be transferred across the network between the agents and the master. The information also needs to be properly updated when configuration changes.

We'd like to fix these issues by moving the translation to the master instead. So something like this:


There are a lot of related issues that should be considered at the same time:

 - Should we still have terminalservers, or let these translation entries specify agents?

 - Should tlwebaccess have a more complex system, based on URIs.

 - How should agents be identified? (bug 4256)

 - Port redirection (bug 3003 and bug 3161)

 - IPv6 (bug 2672)

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