Filter
Top Products
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]
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 Containers]
- 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 resource pools 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, free CPU capacity and memory size of the virtual machine are not changed.
*3: This does not include the overhead used for the VM host.
*4: This includes not only the resources for active virtual machines, but also those of resources of stopped virtual machines.
[VMware]
This includes the overhead memory used for the virtual machine.
The resources of VMware FT secondary virtual machines are included.
*5)
[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:
- When the policy is share
Total_resource_capacity (*3) multiplied by the share (%)
- When the policy is the VM host corresponding to the spare server
Total_resource_capacity (*3) multiplied by 100 (%)
- When the policy is a VM host not corresponding to the spare server
Total_resource_capacity (*3) multiplied by 0 (%)
- When the policy is slots
Total_resource_capacity (*3) multiplied by 0 (%)
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 spare server and multiple VM hosts are defined for the spare server
- 249 -