The pool list in the resource list display the resource folders, total size of resources, and free space available.
In the L-Server list, when the server is a physical L-Server, the physical server for the L-Server is displayed.
When the server is a virtual L-Server, the name of the VM host where the L-Server operates is displayed.
When the [Current resource] checkbox and the [Preserved resource] checkbox are selected, resources that have been allocated and resources in use are displayed.
For the already allocated resources, the following information is displayed, depending on the status of resource allocation.
allocated
Resource name
preserved
Resource name + "(preserved)"
defined
"(defined)"
For resources in use, the resources configured as [Physical server] or [VM host] are displayed as icon + resource name.
If you select the [Resource List] tab with a resource pool selected in the orchestration tree, a list of information for the resources that belong to the resource pool are displayed.
If you select the [Resource Details] tab, detailed information such as the total size of data and free space in the resource pool is displayed.
Also, if you select the [Available Pool] tab, a list of the resource pools that the user has usage rights for and the resources that belong to those pools is displayed.
For virtual storage resources with Thin Provisioning attributes configured, the virtually allocated size will be displayed inside the used amount. Also, depending on the value of the virtually allocated size, the display of free capacity may differ as follows:
When the virtually allocated size is less than the total size of virtual storage resources
The area not virtually allocated is displayed in the free capacity.
When the virtually allocated size is more than the total size of virtual storage resources
The area exceeding the capacity is displayed preceded by a minus ("-") in the free capacity.
For VMware datastores, Hyper-V Cluster Shared Volumes (CSV), and Citrix XenServer storage repositories, when storage pools with Thin Provisioning attributes are registered, they are displayed as explained above.
Example
When the total size of virtual storage resources is 20 GB, and the virtually allocated size is 10 GB:
Total Capacity: 20.0 GB
Free Capacity: 10.0 GB
When the total size of virtual storage resources is 20 GB, and the virtually allocated size is 30GB:
Total Capacity: 20.0 GB
Free Capacity: -10.0GB
The combined total of the capacity of the virtual storage and disk resources registered in the resource pool is displayed for the total capacity of the storage pool. If a disk resource that has been separated from a virtual storage and that virtual storage exist in the same resource pool, the capacity of the disk resource will not be included in the calculation of the total storage capacity of the storage pool.
Total CPU and Memory Capacity of the VM Pool
The total amount calculated using the following formula is displayed in all VM hosts registered in the resource pool, as the total CPU and memory capacity of the VM pool.
Physical resource amount of a VM host - resource amount occupied by a VM host |
The physical resource amount occupied by a VM host is as follows:
Server Virtualization Software | CPU Capacity | Memory Size |
|---|---|---|
VMware | Total of CPU reservations of system resources configured in a VM host (Total of reservation of the elements except [host] of a [System Resource Pool]) | Total of memory reservations of system resources configured in a VM host (Total of reservation of the elements except [host] of a [System Resource Pool]) |
Hyper-V | Number of physical CPUs * physical CPU performance values * CPU reservation values configured in a VM host (%) / 100 | Memory reservation values configured in a VM host |
Solaris Zones |
| The memory size is defined in the following order of priority: If neither setting is configured, it is regarded as 0 has been specified.
|
OVM for SPARC | Number of CPUs configured in the control domain * physical CPU performance values | Memory capacity configured in the control domain |
RHEL-Xen | Number of physical CPUs * physical CPU performance values * 20(%) / 100 | Memory capacity used for a VM host |
KVM | Number of physical CPUs * physical CPU performance values * CPU reservation value (%) / 100 | Memory reservation value (GB) |
Citrix Xen | Number of physical CPUs * physical CPU performance values * CAP values of VM host (control domain) virtual CPUs / 100 | Dynamic maximum memory size of the VM host (control domain) |
OVM for x86 3.x | 0 | Memory capacity used for a VM host |
Note
When all of the following conditions are met, the capacity reserved for failover is displayed in [CPU Capacity] and [Memory Capacity] under [VM Host List] and [Capacity] on the [Resource Details] tab. For VM hosts for which the HA function is unavailable, or for operations with no reservation for failover, a hyphen ("-") is displayed.
When the HA function provided by server virtualization software is available for the VM hosts, and CPU capacity and memory capacity are reserved for failover
In the case of VM hosts that meet all of the following conditions, the total capacity and the free capacity of the CPU and memory resources are set to 0. Moreover, it is not added to the total capacity and the free space of the VM pool.
The VM host is configured on a physical L-Server.
The VM host is registered in a VM pool.
The physical server on which the VM host operates is released due to the usage change of a physical server.
If the VM host and the physical server on which the VM host operates do not meet all of the following conditions, free space will be displayed as 0.
The power status is "ON".
The status is "normal".
Maintenance mode has not been set.
The maintenance mode of server virtualization software has not been set.
[VMware]
For VM hosts for which standby mode has been set by server virtualization software, calculation results are displayed for free space even when the status is "stop".
[KVM]
The default value of CPU reservation value (%) is 20%.
The default value of Memory reservation value (GB) is 2GB.
The CPU reservation value will be 0% if Resource Orchestrator cannot obtain information of physical servers.
Resource Orchestrator obtains information of physical servers from ServerView Agents for Linux.
Confirm the configuration of ServerView Agents for Linux.
Refer to "Required Software Preparation and Checks" in "2.2.1.1 Software Preparation and Checks" in the "Setup Guide CE".
In Resource Details for the VM host, and when using the command (rcxadm pool list -name Resource_pool_name), the total CPU capacity is displayed in the format of CPU_performance * CPU_core_count. CPU performance is displayed as a number truncated to one decimal place. Therefore, depending on the value of the second decimal place of CPU performance, CPU capacity may not match the actual free CPU capacity.
Max. Number of Possible L-Servers View
This section explains how to display the converted number of L-Servers that can be created with VM pools, server pools, and storage pools.
Left-click the target VM pool in the orchestration tree, and select the [Resource List] tab.
In the [Template] selection list, select the L-Server template to convert.
Click the [OK] button.
The number of L-Servers that can be created is displayed in [Number of creatable L-Servers].
Note
When the status of the VM host and virtual storage is one other than "normal", the resource will be excluded from L-Server allocation regardless of its available space.
[VMware]
The VM hosts for which standby mode has been set by server virtualization software are excluded from the targets of L-Server deployment, and other VM hosts in the same cluster become the deployment target location.
[Hyper-V]
When using an L-Server template with dynamic memory settings enabled, VM hosts that do not support dynamic memory are excluded from being the targets of L-Server deployment. In this case, "0" is displayed for the L-Server conversion number, even when there is available space on resources.
However, a value corresponding to the available space of the resource will be displayed for the L-Server converted number.
When using physical L-Servers, the L-Server converted number of virtual storage is an estimate, and an error may occur during L-Server creation.
The Available Space on Resources and the Space Displayed for [Number of creatable L-Servers]
The available space on resources and the space displayed for [Number of creatable L-Servers] are calculated as follows:
Item | Calculation Method | Remarks |
|---|---|---|
Number of L-Servers that can be created | The following smallest value is displayed:
| - |
CPU, memory | Total_resource_capacity (*2) - (Total_of_resources_used_for_virtual_machines (*3)) - Reservation_capacity_for_the_VM_host (the capacity reserved for the HA function enabled on the VM software) (*4) | - |
Addresses and available space on the network | Total_resource_capacity - (Total_of_resources_used_for_L-Server (*5)) | - |
Free storage space | Total_resource_capacity - (Total_of_resources_used_for_L-Server (*5) + Total_of_images (*6)) | - |
Free disk space | Free space as a resource is not displayed. The free space is calculated as the free space of a resource pool when all of the following conditions are met:
Number of creatable L-Servers is displayed as follows:
| [Hyper-V] As the saved disk resources that are created from the virtual machine cannot be used as system disks, the number is 0, even if the L-Server is unused. |
*1:
[VMware]
This does not include the overhead memory allocated when creating a virtual machine from an L-Server template. Therefore, the displayed number of L-Servers may not be able to be created.
*2: This does not include the overhead used for the VM host.
*3: This includes not only the resources for active virtual machines, but also those of resources of stopped virtual machines. Powered off L-Servers for which the server release settings are configured for powering off are not included.
[VMware]
This includes the overhead memory used for the virtual machine. The resources of VMware FT secondary virtual machines are included.
[Citrix Xen]
As the CPU performance values of virtual machines created using XenCenter cannot be obtained by VM management software, the CPU usage level will be calculated as 0.
*4: For details on the VM host reservation amount, refer to "Reservation Capacity for the VM Host".
*5: This includes not only the resources for active L-Servers, but also those of resources of stopped L-Servers.
*6: Images include cloning images and snapshots. However, the size of images is not displayed.
[Xen]
When using RHEL5-Xen on the managed server, refer to "8.4.7 Advisory Notes for RHEL5-Xen Usage" in the "Setup Guide CE".
Reservation Capacity for the VM Host
[VMware]
This is the resource capacity secured when VMware HA admission control is enabled. This is calculated according to the policy of the admission control. Formulas for individual policies are as follows:
Policy | Calculation Method |
|---|---|
When the policy is "Percentage of cluster resources reserved as failover spare capacity" | Total_resource_capacity (*) * share (%) |
When the policy is the VM host which corresponds to the "Specify failover hosts" | Total_resource_capacity (*) * 100 (%) |
When the policy is a VM host which does not correspond to the "Specify failover hosts" | Total_resource_capacity (*) * 0 (%) |
When the policy is "Host failures the cluster tolerates" | Total_resource_capacity (*) * 0 (%) |
* Note: This does not include the overhead used for the VM host.
The reservation capacity for the VM host is not secured with the following policies. If an L-Server is deployed with those policies, the L-Server may not be powered ON due to a shortage of resources.
When the policy is the "Specify failover hosts" and multiple VM hosts are defined for the "Specify failover hosts"
When the policy is "Host failures the cluster tolerates"
CPU and Memory Free Space of VM Pools Configured as Resource Pools for Overcommit
For resource pools (VM pools) configured as a resource pool for overcommit, the capacity is calculated according to the specified calculation method for free space.
When configured to calculate using a maximum value, free CPU capacity/memory size are calculated based on the CPU performance/memory size of the virtual machine.
In resource pools (VM pools) which do not use overcommit, only the upper limit values are supported.
Point
When creating a virtual L-Server, if the CPU reservation performance and memory reservation capacity are not specified, the values are configured as follows:
CPU reservation performance: 0
Memory reservation capacity: memory capacity or initial memory size
[VMware]
When configured to calculate using a reservation value, free CPU capacity/memory size are calculated based on the CPU performance/memory size reserved for the virtual machine. The number of L-Servers that can be created is calculated based on the CPU reservation performance and the memory reservation capacity specified in the L-Server template.
When the free capacity for VM pools is configured to be calculated using a maximum value, for the virtual machine for which limit values of CPU/memory has been set to "Unlimited" using VM management software, the calculation is performed assuming the following values as the maximum values:
When no limit has been set for CPU performance
The physical CPU performance on the VM host is used
When no limit has been set for memory size
The memory size set for the virtual machine
[Hyper-V]
When configured to calculate using a reservation value, the values referred to for calculation vary depending on the dynamic memory settings for the virtual machine and the L-Server template, as follow:
When Dynamic Memory is Enabled
Free CPU capacity and memory size are calculated based on the CPU performance and initial memory size reserved for the virtual machine.
Free CPU capacity and memory size are calculated based on the CPU performance and initial memory size reserved for the L-Server template.
When Dynamic Memory is Disabled
Free CPU capacity/memory size are calculated based on the CPU performance/memory size reserved for the virtual machine.
The number of L-Servers that can be created is calculated based on the CPU reservation performance and memory capacity specified in the L-Server template.
[KVM] [Citrix Xen] [OVM for x86 3.x]
When configured to calculate using a reservation value, free memory size is calculated based on the memory reservation capacity/memory size for the virtual machine. The free CPU capacity is not changed.
[Solaris Zones]
The number of CPUs and the CPU performance of an L-Server are displayed as "-" when the following conditions are met because the resources are not managed using Resource Orchestrator.
A cap value for the CPU has not been set in the non-global zone.
The non-global zone is managed using the resource pools for Solaris Zones that are not the targets of management.
When the conditions are not met, the cap values of CPUs are used for the number of CPUs and the CPU performance.
For details, refer to "E.6.2 Preparations for Servers" in the "Design Guide CE".
When the number of CPUs and CPU performance are displayed as "-", the amount of resources used by an L-Server will be calculated using 0.
When something other than "-" is displayed for the number of CPUs and CPU performance, those values are used for calculation.
The memory size of an L-Server is displayed as "-" when a cap value of memory has not been set in a non-global zone.
When a cap value has been set, the value is set for the memory size of an L-Server.
When memory size is displayed as "-", the amount of resources used by an L-Server will be calculated using 0.
When something other than "-" is displayed for memory size, that value is used for calculation.
When configured to calculate using a reservation value, the free CPU capacity and memory size of the VM host are not changed.
[OVM for SPARC]
When installing an OS, if the number of CPUs, the CPU performance value, or memory size are "-", the amount of resources that the L-Server uses is calculated as 0.
When the number of CPUs, the CPU performance, and the memory size of L-Server are stored, those values are used for the calculation.
When configured to calculate using a reservation value, the free CPU capacity and memory size of the VM host are not changed.
Conversion Number for L-Servers Corresponding to VM Pools and Storage Pools
In the display of the conversion number for L-Servers corresponding to VM pools and storage pools, depending on the VM type and CPU architecture of the virtual L-Server template, the number of L-Servers that can be created is as below.
When VM type is specified for the L-Server template
The number of L-Servers that can be created is displayed for the resource that corresponds to the specified VM type.
When there are no resources that correspond to the specified VM type, "0" is displayed.
When VM type is not specified for the L-Server template
The number of L-Servers that can be created is displayed for the resources that correspond to the specified CPU architecture.
When there are no resources that correspond to the specified CPU architecture, "0" is displayed.
For the definition of the L-Server template, refer to "15.2.2 Virtual L-Server Templates" in the "Reference Guide (Command/XML) CE".
[OVM for SPARC]
In OVM for SPARC, CPU performance is the VM host's CPU performance. Therefore, the CPU performance of the L-Server template is disregarded. The L-Server conversion number is calculated from "CPU performance of VM host x the number of CPUs" and memory size.
CPU and Memory Resource Amount of VM Pools [OVM for SPARC]
When registering the VM host (VM host1) of OVM for SPARC and the VM host (VM host2) configured on the guest domain in the VM pool, the CPU size and the memory resource amount are calculated as below.
When registering the VM host in the same VM pool
Total Capacity
The resource amount of VM host2 is not added to the total amount of VM pools, since the resources are included in the resource amount of VM host1.
The resource amount of VM host2 occupied by the VM host is subtracted from the total amount of VM pools.
Free Space
The free space of VM host1 and VM host2 is added to the free space of VM pools, as in the general calculation method.
When registering the VM hosts in different VM pools
Total Capacity
The resource amounts of VM host1 and VM host2 (physical resource amount - resource amount occupied by a VM host) is added to the total amount of VM pools, as in the general calculation method.
Free Space
The free space of VM host1 and VM host2 is added to the VM pools, as in the general calculation method.
Point
For details on how to select the deployment location of a virtual L-Server, refer to "Selection of L-Server Deployment Location" of "2.2.3 L-Server" in the "Design Guide CE".
