Hi everyone,
As some of you may know, I have started developing crmsh together with
Dejan, and have been working on new features for an eventual
2.0-release some time next year.
Location constraints have gotten some new capabilities in recent
versions of Pacemaker, and I have some suggested
On 2013-12-13T10:16:41, Kristoffer Grönlund kgronl...@suse.com wrote:
Lars (lmb) suggested that we might switch to using the { } - brackets
around resource sets everywhere for consistency. My only concern with
that would be that it would be a breaking change to the previous crmsh
syntax.
Hi,
Just thought that I was missing in location, something like: node=any :)
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started:
Am Freitag, 13. Dezember 2013, 10:25:48 schrieb Lars Marowsky-Bree:
On 2013-12-13T10:16:41, Kristoffer Grönlund kgronl...@suse.com wrote:
Lars (lmb) suggested that we might switch to using the { } - brackets
around resource sets everywhere for consistency. My only concern with
that would be
Hi All,
I see in PCMK Expl.
Explein
http://clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/s-resource-ordering.html#_mandatory_ordering
What the parameter kind? Written since 1.1.2
This unrealized plans or something I do not understand?
On 2013-12-13T13:51:27, Andrey Groshev gre...@yandex.ru wrote:
Just thought that I was missing in location, something like: node=any :)
Can you describe what this is supposed to achieve?
any is the default for symmetric clusters anyway.
Regards,
Lars
--
Architect Storage/HA
SUSE LINUX
On Fri, 13 Dec 2013 13:57:59 +0400
Andrey Groshev gre...@yandex.ru wrote:
Hi All,
I see in PCMK Expl.
Explein
http://clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/s-resource-ordering.html#_mandatory_ordering
What the parameter kind? Written since 1.1.2
This unrealized
On Fri, 13 Dec 2013 10:55:32 +0100
Michael Schwartzkopff m...@sys4.de wrote:
Order for colocations and order constraints: Please don't do it.
Everybody got use to the ordering as it is now. It also makes sense.
Please remember the irritations we had moving from heartbeat 2.0
(with XML,
On 2013-12-13T11:46:05, Kristoffer Grönlund kgronl...@suse.com wrote:
This worries me as well, however the current syntax for constraints is
confusing and error-prone.
Right. At least the { } would make it clear to users that it's now a
resource set and not merely more than 2 in the same
Hi All,
I have a 3 node setup with HB+pacemaker. I wanted to run redis in
master-slave mode using an ocf script.
https://groups.google.com/forum/#!msg/redis-db/eY3zCKnl0G0/lW5fObHrjwQJ
But with the below configuration , I am able to start in master-slave mode
but pacemaker is not monitoring the
Please do not merge colocation and order together in a way that only none or both is present.
Example 1: Resource A communicates with resource B over network but A must run before B.
In this case only order is needed without colocation.
Example 2: Resource A and B share a local directory
On 2013-12-13T13:11:30, Rainer Brestan rainer.bres...@gmx.net wrote:
Please do not merge colocation and order together in a way that only none or
both is present.
This was never the plan.
The idea was to offer an additional construct that provides both
properties, since *most of the time*,
Am Freitag, 13. Dezember 2013, 13:34:24 schrieb Dvorak Andreas:
Dear all,
after a little break I am coming back to my problem to configure heartbeat /
interconnect with cman. Meanwhile I know that cman is the recommended stack
on RHEL6.
I have a pacemaker cluster with cman that is working,
- Original Message -
From: Andrey Groshev gre...@yandex.ru
To: The Pacemaker cluster resource manager pacemaker@oss.clusterlabs.org
Sent: Thursday, December 12, 2013 4:14:20 AM
Subject: Re: [Pacemaker] Time to get ready for 1.1.11
And why not include it?
2013/12/12 Andreas Kurz andr...@hastexo.com
On 2013-12-12 17:53, Michael Böhm wrote:
How can i fix this? Its only a simple call in line 142:
NODENAME=$(ocf_local_nodename)
This function is also part of the ocf-shellfuncs in newer resource-agent
versions ... since that version your
I am confused on where and what to download pacemaker's doc and software
On the documentation:
I am running SUSE, per http://clusterlabs.org/doc/
I should look at
SLES11: 1.1-plugin
But it does not match any of the description:
Pacemaker 1.1 for Corosync 2.x and crmsh
Pacemaker 1.1 for Corosync
I can't speak to SUSE, but I can say that you want the 'crmsh' version
of the pacemaker docs.
On 13/12/13 14:32, John Wei (John, RDCC) wrote:
I am confused on where and what to download pacemaker’s doc and software
On the documentation:
I am running SUSE, per
Hi,
I'm trying to build Pacemaker-1.1.10 (from git), with corosync 2.3.2 and libqb
0.16.0 on a CentOS 5.10 64b system.
I have latest auto tools (automake 1.14, autoconf 2.69, lib tool 2.4,
pkg-config 0.27.1)
For Pacemaker, I'm doing:
./autogen.sh
./configure --with-corosync --with-cs-quorum
13.12.2013 15:39, Lars Marowsky-Bree wrote:
On 2013-12-13T13:11:30, Rainer Brestan rainer.bres...@gmx.net wrote:
Please do not merge colocation and order together in a way that only none or
both is present.
This was never the plan.
The idea was to offer an additional construct that
On 2013-12-13T19:32:53, John Wei (John, RDCC) joh...@huawei.com wrote:
I am confused on where and what to download pacemaker's doc and software
On the documentation:
I am running SUSE, per http://clusterlabs.org/doc/
Hi John,
which version of SUSE are you running? For openSUSE, you can
On 2013-12-14T01:11:17, Vladislav Bogdanov bub...@hoster-ok.com wrote:
The idea was to offer an additional construct that provides both
properties, since *most of the time*, that's what users want. In the
interest of clarity and brevity in the configuration, this would be
quite useful.
21 matches
Mail list logo
