Is it possible to put a location constraint on a resource such that it
will only run on a pacemaker-remote node? Or vice-versa, so that a
resource will not run on a pacemaker-remote node?
At a glance, this doesn't seem possible as the pacemaker-remote node
does not exist as a entry in the CIB, so
*From:* Andrew Beekhof
*Sent:* 2014-09-02 02:58:53 EDT
*To:* The Pacemaker cluster resource manager
*Subject:* Re: [Pacemaker] pacemaker-remote container as a clone resource
> On 1 Sep 2014, at 1:32 pm, Patrick Hem
*From:* Andrew Beekhof
*Sent:* 2014-08-31 23:16:10 EDT
*To:* The Pacemaker cluster resource manager
*Subject:* Re: [Pacemaker] pacemaker-remote container as a clone resource
> On 1 Sep 2014, at 12:41 pm, Patrick Hemmer wrote:
>
>> From: Andrew Beekhof
>> Sent: 2014-08-31
*From:* Andrew Beekhof
*Sent:* 2014-08-31 19:57:43 EDT
*To:* The Pacemaker cluster resource manager
*Subject:* Re: [Pacemaker] pacemaker-remote container as a clone resource
> On 31 Aug 2014, at 6:09 pm, Patrick Hemmer wrote:
>
>> I'm interested in creating a resource that
I'm interested in creating a resource that will control host containers
running pacemaker-remote. The catch is that I want this resource to be a
clone, so that if I want more containers, I simply increase the
`clone-max` property. The problem is that the `remote-node` meta
parameter is set on the c
*From: *Andrew Beekhof
*Sent: * 2014-06-21 21:40:44 EDT
*To: *The Pacemaker cluster resource manager
*Subject: *Re: [Pacemaker] Alternative communication engine to corosync
(etcd/consul/zookeeper/doozerd)
> IF someone else implemented such a thing I would be happy to look at
> including support
*From: *Andrew Beekhof
*Sent: * 2014-06-20 04:48:25 EDT
*To: *The Pacemaker cluster resource manager
*Subject: *Re: [Pacemaker] Alternative communication engine to corosync
(etcd/consul/zookeeper/doozerd)
> On 20 Jun 2014, at 2:14 pm, Patrick Hemmer wrote:
>
>> After the demis
After the demise of the old heartbeat service, and the switch to
corosync as the primary (sole) method of communication between nodes,
has there ever been any consideration into using services such as etcd,
consul, zookeeper, or doozerd?
These alternative communication engines offer some stuff tha
*From: *Andrew Beekhof
*Sent: * 2014-06-11 02:36:15 EDT
*To: *The Pacemaker cluster resource manager
*Subject: *Re: [Pacemaker] resources not rebalancing
> On 11 Jun 2014, at 3:44 pm, Patrick Hemmer wrote:
>
>>> Right. But each node still has 4998000+ units with which
*From: *Andrew Beekhof
*Sent: * 2014-06-10 02:25:09 EDT
*To: *The Pacemaker cluster resource manager
*Subject: *Re: [Pacemaker] resources not rebalancing
> On 5 Jun 2014, at 10:38 am, Patrick Hemmer wrote:
>
>> From: Andrew Beekhof
>> Sent: 2014-06-04 20:15:22 EDT
>> T
*From: *Andrew Beekhof
*Sent: * 2014-06-04 20:15:22 EDT
*To: *The Pacemaker cluster resource manager
*Subject: *Re: [Pacemaker] resources not rebalancing
> On 5 Jun 2014, at 12:57 am, Patrick Hemmer wrote:
>
>> From: Andrew Beekhof
>> Sent: 2014-06-04 04:15:48 E
>> T
*From: *Andrew Beekhof
*Sent: * 2014-06-04 04:15:48 E
*To: *The Pacemaker cluster resource manager
*Subject: *Re: [Pacemaker] resources not rebalancing
> On 4 Jun 2014, at 4:22 pm, Patrick Hemmer wrote:
>
>> Testing some different scenarios, and after bringing a node back online,
Testing some different scenarios, and after bringing a node back online,
none of the resources move to it unless they are restarted. However
default-resource-stickiness is set to 0, so they should be able to move
around freely.
# pcs status
Cluster name: docker
Last updated: Wed Jun 4 06:09:26 20
Is there any way to view the currenly in-process operations? Basically
I'd like to be able to see when a resource is currently in the middle of
a start/stop/monitor operation.
A specific pain point on this, I have resource A and resource B. B
depends on A, and has an order constraint to start last
-12-06T11:21:02, Patrick Hemmer wrote:
>
>>> So where is the problem? If the script returns "ERROR" than pacemaker has
>>> to
>>> acct accordingly.
>> If the script returns "ERROR" the `on-fail=ignore` should make it do
>> nothing. Amazon&
-12-06T11:21:02, Patrick Hemmer wrote:
>
>>> So where is the problem? If the script returns "ERROR" than pacemaker has
>>> to
>>> acct accordingly.
>> If the script returns "ERROR" the `on-fail=ignore` should make it do
>> nothing. Amazon&
n-fail=ignore not restarting when
>> resource
>> reported as stopped
>>
>>> Am Freitag, 6. Dezember 2013, 10:11:07 schrieb Patrick Hemmer:
>>>> I have a resource which updates DNS records (Amazon's Route53). When it
>>>> performs it's `monit
I have a resource which updates DNS records (Amazon's Route53). When it
performs it's `monitor` action, it can sometimes fail because of issues
with Amazon's API. So I want failures to be ignored for the monitor
action, and so I set `op monitor on-fail=ignore`. However now when the
monitor action c
It looks like when using pacemaker with cman, pacemaker gets the name of
the node from the 'name' attribute. Is there any way to
override this?
If the node has multiple interfaces, I may want corosync to use an
interface other than the node's main interface as the main interface for
communic
19 matches
Mail list logo
