"maintenance mode" is what I certainly want to do. I misunderstood the intention of is_managed. Is the implementation about ignore monitoring included in the next release? and the "disabled" field of "op" objects would be useful if it works well. (it did work with v2.0.8)
Thanks, Junko > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Lars Marowsky-Bree > Sent: Monday, June 18, 2007 8:05 PM > To: General Linux-HA mailing list > Subject: Re: [Linux-HA] failcount is up despite "is_managed" is false > > On 2007-06-18T08:31:46, Max Hofer <[EMAIL PROTECTED]> wrote: > > > If i remember correctly the resource is still monitored, even > > if you set is_managed to false. This is needed because other > > resource may depend on the unmanagened resource. > > > > is_managed false ---> this resource is not started/stopped by the > > cluster manager (but not "this resource is not monitored anymore"). > > We had a discussion (off list) last week. I think the conclusion was to > ignore monitoring failures for is_managed false resources, but it might > not be implemented yet ... > > I think the real problem is that is_managed is being used as a > "maintenance mode", while it was originally intended to feed the status > of resources which we don't manage (hence the name) into the system; > that's two slightly different expectations ... > > > Regards, > Lars > > -- > Teamlead Kernel, SuSE Labs, Research and Development > SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) > "Experience is the name everyone gives to their mistakes." -- Oscar Wilde > > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
