Hi all,
The final release of Pacemaker version 2.0.5 is now available at:
https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.0.5
Highlights include:
* A fix for the ACL bypassing bug previously mentioned on this mailing
list and described in CVE-2020-25654.
* The CIB now
The third, and hopefully final, release candidate for Pacemaker 2.0.5 is now
available at:
https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.0.5-rc3
This release candidate largely consists of build and CI testing changes. There
is not
much that should affect most users.
The second release candidate for Pacemaker 2.0.5 is now available at:
https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.0.5-rc2
The most important change in this release candidate is a fix for the
ACL bypassing bug previously mentioned on this mailing list, and
described in
Hi all,
I am happy to announce that source code for the first release candidate
for Pacemaker version 2.0.5 is now available at:
https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.0.5-rc1
Highlights previously discussed on this list include supporting both
number and integer
This is the kind of stuff I've been working on a lot, so hopefully I've
added enough tools to make this easy to do. If not, I guess I've got
more work to do.
What's your time frame, are you lucky enough to be able to use the latest
pacemaker releases, and are you going to use command line tools
> Xpath would be powerful but crm_mon is intended to be useful without
> any XML knowledge so I'd hesitate on that. Regular expressions are
> interesting though.
xpath would be tough.
Regexes would be much easier, I think. It would require me to do a little
bit of rewriting to add a function
> the change you proposed did not work. But then I noticed, I dont have
> installed ncurses-devel - after installation the compilation went OK. I
> think it is solved for my case, but probably some bug remains...
ncurses is not a strict requirement of pacemaker, so we can't really make
its
> *crm_mon_curses.c:300:1: error: args to be formatted is not
> ‘...’ curses_indented_printf(pcmk__output_t *out, const char *format,
> va_list args) { ^~crm_mon_curses.c:300:1: error:
> conflicting types for ‘curses_indented_printf’In file included from
>
> We're finalizing meeting room arrangements and hotel discounts for the
> Feb. 5-6 ClusterLabs Summit in Brno, and we don't have much space for
> additional attendees.
>
> I currently have attendees from Alteeve, Canonical, IBM, Linbit, NTT,
> Proxmox, Red Hat, and SUSE, as well as one
> The output of the webpage is quite nice, you get a short and quick overview.
> Only some inactive resources are displayed in yellow which is impossible to
> read.
>
> Is there a way to configure the output of the hmtl-file so that it's better
> readable ?
All the formatting is hardcoded, so
> As XML is only as good as ist structure, would you present the structure of
> such XML output?
If you enjoy reading XML that describes XML, you can check out the schema here:
https://github.com/ClusterLabs/pacemaker/blob/master/xml/api/stonith_admin-1.0.rng
Also note command-output-1.0.rng in
> The pacemaker CLI commands don't always say anything when invalid
> option combinations are used (fixing that is one of the many things on
> the "would-be-nice" list).
If you run into a nonsense option combination, file a bug and CC me on it
and I'll take a look at it. I've been adding options
12 matches
Mail list logo
