Hello!
one thing in advance, yes I have read the OCF developer guide and I know
that generally the cluster manager should take care of timeouts.
Anyway I am in a special situation where I want my resource agent to
monitor a timeout itself and return rather partly configured then to
timeout,
Am 04.11.2014 13:57, schrieb Felix Zachlod:
So for my RA to do this I would need access to an environment variable
that specifies the timeout of a specific action.
Okay have found the answer myself studying the ocf-tester which sets
OCF_RESKEY_CRM_meta_timeout
so no answer needed anymore
Am 29.10.2014 01:39, schrieb Andrew Beekhof:
I just have one question about how a resource agent should behave on reload
invoked if the resource is currently stopped. Should the resource be started or remain
stopped?
I don't think that is defined. Certainly pacemaker wont trigger that case
Hello folks,
I just have one question about how a resource agent should behave on
reload invoked if the resource is currently stopped. Should the
resource be started or remain stopped? I did not find anything about
that in the documentation, in gernel there are not mant informations
about
Hello Andrew,
Am 06.10.2014 04:30, schrieb Andrew Beekhof:
On 3 Oct 2014, at 5:07 am, Felix Zachlod fz.li...@sis-gmbh.info wrote:
Am 02.10.2014 18:02, schrieb Digimer:
On 02/10/14 02:44 AM, Felix Zachlod wrote:
I am currently running 8.4.5 on to of Debian Wheezy with Pacemaker 1.1.7
Am 01.10.2014 20:46, schrieb Digimer:
At some point along the way, both nodes were Primary while not
connected, even if for just a moment. Your log snippet above shows the
results of this break, they do not appear to speak to the break itself.
Even easier to reproduce is the problem when I
Am 02.10.2014 08:44, schrieb Felix Zachlod:
Am 01.10.2014 20:46, schrieb Digimer:
At some point along the way, both nodes were Primary while not
connected, even if for just a moment. Your log snippet above shows the
results of this break, they do not appear to speak to the break itself.
Even
Am 02.10.2014 09:01, schrieb Felix Zachlod:
Am 02.10.2014 08:44, schrieb Felix Zachlod:
Am 01.10.2014 20:46, schrieb Digimer:
At some point along the way, both nodes were Primary while not
connected, even if for just a moment. Your log snippet above shows the
results of this break, they do
Am 02.10.2014 18:02, schrieb Digimer:
On 02/10/14 02:44 AM, Felix Zachlod wrote:
I am currently running 8.4.5 on to of Debian Wheezy with Pacemaker 1.1.7
Please upgrade to 1.1.10+!
Are you referring to a special bug/ code change? I normally don't like
building all this stuff from source
Hello!
I'm currently experimenting how a good DRBD Dual Primary Setup can be
achieved with Pacemaker. I know all of the you have to have good
fencing in place things ... that is just what I'am currently trying to
test in my setup beside other things.
But even without a node crashing or the
Hello List,
I am currently trying to add a third node only for giving a quorum a to
the cluster in case a servicing node fails. But oviously I can't get it
right.
The third node is forced to standby and I put a location constraint just
like described in:
Am 26.09.2014 12:46, schrieb Felix Zachlod:
Hello List,
I am currently trying to add a third node only for giving a quorum a to
the cluster in case a servicing node fails. But oviously I can't get it
right.
Ok just to answer myself quickly. I found out that symetric-cluster=false
Hello Joseph!
-Ursprüngliche Nachricht-
Von: Joseph-Andre Guaragna [mailto:joseph-an...@rdmo.com]
Gesendet: Freitag, 12. April 2013 17:19
An: pacemaker@oss.clusterlabs.org
Betreff: [Pacemaker] iscsi target mounting readonly on client
You have to make two things absolutely shure.
1.
Hello gain folks,
I have been implementing a reload action for a resource agent. The action is
advertised in the meta-data and it works when invoking it directly.
According to http://linux-ha.org/wiki/OCF_Resource_Agents and
Hello!
-Ursprüngliche Nachricht-
Von: David Vossel [mailto:dvos...@redhat.com]
Gesendet: Donnerstag, 11. April 2013 16:57
An: The Pacemaker cluster resource manager
Betreff: Re: [Pacemaker] RA Supporting the reload action
Can you paste your agent's metadata in here or in pastebin
Hello!
I have another problem with my resource agent which should run in a master
slave fashion.
I successfully tested the RA with ocf-tester and it completes any promote or
demote action:
fctarget[14659]: DEBUG: Resource is running
fctarget[14659]: DEBUG: Resource is currently running as Slave
Hello Rainer,
Hi Felix,
maybe my hint is worthless, but have you implemented the crm_master calls
in your RA ?
I had not. And that was it - so simple :-)
Thanks
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
Hello Andrew,
hello everyone else.
All the other replies will work, however the original intention was that
people
would use
Thank you all for your replies. I will try the different approaches and see
which one fits best for us.
regards, Felix
Hi again,
I'd be interested to hear your conclusions.
I am currently trying your suggestion with using rules. Can anyone tell how
to apply such a config via the crm shell? I usually do not edit the xml
directly. But I cant find a way to do via the crm shell and did not find any
documentation
Hello Jake,
Might not be quite what your looking for but...
http://crmsh.nongnu.org/crm.8.html#cmdhelp_configure
Under that section find location and it talks about rule parameters
Yes I read that. But it does not work this way for the params section. I now
edited the XML and added the
It seems no rule has been selected here and it has fallen back to the
default.
It looks similar on the other node- but some times it seems that the
script is
being called with the correct params (without changing the cib, of
course). I
have no idea, why the crm seems to randomly select one of
Hello Rainer
-Ursprüngliche Nachricht-
Von: Rainer Brestan [mailto:rainer.bres...@gmx.net]
Gesendet: Dienstag, 9. April 2013 19:39
An: The Pacemaker cluster resource manager
Betreff: Re: [Pacemaker] Clone Resources Individual Configuration per Node
Hi Felix,
thats exactly the
Hello List,
I am up to writing a resource agent for Pacemaker which shall be used in a
Master/Slave manner. So the cluster shall always run two instances and one
of them shall be Master. My clone instances need a different configuration
depending on the node that they are running on. I know I
23 matches
Mail list logo
