Hello -
It's there. And here is the basic configuration that works all right for me.
Unfortunately I didn't find a way how to make Pacemaker to run reload on one
resource after start of another so I just put order constraint for start
action. BIND does a quick restart when IP failes over:
node cs51
node cs52
primitive Bind ocf:heartbeat:named \
params monitor_request="localhost.localdomain"
monitor_response="127.0.0.1" \
op monitor interval="30s" timeout="20s"
primitive BindIP ocf:heartbeat:IPaddr2 \
params ip="192.168.1.130" \
op monitor interval="30s" timeout="20s"
clone BindClone Bind \
meta clone-max="2" clone-node-max="1" target-role="Started"
colocation IP_to_Bind +inf: BindIP BindClone
order Bind_Strart_After_IP_Start +inf: BindIP:start BindClone:start
OC: CentOS 5.7
Pacemaker: pacemaker-1.1.5-1.1.el5
ResourceAgents: resource-agents-3.9.2-1el5 + named RA from GIT
On Wed, Oct 5, 2011 at 5:08 AM, Max Williams <max.willi...@betfair.com>wrote:
> OK I’ll wait until it is in GIT.****
>
> ** **
>
> Is there a way I could edit the LSB RA to take ‘reload’? Where is the RA
> file for LSB init scripts? Or is it built in to Pacemaker?****
>
> ** **
>
> Thanks,****
>
> Max****
>
> ** **
>
> *From:* Serge Dubrouski [mailto:serge...@gmail.com]
> *Sent:* 05 October 2011 04:32
>
> *To:* The Pacemaker cluster resource manager
> *Subject:* Re: [Pacemaker] Reloading a resource after a failover****
>
> ** **
>
>
> Please also notice that named RA in the git is a little bit broken. You
> need to apply a patch that I recently sent, or wait little bit till it's
> applied to GIT.****
>
> ** **
>
> On Tue, Oct 4, 2011 at 8:08 AM, Florian Haas <flor...@hastexo.com> wrote:*
> ***
>
> On 2011-10-04 12:26, Max Williams wrote:
> > Thanks Serge.
> >
> > How exactly do I tell pacemaker to use this RA? Is there an ‘import’
> > command I need to run?****
>
> No, you just drop the resource agent in the appropriate provider
> directory (/usr/lib/ocf/resource.d/<provider/) and set its x bit. Then
> it immediately becomes available to the LRM and Pacemaker.****
>
>
> > Also, does this mean I need to change some of the paths in the RA?****
>
> Yes it does. Well, really it means you're using an elderly version of
> the resource agents package which expects the heartbeat shellfuncs
> library in a different location than the new RA.****
>
>
> > [root@host001 ~]# ocf-tester -n named
> > /usr/lib/ocf/resource.d/heartbeat/named
> >
> > Beginning tests for /usr/lib/ocf/resource.d/heartbeat/named...
> >
> > /usr/lib/ocf/resource.d/heartbeat/named: line 16:
> > /usr/lib/ocf/lib/heartbeat/ocf-shellfuncs: No such file or directory
> >
> > * rc=1: Your agent has too restrictive permissions: should be 755
> >
> > /usr/lib/ocf/resource.d/heartbeat/named: line 16:
> > /usr/lib/ocf/lib/heartbeat/ocf-shellfuncs: No such file or directory****
>
> If you change the path in that line 16 to
> "/usr/lib/ocf/resource.d/heartbeat/.ocf-shellfuncs" (note leading dot in
> filename and resource.d, not lib), then the RA should be able to find
> the shell function library.
>
> What's a much better idea though is of course to move to a recent
> version of resource-agents, but that may or may not be an option for you.
>
> Hope this helps.
> Cheers,
> Florian
>
> --
> Need help with High Availability?
> http://www.hastexo.com/now
>
>
> _______________________________________________
> 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.****
>
> ________________________________________________________________________
> In order to protect our email recipients, Betfair Group use SkyScan from
> MessageLabs to scan all Incoming and Outgoing mail for viruses.
>
> ________________________________________________________________________
>
> _______________________________________________
> 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
