[racktables-users] Re: how to use "Virtual Resources" correctly
- From: "Aaron Dummer" <aaron@xxxxxxxxxxx>
- To: racktables-users@xxxxxxxxxxxxx
- Date: Mon, 21 Feb 2011 10:05:14 -0600
From the object page select the Add more tab. Under Virtual objects
select a type of VM cluster and type a common name.
Then go to the server object that is acting as the Hypervisor and
select the Properties tab. Change Hypervisor to yes and then click
on the paper clip next to Select container, this will give you a new
window where you can select the VM cluster previously created.
Follow this step for each of the Hypervisors in that cluster. Now
the next steps are al little grey to me as I'm not sure if you
should assign the VM to the cluster, the hypervisor it is running on
or to both. Can anyone shed some light on this?
By playing around you have gotten a good idea of how Virtual Resources
were intended to work.
VM resources can be arranged in a number of ways so Virtual Resources
were designed in a generic fashion to be able to handle most of the
scenarios. Here are a couple:
1. A physical server which hosts VMs. The server may be running a
bare-metal hypervisor such as ESXi or a full-blown OS like Windows XP
and an application-based hypervisor such as VMware Server or Player.
In this scenario, the server object would act as the container for VMs.
2. A clustered environment. In this case, multiple physical servers
each run a bare-metal hypervisor and are grouped together in a logical
cluster. One or more resource pools may or may not exist within the
cluster. VMs may be assigned to a pool or to the cluster itself. In
this scenario, either the cluster or resource pool objects would act
as the container for VMs. The cluster would act as the container for
the servers and resource pool objects. In the case of virtual
switches, either a server or cluster would act as the container,
depending on the type of vSwitch.
Also, the reason objects may have multiple containers is to handle the
case of blade servers acting as hypervisors. In that scenario, the
individual blade may have two containers - the blade server chassis
and the VM cluster.
At some point this will be documented in the wiki.
--
Aaron Dummer
Other related posts:
