[ClusterLabs] Adding HAProxy as a Resource
tojeline at redhat.com
Thu Jul 25 03:50:53 EDT 2019
It looks like your pacemaker binaries do not support systemd resources.
If that is the case then there is nothing pcs can do about that.
Pacemaker experts should be able to shed some light on this.
Dne 25. 07. 19 v 9:23 Somanath Jeeva napsal(a):
> Systemd unit file is available for haproxy but the pcs resource standard command does not list systemd standard .
> Also I am not using the pacemaker packages from redhat. I am using the packages downloaded from clusterlabs.
> With Regards
> Somanath Thilak J
> -----Original Message-----
> From: Tomas Jelinek <tojeline at redhat.com>
> Sent: Monday, July 15, 2019 5:58 PM
> To: users at clusterlabs.org
> Subject: Re: [ClusterLabs] Adding HAProxy as a Resource
> Do you have a systemd unit file for haproxy installed?
> Does 'crm_resource --list-standards' print 'systemd'?
> Does 'crm_resource --list-agents systemd' print 'haproxy'?
> Note that when you use full agent name (that is including : ) it is case sensitive in pcs.
> Dne 11. 07. 19 v 10:14 Somanath Jeeva napsal(a):
>> I am using the resource agents built from clusterlabs and when I add the systemd resource I am getting the below error .
>> $ sudo pcs resource create HAPROXY systemd:haproxy op monitor
>> Error: Agent 'systemd:haproxy' is not installed or does not provide
>> valid metadata: Metadata query for systemd:haproxy failed: -22, use
>> --force to override
>> With Regards
>> Somanath Thilak J
>> -----Original Message-----
>> From: Kristoffer Grönlund <kgronlund at suse.com>
>> Sent: Thursday, July 11, 2019 1:22 PM
>> To: Cluster Labs - All topics related to open-source clustering
>> welcomed <users at clusterlabs.org>
>> Cc: Somanath Jeeva <somanath.jeeva at ericsson.com>
>> Subject: Re: [ClusterLabs] Adding HAProxy as a Resource
>> On 2019-07-11 09:31, Somanath Jeeva wrote:
>>> Hi All,
>>> I am using HAProxy in my environment which I plan to add to
>>> pacemaker as resource. I see no RA available for that in resource agent.
>>> Should I write a new RA or is there any way to add it to pacemaker as
>>> a systemd service.
>> haproxy works well as a plain systemd service, so you can add it as systemd:haproxy - that is, instead of an ocf: prefix, just put systemd:.
>> If you want the cluster to manage multiple, differently configured instances of haproxy, you might have to either create custom systemd service scripts for each one, or create an agent with parameters.
>>> With Regards
>>> Somanath Thilak J
>>> Manage your subscription:
>>> ClusterLabs home:
>>> b c3ba-5da4e39ebe912cdf&q=1&u=https%3A%2F%2Fwww.clusterlabs.org%2F
>> Manage your subscription:
>> ClusterLabs home: https://www.clusterlabs.org/
More information about the Users