Re: [ClusterLabs] How to generate RPMs for Pacemaker release 2.x on Centos

2018-10-17 Thread Jan Pokorný
On 15/10/18 14:46 +, Lopez, Francisco Javier [Global IT] wrote: > I could not do that way as this box does not have access to Internet. > Will see how to deal with this. As Ken mentioned, current upstream-devised RPM packaging practices are wrapped around the assumption of working with git

Re: [ClusterLabs] Re: How to generate RPMs for Pacemaker release 2.x on Centos

2018-10-17 Thread Ken Gaillot
On Wed, 2018-10-17 at 15:58 +, Lopez, Francisco Javier [Global IT] wrote: > Hello guys. > > I finally created the RPMs for Pacemaker and Resource Agents. I will > paste > in this thread the way to do that so it can help any other like me :- > ) > > I need a final update, hopefully, from you

Re: [ClusterLabs] Re: How to generate RPMs for Pacemaker release 2.x on Centos

2018-10-17 Thread Lopez, Francisco Javier [Global IT]
Hello guys. I finally created the RPMs for Pacemaker and Resource Agents. I will paste in this thread the way to do that so it can help any other like me :-) I need a final update, hopefully, from you guys about this issue ... I need to know if there is any compatibility or certification matrix

Re: [ClusterLabs] Fwd: Not getting Fencing monitor alerts

2018-10-17 Thread Ken Gaillot
On Wed, 2018-10-17 at 12:18 +0530, Rohit Saini wrote: > Hi Klaus, > Please see answers below for your queries: > > Do you have any evidence that monitoring is happening when "resources > are unreachable" > ( == fence_virtd is reachable?) like logs? > [Rohit] Yes, monitoring is happening. I have

[ClusterLabs] fence-agents v4.3.1

2018-10-17 Thread Oyvind Albrigtsen
ClusterLabs is happy to announce fence-agents v4.3.1, which is a bugfix release for v4.3.0. The source code is available at: https://github.com/ClusterLabs/fence-agents/releases/tag/v4.3.1 The most significant enhancements in this release are: - bugfixes and enhancements: - fence_openstack:

Re: [ClusterLabs] corosync in multicast mode produces lots of unicast traffic

2018-10-17 Thread Jan Friesse
Klaus, Hi Jan! Thanks for your answer. I have a Proxmox cluster which uses Corosync as cluster engine. Corosync uses the "default" multicast configuration. Nevertheless, using tcpdump I see much more packets sent by corosync using unicast between the node members than multicast packets. Is

[ClusterLabs] resource-agents v4.2.0 rc1

2018-10-17 Thread Oyvind Albrigtsen
ClusterLabs is happy to announce resource-agents v4.2.0 rc1. Source code is available at: https://github.com/ClusterLabs/resource-agents/releases/tag/v4.2.0rc1 The most significant enhancements in this release are: - new resource agents: - aliyun-vpc-move-ip - gcp-pd-move - gcp-vpc-move-ip -

Re: [ClusterLabs] corosync in multicast mode produces lots of unicast traffic

2018-10-17 Thread Klaus Darilion
Hi Jan! Thanks for your answer. >> I have a Proxmox cluster which uses Corosync as cluster engine. >> Corosync uses the "default" multicast configuration. Nevertheless, >> using tcpdump I see much more packets sent by corosync using unicast >> between the node members than multicast packets. >>

Re: [ClusterLabs] Fwd: Not getting Fencing monitor alerts

2018-10-17 Thread Rohit Saini
Hi Klaus, Please see answers below for your queries: Do you have any evidence that monitoring is happening when "resources are unreachable" ( == fence_virtd is reachable?) like logs? *[Rohit]* Yes, monitoring is happening. I have already tested this. I'm getting pcs alerts accurately when

Re: [ClusterLabs] corosync in multicast mode produces lots of unicast traffic

2018-10-17 Thread Jan Friesse
Klaus, Hi! I have a Proxmox cluster which uses Corosync as cluster engine. Corosync uses the "default" multicast configuration. Nevertheless, using tcpdump I see much more packets sent by corosync using unicast between the node members than multicast packets. Is this normal behavior? If