On Wed, Jul 03, 2013 at 12:42:55AM +0300, Vladislav Bogdanov wrote:
02.07.2013 20:05, Dejan Muhamedagic wrote:
On Tue, Jul 02, 2013 at 11:05:01AM +0300, Vladislav Bogdanov wrote:
28.06.2013 17:47, Dejan Muhamedagic wrote:
...
If you want to test here's a new patch. It does work with
Hi,
On Tue, Jul 02, 2013 at 10:36:37PM +0200, Arnold Krille wrote:
Just a small comment, maybe of benefit to others...
On Mon, 01 Jul 2013 16:31:13 -0400 William Seligman
selig...@nevis.columbia.edu wrote:
Poisoned resource
This is the one you can directly attribute to my stupidity.
Dejan Muhamedagic deja...@fastmail.fm schrieb am 03.07.2013 um 10:29 in
Nachricht 20130703082919.GB4831@walrus.homenet:
[...]
New resources can also be tested on all nodes by crm configure
rsctest. The test is completely driven by crmsh and won't disturb
the cluster in any way.
Can you sketch
On 2013-07-03T00:20:19, Vladislav Bogdanov bub...@hoster-ok.com wrote:
I do not edit them. I my setup I generate full crm config with
template-based framework.
And then you do a load/replace? Tough; yes, that'll clearly overwrite
what is already there and added by scripts that more dynamically
Le 02/07/2013 00:53, Chris Feist a écrit :
pcs resource create myping ocf:pacemaker:ping
host_list=www.microsoft.com timeout=5 op monitor interval=10
You want to put the host_list and timeout before 'op' because they're
options for the ocf:pacemaker:ping resource agent.
And maybe ping a more
On 2013-07-03T10:26:09, Dejan Muhamedagic deja...@fastmail.fm wrote:
Not sure that is expected by most people.
How you then delete attributes?
Tough call :) Ideas welcome.
Set them to an empty string, or a magic #undef value.
It's not only for the nodes. Attributes of resources should be
Am 03.07.2013 12:03, schrieb Florian Crouzat:
Le 02/07/2013 00:53, Chris Feist a écrit :
pcs resource create myping ocf:pacemaker:ping
host_list=www.microsoft.com timeout=5 op monitor interval=10
You want to put the host_list and timeout before 'op' because they're
options for the
Hi Lars,
On Wed, Jul 03, 2013 at 12:05:17PM +0200, Lars Marowsky-Bree wrote:
On 2013-07-03T10:26:09, Dejan Muhamedagic deja...@fastmail.fm wrote:
Not sure that is expected by most people.
How you then delete attributes?
Tough call :) Ideas welcome.
Set them to an empty string, or a
Hi Ulrich,
On Wed, Jul 03, 2013 at 11:50:59AM +0200, Ulrich Windl wrote:
Dejan Muhamedagic deja...@fastmail.fm schrieb am 03.07.2013 um 10:29 in
Nachricht 20130703082919.GB4831@walrus.homenet:
[...]
New resources can also be tested on all nodes by crm configure
rsctest. The test is
03.07.2013 13:00, Lars Marowsky-Bree wrote:
On 2013-07-03T00:20:19, Vladislav Bogdanov bub...@hoster-ok.com wrote:
I do not edit them. I my setup I generate full crm config with
template-based framework.
And then you do a load/replace? Tough; yes, that'll clearly overwrite
Actually 'load
03.07.2013 15:43, Dejan Muhamedagic wrote:
Hi Lars,
On Wed, Jul 03, 2013 at 12:05:17PM +0200, Lars Marowsky-Bree wrote:
On 2013-07-03T10:26:09, Dejan Muhamedagic deja...@fastmail.fm wrote:
Not sure that is expected by most people.
How you then delete attributes?
Tough call :) Ideas
On Tue, Jul 02, 2013 at 07:53:52AM +0300, Vladislav Bogdanov wrote:
01.07.2013 18:29, Dejan Muhamedagic wrote:
Hi,
On Mon, Jul 01, 2013 at 05:29:31PM +0300, Vladislav Bogdanov wrote:
Hi,
I'm trying to look if it is now safe to delete non-running nodes
(corosync 2.3, pacemaker HEAD,
I'm setting up a 4-node cluster where 2 of the nodes will run an
active/active DRBD and the other two nodes will be available in case one
of the active nodes fails.
I can almost get this working fine. But, what I can't seem to figure
out is how to restrict the DRBD Masters to only certain
13 matches
Mail list logo
