On 2008-01-28T09:04:45, chris barry <[EMAIL PROTECTED]> wrote:
> Thanks Andrew. I am aware of this agent. It does not however work using
> the viperltoolkit APIs, nor can it use VirtualCenter, so it's not a
> workable option for me - hence the fenced script ;). In a clustered ESX
> environment that supports the live migrating of VMs, using the
> VirtualCenter to transparently and automatically locate and access VMs
> that require fencing (that may be on any box at any time) is the ideal
> solution. I guess I'll re-examine the format of the various existing
> scripts and just go from there.
Yes, that would be a great idea.
In effect, you're escalating the fencing request to a higher (or outer) level
cluster.
You just need to be able to handle the case where the host running the
guest is unreachable; so the outer level also needs to implement fencing
for failed physical nodes to provide the required IO fencing guarantees.
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/
