> > > > > > The RAs would add/remove the required processes on start/promote or > > > demote/stop. (So procd itself would not need to be master-slave.) > > > > It's a little bit unclear here. An RA will have to decide if it wants > > its processes be monitored? Based on what principles then? Will it be > > mandatory for all RAs to "sign in" for that addtional monitoring? > > RAs will have to decide that, yes. They know the resource, right? ;-) > > Whatever principles make sense for the specific RA - according to > instance attributes specified, the current role etc. The RA really knows > best.
Right, but that doesn't mean that they know user best. As I see it a user will have to put some addtional parameters to cib.xml to indicate that he wants additional monitoring for a resourse. What is the advantage over the current way then? > > Mandatory? No, of course not. RAs which don't simply won't get the > additional monitoring. > > > > > 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-Dev: [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev > Home Page: http://linux-ha.org/ > -- Serge Dubrouski. _______________________________________________________ Linux-HA-Dev: [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/
