<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
<html><head><meta http-equiv="content-type" content="text/html; charset=UTF-8"></head><body style="font-family:Arial;font-size:14px"><p>
Philippe,<br><br>
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.<br><br>
Home-dirs come from a shared NFS cluster, who has a ZFS filesystem per user.<br><br>
The master is configured then with "agentname:username" pairs so redirect each user to his personal agent host.<br><br>
Load-balancing users across agents is no longer relevant of course.<br><br>
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.<br><br>
good luck , fella !<br>
Rob<br><br>
Quoting "Duthoit, Philippe" <<a href="mailto:philippe.duthoit@be.verizon.com">philippe.duthoit@be.verizon.com</a>>:</p>
<blockquote style="border-left:2px solid blue;margin-left:2px;padding-left:12px;" type="cite">
<div class="WordSection1">
<p class="MsoNormal">
<span style="color:#1F497D">I have 2 Agents, A and B, 1 Manager M</span></p>
<p>
</p>
<p class="MsoNormal">
<span style="color:#1F497D">Based on username I would have A –users logged into Agent A</span> <span style="color:#1F497D">, and off course B-users logged into Agent B</span></p>
<p>
</p>
<p class="MsoNormal">
</p>
<p>
</p>
<p>
</p>
<p class="MsoNormal">
<span style="color:#1F497D">I can read in the manual we can create groups and have these groups forced to certain servers</span></p>
<p>
</p>
<p class="MsoNormal">
</p>
<p>
</p>
<p>
</p>
<p class="MsoNormal">
<span style="color:#1F497D">How can I create these groups ?</span></p>
<p>
</p>
<p class="MsoNormal">
<span style="color:#1F497D">The groups are unix groups, but do I need to create these users on the Manager ? That would be odd ?</span></p>
<p>
</p>
<p class="MsoNormal">
</p>
<p>
</p>
<p>
</p>
<p class="MsoNormal">
<span style="color:#1F497D">P.</span></p>
<p>
</p>
<p class="MsoNormal">
</p>
<p>
</p>
<p>
</p>
<p class="MsoNormal">
</p>
<p>
</p>
<p>
</p>
<p class="MsoNormal">
</p>
<p>
</p>
<p>
</p>
<p class="MsoNormal">
<span style="color:#1F497D">14.4.9. Forcing sessions for some users to certain agent hosts</span></p>
<p>
</p>
<p class="MsoNormal">
</p>
<p>
</p>
<p>
</p>
<p class="MsoNormal">
<span style="color:#1F497D">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.</span></p>
<p>
</p>
<p class="MsoNormal">
</p>
<p>
</p>
<p>
</p>
<p class="MsoNormal">
<span style="color:#1F497D">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.</span></p>
<p>
</p>
<p class="MsoNormal">
</p>
<p>
</p>
<p>
</p>
<p class="MsoNormal">
<span style="color:#1F497D">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.</span></p>
<p>
</p>
<p class="MsoNormal">
</p>
<p>
</p>
<p>
</p>
<p class="MsoNormal">
<span style="color:#1F497D">An example:</span></p>
<p>
</p>
<p class="MsoNormal">
</p>
<p>
</p>
<p>
</p>
<p class="MsoNormal">
<span style="color:#1F497D">/vsmserver/explicit_agentselection = +group1:agent1 +group2:agent3 user1:agent1</span></p>
<p>
</p>
<p class="MsoNormal">
<span style="color:#1F497D">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.</span></p>
<p>
</p>
<p class="MsoNormal">
</p>
<p>
</p>
<p>
</p>
<p class="MsoNormal">
<span style="color:#1F497D">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.</span></p>
<p>
</p>
</div>
<br><p style="COLOR: #696969; FONT-SIZE: 0.96em">
<strong>NV Verizon Belgium Luxembourg SA</strong> - registered office : Culliganlaan 2 E, B-1831 Diegem, Belgium - BTW BE 0452.182.326 RPR Brussel<br><strong>Verizon Terremark NV</strong> - primary and registered office : Culliganlaan 2 E, B-1831 Diegem, Belgium - BTW BE 0455.138.450 RPR Brussel<br>
Secondary office : Zeelsebaan 83 Z, B-9200 Dendermonde, Belgium</p>
</blockquote>
<br><br></body></html>