[This email was originally posted to the gluster-infra list. Since that list is used for coordination between members who work on the infrastructure of the project, I am redirecting it to gluster-users for better visibility and responses.] On Thu, Mar 28, 2019 at 1:13 AM Guy Boisvert <guy.boisvert at ingtegration.com> wrote:> > Hi, > > New to this mailing list. I'm seeking people advice for GlusterFS > HA in the context of KVM Virtual Machines (VM) storage. We have 3 x KVM > servers that use a 3 x GlusterFS nodes. The Volumes are 3 way replicate. > > My question is: You guys, what is your network architecture / setup > for GlusterFS HA? I read many articles on the internet. Many people are > talking about bonding to a switch but i don't consider this as a good > solution. I'd like to have Gluster and KVM servers linked to at least 2 > switches to have switch / wire and network car redundancy. > > I saw people using 2 x dumb switches with bonding mode 6 on their > servers with mii monitoring. It seems to be about good but it could > append that mii is up but frames / packets won't flow. So it this case, > i can't imagine how the servers would handle this. > > Another setup is dual dumb switches and running Quagga on the > servers (OSPF / ECMP). This seems to be the best setup, what do you > think? Do you have experience with one of those setups? What are your > thoughts on this? Ah and lastly, how can i search in the list? > > > Thanks! > > > Guy > > -- > Guy Boisvert, ing. > IngTegration inc. > http://www.ingtegration.com > https://www.linkedin.com/pub/guy-boisvert/7/48/899/fr > > AVIS DE CONFIDENTIALITE : ce message peut contenir des > renseignements confidentiels appartenant exclusivement a > IngTegration Inc. ou a ses filiales. Si vous n'etes pas > le destinataire indique ou prevu dans ce message (ou > responsable de livrer ce message a la personne indiquee ou > prevue) ou si vous pensez que ce message vous a ete adresse > par erreur, vous ne pouvez pas utiliser ou reproduire ce > message, ni le livrer a quelqu'un d'autre. Dans ce cas, vous > devez le detruire et vous etes prie d'avertir l'expediteur > en repondant au courriel. > > CONFIDENTIALITY NOTICE : Proprietary/Confidential Information > belonging to IngTegration Inc. and its affiliates may be > contained in this message. If you are not a recipient > indicated or intended in this message (or responsible for > delivery of this message to such person), or you think for > any reason that this message may have been addressed to you > in error, you may not use or copy or deliver this message to > anyone else. In such case, you should destroy this message > and are asked to notify the sender by reply email.