Multiple colocation with same resource group
Tony Stocker <tony.stocker <at> nasa.gov>
2014-02-21 12:37:40 GMT
I have the following type of scenario. I have established a resource
group which does a number of infrastructure type things: sets IP
addresses, sets correct password files, sets correct system links and
mount points, etc. I now have a bunch of primitives that I want to
colocate with this resource group, but I do not want them part of the
group because I do not want the failure/reset of one to cause the others
For example, I'm running a FTP server, a HTTP server, a SMTP server, and
an OpenDAP backend server on the server that runs the resource group. Now
if I simply add them to the existing resource group in the order they're
listed above, then if the HTTP server gets reset during a monitor action,
it will cause the SMTP server and OpenDAP backend to shutdown and then
restart them after it restarts the HTTP server -- even if those 2 are not
actually dependent on the HTTP server. This is how resource groups work,
I get that.
What I want is a configuration where each of those four servers is
colocated with the resource group "in parallel" (for lack of a more
accurate term) such that a reset of one of the four servers follwing a
failed monitor action does not trigger a reset of any other resource. So
would the following configuration work or would it create a 'resource set'
(extraneous information such as params stripped for ease of reading):
primitive ip ocf:heartbeat:IPaddr2 params ip="126.96.36.199"
primitive job ocf:pps:jobfile params role="test" job="first"
primitive pwd ocf:pps:pwdfile params role="test"
primitive ftpd ocf:pps:proftpd
primitive httpd ocf:heartbeat:apache