On 2008-04-08T06:56:25, Serge Dubrouski <[EMAIL PROTECTED]> wrote:
> > - RAs should "sign in" with it for the processes they want monitored,
> > instead of listing the processes in the procd configuration section
> > (means it gets decoupled from the CIB further). The RAs could write a
> > record to /var/run/heartbeat/procd/<resource-id>, for example.
> >
> > 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.
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/
