[Linux-ha-dev] Ordering of OCF Start, Stop and Monitor actions

[Doug Knight]

Hi All,
I currently am running a two node cluster (host1 and host2) with version
2.0.8. I have a resource defined with a place constraint of "#uname eq
host1", so that it will start on host1 (using an OCF RA script,
including all of the required methods). The resource itself has
target_role set to "stopped". 

Question 1: Is the monitor method called regularly on both nodes to make
sure the resource is not running?

Next, I change the target_role to "started" (i.e. I use the GUI and
click the start button).

Question 2: What is the order of OCF methods called to bring up the
resource? Is Monitor called before Start on host1? Does Stop and/or
Monitor ever get called on host2? 

Resource is up and running on host1, and I decide to move the resource
to host2. I click the constraint and change it to "#uname eq host2". The
resource stops on host1 and starts on host2.

Question 3: Same idea, what are the sequence of method calls to migrate
the resource from host1 to host2?

I'm trying to thoroughly understand the sequence of events that occurs
for each phase in support of the Postgres WAL file forwarding
configuration I posted last week ("[Linux-HA] Two node cluster with
Postgres in WAL file fwding mode", started March 1).

Thanks,
Doug Knight
WSI Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.community.tummy.com/pipermail/linux-ha-dev/attachments/20070314/058e82df/attachment.html