Adrian, A few more comments below to maybe make it clearer...
----- Original Message ----- > From: "Adrian Gibanel" <adrian.giba...@btactic.com> > To: "The Pacemaker cluster resource manager" > <pacemaker@oss.clusterlabs.org> > Sent: Sunday, August 19, 2012 12:22:54 PM > Subject: Re: [Pacemaker] Help on setting order of resources > Ok. Now the order of resources seems to work as I first expected. > I seem to have other problems which I'll comment later probably in a > new thread if I'm not able to deal with them. > Thank you again! Glad it helped! > ----- Original Message ----- > > De: "Adrian Gibanel" <adrian.giba...@btactic.com> > > > Para: "The Pacemaker cluster resource manager" > > <pacemaker@oss.clusterlabs.org> > > > Enviados: Domingo, 19 de Agosto 2012 10:27:34 > > > Asunto: Re: [Pacemaker] Help on setting order of resources > > > Now that I'm reading about that it makes sense. So it removes my > > idea > > of: Colocation = Put in the same machine/server. > Not quite sure I understand what you're saying here... Colocation does = Put in the same machine/server Just didn't have the "order" inside of colocation statement correct > > I copy and paste from Configuration Explained pdf: > > > --- > > > Well, I'm going to try to reverse the "order" in the colocation > > statement. > > > Now it makes sense why insisted me on setting up resources inside > > groups. It seems that makes things easier indeed. > Groups - shortcut to order and colocation statements (so yes I think they are easier - as long as you are already confortable with the order/colocation concepts) Resources inside groups are ordered as written and collocated in reverse - that's my trick to remember the "normal" way a collocation statement is written. "Usually" the opposite of the order statement i.e. order sample_order 1 2 3 colocation sample_colo inf: 3 2 1 And I always review them by reading them with their "action" between the resources i.e. order of sample_order is 1 then 2 then 3 colocation of sample_colo is always 3 with 2 with 1 Hope that makes it a bit clearer! Jake > > Thank you! > > > ----- Mensaje original ----- > > > > De: "Jake Smith" <jsm...@argotec.com> > > > > Para: "The Pacemaker cluster resource manager" > > > > <pacemaker@oss.clusterlabs.org>, Pacemaker@oss.clusterlabs.org > > > > Enviados: Domingo, 19 de Agosto 2012 6:00:16 > > > > Asunto: Re: [Pacemaker] Help on setting order of resources > > > > One thing I see after looking quickly is it looks like the > > > > collocation statement is backwards. > > > > You want MyZimbra to run where ZimbraDataClone:Master runs and > > > > ZimbraDataClone: Master to run where MySystem runs correct ? > > > > Collocation is like saying on or with between each resource and > > > is > > > > usually the opposite order of the similar/matching order > > > statement: > > > > colocation everything-together inf: MyZimbra > > > ZimbraDataClone:Master > > > > MySystem > > > > The above is like saying MyZimbra with ZimbraDataClone: Master > > > with > > > > MySystem > > > > There may be more things that need work but that's what I saw > > > after > > > a > > > > quick look > > -- > Adrián Gibanel > I.T. Manager > +34 675 683 301 > www.btactic.com > Ens podeu seguir a/Nos podeis seguir en: > i > Abans d´imprimir aquest missatge, pensa en el medi ambient. El medi > ambient és cosa de tothom. / Antes de imprimir el mensaje piensa en > el medio ambiente. El medio ambiente es cosa de todos. > AVIS: > El contingut d'aquest missatge i els seus annexos és confidencial. Si > no en sou el destinatari, us fem saber que està prohibit > utilitzar-lo, divulgar-lo i/o copiar-lo sense tenir l'autorització > corresponent. Si heu rebut aquest missatge per error, us agrairem > que ho feu saber immediatament al remitent i que procediu a destruir > el missatge . > AVISO: > El contenido de este mensaje y de sus anexos es confidencial. Si no > es el destinatario, les hacemos saber que está prohibido utilizarlo, > divulgarlo y/o copiarlo sin tener la autorización correspondiente. > Si han recibido este mensaje por error, les agradeceríamos que lo > hagan saber inmediatamente al remitente y que procedan a destruir el > mensaje . > _______________________________________________ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > Project Home: http://www.clusterlabs.org > Getting started: > http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org _______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
