On 18/06/19 13:08 +, Michael Powell wrote:
> * The document does not specify where the agent should be installed.
> (On /usr/sbin.)
This could give a precise answer:
https://github.com/ClusterLabs/pacemaker/blob/Pacemaker-2.0.2/lib/fencing/st_rhcs.c#L33
> * The document does not mention
Thanks for the help. I'm not sure how I missed the earlier reply, but this was
most helpful. I elected to follow the 2nd option suggested: rewrite the
custom fence agent to conform to the FenceAgentAPI.md document. I do have a
couple of comments/questions regarding the FenceAgentsAPI.md
On Fri, 2019-05-31 at 22:32 +, Michael Powell wrote:
> Although I am personally a novice wrt cluster operation, several
> years ago my company developed a product that used Pacemaker. I’ve
> been charged with porting that product to a platform running Centos
> 7.6. The old product ran
Although I am personally a novice wrt cluster operation, several years ago my
company developed a product that used Pacemaker. I've been charged with
porting that product to a platform running Centos 7.6. The old product ran
Pacemaker 1.1.13 and heartbeat. For the most part, the transition
