[Pacemaker] Reminder: Pacemaker-1.1.10-rc5 is out there

Lars Marowsky-Bree lmb at suse.com
Thu Jun 27 10:52:58 EDT 2013


On 2013-06-27T20:50:34, Andrew Beekhof <andrew at beekhof.net> wrote:

> There was one :-)
> I merged the best bits of three parallel CPG code paths.
> The things that prompted the extra bits in one also applied to the others.

Ah, that wasn't so obvious to me when I tried making sense of the
commit. ;-) But that's cleared up now.

> Maybe you're right, maybe I should stop fighting it and go with the
> firefox approach.
> That certainly seemed to piss a lot of people off though...

If there's one message I've learned in 13 years of work on Linux HA,
then it is that people are *always* going to be pissed off. ;-)

> Then I guess I'm confused by what you meant by:
> >>> Distributions can take care of them when they integrate them; basically
> >>> they'll trickle through until the whole stack the distributions ship
> >>> builds again.
> Didn't that relate to essentially holding back not-critical-to-you changes?

Yes and no. Not in the sense of backports or selective back-outs (as
long as I can avoid them), but in as only releasing the update once the
downstream dependencies have also been adjusted.

> The day you suggest every message include a unique and immutable ID...
> lets just say you'd better start polishing that katana.

Trying to find the time to look more into SNMP interfaces and traps.
That'd probably address some more of the concerns about customers having
to churn through the logs.

And, of course, tools like crm shell's history explorer help a lot,
because that abstracts the automatic parsing from users.


Regards,
    Lars

-- 
Architect Storage/HA
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde





More information about the Pacemaker mailing list