On 2017-09-18 02:55 PM, Ken Gaillot wrote:
> On Mon, 2017-09-18 at 13:53 -0400, Digimer wrote:
>> On 2017-09-18 01:48 PM, Ken Gaillot wrote:
>>> As discussed at the recent ClusterLabs Summit, I plan to start the
>>> release cycle for Pacemaker 1.1.18 soon.
>>>
>>> There will be the usual bug
On Mon, 2017-09-18 at 13:53 -0400, Digimer wrote:
> On 2017-09-18 01:48 PM, Ken Gaillot wrote:
> > As discussed at the recent ClusterLabs Summit, I plan to start the
> > release cycle for Pacemaker 1.1.18 soon.
> >
> > There will be the usual bug fixes and a few small new features, but
> the
> >
On 2017-09-18 01:48 PM, Ken Gaillot wrote:
> As discussed at the recent ClusterLabs Summit, I plan to start the
> release cycle for Pacemaker 1.1.18 soon.
>
> There will be the usual bug fixes and a few small new features, but the
> main goal will be to provide a final 1.1 release that Pacemaker
As discussed at the recent ClusterLabs Summit, I plan to start the
release cycle for Pacemaker 1.1.18 soon.
There will be the usual bug fixes and a few small new features, but the
main goal will be to provide a final 1.1 release that Pacemaker 2.0 can
branch from.
As such, 1.1.18 will start to
The license would be GPL, I suppose, whatever enthusiasts and community
contributors usually do. And yes, it would be fun to know I contributed
something to the repo.
--
Eric Robinson
> -Original Message-
> From: Kristoffer Grönlund [mailto:kgronl...@suse.com]
> Sent: Monday,
Eric Robinson writes:
> This is obviously beta as it currently only works with a manual failover. I
> need to add some code to handle an actual node crash or power-plug test.
>
> Feedback, suggestions, improvements are welcome. If someone who knows awk
> wants to clean
Thanks for the clarification.
So we will stay with the work-around to have dependent resources unmanaged
while cleaning up.
Kind regards
Andreas Cart
-Original Message-
From: Ken Gaillot [mailto:kgail...@redhat.com]
Sent: Freitag, 15. September 2017 17:58
On Fri, 2017-09-15 at 15:23