This section explains the concept for separating tenants (necessity of local pool creation) for each resource pool.
This section explains the concept for separating tenants of server pools.
Servers of differing models can be placed in the same server pool.
When performing server redundancy, consider a server pool to use as the work servers and spare server pool to use as backup servers.
Use the same pool for servers and spare servers
As well as the work server, a spare server must also be considered.
Separate the server pool and spare server pool
The server pool can be placed in a local pool, and the spare server pool can be placed in a global pool.
This section explains the concept for separating tenants of VM pools.
VM hosts of different server virtualization software can be stored in VM pools.
Even if a VM host exists in one VM pool, virtual L-Servers can be placed in a different tenant. Therefore, it is not necessary to separate VM pools.
However, local VM pools must be created for each tenant in the following cases:
Consolidate VM hosts comprising VMwareDRS or HA in VM pools under the same tenant. A virtual machine may operate beyond tenants by VM management software control, when VM hosts are registered in different tenants.
Place VM pools separately for each tenant when considering the vulnerabilities and loads of VM hosts.
This section explains the concept for separating tenants of storage pools.
Virtual storage resources or disk resources of differing server virtualization software can be placed in the same storage pool.
Disk resources generated from virtual storage resources and disk resources created in advance can also be stored together.
In the following cases, place storage pools separately for each tenant:
When separating storage pools according to usage
When maintaining unique user information for security reasons
When giving consideration to performance
When using them as shared disks (from the disk resources created in advance)
When using thin provisioning
When using Automatic Storage Layering
This section explains the concept for separating tenants of network pools.
Network pools should be separated for each tenant for security reasons.
Network pools can be shared in environments that allow communication between tenants, such as intranets.
This section explains the concept for separating tenants of address pools.
MAC addresses and WWNs can be stored together in an address pool. However, they can easily be managed in separate address pools as the required resources differ depending on the server type. Use the same method of separation as for server pools.
MAC address (Media Access Control address) | WWN | |
|---|---|---|
Blade servers (VIOM is required) | Yes | Yes |
Rack mount servers (HBA address rename is required) | No | Yes |
In the following cases, separate address pools:
When separating the LAN for each tenant, and registering MAC addresses for firewalls etc.
When separating the SAN for each tenant, and setting WWNs for fibre channel switch zoning
When using software that is aware of MAC addresses for license authentication etc.
This section explains the concept for separating tenants of image pools.
For images of tenant-independent operating systems, it is not necessary to separate image pools.
It is necessary to separate image pools for each tenant for images that have tenant-unique information.
Specify the settings for tenant-unique applications, and then perform measures such as collecting images.
