Hi All,
To get people started with the new things going on with kronosnet and
corosync3, I've written a document which explains what you can do with
the new configuration options, how to set up multiple links and much,
much more.
It might be helpful for people who want to write configuration tool
On Mon, 15 Jan 2018 11:05:52 -0600
Ken Gaillot wrote:
> On Thu, 2018-01-11 at 10:24 -0600, Ken Gaillot wrote:
> > On Thu, 2018-01-11 at 01:21 +0100, Jehan-Guillaume de Rorthais wrote:
> > > On Wed, 10 Jan 2018 16:10:50 -0600
> > > Ken Gaillot wrote:
> > >
> > > > Pacemaker 2.0 will be a maj
On Mon, 15 Jan 2018 11:19:27 -0600
Ken Gaillot wrote:
> On Mon, 2018-01-15 at 18:08 +0100, Klaus Wenninger wrote:
> > On 01/15/2018 05:51 PM, Ken Gaillot wrote:
> > > Currently, Pacemaker will use the same detail log as corosync if
> > > one is
> > > specified (as "logfile:" in the "logging {..
As we look to release Pacemaker 2.0 and (separately) update the OCF
standard, this is a good time to revisit the terminology and syntax we
use for master/slave resources.
I think the term "stateful resource" is a better substitute for
"master/slave resource". That would mainly be a documentation c
On 2018-01-16 05:33 PM, Ken Gaillot wrote:
> As we look to release Pacemaker 2.0 and (separately) update the OCF
> standard, this is a good time to revisit the terminology and syntax we
> use for master/slave resources.
>
> I think the term "stateful resource" is a better substitute for
> "master/
>>> Ken Gaillot schrieb am 16.01.2018 um 23:33 in
>>> Nachricht
<1516142036.5604.3.ca...@redhat.com>:
> As we look to release Pacemaker 2.0 and (separately) update the OCF
> standard, this is a good time to revisit the terminology and syntax we
> use for master/slave resources.
>
> I think the
