Art Peck wrote:
This is a near-perfect application for AMGH. Check out Bob Doolittle's blog. He as a really nice how-to on AMGH. You script could figure out which server you prefer based on whatever criteria you decide and return just that hostname.
Thanks for the plug, Art. Note, however that this would require splitting the groups into two separate FOGs.
I kind of like the previous example however, because it still does session location across both sites. The problem with using two FOGs and AMGH is that if all of the "local" servers are down, and you get a server at the "remote" site, then when your local servers come back up and you reconnect your DTU will create a new session in the "local" FOG again and not automatically reconnect to the remote session.
The problem with disabling load balancing is, well, no load balancing. :) And users will continue to transparently use remote sessions after local servers come back up, until they logout/login again. That may or may not be what you want.
There are pros and cons to both approaches. If you consider it a rare case for all local servers to go down, then perhaps you can afford the cost of cleaning up the remote sessions when local servers come back up. In that case, using AMGH and retaining load balancing might be a good solution. If that's too hard on your users and admin staff, then maybe disabling load balancing might be preferable.
If you disable load balancing, it's crucial that you make sure to use some sort of randomization in the server list, so all your DTUs don't always bind to the first server in the list. The .parms file provides a mechanism for randoming the server list. I don't recall the randomizing details for the other mechanisms, sorry.
-Bob _______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
