[Pacemaker] Pacemaker multi node configuration

Mon Oct 10 04:17:37 EDT 2011

Hello Andreas, you are 100% right about leaving an idle node instead of
balancing all the VM
Among all the four nodes. But the choice was to have and idle node that can
guest all the
VMs running the core business applications in the three production nodes. So
even if all three
Production nodes will go down all the core business applications will keep
on running.
Of course, when I will have clarified exactly how to setup the node in case
of fault I
Can try some different locations in case of fault.

I hope you don't mind having a look at the attached doc. I followed the
configuration 
found in "HA virtualization with KVM -ISCSI - Pacemaker" by Florian Hass,
adding few 
lines in order to have the VM running only in the production node and if it
will fail 
will keep on running on the backup node. As I have read, that all the nodes
must to be active,
my doubt is that the same VM will try start on two nodes at the same time.

Please let me know if the attached configuration can work or there is
something missing.

Thank you so much for helping me.

My best regards.

Luciano

-----Original Message-----
From: Andreas Kurz [mailto:andreas at hastexo.com] 
Sent: sabato 8 ottobre 2011 0.44
To: pacemaker at oss.clusterlabs.org
Subject: Re: [Pacemaker] Pacemaker multi node configuration

Hello,

On 10/05/2011 03:38 PM, Luciano Sitzia wrote:
> Hello Nick, I have already read this tutorial and for two node
configuration
> is quite clear
> but I didn't get how to setup four primary nodes switching to the same
> secondary if one of 
> them will fail.

First a  question: Why would you want one node being completely idle
while it could run VMs and help decreasing per node load?

One solution I could think of for a such a dedicated cold standby server:

* for every VM resource set a score e.g. 100 for one preferred node out
of the four servers

* set a lower score e.g. 10 for every VM for the cold standby server

... on node failure (one of "the four"), the first destination for its
VMs will be the standby node as it has the next best score. The question
is what should happen on multi node failures .... or do you plan to not
let them happen? ;-)

For such a scenario I'd recommend having a look at the utilization
feature of pacemaker 1.1 in combination with different priorities for
your vms.

Regards,
Andreas

-- 
Need help with Pacemaker?
http://www.hastexo.com/now

> Do you have a tutorial/example where this situation is explained.
> 
> Thank you again.
> 
> My  best regards.
> 
> Luciano
> 
> -----Original Message-----
> From: Nick Khamis [mailto:symack at gmail.com] 
> Sent: mercoledì 5 ottobre 2011 14.45
> To: The Pacemaker cluster resource manager
> Subject: Re: [Pacemaker] Pacemaker multi node configuration
> 
> The DRBD site has a nice tutorial on Pacemaker + KVM. The rest of the
> example
> cover Xen etc...
> 
>
http://www.linbit.com/en/education/tech-guides/highly-available-virtualizati
> on-with-kvm-iscsi-pacemaker/
> 
> Nick.
> 
> On Wed, Oct 5, 2011 at 8:31 AM, Luciano Sitzia
> <l.sitzia at lsinformatica.net> wrote:
>> Hello, I read pacemaker from scratch and pacemaker explained and I
> succeeded
>> in setting Active/passive clusters between two
>>
>> Node. Now I have to configure a cluster shared failover where four
servers
>> are running KVM with all VM on  the shared storage
>>
>> SAN with GFS2 , one more server acts as KVM failover. I tried to realize
> how
>> to configure it but I got totally lost.
>>
>> Can you help me sending  me a sample configuration to understand what I
>> should do.
>>
>>
>>
>> Thanks in advance my best regards.
>>
>>
>>
>> Luciano
>>
>>
>>
>> Luciano Sitzia
>>
>> Via Palazzi, 8/G
>>
>> 51030 Serravalle Pistoiese (PT) Italy
>>
>> Telefono : +390572953457 -+390572386136
>>
>> FAX : +390572294506
>>
>>
>>
>> Informativa Privacy (ex D.lgs 196/03)
>> Le informazioni contenute nel presente documento e relativi allegati
> possono
>> essere riservate e sono destinate esclusivamente alla persona od alla
>> Società indicata come destinatario. La diffusione e la distribuzione del
>> presente documento a soggetti diversi da quelli indicati, od in generale
>> qualsivoglia utilizzo illecito dei dati ivi contenuti, è proibita sia ai
>> sensi dell’art. 616 del Codice Penale che dal D. Lgs 196/03 in materia di
>> protezione dei dati personali (Privacy). Se avete ricevuto per errore
> questo
>> documento siete pregati di distruggerlo e di comunicarcelo prontamente
>> tramite e-mail o fax.
>>
>> This email and any files transmitted with it are confidential and
intended
>> solely for the use of the individual or entity to whom they are
addressed.
>> This communication may contain confidential material. If you are not the
>> intended recipient or the person responsible for delivering the email to
> the
>> intended recipient, be advised that you have received this email in error
>> and that any use, dissemination, forwarding, printing, or copying of this
>> email is strictly prohibited. If you have received this email in error
>> please notify the sender.
>>
>>
>>
>>
>>
>> _______________________________________________
>> Pacemaker mailing list: Pacemaker at 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
>>
>>
> 
> _______________________________________________
> Pacemaker mailing list: Pacemaker at 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
> 
> 
> 
> 
> _______________________________________________
> Pacemaker mailing list: Pacemaker at 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker

_______________________________________________
Pacemaker mailing list: Pacemaker at 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker

-------------- next part --------------
A non-text attachment was scrubbed...
Name: Pacemaker_KVM_ISCSI_MOD.pdf
Type: application/pdf
Size: 29642 bytes
Desc: not available
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20111010/37ff7239/attachment-0003.pdf>