I am using KVM with Redhat Cluster/DRBD for shared nothing: <a href="http://crunchtools.com/kvm-cluster-with-drbd-gfs2/">http://crunchtools.com/kvm-cluster-with-drbd-gfs2/</a><div><br><br><div class="gmail_quote">On Wed, Dec 15, 2010 at 3:38 PM, Scott Merrill <span dir="ltr"><<a href="mailto:skippy@skippy.net" target="_blank">skippy@skippy.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">The discussion on Hadoop is interesting, and I do hope a presentation<br>
or two results. If I can help coordinate, please let me know.<br>
<br>
On a similar vein, how are you folks handling the management of<br>
virtualized servers in your environments? It's trivial with KVM and<br>
similar tools to run a couple of virtual instances on a single<br>
physical box. It's not so trivial to run those virtual instances in a<br>
highly available fashion across a cluster of physical machines.<br>
<br>
VMware makes a pretty penny with VMotion, Storage VMotion, and similar<br>
technology, and by providing a nice management interface to this<br>
issue. Alas, those management tools are Windows-only.<br>
<br>
Red Hat has a product (by way of acquisition) called Red Hat<br>
Enterprise Virtualization Manager (RHEV-M). This, too, is currently a<br>
Windows-only solution.<br>
<br>
I've looked at a lot of IaaS ("Infrastructure as a Service"), elastic<br>
cloud, and similar solutions in the last couple of days. None of these<br>
are what I want, particularly. I'm not looking to sell or chargeback<br>
for our infrastructure, and I'm not looking for variable ad-hoc<br>
resource allocation.<br>
<br>
What I want is a reliable means of keeping a number of virtual servers<br>
up and accessible across a number of physical boxes, such that any<br>
physical box can be taken offline for maintenance (for example,<br>
rolling reboots across physical hosts).<br>
<br>
luci and ricci are are start, but they're nowhere near as end user<br>
friendly as the VMware tools. This is not a big concern for me, but it<br>
is an issue for those with whom I work, who might be expected to<br>
provide on-demand support if I get hit by a bus (or am just home<br>
sick).<br>
<br>
Anyone else tackling these issues? Would you care to present to COLUG<br>
on how you're managing things?<br>
<br>
Thanks,<br>
Scott<br>
_______________________________________________<br>
colug-432 mailing list<br>
<a href="mailto:colug-432@colug.net" target="_blank">colug-432@colug.net</a><br>
<a href="http://lists.colug.net/mailman/listinfo/colug-432" target="_blank">http://lists.colug.net/mailman/listinfo/colug-432</a><br>
</blockquote></div><br>
</div>