Tenant Details - OpenStack Test

In OpenStack, tenants (also known as projects) are created and managed using services executed by the OpenStack Controller. Each tenant/project is a logical container for resources and represents an isolated environment where users can create and manage their own instances (virtual machines), networks, storage volumes, and security groups. Administrators can set up quotas for each tenant in the cloud infrastructure. This enables multiple tenants/projects to use same cloud infrastructure without interfering with each other’s permissions and resources.

This test monitors the tenants/projects managed by the target controller and reports the amount of local storage available to each tenant/project. In the process, this test also reveals the total memory and vCPUs utilization of each tenant. Using these metrics, administrators can identify the tenant/project that over-utilized the memory and CPU resources and initiate remedial actions to optimize resource utilization. This also enables administrators to allocate more resources to support operations on the tenant/project (if required) and plan for the resource requirements in future.

Target of the test : An OpenStack Controller

Agent deploying the test : A remote agent

Outputs of the test : One set of results for each tenant

Configurable parameters for the test
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: The eG manager license should allow the detailed diagnosis capability Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
Total local storage	Indicates the total amount of local storage available to this tenant/project.	GB	The detailed diagnosis of this measure reveals the names of virtual machines (VMs), state of each VM, memory allocated to each VM in MB, number of vCPUs used by each VM, amount of local storage allocated to each VM, flavor of each VM, the total uptime of each VM, ID each VM and tenant ID.
Total memory usage	Indicates the total amount of memory used by this tenant/project.	MB
Total vCPU usage	Indicates the total number of vCPUs used by this tenant/project.	Number
Server exist duration	Indicates the lifespan of virtual machines on this tenant/project until they are manually terminated or deleted.	Hours