[Pacemaker] Enable remote monitoring

[Dejan Muhamedagic]

On Thu, Nov 08, 2012 at 12:10:24PM +0100, Lars Marowsky-Bree wrote:
> On 2012-11-08T11:54:04, Dejan Muhamedagic <dejanmm at fastmail.fm> wrote:
> 
> > > Downside, that I have just realized - resources which depend on this
> > > one, and might want to depend on a service the container provides.
> > > 
> > > (This could be an argument to go back to the "configure them as
> > > primitives that are managed-by-proxy via the container resource", sigh.)
> > 
> > Not necessarily if this is handled by the RA (as in Xen or
> > VirtualDomain). And it should really be so. Even if we provide a
> > solution just for Linux guests that should cover most
> > installations. I guess that other OS (won't name them here) would
> > come along eventually.
> 
> Uh? How should this be handled by the RA? Can you elaborate?

For instance, using expect to wait for the login prompt on the
console. Or, if that's possible, employing libvirt to get the
current runlevel. We already discussed this. Your objection was
that this won't work with the other OS.

Cheers,

Dejan

> Regards,
>     Lars
> 
> -- 
> Architect Storage/HA
> SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg)
> "Experience is the name everyone gives to their mistakes." -- Oscar Wilde
> 
> 
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org