On Thu, 2021-05-20 at 07:53 +0300, Andrei Borzenkov wrote:
> On 20.05.2021 00:33, kgail...@redhat.com wrote:
> > Hi all,
> >
> > We squeezed one more feature into the Pacemaker 2.1.0 release for
> > rc2:
> > the ability to search multiple directories for OCF resource agents.
> >
> > Previously,
On 20.05.2021 00:33, kgail...@redhat.com wrote:
> Hi all,
>
> We squeezed one more feature into the Pacemaker 2.1.0 release for rc2:
> the ability to search multiple directories for OCF resource agents.
>
> Previously, the OCF root (typically /usr/lib/ocf) could be specified at
> build time via
Hi all,
We squeezed one more feature into the Pacemaker 2.1.0 release for rc2:
the ability to search multiple directories for OCF resource agents.
Previously, the OCF root (typically /usr/lib/ocf) could be specified at
build time via ./configure --with-ocfdir, and all resource agents had
to be
Update: I've decided to bump Pacemaker's minimum dependencies higher.
This allows us to have a readily available platform to use with our
continuous integration testing, to ensure we support what we claim to,
rather than finding out much later after the fact that we broke some
build.
I'm now
Hi all,
The Pacemaker 2.1.0 release, expected toward the middle of this year,
will be backward compatible in the CIB and C API. The middle version
number is being bumped to draw attention to more significant changes
than usual, including changes that may affect custom scripts or
building
Hi all,
A recurring request we've seen from Pacemaker users is a feature called
"non-critical resources" in a proprietary product and "independent
subtrees" in the old rgmanager project.
An example is a large database with an occasionally used reporting
tool. The reporting tool is colocated or
Hi all,
The Pacemaker 2.1.0 release, expected toward the middle of this year,
will be fully backward compatible in both the CIB and the C API. The
middle version number is being bumped to draw attention to more
significant changes than usual, including changes that may affect
custom scripts or
Hi all,
The recent 2.0.5 release will be the last in Pacemaker's 2.0 series.
The next release (toward the middle of this year) will be 2.1.0, which
will be fully backward compatible in both the CIB and the C API.
The middle number is being bumped to draw attention to more significant
changes
Hi all,
Soon, the first release candidate for Pacemaker 2.0.5 will come out,
with final release expected by the end of the year. Chris Lumens will
coordinate the 2.0.5 release, so look for announcements from him soon.
Beyond that, we are planning a 2.1.0 release in the first half of next
year.
