[Pacemaker] Design question. Service running everywhere

[Andreas Kurz]

On 06/12/2012 10:17 PM, Arturo Borrero Gonzalez wrote:
> Hi there!
> 
> I've some questions for you.
> 
> I'm deploying a new cluster with a service inside that doesn't matter.
> The important of the service is that is running in everywhere by it's
> own internal functionality.
> So start/stop the resource in a given node is the same that doing it
> in the rest. All nodes will suffer that start/stop effect.
> 
> This is causing me some issues with Pacemaker.
> 
> As far as I know, pacemaker monitor the resource in each node (in this
> case /etc/init.d/service status, because it's an LSB resource).
> But /etc/init.d/service status will return the same as long as the
> service is the same in all nodes.
> 
> I don't know if working with clones will give some advantages. I need
> pacemaker to manage IPVs and other stuff.

Yes, that LSB service running on all nodes is a typical scenario for an
anonymous cloned resource.

Regards,
Andreas

-- 
Need help with Pacemaker?
http://www.hastexo.com/now

> 
> Shall I not use pacemaker with this service? Or, do I need some
> special configuration or design options?
> 
> Best regards.
> 





-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 222 bytes
Desc: OpenPGP digital signature
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20120613/e49d3b0a/attachment-0004.sig>