Gluster v 3.3 with KVM and High Availability

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Jul 11, 2012 at 12:58:39PM -0500, Mark Nipper wrote:
> On 11 Jul 2012, Barlow, Jim D wrote:
> > As far as fencing  goes, I have done nothing.     I'm manually as carefully as I can manage  using virt-manager.    I've already accidentally started the same VM on two bricks.  Watch your autostart settings on the VMs :-)   
> 
> 	Sanlock definitely seems like the way to go with this.  I
> hadn't even heard of it until someone mentioned it here the other
> day.

Interesting, that's new to me too.

Your other option is to use a cluster manager layer like ganeti. This has
the advantage that you don't have to worry about copying your libvirt
configs around (i.e.  once a node has crashed, you need a copy of its
libvirt XML somewhere else so you can boot it on another node)


[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux