On 1/4/2012 5:11 AM, Jim Avery wrote:
> Another advantage is if you add or remove host servers to the cluster
> you only need to change the one host definition.
>
> You could use check_cluster as the host check for your fake host, then
> its status would be meaningful too. I'll have a go at doing
On 4 January 2012 07:53, Claudio Kuenzler wrote:
> I created a fake host (with IP 0.0.0.0) for the cluster with active checks
> and notifications disabled.
> This way I have one and the same parent for all VM's in that cluster.
>
> Let me show it this way:
>
> switch ---> esx1> VM-CLU
I created a fake host (with IP 0.0.0.0) for the cluster with active checks
and notifications disabled.
This way I have one and the same parent for all VM's in that cluster.
Let me show it this way:
switch ---> esx1> VM-CLUSTER-1 --> VM1
| > esx2> | --
On 3 January 2012 20:58, alexus wrote:
> I have few hyper-visors that running bunch of VMs. Each VM runs on a
> HV and can be migrated from one host to another at any given time for
> whatever reason(s).
> Should I specify all HVs (where VM can run) for each VM as a parent?
That's what I do, yes.
I have few hyper-visors that running bunch of VMs. Each VM runs on a
HV and can be migrated from one host to another at any given time for
whatever reason(s).
Should I specify all HVs (where VM can run) for each VM as a parent?
--
http://alexus.org/
--
