Quoting Tracy R Reed <[EMAIL PROTECTED]>:
Sure. But the vast majority of our servers are idle 99% of the time.
The stuff sits on separate servers mainly for reliability and
maintainability reasons. Also sometimes we need different versions of
A couple other things we've been looking at virtualizion on linux for...
1. Ability to migrate running processes if needed. When you've got
jobs that can run for days if not weeks, this can be a huge gain.
2. Using VMs on top of a standard image across hosts to temporarily
boot previously supported images when required. Hopefully eventually
use grid tools to automate creation/tear-down of said VMs
automatically when jobs need them.
2a. Some of our ISVs (and others) are apparently eyeing possibly
selling their software as self-contained VM instances... this
guarantees the software runs and lowers their support issues with
varying distributions/versions, removes the constant needs for testing
with various versions of libraries, etc.
3. Use of VMs like containers on solaris.. complete isolation of
system resources for jobs.. so even if a program has a bug that makes
it go hog wild on resources (I've seen apps send a 128Gig box OOM
inside of a minute, and the OS could/did not handle it) it won't
effect the other. Limits can do this too, just looking at options and
comparing.
4. Possibly replacing most desktops with thin clients (I personally
think NX is the best choice, and there are clients for it for at least
Wyse and HP thin clients) to a VM so the user can do anything they
want without effecting others, even if they completely trash the box.
#1 comes back in too if we can migrate them if/when needed.
Mostly thinking paravirt vs full virt at this point.
--
Mike Marion-Unix/Linux Admin-http://www.miguelito.org
"In the closed-source world, Version 1.0 means "Don't touch this if
you're prudent."; in the open-source world it reads more like "The
developers are willing to bet their reputations on this." - Eric Raymond
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list