The only VMWare functionality that allows a VM to be "spread across
multiple hosts" is vLockstep (VMWare Fault Tolerance). This
functionality makes an identical clone of a VM on another host and
replays actions taken on the primary against the cloned VM.

So... not really spreading a single VM across multiple hosts but rather
synchronous replication of all changes to one VM's state to a clone of it.

Advertising

That said, this is about the least "cloudy" thing I can imagine and
isn't something that a cloud-native application should rely on.

Based on the OP's original question, he may also be referring to VMWare
DPM functionality, which is something that automatically live migrates
(via vMotion) VMs from one host to another in a cluster in order to
consolidate and then powers down the free hosts.

I read the VMWare page. AFAICT they are not saying that a VM can be
spread across multiple physical hosts. A "resource pool" appears to be a
quota pool. They are using a quota model somewhat like the
kube-arbitrator
<https://github.com/kubernetes-incubator/kube-arbitrator>, where quota
is a guaranteed minimum (rather than a maximum like Kubernetes
ResourceQuota), and they're saying that if there is unused quota in some
pool, then it becomes available to other pools on a temporary basis. So
a VM may be drawing resources (quota) from multiple resource (quota)
pools, but the VM is only actually running on a single physical host.

--
You received this message because you are subscribed to the Google Groups "Kubernetes
user discussion and Q&A" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to kubernetes-users+unsubscr...@googlegroups.com.
To post to this group, send email to kubernetes-users@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.