On 22.01.2018 16:44, Ken Gaillot wrote:
> On Mon, 2018-01-22 at 14:18 +0100, Ulrich Windl wrote:
>> Did you try meta clone-node-min=3?
> clone-min does not affect the clone it's configured on, but rather
> anything ordered relative to it via a constraint. It's for the case
> where a resource
On Mon, 2018-01-22 at 14:18 +0100, Ulrich Windl wrote:
> Did you try meta clone-node-min=3?
clone-min does not affect the clone it's configured on, but rather
anything ordered relative to it via a constraint. It's for the case
where a resource needs a certain number of instances running before
On 01/22/2018 02:55 PM, alu...@poczta.onet.pl wrote:
> Unfortunately meta clone-min introduced since 1.1.14 but I am using
> 1.1.12.
>
> Is there any other options to have such type of resource? If not I
> have to updatepacemaker software.
Other possibility coming to my mind would be 3 primitives
Unfortunately meta clone-min introduced since 1.1.14 but I am using 1.1.12.
Is there any other options to have such type of resource? If not I have
to updatepacemaker software.
On 22.01.2018 14:18, Ulrich Windl wrote:
> Did you try meta clone-node-min=3?
>
>
"alu...@poczta.onet.pl"
Did you try meta clone-node-min=3?
>>> "alu...@poczta.onet.pl" schrieb am 22.01.2018 um
>>> 13:29
in Nachricht <844fdf99-1680-3ed8-6afc-8b3e2ddea...@poczta.onet.pl>:
> I need to create configuration when one resource is active on all nodes
> and is only active when all