[Pacemaker] Use of Pacemaker to configure a new resource

[David Vossel]

----- Original Message -----
> From: "Aarti Sawant" <aartipsawant10 at gmail.com>
> To: "The Pacemaker cluster resource manager" <pacemaker at oss.clusterlabs.org>
> Sent: Wednesday, November 20, 2013 3:55:40 AM
> Subject: [Pacemaker] Use of Pacemaker to configure a new resource
> 
> Hello,
> 
> I have a PostgreSQL replication set up. It consists of master A and
> standby B & C which are directly connecting to master. I am using a
> tool called WANPRoxy for compression of data to be transferred between
> master and standby. In case of failure of master, I want WANProxy to
> run on any of the standbys.
> 
> As far as I understand, this can be done by scripting OCF Resource
> Agent for WANProxy?

Yes, you could make your own custom OCF script to manage WANProxy, or you could potentially have pacemaker start WANProxy using whatever init script is shipped with the daemon as well.

> So my primary question is that can Pacemaker be used to start WANProxy
> compression on different machine when one of my machine fails?

yes, This sounds like basic resource failover, which is the primary reason people use Pacemaker.

> 
> The command to start WANProxy is
> wanproxy -c /home/user_name/server_v2.conf
> 
> Also , I want to know if by using some parameters
> 
> in Resource Agents, can pacemaker also modify configuration files of
> compression tools like WANProxy, ssl ,ssh?

Pacemaker simply executes resource-agent scripts and is not concerned with what those scripts do.  If you want to modify configuration files for some reason, build that logic into your custom OCF scripts and pacemaker will execute.

-- Vossel

> 
> Thanks,
> Aarti Sawant
> NTTDATA OSS Center Pune
> 
> 
> _______________________________________________
> Pacemaker mailing list: Pacemaker at 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://bugs.clusterlabs.org
>