[Thinlinc-technical] Forcing sessions for some users to certain agent hosts

[Rob De Langhe]

  Philippe,

since my users are not related to each other (and not trustworthy collegues
;-) ) I wanted them to fully isolated from each other : I create individual
agents for each and every user, using a standard Ubuntu container as
reference , then cloning and customizing this container into new containers
for each user. Takes about 1 minute to complete.

Home-dirs come from a shared NFS cluster, who has a ZFS filesystem per
user.

The master is configured then with "agentname:username" pairs so redirect
each user to his personal agent host.

Load-balancing users across agents is no longer relevant of course.

And users are found by all servers through a common LDAP service, I
understood that it's only the agent who needs to be able to authenticate
users.

good luck , fella !
Rob

Quoting "Duthoit, Philippe" <philippe.duthoit at be.verizon.com>:

> I have 2 Agents, A and B, 1 Manager M
>
>     
>
>    Based on username I would have A –users logged into Agent A , and
off
> course B-users logged into Agent B
>
>     
>
>     
>
>     
>
>     
>
>    I can read in the manual we can create groups and have these groups
> forced to certain servers
>
>     
>
>     
>
>     
>
>     
>
>    How can I create these groups ?
>
>     
>
>    The groups are unix groups, but do I need to create these users on
> the Manager ? That would be odd ?
>
>     
>
>     
>
>     
>
>     
>
>    P.
>
>     
>
>     
>
>     
>
>     
>
>     
>
>     
>
>     
>
>     
>
>     
>
>     
>
>    14.4.9.  Forcing sessions for some users to certain agent hosts
>
>     
>
>     
>
>     
>
>     
>
>    In some situations, it is desirable to force sessions for certain
> users to be started on a specific agent host. Examples of when this is
> needed is when testing a new server platform, allowing a group of test
> users to run their sessions on the new platform, and when configuring
> desktops with the ThinLinc Desktop Customizer (as described in Chapter
> 17, Building Custom Linux Desktops with the ThinLinc Desktop Customizer
> ), where you want to end up on the same server every time to make it
> easier to copy the resulting files to all other hosts.
>
>     
>
>     
>
>     
>
>     
>
>    ThinLinc provides a mechanism for this. By creating a unix group and
> associating it with a specific agent server, sessions for users that are
> members of the group will always be created on the agent host in
> question. Individual users may also be specified in this way.
>
>     
>
>     
>
>     
>
>     
>
>    The configuration parameter used for this is
> /vsmserver/explicit_agentselection. Add pairs of user/group and agent
> hostnames as a space-separated list to this parameter. The names of
> groups should be prepended by a + sign, to identify them as groups.
>
>     
>
>     
>
>     
>
>     
>
>    An example:
>
>     
>
>     
>
>     
>
>     
>
>    /vsmserver/explicit_agentselection = +group1:agent1 +group2:agent3
> user1:agent1
>
>     
>
>    Since only one server can be associated with each group, no load
> balancing is used. That means that if a user that is a member of group1
> requests a session, and agent1 is down, no session will be created.
>
>     
>
>     
>
>     
>
>     
>
>    If a server associated with a group is also listed in
> /vsmserver/terminalservers, sessions will be created for all users, not
> only the ones that are members of the group associated with the server.
> If the server is not listed in /vsmserver/terminalservers, only users in
> the group associated with the server will have sessions on the server.
>
>     
>
>   NV VERIZON BELGIUM LUXEMBOURG SA - registered office : Culliganlaan 2
> E, B-1831 Diegem, Belgium - BTW BE 0452.182.326 RPR Brussel
> VERIZON TERREMARK NV - primary and registered office : Culliganlaan 2 E,
> B-1831 Diegem, Belgium - BTW BE 0455.138.450 RPR Brussel
> Secondary office : Zeelsebaan 83 Z, B-9200 Dendermonde, Belgium
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cendio.se/pipermail/thinlinc-technical/attachments/20150505/8b7925eb/attachment-0007.html>