[Pacemaker] Move resources on failure
Hallo! I'm a newbie and I've just set up a small cluster wich consists of two nodes with apache and one mutual ip address. I use corosync and pacemaker. When I kill apache process crm restarts it so that apache continues working, but I want (in case of apache process failure) to make crm move the whole bunch of resources to another node instead. Is it possible? This is my config crm(live)configure# show node centos1 \ attributes standby="off" node centos2 \ attributes standby="off" primitive mutip1 ocf:heartbeat:IPaddr \ params ip="192.168.1.200" cidr_netmask="255.255.255.255" nic="eth0" \ op monitor interval="5s" timeout="20s" primitive website lsb:httpd \ op monitor interval="15" timeout="15" start-delay="15" \ meta target-role="Started" colocation ipapache inf: mutip1 website order apache-after-ip inf: mutip1 website property $id="cib-bootstrap-options" \ dc-version="1.0.11-1554a83db0d3c3e546cfd3aaff6af1184f79ee87" \ cluster-infrastructure="openais" \ expected-quorum-votes="2" \ no-quorum-policy="ignore" \ stonith-enabled="false" --- WBR, Sergey ___ 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
[Pacemaker] Pacemaker Cloud Policy Engine Red Hat Summit slides and Mailing List
In February we announced our intentions to work on a cloud-specific high availability solution on this list. The code is coming along, and we have reached a point where we should have a mailing list dedicated to cloud specific topics of Pacemaker. The mailing list subscription page is: http://oss.clusterlabs.org/mailman/listinfo/pcmk-cloud To see how we have progressed since February, have a look at the source in our git repo, or take a look at the Red Hat Summit 2011 slides where our work was presented this last week : http://www.redhat.com/summit/2011/presentations/summit/whats_new/thursday/dake_th_1130_high_availability_in_the_cloud.pdf If your interested in cloud high availability technology, please feel free to participate on our mailing lists. Your input there is invaluable to ensuring we deliver a great project that downstream distros and administrators can use. ___ 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
Re: [Pacemaker] Move resources on failure
Sergey V. Arlashin writes: > Hallo! > I'm a newbie and I've just set up a small cluster wich consists of two nodes with apache and one mutual ip > address. I use corosync and pacemaker. > When I kill apache process crm restarts it so that apache continues working, but I want (in case of apache > process failure) to make crm move the whole bunch of resources to another node instead. > Is it possible? > > This is my config > > crm(live)configure# show > node centos1 \ > attributes standby="off" > node centos2 \ > attributes standby="off" > primitive mutip1 ocf:heartbeat:IPaddr \ > params ip="192.168.1.200" cidr_netmask="255.255.255.255" nic="eth0" \ > op monitor interval="5s" timeout="20s" > primitive website lsb:httpd \ > op monitor interval="15" timeout="15" start-delay="15" \ > meta target-role="Started" > colocation ipapache inf: mutip1 website > order apache-after-ip inf: mutip1 website > property $id="cib-bootstrap-options" \ > dc-version="1.0.11-1554a83db0d3c3e546cfd3aaff6af1184f79ee87" \ > cluster-infrastructure="openais" \ > expected-quorum-votes="2" \ > no-quorum-policy="ignore" \ > stonith-enabled="false" > > --- > WBR, Sergey > Hello Sergey, is it necessary to induce resource relocation by killing apache? I would use 'crm migrate resAPACHE' on the active node (for example). You must not forget to finish with 'crm unmigrate resAPACHE' at some point in your examples, otherwise 'resAPACHE' would not return to your formerly active node in any case ;) It is possible I think, but I am not that far yet. BTW: why do you use 'lsb:httpd' instead of 'ocf:heartbeat:apache' ? The pacemaker resource agent is much more reliable in a cluster structure. Killing 'resAPACHE' using the ocf agent produces migration-threshold (infinity) and fail-count (+1) scores which surely can be used to move the resource to another node. I, too, am still learning how that is achieved. Greets Thomas ___ 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
Re: [Pacemaker] Move resources on failure
http://www.clusterlabs.org/doc/en-US/Pacemaker/1.0/html/Pacemaker_Explained/s-resource-options.html#id649472 Look for migration-threshold. Do not use LSB script for apache, instead carefully study all features of OCF one. On Sun, May 8, 2011 at 8:45 AM, Sergey V. Arlashin < maillist.arlas...@yandex.ru> wrote: > Hallo! > I'm a newbie and I've just set up a small cluster wich consists of two > nodes with apache and one mutual ip address. I use corosync and pacemaker. > When I kill apache process crm restarts it so that apache continues > working, but I want (in case of apache process failure) to make crm move the > whole bunch of resources to another node instead. > Is it possible? > > This is my config > > crm(live)configure# show > node centos1 \ >attributes standby="off" > node centos2 \ >attributes standby="off" > primitive mutip1 ocf:heartbeat:IPaddr \ >params ip="192.168.1.200" cidr_netmask="255.255.255.255" nic="eth0" > \ >op monitor interval="5s" timeout="20s" > primitive website lsb:httpd \ >op monitor interval="15" timeout="15" start-delay="15" \ >meta target-role="Started" > colocation ipapache inf: mutip1 website > order apache-after-ip inf: mutip1 website > property $id="cib-bootstrap-options" \ >dc-version="1.0.11-1554a83db0d3c3e546cfd3aaff6af1184f79ee87" \ >cluster-infrastructure="openais" \ >expected-quorum-votes="2" \ >no-quorum-policy="ignore" \ >stonith-enabled="false" > > > --- > WBR, Sergey > > > > ___ > 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker > -- Serge Dubrouski. ___ 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
[Pacemaker] filesystem could not mount after reboot
Hi all yesterday my lab balckout, this morning when I start pacemaker I find the filesystem could not be mounted, There is no use of crm resource cleanup, after delete the files /var/lib/heartbeat/crm/*, and then restart corosync it works,I do not understand why?___ 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
