vRealize Operations Management Pack
for OpenStack
This document supports the version of each product listed and
supports all subsequent versions until the document is
replaced by a new edition. To check for more recent editions
of this document, see
http://www.vmware.com/support/pubs
.
You can find the most up-to-date technical documentation on the VMware Web site at:
http://www.vmware.com/support/
The VMware Web site also provides the latest product updates.
If you have comments about this documentation, submit your feedback to:
Copyright © 2014 VMware, Inc. All rights reserved. Copyright and trademark information.
VMware, Inc.
3401 Hillview Ave. Palo Alto, CA 94304 www.vmware.com
Contents
About This Book 5
1
Introduction to the vRealize Operations Management Pack for OpenStack 7
2
Installing and Configuring the Management Pack for OpenStack 9
Integrate the Management Pack for Openstack with vRealize Management Packs 9 Install the Management Pack 10
Configure the OpenStack Instance 11
View Management Pack for OpenStack Objects 12
3
Prerequisites forInstalling and Configuring the Hyperic Agent and Hyperic
Plug-Ins for OpenStack 15
Install the Hyperic Agent in OpenStack 16 Configure the MySQL Plug-In 16
Configure the Apache Web Server Plug-In 16 Configure the RabbitMQ Plug-In 17
Install the Memcached Plug-In 17
4
Management Pack for OpenStack Dashboards 19
Displaying OpenStack Dashboards 19 OpenStack Controllers Dashboard 20
OpenStack Compute Infrastructure Dashboard 20 OpenStack Network Infrastructure Dashboard 21 OpenStack vCenter Storage Infrastructure Dashboard 22 OpenStack Tenants Dashboard 23
5
Working with the Management Pack for OpenStack 25
Open an External Application 26
Configuring OpenStack with Log Insight 26
6
Management Pack for OpenStack Alert Definitions 29
7
Management Pack for OpenStack Capacity Models 45
8
Management Pack for OpenStack Object Model 49
OpenStack Objects and Metrics 49
9
Management Pack for OpenStack Reports 71
About This Book
The vRealize Operations Management Pack for OpenStack takes you through the process of deploying a working instance of Management Pack for OpenStack within your vCenter environment. It also describes the prerequisites for OpenStack, plug-in installation and configuration, and how to work in the
Management Pack for OpenStack environment.
Intended Audience
This information is intended for any network engineer, network administrator, network manager, or network operations manager who is involved with the daily operations related to deployment,
configuration, change management, troubleshooting, and capacity management of OpenStack networking technologies. In addition, it is intended for any cloud operations manager, cloud infrastructure manager, or virtual administrator who has operation responsibility for troubleshooting virtual infrastructure problems, and within this infrastructure OpenStack has been deployed.
VMware Technical Publications Glossary
VMware Technical Publications provides a glossary of terms that might be unfamiliar to you. For definitions of terms as they are used in VMware technical documentation, go to
Introduction to the
vRealize Operations Management
Pack for OpenStack
1
The Management Pack for OpenStack extends the operational management capabilities of the vRealize Operations platform to provide operational control of OpenStack environments.
This management pack is intended for administrators who are operating an OpenStack cloud. It includes the following key features:
n Performance and availability monitoring of OpenStack infrastructure and services. n Pre-defined dashboards for:
n Cloud Controllers Health n Compute Infrastructure n vCenter Storage Infrastructure n Network Infrastructure
n Tenants Inventory, Health and Quota usage
n Visibility into cloud resources running on any VMware ESX, KVM, XEN, or Hyper-v technologies. n Advanced performance and capacity analytics for OpenStack inventory running on any VMware ESX
and NSX technologies.
n Pre-defined alerts for several common OpenStack operational problems. n Report templates for the following objects.
n OpenStack Tenant Inventory n OpenStack Infrastructure Capacity n OpenStack Alerts
Installing and Configuring the
Management Pack for OpenStack
2
Using the Management Pack for OpenStack, you can collect inventory and capacity information of compute nodes registered with OpenStack, and inventory and availability of tenants and provisioned virtual machines or networks.
This chapter includes the following topics:
n “Integrate the Management Pack for Openstack with vRealize Management Packs,” on page 9 n “Install the Management Pack,” on page 10
n “Configure the OpenStack Instance,” on page 11
n “View Management Pack for OpenStack Objects,” on page 12
Integrate the Management Pack for Openstack with vRealize
Management Packs
To enhance monitoring and data collection capabilities, you can integrate the
Management Pack for OpenStack with the vRealize Operations Management Pack for vCenter, vRealize Operations Management Pack for vRealize Hyperic, and the
vRealize Operations Management Pack for NSX for Multi-Hypervisor.
If you intend to work with all four management packs, for the most efficient use of resources, configure the adapters of the management pack in the following order.
1 Management Pack for vCenter.
2 Management Pack for NSX for Multi-Hypervisor and Management Pack for vRealize Hyperic. The order of these two management packs is not important.
3 Management Pack for OpenStack.
NOTE Each management pack populates a particular area of the user interface with specific data. If you
choose not to integrate the Management Pack for OpenStack with these management packs, some areas of the OpenStack user interface will not be populated with data.
Management Pack Required by Description
vRealize Management Pack for
vCenter Openstack vCenter Storage Infrastructuredashboard If the OpenStack deployment isusing vCenter for the compute component, vRealize
Management Pack for vCenter provides integration with the data that the management pack collects for vCenter, such as additional metrics and capacity calculations.
vRealize Operations
Management Pack for vRealize Hyperic
n OpenStack Controllers dashboard n OpenStack Controllers navigation tree
The
Management Pack for OpenStack takes advantage of the plug-in for vRealize Hyperic for monitoring the availability and resource use of OpenStack controller services, such as nova-compute, neutron-server, and cinder-volume. The plug-in is available on the Solution Exchange and is also provided with vRealize Hyperic 5.8.4. In addition, by integrating with vRealize Hyperic, you can monitor the availability and resource use of OpenStack web, database and messaging applications, including MySQL, Apache, RabbitMQ, and Memcached.
vRealize Operations
Management Pack for NSX for Multi-Hypervisor
OpenStack Network Infrastructure dashboard If the OpenStack deployment is using NSX for Multi-Hypervisor for the networking component, vRealize Operations
Management Pack for NSX for Multi-Hypervisor provides integration with the data that the management pack collects for NSX for Multi-Hypervisor, such as additional metrics, and monitoring of the networking infrastructure.
Install the Management Pack
A management pack is the part of the solution that you install.
Prerequisites
The solution that you downloaded includes a PAK file. Save that PAK file to a temporary folder on your local system.
Procedure
1 Log in to the vRealize Operations Manager user interface with admin privileges.
2 In the left pane of vRealize Operations Manager, click the Administration icon and click Solutions. 3 On the Solutions tab, click the plus sign.
4 Browse to locate the temporary folder and select the PAK file. For example, managementpack_name-buildnumber.pak.
5 Click Upload.
The upload might take several minutes. 6 Read and accept the EULA, and click Next.
Installation details appear in the window during the process. 7 Ensure that you install the PAK file on the master node. 8 When the installation is complete, click Finish.
What to do next
Configure an adapter instance for the management pack.
Configure the OpenStack Instance
After you install the management pack, add and configure an instance to start collecting data.
Procedure
1 In the left pane of vRealize Operations Manager, click the Administration icon and click Solutions. 2 On the Solutions tab, click Management Pack for OpenStack, and click the Configure icon. 3 Configure the instance settings.
Option Description
Name Enter a name for the adapter instance.
Description Enter a description for the adapter instance.
OpenStack API Host Enter the host name or IP address where the KeyStone service is running. This service provides an entry point to the OpenStack API.
Port Enter the port number where the KeyStone service is running. The default
port number is 5000.
Connection Type Select the connection type with which the management pack should
communicate with OpenStack. The option set by default is HTTPS.
Endpoint Type Endpoints are the APIs used to call the different OpenStack services. Select the set of endpoints which vRealize Operations Manager uses when connecting with the OpenStack API.
n Detect Automatically. This option is selected by default, and can be
used if you do not know where vRealize Operations Manager is installed.
n Public Only. Select if vRealize Operations Manager is installed outside
the management network.
n Admin Only. Select if vRealize Operations Manager is installed inside
the management network.
n Internal Only. Select if you want to use the Internal service endpoints
that are registered with OpenStack
Support Auto Discovery Auto discovery enables the management pack to discover resources and
monitor the OpenStack deployment. This option is set to True by default, and should not be changed.
Option Description
Credential name Enter the name by which you are identifying the configured credentials.
OpenStack Username Enter the username with which you connect to OpenStack. OpenStack Password Enter the password with which you connect to OpenStack.
Admin Tenant Enter the name of a tenant for which you have an admin role. For the most
complete discovery possible, you should have the admin role on all tenants.
5 Click Test Connection to validate the connection.
6 The Advanced Settings area includes the Collector drop-down box, in which you can select the
collector upon which you want to run the adapter instance. A collector gathers objects into its inventory for monitoring. The collector specified by default has been selected for optimal data collecting.
7 Click Save Settings.
The adapter instance is added to the list.
What to do next
Verify that the adapter is configured and collecting data by viewing application-related data.
Table 2‑2. Successful Configuration Indicators
Where to View the Information Information to View
Collection Status and Collection State columns in the Management Pack for OpenStack Solutions Details pane on the Solutions tab.
The strings Collecting or Data receiving appear approximately ten minutes after you have configured the adapter.
Environment Overview The objects related to OpenStack are added to the inventory trees.
Dashboards Management Pack for OpenStack dashboards are added to the vRealize Operations Manager dashboards.
n OpenStack Controllers
n OpenStack Compute Infrastructure n OpenStack Network Infrastructure n OpenStack vCenter Storage Infrastructure n OpenStack Tenants
Click the Home icon in the left pane of
vRealize Operations Manager to view dashboards.
View Management Pack for OpenStack Objects
When the Management Pack for OpenStack has been installed and configured, the following objects are added to the Inventory trees in the vRealize Operations Manager Environment.
Check that the OpenStack environment is configured correctly by viewing OpenStack objects.
Procedure
1 In the left pane of vRealize Operations Manager, click the Environment icon.
2 In the Environment Overview, scroll down the list, and under the Inventory Trees list, click All
Objects.
3 In the All Objects list, click the arrow next to MP for OpenStack. OpenStack objects are displayed in the expanded list.
Table 2‑3. Management Pack for OpenStack Objects
Object Description
MP for OpenStack Instance Represents an instance of the OpenStack adapter. Non-ESX Host System Represents a non-ESX hypervisor that is registered with
OpenStack.
Non-ESX Virtual Machine Represents a virtual machine that has been provisioned by a user and is running on a non-ESX hypervisor.
OpenStack Compute Infrastructure Represents an aggregation of all hosts and clusters that are registered with OpenStack.
OpenStack Compute Services Represents an aggregation of all Nova services in the OpenStack environment.
OpenStack External Logical Switch Represents an external logical switch that has been provisioned by a tenant. If NSX for Multi-Hypervisor is being used, this object type is not used.
OpenStack Group Internal object that is used by the
Management Pack for OpenStack for grouping certain objects together in order to show them on the dashboards. OpenStack Logical Router Represents an logical router that has been provisioned by a
tenant. If NSX for Multi-Hypervisor is being used, this object type is not used.
OpenStack Logical Switch Represents an logical switch that has been provisioned by a tenant. If NSX for Multi-Hypervisor is being used, this object type is not used.
OpenStack Management Services Represents an aggregation of all KeyStone, Ceilometer, and support services in the OpenStack environment.
OpenStack Network Infrastructure Represents an aggregation of all NSX for Multi-Hypervisor controllers, gateway services, and transport zones that are registered with OpenStack.
OpenStack Network Services Represents an aggregation of all Neutron services in the OpenStack environment.
OpenStack Storage Infrastructure Represents an aggregation of all vCenter datastores that are registered with OpenStack. This is only applicable when using OpenStack with vCenter.
OpenStack Storage Services Represents an aggregation of all Cinder, Glance, and Swift services in the OpenStack environment.
OpenStack Tenant Represents a project in OpenStack, along with all provisioned instances, networks, and routers.
Prerequisites forInstalling and
Configuring the Hyperic Agent and
Hyperic Plug-Ins for OpenStack
3
Integration with the Hyperic agent enables wider monitoring capabilities through MySQL, Apache, Rabbit MQ, Memcached, and OpenStack plug-ins.
Table 3‑1. vRealize Hyperic Plug-Ins for OpenStack
Plug-in Description
MySQL Monitors the MySQL database. This plug-in is installed when the Hyperic agent is installed.
Apache web server Monitors the Apache server. This plug-in is installed when the Hyperic agent is installed.
RabbitMQ Monitors the RabbitMQ messaging server. This plug-in is installed when the Hyperic agent is installed.
Memcached Monitors Memcached caching applications. This plug-in is not provided with vRealize Hyperic, and must be downloaded from the VMware Solution Exchange. OpenStack Monitors OpenStack related services. This plug-in is
installed when vRealize Hyperic 5.8.4 is installed.
Before you install and configure Hyperic plug-ins in vRealize Hyperic, verify that the following configurations are implemented in vRealize Hyperic. For more information about how to configure vRealize Hyperic, see http://pubs.vmware.com/hyperic-58/index.jsp#Welcome/welcome.html.
n Verify that the following tasks are performed so that Management Pack for vRealize Hyperic can create
a relationship between the platform resource and the vCentger virtual machine.
n vCentger credentials are configured in Hyperic. See
http://pubs.vmware.com/hyperic-58/index.jsp#com.vmware.hyperic.administration.doc/GUID-851 457EA-32EA-4657-B126-B4A7EDD1C8A4.html
n Virtual machines running the Hyperic agent, are also running VMware Tools. The
Management Pack for vRealize Hyperic requires VMware Tools. See
https://pubs.vmware.com/vsphere-50/index.jsp#com.vmware.vmtools.install.doc/GUID-08BB9465-D40A-4E16-9E15-8C016CC8166F.html.
n Import the following OpenStack resources to the Hyperic Inventory. n Keystone Service
n Nova Service n Neutron Service
n Ceilometer Service n RabbitMQ n MySQL n Apache n Memcached
This chapter includes the following topics:
n “Install the Hyperic Agent in OpenStack,” on page 16 n “Configure the MySQL Plug-In,” on page 16
n “Configure the Apache Web Server Plug-In,” on page 16 n “Configure the RabbitMQ Plug-In,” on page 17
n “Install the Memcached Plug-In,” on page 17
Install the Hyperic Agent in OpenStack
Download a Hyperic agent for each virtual machine that is running OpenStack services.
Prerequisites
Ensure that the Hyperic agent corresponds with your Hyperic server. For example, if you are running Hyperic server 5.8.4, download the Hyperic agent for Hyperic 5.8.4.
Procedure
1 Run tar -xvf <downloaded_hyperic_agent> to extract the file.
2 Run cd <hyperic_extracted>/bin to extract the files.
3 Run ./hq-agent start and follow the instructions to complete agent setup.
Configure the MySQL Plug-In
The MySQL plug-in is installed when the Hyperic agent is installed.
Procedure
1 In the Hyperic server, access the Configuration page.
2 Configure the jdbcUrl, username, password, and port options.
Configure the Apache Web Server Plug-In
The Apache Web Server plug-in is installed when the Hyperic agent is installed.
Procedure
1 In the Hyperic server, access the Configuration page. 2 Configure the hostname, port, and ssl connection options.
3 Enter the URL of the server status path to be monitored: <path<a="><path<>. For example, http://<apache-server-ip>:80/<path.
Configure the RabbitMQ Plug-In
The RabbitMQ plug-in is installed when the Hyperic agent is installed.
Procedure
1 On the host where the Rabbit MQ server is installed, enter rabbitmq-plugins enable rabbitmq_management.
This enables plug-in management. 2 Restart the RabbitMQ Server.
3 Access http://server-name:55672 to verify that the server is enabled.
4 In the Hyperic server, access the Configuration page, and configure the management port, username, and password options.
Install the Memcached Plug-In
The Memcached plug-in is not provided with Hyperic, and must be downloaded from the VMware Solution Exchange.
Prerequisites
Download the Memcached plug-in at https://solutionexchange.vmware.com/store/products/memcached-plugin-for-hyperic#.VEAtO_ldU1I
Procedure
1 In the Hyperic server, click the Administration tab. 2 Access the Plugin Manager, and click Add/Update Plugins. 3 Follow the instructions to install the plug-in.
You do not need to configure any options. When Memcached is running, the resource is detected.
Management Pack for OpenStack
Dashboards
4
The Management Pack for OpenStack dashboards enable you to diagnose and troubleshoot problems in your OpenStack environment.
For information about how to configure the options on the dashboard widgets, see the vRealize Operations Manager documentation, at https://www.vmware.com/support/pubs/. This chapter includes the following topics:
n “Displaying OpenStack Dashboards,” on page 19 n “OpenStack Controllers Dashboard,” on page 20
n “OpenStack Compute Infrastructure Dashboard,” on page 20 n “OpenStack Network Infrastructure Dashboard,” on page 21 n “OpenStack vCenter Storage Infrastructure Dashboard,” on page 22 n “OpenStack Tenants Dashboard,” on page 23
Displaying OpenStack Dashboards
Management Pack for OpenStack dashboards are displayed in the vRealize Operations Manager Home page after the management pack is installed. If you have numerous dashboards open in
vRealize Operations Manager, the OpenStack dashboards may not be visible. Instead of scrolling through your available dashboards, you can select them from the dashboard list.
Procedure
1 In the left pane of vRealize Operations Manager click the Home icon.
2 In the right pane, click Dashboard List, and from the drop-down menu point to OpenStack, and select the OpenStack dashboard you want to work with.
The selected dashboard is displayed in the vRealize Operations Manager Home page.
3 To ensure that Management Pack for OpenStack dashboards are always available in the Home page, click Dashboard List, and make sure that the OpenStack check box is selected.
OpenStack Controllers Dashboard
The OpenStack Controllers dashboard provides a high level view of the compute, network, storage, and management services. This dashboard enables you to detect health-related problems at the service level, and then drill-down to the individual processes by viewing the topology and alerts.
To view service-related information in the Controller Service Topology widget, the
Management Pack for vRealize Hyperic must be installed and configured in vRealize Operations Manager. In addition, the OpenStack plug-in must be installed in vRealize Hyperic.
Table 4‑1. OpenStack Controllers Dashboard Widgets
Widget Description
Controller Service Inventory Provides a high level view of the compute, network, storage, and management services in your environment. Select an object to show detailed information about the controller service in the dashboard.
Hover over an object to display capacity-related details. Controller Service Topology Displays the individual services running on the controllers.
The health of the services impacts the controller service object in the Controller Service Inventory widget. For example, if 50% of the services of a particular type are down, the object is orange.
To display an extended view that includes other connected objects, right-click an object, select Expand Node, and select the objects you want to include in the expanded view.
Controller Service Metrics When you select a controller in the Controller Service Inventory, this widget displays the number of services that have been configured and running. When you select a service in the Controller Service Topology widget, this widget provides related resource usage data.
Controller Service Alerts Displays alerts for objects selected in the Controller Service Topology widget.
OpenStack Compute Infrastructure Dashboard
The OpenStack Compute Infrastructure dashboard displays top level objects that show the correlation between the environment and the infrastructure components of that type. This top level view provides you with enough information to determine if there is sufficient capacity for users to provision virtual machines.
Table 4‑2. OpenStack Compute Infrastructure Dashboard Widgets
Widget Description
Compute Inventory Displays a high level view of the components in the compute infrastructure. Each component is represented by a box. Select an object to view related components in the dashboard.
Hover over an object to display capacity-related details. Compute Infrastructure Displays related components of the object selected in the
Compute Inventory widget.
Hover over an object to view health and capacity related details.
To display an extended view that includes other connected objects, right-click the object, select Expand Node, and select the objects you want to include in the expanded view.
Table 4‑2. OpenStack Compute Infrastructure Dashboard Widgets (Continued)
Widget Description
Compute Resource Utilization Displays a heatmap of the workloads of the different objects registered with OpenStack. The workloads are broken down by cluster. A threshold is set at 80% of the workload. The heatmap remains green and healthy as long as the workload remains below 80% of the capacity. You can view heatmaps for the cluster CPU, ESX Host CPU, cluster memory, and ESX Host memory workloads, and Non-ESX Host memory usage by selecting the required option from the Configurations drop-down menu. Compute Alerts Displays alerts for selected objects. Also displays
risk-based alerts that are opened if the infrastructure is approaching capacity. Risk alerts are opened when capacity has reached a threshold of 85%, 90% and 95%.
OpenStack Network Infrastructure Dashboard
The OpenStack Network Infrastructure dashboard provides you with a high level view of the networking infrastructure.
The networking infrastructure is only available if you are using NSX for Multi-Hypervisor as your networking component, and you have configured the NSX for Multi-Hypervisor adapter. If you are not using NSX for Multi-Hypervisor as your networking component, this dashboard will not display any information.
Table 4‑3. OpenStack Network Infrastructure Dashboard Widgets
Widget Description
Network Inventory Provides a high level view of your networking
infrastructure: NSX-MH Controllers, NSX-MH Transport Zone, and NSX-MH Gateway Service. Select an object to view related components and information in the dashboard.
Hover over an object to display health and configuration related details.
Network Infrastructure Displays related components of the object selected in the Network Inventory widget.
Hover over an object to view health and capacity related details.
To display an extended view that includes other connected objects, right-click an object, select Expand Node, and select the objects you want to include in the expanded view.
Network Infrastructure Resource Utilization Displays a heatmap of the workloads of the different network objects. A threshold is set at 80% of the workload. The heatmap remains green and healthy as long as the workload remains below 80% of the capacity. You can view heatmap for the Controller memory, Controller filesystem, Gateway CPU, Gateway memory, Gateway swap memory, and Gateway filesystem workloads by selecting the required option from the Configurations drop-down menu.
Network Alerts Displays alerts for objects selected in the Network Infrastructure widget.
OpenStack vCenter Storage Infrastructure Dashboard
If you are using VMware vCenter host as your computing infrastructure, the OpenStack vCenter Storage Infrastructure dashboard displays the data stores in your environment.
If you are not using vCenter as your computing infrastructure, vRealize Operations Manager can not access data about the storage devices registered with OpenStack, and the OpenStack vCenter Storage
Infrastructure dashboard does not display data.
Table 4‑4. OpenStack vCenter Storage Infrastructure Dashboard Widgets
Widget Description
vCenter Storage Inventory Displays the data stores available in your environment. Hover over an object to display capacity-related details. vCenter Storage Infrastructure Displays related components of the object selected in the
vCenter Storage Inventory widget.
Hover over an object to view health and capacity related details.
To display an extended view that includes other connected objects, right-click an object, select Expand Node, and select the objects you want to include in the expanded view.
vCenter Storage Resource Utilization Displays a heatmap representing capacity of the data stores. The configurations are broken down by cluster. A threshold is set at 80% of the capacity. The heatmap remains green and healthy as long as the usage remains below 80% of the capacity. You can view heatmaps for the datastore diskspace usage, IOPs, and average latency by selecting the required option from the Configurations drop-down menu.
vCenter Storage Alerts Displays alerts for objects selected in the vCenter Storage Infrastructure widget.
OpenStack Tenants Dashboard
The OpenStack Tenants dashboard provides you with a list of all OpenStack tenants, and the ability to view quota usage, provisioned objects, and alerts for each tenant.
Table 4‑5. OpenStack Tenants Dashboard Widgets
Widget Description
Tenant Quota Usage Displays the current quota usage of each tenant in the environment, and enables you to see if a tenant is close to reaching one of its quota limits. Each tenant is represented by a box. Each box is proportionate to the size of the tenant quota. In addition, a threshold is defined at 80% of the quota, at which point the box starts to turn red.
You can view the Tenants instance, vCPU, and vRAM, by selecting the required configuration from the
Configurations drop-down menu.
Tenant Inventory Provides a view of the objects that the tenant has provisioned and how they are connected together. The view expands from Tenant, to virtual machine to switch. To display an extended view that includes other connected objects, right-click an object, select Expand Node, and select the objects you want to include in the expanded view. For example, you can expand the view of a logical switch and display the logical router that it is connected to. Hover over any object to see more information about the object such as its name and its health.
Tenant List Displays a list of all the tenants in the environment. Click a tenant in this list to display the tenant in the Tenant Inventory widget.
Tenant Alerts Displays alerts for objects selected in the Tenant Inventory widget. Alerts are displayed from both an object
perspective, and from a tenant perspective. For example, if you tried to provision a virtual machine and it failed, an alert would be displayed on the object that failed to provision and also on its tenant. This enables you to diagnose problems on both the object and the tenant.
Working with the
Management Pack for OpenStack
5
The Management Pack for OpenStack provides you with a high level view of your OpenStack environment and enables you to drill down to more object-specific information by opening selected objects in external applications. You can investigate problems and better analyze the provided information. You can also make configuration changes, as required.
Table 5‑1. Examples of Use
Application Example of Use
View logging information in Log Insight. Information includes, component logs, neutron logs, nova logs, and API request logs.
NOTE To view logging information in Log Insight, you
must first integrate Log Insight with the Management Pack for OpenStack.
If a provisioning attempt fails, view the Nova logs in Log Insight to determine any errors that occurred. Open tenant-related objects in OpenStack Horizon. If a tenant is approaching their quota, open the tenant in
OpenStack Horizon and its quota.
This chapter includes the following topics:
n “Open an External Application,” on page 26
Open an External Application
Open selected objects in an external application to make configuration changes or to view application-related information.
Table 5‑2. Applications and objects
Application Available on these objects
Log Insight n Compute Infrastructure n Compute Services n Host System
n Non-ESX Host System n Virtual Machine
n Non-ESX Virtual Machine n Network Services n Logical Router n Storage Services n Management Services n Logical Switch
OpenStack Horizon n Tenant
n Non-ESX Host System n Non-ESX Virtual Machine n Logical Switch
n External Logical Switch n Logical Router n Virtual Machine
vSphere Web Client n Virtual Machine n Host System NSX Manager n Controller n Transport Zone n Gateway Service n Logical Switch n Logical Router Procedure
1 Select the required object in a widget.
2 In the widget toolbar, click the Dashboard Navigation icon, and from the drop-down menu, select the application you want to open.
The external application is opened and you can view application-related information about the object.
What to do next
Analyze the information in the application. Make any configuration changes. Continue to monitor the object in vRealize Operations Manager
Configuring OpenStack with Log Insight
The Management Pack for OpenStack enables you to open selected objects in Log Insight, and view logging information for the object. OpenStack does not support automatic configuration of logging information, and if you want to forward logging information to Log Insight, you must configure the OpenStack host
Procedure
1 On each host, locate the config file for OpenStack components. For example, /etc/nova/nova.conf, /etc/neutron/neutron.conf.
2 In the config file, set the use_syslog parameter to true.
3 Specify the forwarding host by running the following command in the /etc/rsyslog.d/50-default.conf file.
# echo "*.* @@<loginsight-hostname>:514" >> /etc/rsyslog.d/50-default.conf
# tail -1 /etc/rsyslog.d/50-default.conf *.* @@<loginsight-hostname>:514
# service rsyslog restart
The name of your config file may be different, but the forwarding information you enter is the same. 4 Restart OpenStack services on the host to apply the changes.
OpenStack begins to forward logging information. Check Log Insight to see if the logs are being forwarded.
Management Pack for OpenStack
Alert Definitions
6
Management Pack for OpenStack alert definitions are a combination of symptoms and recommendations that identify problem areas in your environment and generate alerts on which you can act for those areas.
Table 6‑1. OpenStack Alert Definitions
Alert Name Object Type Symptom Impact Severity
Nova-objectstore
service is unavailable Nova ControllerService Self Metric: Nova-ObjectStore Process Metrics|
AVAILABILITY| Availability < 1
Health Critical Nova-api service is
unavailable Nova ControllerService Self Metric: Nova-Api Process Metrics| AVAILABILITY| Availability < 1
Health Critical Nova-scheduler
service is unavailable Nova ControllerService Self Metric: Nova-Scheduler Process Metrics| AVAILABILITY| Availability < 1
Health Critical Nova-conductor
service is unavailable Nova ControllerService Self Metric: Nova-Conductor Process Metrics|
AVAILABILITY| Availability < 1
Health Critical Nova-consoleauth
service is unavailable Nova ControllerService Self Metric: Nova-ConsoleAuth Process Metrics|
AVAILABILITY| Availability < 1
Health Critical Nova-console service
is unavailable Nova ControllerService Self Metric: Nova-Console Process Metrics| AVAILABILITY| Availability < 1
Health Critical Nova-cert service is
unavailable Nova ControllerService Metric: Nova-CertProcess Metrics| AVAILABILITY| Availability < 1
Alert Name Object Type Symptom Impact Severity
Nova-compute service
is unavailable Nova ControllerService Self Metric: Nova-Compute Process Metrics| AVAILABILITY| Availability < 1
Health Critical Nova-xvpvnc-proxy
service is unavailable Nova ControllerService Self Metric: Nova-XvpvncProxy Process Metrics| AVAILABILITY| Availability < 1
Health Critical Nova-novnc-proxy
service is unavailable Nova ControllerService Self Metric: Nova-NoVncProxy Process Metrics|
AVAILABILITY| Availability < 1
Health Critical Nova-network service
is unavailable Nova ControllerService Self Metric: Nova-Network Process Metrics| AVAILABILITY| Availability < 1
Health Critical One or more nova-api
services are unavailable
OpenStack Compute
Services Self Metric: Service| Nova:Nova-ApiRunning (%) < 100
Health Warning The majority of
nova-api services are unavailable
OpenStack Compute
Services Self Metric: Service| Nova:Nova-ApiRunning (%) <= 50
Health Immediate All nova-api services
are unavailable OpenStack ComputeServices Self Metric:Service| Nova:Nova-ApiRunning (%) =0
Health Critical One or more nova-cert
services are unavailable
OpenStack Compute
Services Self Metric:Service|Nova:Nova-Cert| Running (%) < 100
Health Warning The majority of
nova-cert services are unavailable
OpenStack Compute
Services Self Metric:Service|Nova:Nova-Cert| Running (%) <= 50
Health Immediate All nova-cert services
are unavailable OpenStack ComputeServices Self Metric:Service|Nova:Nova-Cert| Running (%) = 0
Health Critical One or more nova
compute services are unavailable
OpenStack Compute
Services Self Metric: Service| Nova:Nova-Compute|Running (%) < 100
Health Warning The majority of
nova-compute services are unavailable
OpenStack Compute
Services Self Metric:Service| Nova:Nova-Compute|Running (%) <= 50 Health Immediate All nova-compute services are unavailable OpenStack Compute
Services Self Metric:Service| Nova:Nova-Compute|Running (%) = 0
Table 6‑1. OpenStack Alert Definitions (Continued)
Alert Name Object Type Symptom Impact Severity
One or more nova-conductor services are unavailable
OpenStack Compute
Services Self Metric: Service| Nova:Nova-Conductor|Running (%) < 100
Health Warning The majority of
nova-conductor services are unavailable
OpenStack Compute
Services Self Metric: Service| Nova:Nova-Conductor|Running (%) <= 50 Health Immediate All nova-conductor services are unavailable OpenStack Compute
Services Self Metric: Service| Nova:Nova-Conductor|Running (%) = 0
Health Critical One or more
nova-console services are unavailable
OpenStack Compute
Services Self Metric: Service|Nova:Nova-Console| Running (%) < 100
Health Warning The majority of
nova-console services are unavailable
OpenStack Compute
Services Self Metric: Service| Nova:Nova-Console|Running (%) <= 50 Health Immediate All nova-console services are unavailable OpenStack Compute
Services Self Metric:Service| Nova:Nova-ConsoleRunning (%) = 0
Health Critical One or more
nova-consoleauth services are unavailable
OpenStack Compute
Services Self Metric: Service| Nova:Nova-ConsoleAuth| Running (%) < 100
Health Warning The majority of
nova-consoleauth services are unavailable
OpenStack Compute
Services Self Metric:Service|Nova:Nova-Console Auth|Running (%) <= 50 Health Immediate All nova-consoleauth services are unavailable OpenStack Compute
Services Self Metric: Service|Nova:Nova-Console Auth|Running (%) = 0
Health Critical One or more
nova-network services are unavailable
OpenStack Compute
Services Self Metric: Service| Nova:Nova-Network|Running (%) < 100
Health Warning The majority of
nova-network services are unavailable
OpenStack Compute
Services Self Metric: Service| Nova:Nova-Network|Running (%) <= 50 Health Immediate All nova-network services are unavailable OpenStack Compute
Services Self Metric: Service| Nova:Nova-NetworkRunning (%) = 0
Health Critical One or more
nova-novnc-proxy services are unavailable
OpenStack Compute
Services Self Metric: Service| Nova:Nova-NoVncProxy| Running (%) < 100
Health Warning
Alert Name Object Type Symptom Impact Severity
The majority of nova-novnc-proxy services are unavailable
OpenStack Compute
Services Self Metric:Service| Nova:Nova-NoVncProxy| Running (%) <= 50 Health Immediate All nova-novnc-proxy services are unavailable OpenStack Compute
Services Self Metric: Service| Nova:Nova-NoVncProxy| Running (%) = 0
Health Critical One or more
nova-objectstore services are unavailable
OpenStack Compute
Services Self Metric: Service| Nova:Nova-ObjectStore|Running (%) < 100
Health Warning The majority of
nova-objectstore services are unavailable
OpenStack Compute
Services Self Metric: Service| Nova:Nova-ObjectStore|Running (%) <= 50 Health Immediate All nova-objectstore services are unavailable OpenStack Compute
Services Self Metric: Service| Nova:Nova-ObjectStore|Running (%) = 0
Health Critical One or more
nova-scheduler services are unavailable
OpenStack Compute
Services Self Metric: Service| Nova:Nova-Scheduler|Running (%) < 100
Health Warning The majority of
nova-scheduler services are unavailable
OpenStack Compute
Services Self Metric: Service| Nova:Nova-Scheduler|Running (%) <= 50 Health Immediate All nova-scheduler services are unavailable OpenStack Compute
Services Self Metric: Service| Nova:Nova-Scheduler|Running (%) = 0
Health Critical One or more
nova-xvpvnc-proxy services are unavailable
OpenStack Compute
Services Self Metric: Service| Nova:Nova-XvpvncProxy| Running (%) < 100
Health Warning The majority of
nova-xvpvnc-proxy services are unavailable
OpenStack Compute
Services Self Metric: Service| Nova:Nova-XvpvncProxy| Running (%) <= 50
Health Immediate All
nova-xvpvnc-proxy services are unavailable
OpenStack Compute
Services Self Metric: Service| Nova:Nova-XvpvncProxy| Running (%) = 0
Health Critical The cinder-api service
is unavailable Cinder ControllerService Self Metric: Cinder-Api Process Metrics| AVAILABILITY| Availability < 1
Health Critical The cinder-scheduler
service is unavailable Cinder ControllerService Self Metric: Cinder-Scheduler Process Metrics|
AVAILABILITY| Availability < 1
Table 6‑1. OpenStack Alert Definitions (Continued)
Alert Name Object Type Symptom Impact Severity
The cinder-volume
service is unavailable Cinder ControllerService Self Metric: Cinder-Volume Process Metrics|
AVAILABILITY| Availability < 1
Health Critical The glance-api service
is unavailable Glance ControllerService Self Metric: Glance-Api Process Metrics| AVAILABILITY| Availability < 1
Health Critical The glance-registry
service is unavailable Glance ControllerService Self Metric: Glance-Registry Process Metrics|
AVAILABILITY| Availability < 1
Health Critical The swift-proxy-server
service is unavailable Swift ControllerService Self Metric: Swift-Proxy-Server Process Metrics| AVAILABILITY| Availability < 1 Health Critical The swift-account-server service is unavailable Swift Controller
Service Self Metric: Swift-Account-Server Process Metrics| AVAILABILITYAvai lability < 1 Health Critical The swift-container-server service is unavailable Swift Controller
Service Self Metric: Swift-Container-Server Process Metrics| AVAILABILITYAvai lability < 1
Health Critical The swift-object-server
service is unavailable Swift ControllerService Self Metric: Swift-Object-Server Process Metrics| AVAILABILITY| Availability < 1
Health Critical One or more
cinder-api services are unavailable
OpenStack Storage
Services Self Metric: Service|Cinder:Cinder-Api| Running (%) < 100
Health Warning The majority of
cinder-api services are unavailable
OpenStack Storage
Services Self Metric: Service|Cinder:Cinder-Api| Running (%) <= 50
Health Immediate All cinder-api services
are unavailable OpenStack StorageServices Self Metric: Service|Cinder:Cinder-Api| Running (%) = 0
Health Critical One or more
cinder-scheduler services are unavailable
OpenStack Storage
Services Self Metric: Service| Cinder:Cinder-Scheduler|Running (%) < 100
Health Warning The majority of
cinder-scheduler services are unavailable
OpenStack Storage
Services Self Metric: Service| Cinder:Cinder-Scheduler|Running (%) <= 50
Health Immediate All cinder-scheduler
services are OpenStack StorageServices Self Metric: Service|Cinder:Cinder- Health Critical
Alert Name Object Type Symptom Impact Severity
One or more cinder-volume services are unavailable
OpenStack Storage
Services Self Metric: Service| Cinder:Cinder-Volume|Running (%) < 100
Health Warning The majority of
cinder-volume services are unavailable
OpenStack Storage
Services Self Metric: Service| Cinder:Cinder-Volume|Running (%) <= 50 Health Immediate All cinder-volume services are unavailable OpenStack Storage
Services Self Metric: Service| Cinder:Cinder-Volume|Running (%) = 0
Health Critical One or more
glance-api services are unavailable
OpenStack Storage
Services Self Metric: Service|Glance:Glance-Api| Running (%) < 100
Health Warning The majority of
glance-api services are unavailable
OpenStack Storage
Services Self Metric: Service|Glance:Glance-Api| Running (%) <= 50
Health Immediate All glance-api services
are unavailable OpenStack StorageServices Self Metric: Service|Glance:Glance-Api| Running (%) = 0
Health Critical One or more
glance-registry services are unavailable
OpenStack Storage
Services Self Metric: Service| Glance:Glance-Registry|Running (%) < 100 Health Warning The majority of glance-registry services are unavailable OpenStack Storage
Services Self Metric: Service| Glance:Glance-Registry|Running (%) <= 50 Health Immediate All glance-registry services are unavailable OpenStack Storage
Services Self Metric: Service| Glance:Glance-Registry|Running (%) = 0
Health Critical One or more
swift-account-server services are unavailable
OpenStack Storage
Services Self Metric: Service| Swift:Swift-Account-Server|Running (%) < 100
Health Warning The majority of
swift-account-server services are unavailable
OpenStack Storage
Services Self Metric: Service| Swift:Swift-Account-Server|Running (%) <= 50
Health Immediate All
swift-account-server services are unavailable
OpenStack Storage
Services Self Metric: Service| Swift:Swift-Account-Server|Running (%) = 0
Health Critical One or more
swift-container-server services are unavailable
OpenStack Storage
Services Self Metric: Service| Swift:Swift-Container-Server| Running (%) < 100
Health Warning The majority of
swift-container-server services are unavailable
OpenStack Storage
Services Self Metric: Service| Swift:Swift-Container-Server| Running (%) <= 50
Table 6‑1. OpenStack Alert Definitions (Continued)
Alert Name Object Type Symptom Impact Severity
All swift-container-server services are unavailable
OpenStack Storage
Services Self Metric: Service| Swift:Swift-Container-Server| Running (%) = 0
Health Critical One or more
swift-object-server services are unavailable
OpenStack Storage
Services Self Metric: Service| Swift:Swift-Object-Server|Running (%) < 100
Health Warning The majority of
swift-object-server services are unavailable
OpenStack Storage
Services Self Metric: Service| Swift:Swift-Object-Server|Running (%) <= 50 Health Immediate All swift-object-server services are unavailable OpenStack Storage
Services Self Metric: Service| Swift:Swift-Object-Server|Running (%) = 0
Health Critical One or more
swift-proxy-server services are unavailable
OpenStack Storage
Services Self Metric: Service| Swift:Swift-Proxy-Server|Running (%) < 100
Health Warning The majority of
swift-proxy-server services are unavailable
OpenStack Storage
Services Self Metric: Service| Swift:Swift-Proxy-Server|Running (%) <= 50 Health Immediate All swift-proxy-server services are unavailable OpenStack Storage
Services Self Metric: Service| Swift:Swift-Proxy-Server|Running (%) = 0
Health Critical The neutron-server
service is unavailable Neutron ControllerService Self Metric: Neutron-Server Process Metrics|
AVAILABILITY| Availability < 1
Health Critical One or more
neutron-server services are unavailable
OpenStack Network
Services Self Metric: Service| Neutron:Neutron-Server|Running (%) < 100 Health Warning The majority of neturon-server services are unavailable OpenStack Network
Services Self Metric: Service| Neutron:Neutron-Server|Running (%) <= 50 Health Immediate All neutron-server services are unavailable OpenStack Network
Services Self Metric: Service| Neutron:Neutron-Server|Running (%) = 0
Health Critical The
keystone-all-service is unavailable KeyStone ControllerService Self Metric:Keystone-All Process Metrics|
AVAILABILITY| Availability < 1
Health Critical The mySQL database
service is unavailable mySQL Self Metric:AVAILABILITY| Availability< 1
Health Critical
Alert Name Object Type Symptom Impact Severity
The Apache server is
unavailable Apache Self Metric:AVAILABILITY| Availability< 1
Health Critical The Rabbit Messaging
service is unavailable RabbitMQ SelfMetric:AVAILABILITY| Availability< 1
Health Critical The memcached
service is unavailable Memcached Self Metric:AVAILABILITY| Availability< 1
Health Critical One or more
keystone-all services are unavailable
OpenStack Management Services
Self Metric: Service| Keystone:Keystone-All|Running (%) < 100 Health Warning The majority of keystone-all services are unavailable OpenStack Management Services
Self Metric: Service| Keystone:Keystone-All|Running (%) <= 50 Health Immediate All keystone-all services are unavailable OpenStack Management Services
Self Metric: Service| Keystone:Keystone-All|Running (%) = 0
Health Critical One or more mySQL
services are unavailable
OpenStack Management Services
Self Metric: Service| MySQL|Running (%) < 100
Health Warning The majority of
mySQL services are unavailable
OpenStack Management Services
Self Metric: Service| MySQL|Running (%) <= 50
Health Immediate All mySQL services
are unavailable OpenStackManagement Services
Self Metric: Service| MySQL|Running (%) = 0
Health Critical One or more Apache
services are unavailable
OpenStack Management Services
Self Metric: Service| Apache|Running (%) < 100
Health Warning The majority of
Apache services are unavailable
OpenStack Management Services
Self Metric: Service| Apache|Running (%) <= 50
Health Immediate All Apache services
are unavailable OpenStackManagement Services
Self Metric: Service| Apache|Running (%) = 0
Health Critical One or more
RabbitMQ services are unavailable
OpenStack Management Services
Self Metric: Service| RabbitMQ|Running (%) < 100
Health Warning The majority of
RabbitMQ services are unavailable
OpenStack Management Services
Self Metric: Service| RabbitMQ|Running (%) <= 50
Health Immediate All RabbitMQ services
are unavailable OpenStackManagement Services
Self Metric: Service| RabbitMQ|Running (%) = 0 Health Critical One or more Memcached services are unavailable OpenStack Management Services
Self Metric: Service| Memcached| Running (%) < 100
Table 6‑1. OpenStack Alert Definitions (Continued)
Alert Name Object Type Symptom Impact Severity
The majority of Memcached services are unavailable OpenStack Management Services
Self Metric: Service| Memcached| Running (%) <= 50 Health Immediate All Memcached services are unavailable OpenStack Management Services
Self Metric: Service| Memcached| Running (%) = 0 Health Critical Virtual Machine is reporting an error status Non-ESX Virtual
Machine Self Metric: Status|Availability < 1 Health Critical Logical Switch is
reporting an error status
OpenStack Logical
Switch Self Metric: Status|Availability < 1 Health Critical One or more ports on
the Logical Switch are down
OpenStack Logical
Switch Self Metric: Port|Status = DOWN Health Critical External Logical
Switch is reporting an error status
OpenStack External
Logical Switch Self Metric: Status|Availability < 1 Health Critical One or more ports on
the external Logical Switch are down
OpenStack External
Logical Switch Self Metric: Port|Status = DOWN Health Critical Logical Router is
reporting an error status
OpenStack Logical
Router Self Metric: Status|Availability < 1 Health Critical One or more ports on
the Logical Router are down
OpenStack Logical
Router Self Metric: Port|Status = DOWN Health Critical One or more
provisioned resources are reporting an error status
OpenStack Tenant Child (Virtual Machine) Metric: Status|Availability < 1 Child (Logical Switch) Metric: Status|Availability < 1 Child (External Logical Switch) Metric: Status| Availability < 1 Child (Logical Router) Metric: Status|Availability < 1 Health Critical Tenant is currently
disabled OpenStack Tenant Self Metric: Status|Availability < 1 Health Warning
Alert Name Object Type Symptom Impact Severity
Tenant resource
creation rate is high OpenStack Tenant Self Metric:Network|Total Networks above dynamic threshold Self Metric: Network|Total Routers above dynamic threshold Self Metric: Instance| Usage above dynamic threshold
Table 6‑1. OpenStack Alert Definitions (Continued)
Alert Name Object Type Symptom Impact Severity
Tenant is approaching
their quota OpenStack Tenant 1 Warninga Self Metric: Instance| Usage (%)>= 85 b Self Metric: CPU|Usage (%)>= 85 c Self Metric: Memory| Usage (%)>= 85 d Self Metric: Floating IP| Usage (%)>= 85 e Self Metric: Security Group| Usage (%)>= 85 2 Immediate a Self Metric: Instance| Usage (%)>= 90 b Self Metric: CPU|Usage (%)>= 90 c Self Metric: Memory| Usage (%)>= 90 d Self Metric: Floating IP| Usage (%)>= 90 e Self Metric: Security Group| Usage (%)>= 90 3 Critical a Self Metric: Instance| Usage (%)>= 95 b Self Metric: CPU|Usage (%)>= 95 c Self Metric: Memory| Usage (%) >= 95 d Self Metric: Floating IP| Usage (%)>= Risk 1 Warning 2 Immediate 3 Critical
Alert Name Object Type Symptom Impact Severity e Self Metric: Security Group| Usage (%)>= 95 Compute infrastructure is approaching capacity OpenStack Compute
Infrastructure 1 Warninga Self Metric: Memory| Demand (%)<= 70 b Self Metric :Disk Space|Usage (%)<= 70 2 Immediate a Self Metric: Memory| Demand (%)<= 80 b Self Metric: Disk Space| Usage (%)<= 80 3 Critical a Self Metric: Memory| Demand (%)<= 90 b Self Metric: Disk Space| Usage (%)<= 90 Risk 1 Warning 2 Immediate 3 Critical
Table 6‑1. OpenStack Alert Definitions (Continued)
Alert Name Object Type Symptom Impact Severity
Host is approaching
capacity Host System 1 Warninga Self Metric: Memory| Usage (%)<= 85 b Self Metric :Disk Space| Demand| Workload (%)<= 85 2 Immediate a Self Metric: Memory| Usage (%)<= 90 b Self Metric: Disk Space| Demand| Workload (%)<= 90 3 Critical a Self Metric: Memory| Usage (%)<= 95 b Self Metric: Disk Space| Demand| Workload (%)<= 95 Risk 1 Warning 2 Immediate 3 Critical Host is approaching
capacity Non-ESX HostSystem 1 Warninga Self Metric: Memory| Usage (%)<= 85 b Self Metric :Disk| Usage (%)<= 85 2 Immediate a Self Metric: Memory| Usage (%)<= 90 b Self Metric: Disk|Usage (%)<= 90 3 Critical a Self Metric: Memory| Usage (%)<= 95 b Self Metric: Disk|Usage (%)<= 95 Risk 1 Warning 2 Immediate 3 Critical
Alert Name Object Type Symptom Impact Severity
Storage infrastructure is approaching capacity
OpenStack Storage
Infrastructure 1 Warninga Self Metric: Capacity| Usage (%)<= 70 2 Immediate a Self Metric: Capacity| Usage (%)<= 80 3 Critical a Self Metric: Capacity| Usage (%)<= 90 Risk 1 Warning 2 Immediate 3 Critical Neutron-DHCP-agent
service is unavailable Neutron ControllerService Self Metric: Neutron-Dhcp-Agent Process Metrics|
AVAILABILITY| Availability <
Health Critical Neutron-l3-agent
service is unavailable Neutron ControllerService Self Metric: Neutron-L3-Agent Process Metrics| AVAILABILITY| Availability < 1 Health Critical Neutron-metadata-agent service is unavailable Neutron Controller
Service Self Metric: Neutron-Metadata-Agent Process Metrics| AVAILABILITY| Availability < 1
Health Critical Neutron-lbaas-agent
service is unavailable Neutron ControllerService Self Metric: Neutron-Lbaas-Agent Process Metrics| AVAILABILITY| Availability < 1 Health Critical Neutron-openvswitch-agent service is unavailable Neutron Controller
Service Self Metric: Neutron-Openvswitch-Agent Process Metrics| AVAILABILITY| Availability < 1
Health Critical One or more
neutron-DHCP-agent services are unavailable
OpenStack Network
Services Self Metric: Service| Neutron:Neutron-Dhcp-Agent| Running (%) < 100 Health Warning The majority of neutron-dhcp-agent services are unavailable OpenStack Network
Services Self Metric: Service| Neutron:Neutron-Dhcp-Agent| Running (%) <= 50
Health Immediate All
neutron-dhcp-agent services are unavailable
OpenStack Network
Services Self Metric: Service| Neutron:Neutron-Dhcp-Agent| Running (%) = 0
Health Critical One or more
neutron-l3-agent services are unavailable
OpenStack Network
Services Self Metric: Service| Neutron:Neutron-L3-Agent|Running (%) < 100
Table 6‑1. OpenStack Alert Definitions (Continued)
Alert Name Object Type Symptom Impact Severity
The majority of neutron-l3-agent services are unavailable
OpenStack Network
Services Self Metric: Service| Neutron:Neutron-L3-Agent|Running (%) <= 50 Health Immediate All neutron-l3-agent services are unavailable OpenStack Network
Services Self Metric: Service| Neutron:Neutron-L3-Agent|Running (%) = 0
Health Critical One or more
neutron-metadata-agent services are unavailable
OpenStack Network
Services Self Metric: Service| Neutron:Neutron-Metadata-Agent| Running (%) < 100
Health Warning The majority of
neutron-metadata-agent services are unavailable
OpenStack Network
Services Self Metric: Service| Neutron:Neutron-Metadata-Agent| Running (%) <= 50
Health Immediate All
neutron-metadata-agent services are unavailable
OpenStack Network
Services Self Metric: Service| Neutron:Neutron-Metadata-Agent| Running (%) = 0
Health Critical One or more
neutron-lbaas-agent services are unavailable
OpenStack Network
Services Self Metric: Service| Neutron:Neutron-Lbaas-Agent| Running (%) < 100 Health Warning The majority of neutron-lbaas-agent services are unavailable OpenStack Network
Services Self Metric: Service| Neutron:Neutron-Lbaas-Agent| Running (%) <= 50
Health Immediate All
neutron-lbaas-agent services are unavailable
OpenStack Network
Services Self Metric: Service| Neutron:Neutron-Lbaas-Agent| Running (%) = 0
Health Critical One or more
neutron-openvswitch-agent services are unavailable
OpenStack Network
Services Self Metric: Service| Neutron:Neutron-Openvswitch-Agent| Running (%) < 100
Health Warning The majority of
neutron-openvswitch-agent services are unavailable
OpenStack Network
Services Self Metric: Service| Neutron:Neutron-Openvswitch-Agent| Running (%) <= 50 Health Immediate All neutron-openvswitch-agent services are unavailable OpenStack Network
Services Self Metric: Service| Neutron:Neutron-Openvswitch-Agent| Running (%) = 0
Health Critical
Management Pack for OpenStack
Capacity Models
7
An object's capacity model, combined with policy settings, is used to determine the value of all badges and sub-badges aside from Health.
The Management Pack for OpenStack capacity model tables describe the capacity models that have been defined for each object type.
OpenStack Compute Infrastructure
The capacity of the Compute Infrastructure is represented by the aggregated capacity of all hosts and clusters registered with OpenStack
Table 7‑1. OpenStack Compute Infrastructure Capacity Model
Container Description Use in Workload
Memory Aggregate amount of physical memory used across all hosts and clusters that are registered with OpenStack.
Yes Disk Space Aggregate amount of local disk space used
across all hosts and clusters that are registered with OpenStack.
Yes
OpenStack Storage Infrastructure
The capacity of the Storage Infrastructure is represented by the aggregated capacity of all vCenter datastores with OpenStack.
Table 7‑2. OpenStack Storage Infrastructure Capacity Model
Container Description Use in Workload
Datastore|Outstanding IO
Requests Aggregate number of outstanding I/O requestsacross all vCenter datatores that are registered with OpenStack. The capacity for this container uses a maximum observed value approach.
Yes Datastore|Reads per second Aggregate rate of reads across all vCenter
datastore that are registered with OpenStack. The capacity for this container uses a maximum observed value approach.
Yes Datastore|Writes per second Aggregate rate of writes across all vCenter
datastores that are registered with OpenStack. The capacity for this container uses a maximum
Container Description Use in Workload
Datastore|Read Rate Aggregate rate of data read across all vCenter datastores that are registered with OpenStack. The capacity for this container uses a maximum observed value approach.
Yes Datastore|Write Rate Aggregate rate of data written across all vCenter
datastores that are registered with OpenStack. The capacity for this container uses a maximum observed value approach.
Yes Disk Space|Usage Aggregate amount of local disk space used
across all hosts and clusters that are registered with OpenStack.
Yes
OpenStack Tenant
The capacity of a Tenant represents the number of provisioned objects relative to the configured quota.
Table 7‑3. OpenStack Tenant Capacity Model
Container Description Use in Workload
Instance Number of virtual machines provisioned by the tenant compared to the quota. No CPU Number of virtual CPUs provisioned across all
virtual machines by the tenant compared to the quota.
No Memory Amount of vRAM provisioned across all virtual
machines by the tenant compared to the quota. No Floating IP Number of floating IPs provisioned by the tenant
compared to the quota. No Security Group Number of security groups provisioned by the
tenant compared to the quota. No
Non-ESX Host
Table 7‑4. Non-ESX Host Capacity Model
Container Description Use in Workload
Memory Amount of physical memory used by the host. Yes Disk Amount of local disk space used by the host. Yes
Capacity Models
Capacity models have not been defined for the following objects.
n OpenStack Network Infrastructure n OpenStack Compute Services n OpenStack Network Services n OpenStack Storage Services n OpenStack Management Services
n OpenStack Logical Switch
n OpenStack External Logical Switch n OpenStack Logical Router
n Non-ESX Virtual Machine
Management Pack for OpenStack
Object Model
8
OpenStack Objects and Metrics
Metrics have not been defined for the following objects.
n OpenStackNetwork Infrastructure
OpenStack Compute Infrastructure
Table 8‑1. OpenStack Compute Infrastructure Metrics
Name Category Type Unit Description Instanced
Provisioned
Capacity Memory Metric GB Total physicalmemory capacity of all Hosts registered with OpenStack.
No Usable Capacity Memory Metric GB Total physical
memory capacity of all Hosts registered with OpenStack, minus the memory overhead. No
Usage Memory Metric GB Total amount of physical memory being used across all Hosts registered with OpenStack.
No Usage Memory Metric % Percentage of
physical memory being used across all Hosts registered with OpenStack
No Demand Memory Metric GB Total amount of
physical memory being demanded across all Hosts
Name Category Type Unit Description Instanced
Demand Memory Metric % Percentage of physical memory being demanded across all Hosts registered with OpenStack
No OpenStack
Instance Usage Memory Metric GB Total amount ofphysical amount memory being used by OpenStack instances across all hosts registered with OpenStack. No OpenStack
Instance Usage Memory Metric % Percentage ofphysical memory being used by OpenStack instances across all hosts registered with OpenStack. No Provisioned
Capacity Disk Space Metric GB Total disk spacecapacity of all Hosts registered with OpenStack
No Usage Disk Space Metric GB Total amount of
disk space being used across all Hosts registered with OpenStack
No Usage Disk Space Metric % Percentage of
disk space being used across all Hosts registered with OpenStack
No OpenStackInstanc
e Usage Disk Space Metric GB Total amount ofdisk space being used by OpenStack instances across all hosts registered with OpenStack No OpenStack
instance Usage Disk Space Metric % Percentage ofdisk space being used by OpenStack instances across all Hosts registered with OpenStack No
Table 8‑1. OpenStack Compute Infrastructure Metrics (Continued)
Name Category Type Unit Description Instanced
Logical Processors CPU Metric Integer Number of logical processors on all Hosts registered with OpenStack No Number of Virtual
CPUs in Use CPU Metric Integer Number ofvCPUs provisioned across all Hosts registered with OpenStack
No OpenStack
Instance Usage CPU Metric Integer Number ofvCPUs provisioned by OpenStack instance across all Hosts registered with OpenStack No
OpenStack Storage Infrastructure
Table 8‑2. OpenStack Storage Infrastructure Metrics
Name Category Type Unit Description Instanced
Total Capacity Capacity Metric GB Total disk space capacity across all vCenter Datastores registered with OpenStack. No Used Space Capacity Metric GB Total amount of
disk space being used across all vCenter Datastores registered with OpenStack.
No Usage Capacity Metric % Percentage of
disk space being used across all vCenter Datastores registered with OpenStack. No Outstanding IO
Requests Datastore Metric OIOs Total number ofoutstanding I/O requests across all vCenter Datastores registered with OpenStack. No
Name Category Type Unit Description Instanced
Max Observed Number of Outstanding IO Operations
Datastore Metric OIOs Maximum observed number of I/O requests across all vCenter Datastores registered with OpenStack. No
Reads per Second Datastore Metric IOPs Total rate of read commands issued across all vCenter Datastores registered with OpenStack. No Max Observed
Reads per Second Datastore Metric IOPS Maximumobserved rate of read commands issued across all vCenter Datastores registered with OpenStack.
No
Writes per Second Datastore Metric IOPS Total rate of write commands issued across all vCenter Datastores registered with OpenStack. No Max Observed
Writes per Second Datastore Metric IOPS Maximumobserved rate of write commands issued across all vCenter Datastores registered with OpenStack.
No
Read Rate Datastore Metric KBps Total rate of data read across all vCenter Datastores registered with OpenStack. No Max Observed
Read Rate Datastore Metric KBps Maximumobserved rate of data read across all vCenter Datastores registered with OpenStack.
