Hypervisor Details - OpenStack Test
Using this test, administrators can receive micro-level view of the composition of the target OpenStack KVM hypervisor. This test reveals the current status of the target hypervisor and the total number of vCPUs and also precisely reports the count of vCPUs the are free to be used on the hypervisor. This test also tracks the memory and local disk utilization on the hypervisor. This enables administrators to rapidly detect potential memory/local storage shortages at the earliest and initiate the appropriate remedial measures. Furthermore, this test reveals the count of cells, sockets and threads utilized on the hypervisor. Using these metrics, administrators can easily take decisions on scaling up the environment without increasing workload and latency. This test also reveals the current workload on the hypervisor, which helps administrators understand whether resources are being utilized adequately or over-utilized.
Target of the test : An OpenStack KVM
Agent deploying the test : A remote agent
Outputs of the test : One set of results for the OpenStack KVM hypervisor that is being monitored.
| Parameter | Description |
|---|---|
|
Test period |
How often should the test be executed. |
|
Host |
The host for which the test is to be configured. |
|
Port |
The port number at which the specified Host listens to. |
|
Project Name |
To enable this test to access the target hypervisor and pull out the performance metrics, you should specify the name of the project that is mapped to the target hypervisor in this text box. To know how to find out the project name from the OpenStack console, refer to Obtaining Project Name and Domain Details from OpenStack Console. |
|
Domain Name and Domain ID |
Specify the name and ID of the domain to which the specified project belongs to against the Domain Name and Domain ID parameters. To know how to find out the domain name and domain ID from the OpenStack console, refer to Obtaining Project Name and Domain Details from OpenStack Console. |
|
User Name, Password and Confirm Password |
To enable this test to pull out the performance metrics, you should configure the test with credentials of a user who is assigned with 'reader' role to access the above-mentioned project. Specify the credentials of such a user in the User Name and Password text boxes. Then, confirm the password by retyping it in the Confirm Password text box. |
|
Identity Version |
Specify the version of the Identity service API that is being used in the OpenStack environment. By default, this parameter is configured with the latest version of the API i.e. v3. |
|
SSL |
By default, the target controller is not SSL-enabled. This indicates that by default, the eG agent communicates with the target controller using HTTP. Accordingly, the SSL flag is set to No by default. If you configure the target controller to use SSL, then make sure that the SSL flag is set to Yes, so that the eG agent communicates with the target controller using HTTPS. |
|
Detailed Diagnosis |
To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:
|
| Measurement | Description | Measurement Unit | Interpretation | ||||||
|---|---|---|---|---|---|---|---|---|---|
|
State |
Indicates the current state of the target hypervisor. |
|
The values this measure reports and their numeric equivalents are provided in the table below:
Note: Typically, this measure reports one of the Measure Values listed in the table above. In the graph of this measure however, the current state of the hypervisor is indicated by its corresponding numeric equivalent only - i.e., 0 and 1. The detailed diagnosis of this measure reveals the name of target hypervisor, the current state of the hypervisor, type, version and IP address of the hypervisor, details related to CPU, service ID of the hypervisor, etc. |
||||||
|
Status |
Indicates whether/not the target hypervisor is enabled. |
|
The values this measure reports and their numeric equivalents are provided in the table below:
Note: Typically, this measure reports one of the Measure Values listed in the table above. In the graph of this measure however, the current status of the hypervisor is indicated by its corresponding numeric equivalent only - i.e., 0 to 1. |
||||||
|
Total vCPUs |
Indicates the total number of vCPUs in the target hypervisor. |
Number |
|
||||||
|
vCPUs used |
Indicates the number of vCPUs that are in use. |
Number |
|
||||||
|
vCPUs free |
Indicates the number of vCPUs that are available for use. |
Number |
A high value is preferred for this measure. |
||||||
|
vCPU usage |
Indicates the percentage of the vCPUs used on the target hypervisor. |
Percent |
|
||||||
|
Cells |
Indicates the number of cells on the target hypervisor. |
Number |
Cells functionality enables you to scale an OpenStack Compute cloud in a more distributed fashion without having to use complicated technologies like database and message queue clustering. Cells functionality supports very large deployments. |
||||||
|
Sockets |
Indicates the number of sockets on the target hypervisor. |
Number |
With sockets, you can configure VMs entirely without networking. In such a case, communication will be allowed only though the sockets. |
||||||
|
Cores |
Indicates the number of cores on the target hypervisor. |
Number |
Cores are connected by an interconnect to create a multi-core system, and have equal access to system resources like memory and input/output ports. |
||||||
|
Threads |
Indicates the number of threads that can be used to run CPU processes on the target hypervisor. |
Number |
|
||||||
|
Total memory |
Indicates the total memory allocated for the target hypervisor. |
GB |
|
||||||
|
Used memory |
Indicates the amount of memory used on the hypervisor. |
GB |
The value of this measure should be low. |
||||||
|
Free memory |
Indicates the amount of memory available for use on the hypervisor. |
GB |
A high value is preferred for this measure. |
||||||
|
Memory usage |
Indicates the percentage of the memory used on the hypervisor. |
Percent |
|
||||||
|
Total local storage |
Indicates the total amount of local disk storage on the target hypervisor. |
GB |
|
||||||
|
Used local storage |
Indicates the amount of local storage used on the hypervisor. |
GB |
The value of this measure should be low. |
||||||
|
Free local storage |
Indicates the amount of local storage available for use on the hypervisor. |
GB |
A high value is preferred for this measure. |
||||||
|
Local storage usage |
Indicates the percentage of local storage used on the hypervisor. |
Percent |
|
||||||
|
Current workload |
Indicates the number of tasks that are currently handled by the hyervisor. |
Number |
This measure is a good indicator of the current workload of the hypervisor. |
||||||
|
Running VMs |
Indicates the number of VMs that are currently running on the hypervisor. |
Number |
|
