On 2012-09-05T15:25:44, Dejan Muhamedagic <de...@suse.de> wrote:
> How about a new element. Something like
>
> primitive vm1 ocf:heartbeat:VirtualDomain
> require vm1 web-test dns-test
How we map this into Pacemaker's dependency scheme is obviously open to
discussion.
> The "require" would imply that the resource vm1 requires
> monitors of web-test and dns-test to succeed, in addition to its
> monitor (if defined).
Perhaps. But an "as-a-whole" attribute for groups to restart handling
might already be enough, since we would want the system to eventually
stabilize at the same state it runs to today (that is, with the group
brought up to the last non-failing resource; otherwise, admins
couldn't login to the VM to fix the problem).
> Monitor ops of web-test and dns-test will run only on the node where
> vm1 is started. They could in also get the environment (parameters) of
> vm1.
That's implicit in the group.
Internally, this could indeed map to a "symmetric" or whatever aspect of
the order dependency, yes, that could be set for the whole group.
> monocf may be just like ocf, sans start and stop operations.
> That would make all ocf RA elligible for this use.
None of the current resource agents would be able to cope with the use
case I suggested, because they expect to run in the OS image where the
service is provided - the idea of using the icinga/nagios plugins is
exactly that they don't have this requirement, and thus can monitor the
VM externally.
For OCF agents, this sort-of already exists: meta is-managed=false.
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
_______________________________________________________
Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/
