If you do decide to use 2 switchs: 1) for KVM Hosts use 2 nics, bridge them and run KVM on the bridge (usually br0), link each nic to a different switch 2) Interlink those switches. Dan -----Original Message----- From: gluster-users-bounces at gluster.org [mailto:gluster-users-bounces at gluster.org] On Behalf Of Nicolas Sebrecht Sent: Wednesday, June 27, 2012 4:13 AM To: Gerald Brandt Cc: gluster-users Subject: Re: about HA infrastructure for hypervisors The 27/06/12, Gerald Brandt wrote: > Hi, > > If your switch breaks, you are done. Put each Gluster server on it's own switch. Right. Handling switch failures isn't what I'm most worried about but I guess that I'll need to add a network link between KVM hypervisors, too. Thanks for this tip, though. > > +----------------+ +----------------+ > > | |------------------| | > > | KVM hypervisor |---+ +-------| KVM hypervisor | > > | | | | | | > > +----------------+ | | +----------------+ > > | | > > +------+ +------+ > > |switch| |switch| > > +------+ +------+ > > | | | | > > +---------------+ | | | | +---------------+ > > | | | | | +-----| | > > | Glusterfs 3.3 |--+ +------)--------| Glusterfs 3.3 | > > | server A | | | server B | > > | |-----------+ | | > > +---------------+ +---------------+ -- Nicolas Sebrecht _______________________________________________ Gluster-users mailing list Gluster-users at gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
