[ClusterLabs] colocation - but do not stop resources on failure

lejeczek peljasz at yahoo.co.uk
Thu Jul 11 06:54:12 EDT 2019

On 10/07/2019 15:41, Ken Gaillot wrote:
> On Wed, 2019-07-10 at 10:30 +0100, lejeczek wrote:
>> On 09/07/2019 20:26, Ken Gaillot wrote:
>>> On Tue, 2019-07-09 at 11:21 +0100, lejeczek wrote:
>>>> hi guys,
>>>> how to, if possible, create colocation which would not stop
>>>> dependent
>>>> resources if the target(that would be systemd agent) resource
>>>> fails
>>>> on
>>>> all nodes?
>>>> many thanks, L.
>>> Sure, just use a finite score. Colocation is mandatory if the score
>>> is
>>> INFINITY (or -INFINITY for anti-colocation), otherwise it's a
>>> preference rather than a requirement.
>> so simple, fantastic, many! thanks.
>> Can already existing constraint be changed/updated, maybe similarly
>> to
>> how resource can? I'm thumbing through man pages but fail to find an
>> answer.
> Yes, but it depends on what configuration interface you're using
> (cibadmin / crm / pcs / etc.), so keep thumbing. ;) You want to change
> the score on an existing constraint, or if the tool doesn't offer that,
> drop the old one and add a new (you can do that in a batch file, or put
> the cluster into maintenance mode first, to avoid any resource
> shuffling while you're doing it).

It would be nice if 'pcs' could do it, would be nice to not have to use
many different tools for same one instrument.

many thanks, L.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: pEpkey.asc
Type: application/pgp-keys
Size: 1757 bytes
Desc: not available
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20190711/db2400a2/attachment.bin>

More information about the Users mailing list