Joshua Penix wrote:
One further thing to consider might be what our extra server capacity
could be used for. No matter what we buy, it's going to be more than
necessary to run our single copy of Plone and the mailing lists. So is
there anything we could do that would benefit the community (either ours
locally or OSS in general), given a bunch of CPU and storage and the
ability to virtualize?
This is the big advantage from my point of view.
We are a Linux user group. Part of our goal is education. Part of that
is trying new things.
Most people do not have access to a 64-bit machine. Most people do not
have access to a machine which can do virtualization. These are
important upcoming technologies. KPLUG would be one of the few places
they could gain some experience.
In addition, most of us are, quite rightly, very leery of touching the
configuration of sparky to just "try something out" even if it's as
"simple" as an upgrade. Having virtualized instances really helps that.
One thing I would note is that virtualization eats RAM and disk. Lots.
4GB RAM is a good start. 200GB disk is a bit small. I have been
playing with CentOS the last couple of days and a fairly standard
install chews up 3GB off the top. That means the images would be about
8-10GB per instance or so. 200GB will disappear pretty fast.
-a
--
KPLUG-Steer@kernel-panic.org
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-steer
