[Pacemaker] Show all resource properties with crmsh

[Andrei Borzenkov]

В Tue, 14 Oct 2014 11:06:28 +0200
Dejan Muhamedagic <dejanmm at fastmail.fm> пишет:

> 
> Do you have any specific meta attributes in mind? Taking a
> cursory look doesn't reveal anything very interesting.
> 

I was recently bitten by "interleave". Having not much experience so
far, I do not know if there are more attributes that can influence
pacemaker decisions. I assume there are or that they may be added. 

> > >
> > > But why would you want to have this?
> > >
> > 
> > Because otherwise I must somehow find what defaults are and this may
> > change from release to release and from vendor to vendor. I simply
> > want to make sure I have all necessary information that may influence
> > cluster behavior.
> 
> We try hard to keep the defaults the same between releases, even
> when they're in retrospective considered to be less than optimal.
> Otherwise, the existing cluster configurations may fail. But
> there's no guarantee.
> 

Exactly :)

> It would be possible to implement a small utility which would
> compare defaults of two RA meta-data. There are also meta-data in
> crmd, pengine, cib, and stonithd, representing various global
> cluster properties.
> 

I'm not sure I understand, but probably simple use case. I get report
of a problem and get logs + cib. I need to understand why pacemaker
made this decision. For this I obviously must know exact configuration.
I simply want to avoid "assuming" anything.

So I'm not interesting in comparing defaults (although this would be
useful for update anyway - as pre-flight check to ensure configuration
won't change in incompatible way). I'm simply interested in getting
actual values without need to dig into sources of this specific version
I happen to work with. Something similar to corosync-cmapctl that dumps
full configuration.