Greetings, all --
If anyone's interested, I wrote a resource agent that works with Microsoft
Azure. I'm no expert at shell scripting, so I'm certain it needs a great deal
of improvement, but I've done some testing and it works with a 2-node cluster
in my Azure environment. Offhand, I don't
On Tue, 2017-09-05 at 21:28 +0300, Vladislav Bogdanov wrote:
> 05.09.2017 17:15, Octavian Ciobanu wrote:
> > Based on ocf:heartbeat:IPaddr2 man page it can be used without an
> static
> > IP address if the kernel has
> net.ipv4.conf.all.promote_secondaries=1.
> >
> > "There must be at least one
On Fri, 2017-09-08 at 15:31 +1000, Leon Steffens wrote:
> Hi all,
>
> We are running Pacemaker 1.1.15 under Centos 6.9, and have a simple
> 3-node cluster with 6 sets of "main" and "backup" resources (just
> Dummy ones):
>
> main1
> backup1
> main2
> backup2
> etc.
>
> We have the following
On Mon, 2017-09-11 at 16:02 +0530, Anu Pillai wrote:
> Hi,
>
> We are using 3 node cluster (2 active and 1 standby).
> When failover happens, CPU utilization going high in newly active
> node as well as other active node. It is remaining in high CPU state
> for nearly 20 seconds.
>
> We have
On Tue, 2017-09-12 at 10:49 +0200, John Gogu wrote:
> Hello,
> I have created a resource group from 2 resources: pcs resource group
> add Group1 IPaddr Email. From the documentation is clear that
> resources are stopped in the reverse order in which are specified
> (Email first, then IPaddr).
>
>
On Fri, 2017-09-15 at 15:23 +, CART Andreas wrote:
> Hello
>
> I think there is a more general misunderstanding on my side.
> I reproduced the “problem” with a very simple test-cluster containing
> just 2 dummy resources:
>
> Pacemaker Nodes:
> deneb682 deneb683
>
> Resources:
>
