Package Exclusivity on Serviceguard node

[Rob Beglinger]

I am migrating an existing stand-alone server into a Serviceguard cluster. The cluster is a two node cluster with two packages. The packages are a Stage instance and a Production instance of the same application. The two packages cannot reside on the same node, they share the same mount points, and the Production will need to have priority over the Stage should a node fail.
Can Serviceguard automatically halt the Stage package if the node that the Production package resides on faults causing it to need to switch to the node that currently hosts the Stage package?
Unfortunately, the developers are unwilling to rewrite the app to allow for unique mount points for the packages.

[Patrick Wallek]

I believe this can be done, BUT it would have to be done in your package control script.

What you would have to do is put some logic into the script that says if the PROD package starts on the secondary machine, then the DEVE package should be shut down first.

[Stephen Doud · Accepted solution]

Edit the production package control script, to
- determine the nodename where the production package is starting
- determine whether the stage package is running, and if so, what node it's running on.
- if the production package is starting on the same node as the stage package, halt the stage package.

This can all be done in the production package control script.

[Rita C Workman]

Just to add to the gents perfect comments.

At the top of the production control script you want to stop the staging pkg, so just add the following statement:

/usr/sbin/cmhaltpkg -n $(/usr/bin/uname -n)

Rgrds,
Rita

[Rob Beglinger]

That's what I thought, I was just hoping for a magic exclusivity flag. Thanks for the help.