Multi-Tenancy in HP Matrix Operating Environment Infrastructure Orchestration

17
Figure 17: ESX resource pool parent
VMware Resource Pools are intended to be used in a multi-tenancy environment to allow the sharing of a VMcluster
(or host) between different organizations. In a clustered situation they are most effective if HA/DRS is switched on as
it allows virtual machine load to be dynamically balanced across hosts.
Figure 18: ESX Resource Pools
Business One
ResourcePool2
10 GB
Orange
ResourcePool1
25 GB
Business One
ResourcePool1
20 GB
Green
ResourcePool1
14 GB
ESXHost ESXHost
Cluster
ComputeResource
(DRS)
…
Root
Resource Pool
60 GB
(invisible)
IO treats ESX Resource Pools like any other compute resource such as a VMhost or physical blade. Thus they must be
placed in an IO server pool in order to be used in a provisioning request such as create service or add server. In
order to make resource allocation tractable, a server pool containing an ESX Resource Pool must be homogeneous
and not contain any other type of compute resource. However there are no restrictions to prevent a provisioning
request from specifying the use of mixed multiple pools, as long as any pool containing an ESX Resource Pool is
homogeneous. A similar restriction applies to cloud resources; a pool containing a cloud resource cannot contain any
other type of compute resource, i.e. not a VMhost, not a blade and not an ESX Resource Pool.
An ESX Resource Pool cannot be shared between organizations. Best practice is for a VMhost, or a VMcluster, to be
managed at the Service Provider level with the ESX Resource Pools that it supports being assigned to organizations.
This hides the actual location of virtual machines from organizations and minimizes the possibility of information
leakage between organizations. However, assigning a VMhost to an organization is not prohibited.
An ESX Resource Pool can be deleted by a Service Provider Administrator using vCenter, though it is strongly
recommended that this not be done. If it does happen then the virtual machines migrate to the parent host or cluster. If
the parent was assigned to the same organization as the ESX Resource Pool then the virtual machines will continue to
be available to the organization, if not the virtual machines become inaccessible to IO.
Cloud Resources represent an external resource/capacity offered by a cloud service provider such as HP Cloud
Services, Amazon EC2, Savvis, and other Matrix environments.
Physical Provisioning Failures
If an IO physical server deployment fails, or IO delete service request fails, then the blade(s) involved are moved to
the organization’s Maintenance pool. The history for the failed create request will also contain message(s) of the
form:
“Renamed the VSE Logical Server <logical-server> to Clean-me-<logical-server> for manual cleanup."