Re: [ClusterLabs] Corosync 3.x and Pacemaker 2.x supported OS versions
Somanath, Hi All , We are planning to update to corosync 3.x and pacemaker 2.x versions. I want to confirm whether this is supported on RHEL 7.X OS version. Answering just Corosync part of the question (eventho pcmk is probably very similar story). If "supported" means officially supported, then no, it is not supported (and never will). If you mean "it is possible to compile there and it will work" then yes, it is "supported". We even have unofficial autogenerated packages: https://kronosnet.org/builds/corosync/. Regards, Honza With Regards Somanath Thilak J ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/ ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] Adding HAProxy as a Resource
Hi Ken, I am using the below versions Pacemaker - 1.1.16 Corosync - 2.4.3 PCS - 0.9 Resource agents - 3.9.6 During running configure I didn’t give any options. I just ran configure.sh and then did a make install. With Regards Somanath Thilak J -Original Message- From: Ken Gaillot Sent: Thursday, July 25, 2019 7:22 PM To: Cluster Labs - All topics related to open-source clustering welcomed ; Tomas Jelinek Subject: Re: [ClusterLabs] Adding HAProxy as a Resource On Thu, 2019-07-25 at 07:23 +, Somanath Jeeva wrote: > Hi > > 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. Hi Somanath, Which version of pacemaker are you using? If you built it from source, did you give any options to the configure command? > > > > With Regards > Somanath Thilak J > > -Original Message- > From: Tomas Jelinek > Sent: Monday, July 15, 2019 5:58 PM > To: users@clusterlabs.org > Subject: Re: [ClusterLabs] Adding HAProxy as a Resource > > Hi, > > 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. > > Regards, > Tomas > > > Dne 11. 07. 19 v 10:14 Somanath Jeeva napsal(a): > > Hi > > > > 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 > > interval=2s > > 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 > > Sent: Thursday, July 11, 2019 1:22 PM > > To: Cluster Labs - All topics related to open-source clustering > > welcomed > > Cc: Somanath Jeeva > > 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. > > > > Hello, > > > > 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. > > > > Cheers, > > Kristoffer > > > > > > > > > > > > > > With Regards > > > Somanath Thilak J > > > > > > > > > ___ > > > Manage your subscription: > > > https://protect2.fireeye.com/url?k=28466b53-74926310-28462bc8-86a1150 > > > b > > > c3ba- > > > bb674f3a9b557cbd=1=https%3A%2F%2Flists.clusterlabs.org%2Fmai > > > l > > > man%2Flistinfo%2Fusers > > > > > > ClusterLabs home: > > > https://protect2.fireeye.com/url?k=4c5edd73-108ad530-4c5e9de8-86a1150 > > > b c3ba-5da4e39ebe912cdf=1=https%3A%2F%2F > > > www.clusterlabs.org%2F > > > > ___ > > Manage your subscription: > > https://lists.clusterlabs.org/mailman/listinfo/users > > > > ClusterLabs home: https://www.clusterlabs.org/ > > > > ___ > Manage your subscription: > https://lists.clusterlabs.org/mailman/listinfo/users > > ClusterLabs home: https://www.clusterlabs.org/ -- Ken Gaillot ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
[ClusterLabs] Strange behaviour of group resource
Hi, I have around 10 filesystems in a group. When I do a crm resource refresh, the filesystems are unmounted and remounted, starting from the fourth resource in the group. Any idea what could be going on, is it expected ? Thanks & Regards Dileep Nair Squad Lead - SAP Base Togaf Certified Enterprise Architect IBM Services for Managed Applications +91 98450 22258 Mobile dilen...@in.ibm.com IBM Services ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] Adding HAProxy as a Resource
On Thu, 2019-07-25 at 07:23 +, Somanath Jeeva wrote: > Hi > > 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. Hi Somanath, Which version of pacemaker are you using? If you built it from source, did you give any options to the configure command? > > > > With Regards > Somanath Thilak J > > -Original Message- > From: Tomas Jelinek > Sent: Monday, July 15, 2019 5:58 PM > To: users@clusterlabs.org > Subject: Re: [ClusterLabs] Adding HAProxy as a Resource > > Hi, > > 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. > > Regards, > Tomas > > > Dne 11. 07. 19 v 10:14 Somanath Jeeva napsal(a): > > Hi > > > > 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 > > interval=2s > > 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 > > Sent: Thursday, July 11, 2019 1:22 PM > > To: Cluster Labs - All topics related to open-source clustering > > welcomed > > Cc: Somanath Jeeva > > 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. > > > > Hello, > > > > 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. > > > > Cheers, > > Kristoffer > > > > > > > > > > > > > > With Regards > > > Somanath Thilak J > > > > > > > > > ___ > > > Manage your subscription: > > > https://protect2.fireeye.com/url?k=28466b53-74926310-28462bc8-86a1150 > > > b > > > c3ba- > > > bb674f3a9b557cbd=1=https%3A%2F%2Flists.clusterlabs.org%2Fmai > > > l > > > man%2Flistinfo%2Fusers > > > > > > ClusterLabs home: > > > https://protect2.fireeye.com/url?k=4c5edd73-108ad530-4c5e9de8-86a1150 > > > b c3ba-5da4e39ebe912cdf=1=https%3A%2F%2F > > > www.clusterlabs.org%2F > > > > ___ > > Manage your subscription: > > https://lists.clusterlabs.org/mailman/listinfo/users > > > > ClusterLabs home: https://www.clusterlabs.org/ > > > > ___ > Manage your subscription: > https://lists.clusterlabs.org/mailman/listinfo/users > > ClusterLabs home: https://www.clusterlabs.org/ -- Ken Gaillot ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] Feedback wanted: Node reaction to fabric fencing
On 24/07/19 12:33 -0500, Ken Gaillot wrote: > A recent bugfix (clbz#5386) brings up a question. > > A node may receive notification of its own fencing when fencing is > misconfigured (for example, an APC switch with the wrong plug number) > or when fabric fencing is used that doesn't cut the cluster network > (for example, fence_scsi). One related idea that'd be better to think through on its own pace, whether it would make sense to maximize the benefit of knowing which kind of behaviour to expect from particular abstracted fencing device. Is it absolute cut-off of the whole node's acting, or is it just a partial isolation where it presumably matters the most (access to disk, access to network resources, ...)? Then, a dichotomy in failure modes could be introduced, since these are effectively _different_ disaster limiting scenarios with different pros and cons (consider also debug-ability). I always had mixed feelings about putting total/partial fencing into the same bucket. Apparently, that information would need to be propagated via the metadata of the agents, meaning pulling more complexity on that level. Broader picture might even be that compositions of the resources could as well point out which kinds of shared resources are in danger of amplifying the failure/causing split brain etc. and hence offer the feedback which of these are yet to be covered if the absolute cut-off is not preferred/available for whatever reason. /me gets back from daydreaming -- Poki pgpoaxij46hZj.pgp Description: PGP signature ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] Feedback wanted: Node reaction to fabric fencing
On Thu, Jul 25, 2019 at 3:20 AM Ondrej wrote: > > Is there any plan on getting this also into 1.1 branch? > If yes, then I would be for just introducing the configuration option in > 1.1.x with default to 'stop'. > +1 for back porting it from someone who just recently hit this (puzzling) behavior. ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] Feedback wanted: Node reaction to fabric fencing
On 7/25/19 1:33 AM, Ken Gaillot wrote: > Hi all, > > A recent bugfix (clbz#5386) brings up a question. > > A node may receive notification of its own fencing when fencing is > misconfigured (for example, an APC switch with the wrong plug number) > or when fabric fencing is used that doesn't cut the cluster network > (for example, fence_scsi). > > Previously, the *intended* behavior was for the node to attempt to > reboot itself in that situation, falling back to stopping pacemaker if > that failed. However, due to the bug, the reboot always failed, so the > behavior effectively was to stop pacemaker. > > Now that the bug is fixed, the node will indeed reboot in that > situation. > > It occurred to me that some users configure fabric fencing specifically > so that nodes aren't ever intentionally rebooted. Therefore, I intend > to make this behavior configurable. > > My question is, what do you think the default should be? > > 1. Default to the correct behavior (reboot) > > 2. Default to the current behavior (stop) > > 3. Default to the current behavior for now, and change it to the > correct behavior whenever pacemaker 2.1 is released (probably a few > years from now) > Sounds, 3) is the best choice. Make it configurable, and keep the current behavior(stop) for backward compatibility for the current minor version, eg. next 2.0.z(3+). Well, the correct behavior (reboot) as the default should be enforced. It should be the same crucial as stop failures of a resource. Make sense in the next minor version, say, 2.1. Thanks, Roger ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] Adding HAProxy as a Resource
Hi, 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. Regards, Tomas Dne 25. 07. 19 v 9:23 Somanath Jeeva napsal(a): Hi 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 Sent: Monday, July 15, 2019 5:58 PM To: users@clusterlabs.org Subject: Re: [ClusterLabs] Adding HAProxy as a Resource Hi, 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. Regards, Tomas Dne 11. 07. 19 v 10:14 Somanath Jeeva napsal(a): Hi 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 interval=2s 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 Sent: Thursday, July 11, 2019 1:22 PM To: Cluster Labs - All topics related to open-source clustering welcomed Cc: Somanath Jeeva 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. Hello, 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. Cheers, Kristoffer With Regards Somanath Thilak J ___ Manage your subscription: https://protect2.fireeye.com/url?k=28466b53-74926310-28462bc8-86a1150 b c3ba-bb674f3a9b557cbd=1=https%3A%2F%2Flists.clusterlabs.org%2Fmai l man%2Flistinfo%2Fusers ClusterLabs home: https://protect2.fireeye.com/url?k=4c5edd73-108ad530-4c5e9de8-86a1150 b c3ba-5da4e39ebe912cdf=1=https%3A%2F%2Fwww.clusterlabs.org%2F ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/ ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] Adding HAProxy as a Resource
Hi 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 Sent: Monday, July 15, 2019 5:58 PM To: users@clusterlabs.org Subject: Re: [ClusterLabs] Adding HAProxy as a Resource Hi, 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. Regards, Tomas Dne 11. 07. 19 v 10:14 Somanath Jeeva napsal(a): > Hi > > 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 > interval=2s > 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 > Sent: Thursday, July 11, 2019 1:22 PM > To: Cluster Labs - All topics related to open-source clustering > welcomed > Cc: Somanath Jeeva > 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. > > Hello, > > 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. > > Cheers, > Kristoffer > >> >> >> >> With Regards >> Somanath Thilak J >> >> >> ___ >> Manage your subscription: >> https://protect2.fireeye.com/url?k=28466b53-74926310-28462bc8-86a1150 >> b >> c3ba-bb674f3a9b557cbd=1=https%3A%2F%2Flists.clusterlabs.org%2Fmai >> l >> man%2Flistinfo%2Fusers >> >> ClusterLabs home: >> https://protect2.fireeye.com/url?k=4c5edd73-108ad530-4c5e9de8-86a1150 >> b c3ba-5da4e39ebe912cdf=1=https%3A%2F%2Fwww.clusterlabs.org%2F > > ___ > Manage your subscription: > https://lists.clusterlabs.org/mailman/listinfo/users > > ClusterLabs home: https://www.clusterlabs.org/ > ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
