>>>>> "Edward" == Edward Ned Harvey <[email protected]> writes:
>> From: John Stoffel [mailto:[email protected]] >> Edward> Better yet, some form of high availability. The ability to Edward> have multiple machines all providing the same services. Take Edward> one down for service, and when it's back up again, take the Edward> other down for service. >> >> I'd love to be able to rollout some sort of high availability setup >> for my engineer's VNC sessions, so that I could move their sessions >> and reboot the VNC servers, etc. >> >> I don't think I can do this, because of NFS mount points that user's >> get into and which need updating, etc. It's *really* hard from what I >> can see to make a robust system where I don't have to reboot once in a >> while. Edward> What I personally do for my users is to designate one system Edward> as the VNC / X11 forwarding / NX / RDP server. Whenever users Edward> open up a GUI terminal on that machine, they're automatically Edward> prompted to connect to some other machine. So the machine Edward> hosting the GUI does nothing but GUI. So there's only one Edward> machine I can't reboot. All the others are fair game, with Edward> some level of planning. (Notify users who are logged into Edward> hosta, that I'd like to reboot hosta, so could they please use Edward> hostb.) Edward> It's not very elegant or effective. Edward> At other sites, we're able to run all our stuff on SGE, so I Edward> can disable some machine from accepting queued jobs, and then Edward> when it's idle, reboot it. This is much more elegant and Edward> effective, but only if you can run all your stuff via SGE or Edward> some other queueing system. We do use NC (from rtda.com) for batch and interactive jobs, which works great for stuff the users submit, and I can manage those hosts easily enough. It's the single big old Sun V880 which has dozens of VNC sessions on it for engineers to use since they all have laptops instead of desktop workstations. That's the system I want to be able to fix without impacting them. One solution would be to just give them each their own VM, then let VMotion move VMs around at need. Expensive though. Edward> Of course you can't do that for *every* thing, but whenever Edward> possible, that's the preference. >> >> I wish I could do it for VNC. I guess I could build a Sun or Linux >> cluster to do this... might even try. Edward> I'm not 100% sure if NX can do this, but you should look at Edward> them. They're commercial BTW. I love their products far Edward> better than VNC or X11 forwarding. Faster, more flexible, Edward> robust, reliable, easy to setup. Etc. They're free for Edward> unlimited personal use, or for a single computer in corporate Edward> use. We keep talking about it, haven't made the plunge yet. John _______________________________________________ Tech mailing list [email protected] http://lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
