On Thu, Mar 29, 2018 at 6:41 AM, Jehan-Guillaume de Rorthais <
j...@dalibo.com> wrote:
> On Wed, 28 Mar 2018 12:40:25 -0500
> Ken Gaillot wrote:
>
> > Hi all,
> >
> > Andrew Beekhof brought up a potential change to help with reading
> > Pacemaker logs.
> >
> > Currently,
Thank you for clarification!
I think you're right, our last config doesn't have any problem with asymmetric
work.
26.03.2018, 22:37, "Ken Gaillot" :
> On Tue, 2018-03-20 at 22:03 +0300, George Melikov wrote:
>> Hello,
>>
>> I tried to create an asymmetric cluster via
On Wed, 28 Mar 2018 12:40:25 -0500
Ken Gaillot wrote:
> Hi all,
>
> Andrew Beekhof brought up a potential change to help with reading
> Pacemaker logs.
>
> Currently, pacemaker daemon names are not intuitive, making it
> difficult to search the system log or understand
Hi all,
Andrew Beekhof brought up a potential change to help with reading
Pacemaker logs.
Currently, pacemaker daemon names are not intuitive, making it
difficult to search the system log or understand what each one does.
The idea is to rename the daemons, with a common prefix, and a name
that
28.03.2018 15:12, Ulrich Windl пишет:
>
> I was hoping "colocation ... ( B C D ) A" to be a shortcut of "colocation ...
> B A", "colocation ... C A", "colocation ... D A"...
>
Well, my understanding is that "colocation { B C D } { A }" should do
exactly that.
>>> Andrei Borzenkov schrieb am 28.03.2018 um 12:39 in
Nachricht :
> 28.03.2018 13:25, Ulrich Windl пишет:
>> Hi!
>>
>> For crmsh-2.1.2+git132.gbc9fde0-18.2 I think there's a bug in the manual
> describing resource sets:
>>
"Ulrich Windl" writes:
> Hi!
>
> For crmsh-2.1.2+git132.gbc9fde0-18.2 I think there's a bug in the manual
> describing resource sets:
>
>sequential
>If true, the resources in the set do not depend on each other
> internally. Setting
28.03.2018 13:25, Ulrich Windl пишет:
> Hi!
>
> For crmsh-2.1.2+git132.gbc9fde0-18.2 I think there's a bug in the manual
> describing resource sets:
>
>sequential
>If true, the resources in the set do not depend on each other
> internally. Setting sequential to true implies
Hi!
For crmsh-2.1.2+git132.gbc9fde0-18.2 I think there's a bug in the manual
describing resource sets:
sequential
If true, the resources in the set do not depend on each other
internally. Setting sequential to true implies a strict order of dependency
within the set.
>>> "Hayden,Robert" schrieb am 27.03.2018 um 20:12 in
Nachricht
:
> Thought I would share an experience with the community. We have RHEL 7.4
> clusters that uses the heartbeat LVM resource (HA-LVM
10 matches
Mail list logo