Hi James, ----- Original Message ----- > From: "A. James Lewis" <ja...@fsck.co.uk> > To: "Gustavo Homem" <gust...@angulosolido.pt>, > xrdp-devel@lists.sourceforge.net > Sent: Thursday, May 28, 2015 11:56:18 AM > Subject: Re: [Xrdp-devel] reconnecting vs new session. > > > You seem to have thought a lot about this kind of setup... so I have > another question... > > You mentioned a pool of servers in your description of how load might be > managed on NFS... but if a user already has a desktop running on a > specific server have you considered any mechanism that might allow them > to be re-connected to the node that has their running desktop?.. >
You need to insert a username (say jlewis) and your terminal needs to lookup: jlewis.vdi.domain and that record must keep track of the machine where you are logged in. If the query returns NXDOMAIN then it should query pool.vdi.domain which resolves to several IPs (round robin) and therefore connects the user to a random machine in the pool. When a user logs in it needs to update a record on a database that syncs to the DNS implementation. When a user logs out it must update the record again with null value. > I guess some kind of long term sticky session load balancer might work The solution above is simpler. > "most" of the time... but ideally you'd want to check which host has > their session already open... but this seems like a very hard problem. > It takes some effort but it might be worth it, depending on the project. > Also, I notice there is an option to kill disconnected sessions... is > there a way to kill them after a set period of time, > Didn't test it. You can also have a regular cron job to do that. Cheers Gustavo ------------------------------------------------------------------------------ _______________________________________________ xrdp-devel mailing list xrdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xrdp-devel
