On Tue, Apr 05, 2011 at 09:42:43AM +0200, Christoph Bartoschek wrote: > Am 04.04.2011 22:14, schrieb Lars Ellenberg: > > On Mon, Apr 04, 2011 at 09:43:27AM +0200, Andrew Beekhof wrote: > >>>>>>>>>> I am missing the state: running degraded or suboptimal. > >>>>>>>>> > >>>>>>>>> Yep, "degraded" is not a state available for pacemaker. > >>>>>>>>> Pacemaker cannot do much about "suboptimal". > > > > > >> Maybe we need to add OCF_RUNNING_BUT_DEGRADED to the OCF spec (and the PE). > > > > And, of course, OCF_MASTER_BUT_ONLY_ONE_FAILURE_AWAY_FROM_COMPLETE_DATA_LOSS > > What about using the standard output of the monitor operation as a > status string that is displayed by crm_mon if available? > > I can imagine that such a change is less intrusive.
Nope. You would need to audit every RA to not provide anything to stdout, or only provide "sanitized" strings to stdout, and so on. No. Since we agree that the "degradedness" will not affect the behaviour of the policy engine, but only serve as a "notification of the user", I'd really rather have the RA place whatever information it wants in the cib explicitly via attributes. -- : Lars Ellenberg : LINBIT | Your Way to High Availability : DRBD/HA support and consulting http://www.linbit.com _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
