On 2008-04-02T16:10:10, Simon Horman <[EMAIL PROTECTED]> wrote:
> > The alternative which I favor is to split the SNMP agents into two, one
> > which deals with heartbeat (the cluster infrastructure) and one which
> > interfaces with Pacemaker.
> >
> > That makes perfect sense, as the Pacemaker agent is useful even when the
> > cluster infrastructure is swapped out for something else, say, openAIS.
> > ;-)
> >
> > And it is reasonable to expect that openAIS will expose slightly
> > different data than the heartbeat infrastructure does.
>
> That also sounds reasonable to me, though I wonder how
> much of the snmp_subagent code would end up being duplicated.
> If its a lot then I think that it might be worth going with
> Dejan's idea.
Point well made, code duplication could be an issue.
Nevertheless, the SNMP agent should be internally separated into the
heartbeat and Pacemaker bits; it'd be great if somebody would look at
supporting openAIS instead of heartbeat too.
I don't much care whether it is a compile-time or run-time choice.
Who wants to officially step forward and be crowned maintainer of the
SNMP agent - all work, no glory? ;-)
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/
