Re: [ClusterLabs] Coming in Pacemaker 2.1.0: OCF resource agent path

On 20.05.2021 00:33, kgail...@redhat.com wrote: > Hi all, > > We squeezed one more feature into the Pacemaker 2.1.0 release for rc2: > the ability to search multiple directories for OCF resource agents. > > Previously, the OCF root (typically /usr/lib/ocf) could be specified at > build time via

[ClusterLabs] Pacemaker 2.1.0-rc2 now available

Hi all, Source code for the second release candidate for Pacemaker version 2.1.0 is now available at: https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.1.0-rc2 Changes since rc1 include new OCF-related build options discussed in an earlier message, compatibility with

Re: [ClusterLabs] #clusterlabs IRC channel

On 2021-05-19 1:10 p.m., Digimer wrote: > On 2021-05-19 12:58 p.m., Digimer wrote: >> On 2021-05-19 12:55 p.m., kgail...@redhat.com wrote: >>> Hello all, >>> >>> The ClusterLabs community has long used a #clusterlabs IRC channel on >>> the popular IRC server freenode.net. >>> >>> As you may have

[ClusterLabs] Coming in Pacemaker 2.1.0: OCF resource agent path

Hi all, We squeezed one more feature into the Pacemaker 2.1.0 release for rc2: the ability to search multiple directories for OCF resource agents. Previously, the OCF root (typically /usr/lib/ocf) could be specified at build time via ./configure --with-ocfdir, and all resource agents had to be

Re: [ClusterLabs] 32 nodes pacemaker cluster setup issue

S Sathish S: Hi Klaus, pacemaker/corosync we generated our own build from clusterlab source code. [root@node1 ~]# cat /etc/redhat-release Red Hat Enterprise Linux Server release 7.4 (Maipo) [root@node1 ~]# uname -r 3.10.0-693.82.1.el7.x86_64 [root@node1 ~]# rpm -qa | grep -iE

Re: [ClusterLabs] #clusterlabs IRC channel

On 2021-05-19 12:58 p.m., Digimer wrote: > On 2021-05-19 12:55 p.m., kgail...@redhat.com wrote: >> Hello all, >> >> The ClusterLabs community has long used a #clusterlabs IRC channel on >> the popular IRC server freenode.net. >> >> As you may have heard, freenode recently had a mass exodus of

Re: [ClusterLabs] #clusterlabs IRC channel

On 2021-05-19 12:55 p.m., kgail...@redhat.com wrote: > Hello all, > > The ClusterLabs community has long used a #clusterlabs IRC channel on > the popular IRC server freenode.net. > > As you may have heard, freenode recently had a mass exodus of staff and > channels after a corporate buy-out that

[ClusterLabs] #clusterlabs IRC channel

Hello all, The ClusterLabs community has long used a #clusterlabs IRC channel on the popular IRC server freenode.net. As you may have heard, freenode recently had a mass exodus of staff and channels after a corporate buy-out that was perceived as threatening the user community's values. Many

Re: [ClusterLabs] 32 nodes pacemaker cluster setup issue

Hi Klaus, pacemaker/corosync we generated our own build from clusterlab source code. [root@node1 ~]# cat /etc/redhat-release Red Hat Enterprise Linux Server release 7.4 (Maipo) [root@node1 ~]# uname -r 3.10.0-693.82.1.el7.x86_64 [root@node1 ~]# rpm -qa | grep -iE 'pacemaker|corosync|pcs'

Re: [ClusterLabs] 32 nodes pacemaker cluster setup issue

On 5/19/21 1:45 PM, Klaus Wenninger wrote: On 5/19/21 12:54 PM, S Sathish S wrote: Hi Klaus, pacemaker/corosync we generated our own build from clusterlab source code. [root@node1 ~]# cat /etc/redhat-release Red Hat Enterprise Linux Server release 7.4 (Maipo) [root@node1 ~]# uname -r

Re: [ClusterLabs] 32 nodes pacemaker cluster setup issue

On 5/19/21 12:54 PM, S Sathish S wrote: Hi Klaus, pacemaker/corosync we generated our own build from clusterlab source code. [root@node1 ~]# cat /etc/redhat-release Red Hat Enterprise Linux Server release 7.4 (Maipo) [root@node1 ~]# uname -r 3.10.0-693.82.1.el7.x86_64 [root@node1 ~]#

Re: [ClusterLabs] 32 nodes pacemaker cluster setup issue

Hi. Have you considered using pacemaker-remote instead? On May 18, 2021 5:55:57 PM S Sathish S wrote: Hi Team, We are setup 32 nodes pacemaker cluster setup each node has 10 resource so total [around 300+ components] are up and running. While performing installation/update with below task

[ClusterLabs] Antw: [EXT] Re: OCFS2 fragmentation with snapshots

>>> Andrei Borzenkov schrieb am 18.05.2021 um 13:05 in Nachricht : > On Tue, May 18, 2021 at 1:52 PM Ulrich Windl > wrote: >> >> Hi! >> >> I thought using the reflink feature of OCFS2 would be just a nice way to > make crash‑consistent VM snapshots while they are running. >> As it is a bit

Re: [ClusterLabs] 32 nodes pacemaker cluster setup issue

In the logs previously in this thread one could see that corosync isn't able to switch to realtime-scheduling. This can lead to timing issues if there is load - doesn't have to be excessive. Corosync had issues enabling realtime-scheduling when e.g. CPUAccounting was enabled. But that should be