tenant user's guide · openstack horizon, the user interface visualizes the health and status...

J2UL-2074-01ENZ0(00)November 2015

FUJITSU SoftwareServerViewCloud Monitoring Manager V1.0

Tenant User's Guide

Trademarks LINUX is a registered trademark of Linus Torvalds.The OpenStack® Word Mark and OpenStack Logo areeither registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation in theUnited States and other countries and are used withthe OpenStack Foundation's permission. We are notaffiliated with, endorsed or sponsored by the OpenStackFoundation, or the OpenStack community.Red Hat is a trademark or a registered trademark of RedHat Inc. in the United States and other countries.Java® is a registered trademark of Oracle and/or itsaffiliates.Python and PyCon are trademarks or registeredtrademarks of the Python Software Foundation.ServerView and Systemwalker are registered trademarksof FUJITSU LIMITED.Other company names and product names aretrademarks or registered trademarks of their respectiveowners.

Copyright FUJITSULIMITED 2015

All rights reserved, including those of translation into otherlanguages. No part of this manual may be reproducedin any form whatsoever without the written permission ofFUJITSU LIMITED.

High Risk Activity

The Customer acknowledges and agrees that the Product is designed, developedand manufactured as contemplated for general use, including without limitation,general office use, personal use, household use, and ordinary industrial use, but is notdesigned, developed and manufactured as contemplated for use accompanying fatalrisks or dangers that, unless extremely high safety is secured, could lead directly todeath, personal injury, severe physical damage or other loss (hereinafter "High SafetyRequired Use"), including without limitation, nuclear reaction control in nuclear facility,aircraft flight control, air traffic control, mass transport control, medical life supportsystem, missile launch control in weapon system. The Customer shall not use theProduct without securing the sufficient safety required for the High Safety Required Use.In addition, FUJITSU (or other affiliate's name) shall not be liable against the Customerand/or any third party for any claims or damages arising in connection with the HighSafety Required Use of the Product.

Export Restrictions

Exportation/release of this document may require necessary procedures in accordancewith the regulations of your resident country and/or US export control laws.

Contents

Tenant User's Guide 3

ContentsAbout this Manual........................................................................... 4

1 Introduction...................................................................................... 6

1.1 Basic Usage Scenario........................................................................................... 7

1.2 The Tenant User's Tasks.......................................................................................7

1.3 Components........................................................................................................... 9

1.4 User Management..................................................................................................9

2 Monitoring Services and Servers.................................................11

2.1 Overview of Services and Servers.................................................................... 11

2.2 Defining Alarms................................................................................................... 12

2.3 Defining Notifications..........................................................................................13

2.4 Working with Data Visualizations...................................................................... 13

Glossary ......................................................................................................... 15

About this Manual


About this ManualThis manual describes how service providers on OpenStack platforms can monitor their cloudresources with FUJITSU ServerView Cloud Monitoring Manager - hereafter referred to as CloudMonitoring Manager (CMM).The manual is structured as follows:

Chapter Description

Introduction Introduces CMM and the basic usage scenario ofmonitoring cloud resources.

Monitoring Services and Servers onpage 11

Describes the basic tasks involved in monitoringcloud resources.

Glossary on page 15 Defines the central terms relevant for CMM.

Readers of this ManualThis manual is directed to service providers who use CMM for monitoring their cloud resourceson OpenStack platforms. The manual assumes that you have basic knowledge of OpenStackenvironments.

Notational ConventionsThis manual uses the following notational conventions:

Add The names of graphical user interface elements like menu options are shownin boldface.

init System names, for example command names and text that is entered fromthe keyboard, are shown in Courier font.

<variable> Variables for which values must be entered are enclosed in angle brackets.

[option] Optional items, for example optional command parameters, are enclosed insquare brackets.

one | two Alternative entries are separated by a vertical bar.

{one | two} Mandatory entries with alternatives are enclosed in curly brackets.

AbbreviationsThis manual uses the following abbreviations:

CMM Cloud Monitoring Manager

IaaS Infrastructure as a Service

ICMP Internet Control Message Protocol

OS Operating System

OSS Open Source Software

About this Manual


PaaS Platform as a Service

SaaS Software as a Service

Available DocumentationThe following documentation on CMM is available:• Overview: A manual introducing CMM. It is written for everybody interested in CMM.• CMM Operator's Guide: A manual for operators describing how to install, operate, and maintain

CMM.• OpenStack Operator's Guide: A manual for OpenStack operators describing how CMM

supports them in monitoring OpenStack services as well as managing the available log data.• Tenant User's Guide: A manual for tenant users describing how CMM supports them in

monitoring their services and virtual machines.

Related Web ReferencesThe following Web references provide information on open source offerings integrated with CMM:• OpenStack: Documentation on OpenStack, the underlying platform technology.• OpenStack Horizon: Documentation on the OpenStack Horizon dashboard.• Monasca Wiki: Information on Monasca, the core of CMM.

More detailed Web references provided in this manual are subject to change without notice.

http://docs.openstack.org/

http://docs.openstack.org/developer/horizon/

https://wiki.openstack.org/wiki/Monasca

1: Introduction


1 IntroductionAs more and more applications are deployed on cloud systems and cloud systems are growing incomplexity, managing the cloud infrastructure is becoming increasingly difficult. Cloud MonitoringManager (CMM) helps mastering this challenge by providing a sophisticated Monitoring as aService solution that is operated on top of OpenStack-based cloud computing platforms.CMM addresses the requirements of large-scale public and private clouds where high numbersof physical and virtual servers need to be monitored and huge amounts of monitoring data needto be managed. It consolidates metrics, alarms, and notifications, as well as health and statusinformation from multiple systems, thus reducing the complexity and allowing for a higher levelanalysis of the monitoring data.CMM covers all aspects of a Monitoring as a Service solution:• Storage of monitoring data in a resilient way.• Multi-tenancy architecture for submitting and streaming metrics. The architecture ensures the

secure isolation of tenant data.• Horizontal and vertical scalability to support constantly evolving cloud infrastructures. When

physical and virtual servers are scaled up or down to varying loads, the monitoring solution canbe adapted accordingly.

• Graphical user interface that is seamlessly integrated into the cloud infrastructure. Based onOpenStack Horizon, the user interface visualizes the health and status of the cloud resourcesand enables user access to all monitoring functionality.

1: Introduction


1.1 Basic Usage ScenarioThe basic usage scenario of setting up and using the monitoring services of CMM looks asfollows:

Tenant users book virtual machines in OpenStack to provide services to end users or to hostservices that they need for their own development activities. CMM helps tenant users ensure thattheir services and the servers on which these services are provided are configured and working asrequired.The OpenStack operator uses CMM to monitor physical and virtual servers, hypervisors, andservices of the underlying platform. In addition, he is responsible for the middleware components,for example, RabbitMQ or database services. The OpenStack operator also prepares themonitoring environment including available metrics for tenant users.The CMM operator is responsible for providing the monitoring services to the tenant users andthe OpenStack operator. This enables the tenant users and the OpenStack operator to focus onoperation and the quality of their services without having to carry out the tedious tasks impliedby setting up and administrating their own monitoring software. The CMM operator uses themonitoring services himself for monitoring the operation of CMM.

1.2 The Tenant User's TasksThe CMM operator and the OpenStack operator are responsible for preparing your monitoringenvironment. The OpenStack operator configures which metrics are available to you. He explicitlyactivates the metrics that you can use for monitoring the virtual machines you have booked.

1: Introduction


Available MetricsMetrics are self-describing data structures that are uniquely identified by a name and a set ofdimensions. Each dimension consists of a key/value pair that allows for a flexible and concisedescription of the data to be monitored, for example, region, availability zone, service tier, orresource ID.The standard metrics include:• Metrics on CPU usage:

For example, the percentage of time the CPU is idle when no I/O requests are in progress, orthe percentage of time the CPU is used at system level or user level.

• Metrics on disk space:For example, the percentage of disk space that is used on a device, or the total amount of diskspace aggregated across all the disks on a particular node.

• Metrics on the average system load over different periods:For example, 1 minute, 5 minutes, or 15 minutes.

• Metrics on memory usage:For example, the number of megabytes of total memory or free memory, or the percentage offree swap memory.

• Metrics on the network:For example, the number of network bytes received or sent per second, or the number ofnetwork errors on incoming or outgoing network traffic per second.

The OpenStack operator configures additional metrics. Please contact your OpenStack operatorfor information on the additional metrics that you can use for monitoring.

Monitoring FunctionsFor monitoring your services and servers, CMM provides functions for alarm and notificationmanagement. Template-based alarm definitions allow for monitoring a dynamically changing set ofresources without the need for reconfiguration. While the number of underlying virtual machines ischanging, for example, this ensures the efficient monitoring of elastic cloud services. Notificationscan be configured in order to inform CMM users when an alarm is triggered.As a tenant user, you can:• Monitor the status of services and servers.• Create, update, and delete alarms.• Create, update, and delete notifications.• View, share, and explore visualizations of the monitoring data.

For details on the monitoring functions, refer to Monitoring Services and Servers on page 11.

1: Introduction


1.3 ComponentsThe following illustration provides an overview of the CMM components:

OpenStackOpenStack is the underlying platform technology of CMM. It allows for the deployment andmanagement of Infrastructure as a Service (IaaS) platforms.

CMM ServiceThe CMM Service is the central CMM component. It is responsible for receiving, persisting, andprocessing monitoring data, as well as providing the data to the users.The CMM Service relies on Monasca, an open source Monitoring as a Service solution. It usesMonasca for high-speed metrics querying and integrates the streaming alarm engine and thenotification engine of Monasca.

CMM Horizon PluginCMM comes with a plugin for the OpenStack Horizon dashboard. The plugin extends the maindashboard in OpenStack with a view for monitoring. This enables CMM users to access themonitoring functions from a central Web-based graphical user interface.Monitoring data is visualized on a comfortable and easy-to-use dashboard which fully integrateswith Grafana, an open source application for visualizing large-scale measurement data.

1.4 User ManagementCMM is fully integrated with Keystone, the identity service which serves as the commonauthentication and authorization system in OpenStack.The CMM integration with Keystone requires any CMM user to be registered as an OpenStackuser. All authentication and authorization in CMM is done through Keystone. If a user requestsmonitoring data, for example, CMM verifies that the user is a valid user in OpenStack and allowedto access the requested metrics.CMM users are created and administrated in OpenStack:• Each user assumes a role in OpenStack to perform a specific set of operations. The

OpenStack role specifies a set of rights and privileges.• Each user is assigned to at least one project in OpenStack. A project defines a set of resources

which can be accessed by the assigned users.

For details on user management, refer to the OpenStack documentation.

http://docs.openstack.org/

1: Introduction


As a CMM tenant user who wants to monitor services and servers, you must fulfill the followingprerequisites:• You must be registered as an OpenStack user.• You must be assigned the cmm-user role or any other role that is authorized to use the CMM

monitoring functions. Additional roles are optional. Contact your OpenStack operator for moreinformation.

• You must be assigned to the project you want to monitor.

2: Monitoring Services and Servers


2 Monitoring Services and ServersFor monitoring your services and the servers on which they are provisioned, you use the CMMmonitoring user interface. You can access this user interface from the OpenStack Horizondashboard.You can define alarms and notifications for monitoring your resources. A monitoring overviewallows you to keep track of your services and servers and quickly check their status.In the following sections, you will find information on how to define alarms and notifications as wellas details on the monitoring overview provided by CMM.

Accessing CMMTo perform monitoring tasks, you must use one of the Web browsers supported by CMM:• Google Chrome 45.0• Microsoft Internet Explorer 11.0 (with Compatibility View disabled)• Mozilla Firefox 40.0

In addition, you must have access to the OpenStack platform as a user with the cmm-user role orany other role that is authorized to use the CMM monitoring functions. In addition, you must beassigned to the project you want to monitor.Log in to the OpenStack platform using the user name and password provided as login informationby OpenStack. This allows you to access the OpenStack Horizon dashboard. The CMMfunctionality is available in the Monitoring menu of the dashboard. You can access all monitoringdata of the project to which you are assigned.

2.1 Overview of Services and ServersCMM provides a comfortable status overview of your services and servers. Use the Overviewmenu option in the Monitoring menu to view the status of your services and servers at a glance.Status information is provided as soon as you have defined an alarm for a service or server:• A service or server in a green box indicates that it is up and running. There are alarms defined

for it, but the defined thresholds have not yet been reached or exceeded.• A service or server in a red box indicates that there is a severe problem that needs to be

checked. One or multiple alarms defined for the service or server have been triggered.• A service or server in a yellow box indicates a problem. One or multiple alarms have already

been triggered, yet, the severity of these alarms is low.• A service or server in a gray box indicates that alarms have been defined, yet, the monitoring

data has not yet been collected and sent.

The Overview menu option enables access to all available monitoring data. Use the options at thetop border of the Overview page to access preconfigured CMM metrics dashboards. You have tocreate your own dashboard that visualizes your monitoring data. For details, refer to Working withData Visualizations on page 13.On the Overview page, you can also click on the box for a service or server to display the list ofdefined alarms. For each alarm, the list shows the current alarm status as well as details of thealarm definition.For each alarm in the list, you can execute the following functions via the options in the pull-downmenu:• The Show Alarm Definition option displays all elements of the alarm definition.



• The Graph Metrics option displays the CMM metrics dashboard that visualizes the relatedmonitoring data.

• The Show History option displays the history of the alarm.• The Delete Alarm option deletes the alarm. Use the Delete Alarms option at the top of the

page to delete multiple alarms in one step.

While the Overview menu option in the Monitoring menu provides access to the monitoringdata of individual services and servers, you can use the Alarms menu option in the Monitoringmenu to access the monitoring data of all your cloud resources. The menu option displays thecomplete list of alarms. The available options for working with the individual alarms correspond tothe options described for the Overview menu option above.

2.2 Defining AlarmsCMM allows you to define alarms for monitoring your cloud resources. An alarm definitionspecifies the metric to be collected and the threshold at which an alarm is to be triggered. If thespecified threshold is reached or exceeded for a cloud resource, notifications can be sent toinform the CMM users involved.You can create simple or complex alarm definitions to handle a large variety of monitoringrequirements. The syntax for defining alarms is based on a simple expressive grammar. Bydefault, alarm expressions are evaluated every 60 seconds.For an alarm definition, you specify the following elements:• Name. An identifier of the alarm. The name must be unique within the project for which you

define the alarm.• Expression. Sub-expressions and logical operators that define the alarm. As soon as this

expression evaluates to true, the alarm is triggered.To define the expression, proceed as follows:1. Select the metric you want to monitor. The select list provides access to all metrics that are

predefined by the OpenStack operator.

2. Select a statistical function for the metric: min to monitor the minimum values, max tomonitor the maximum values, sum to monitor the sum of the values, count for the monitorednumber, or avg for the arithmetic average.

3. Enter one or multiple dimensions in the Add dimension field to further qualify the metric.Dimensions filter the data to be monitored. Each dimension consists of a key/value pairthat allows for a flexible and concise description of the data to be monitored, for example,region, availability zone, service tier, or resource ID.The dimensions available for the selected metric are displayed in the Matching Metricssection. Type the name of the dimension you want to associate with the metric in the Adddimension field. You are offered select lists that enable you to add dimensions.

4. Enter the threshold value at which an alarm is to be triggered, and combine it with arelational operator: <, >, <=, or >=.The unit of the threshold value is related to the metric for which you define thethreshold, for example, the unit is percentage for cpu.system_perc or MB fordisk.total_used_space_mb.



Note: If you need to define alarm definitions that are more complex or that need to deviate fromevaluating the metric every 60 seconds, create the alarm definition first and update itafterwards. The Edit Alarm Definition page allows you to directly edit the expressionsyntax. Use the link provided in the upper area of the page to access information on thesyntax that can be used.

• Apply function to metrics. The defined dimensions can be disabled. Select As a group if youwant them to be ignored in the expression that is to be evaluated. Select Individually if youwant the dimensions to be taken into account.

• Description. A short description that depicts the purpose of the alarm.• Severity. The following severities for an alarm are supported: Low, Medium, High, or Critical.

The severity effects the status information on the Overview page. If an alarm that is defined asCritical is triggered, the corresponding service or server is displayed in a red box. If an alarmthat is defined as Low, Medium, or High is triggered, the corresponding service or server isdisplayed in a yellow box.

• Notifications. Alerts to be used when an alarm is triggered. Use Add more for specifyingmore than one notification. As soon as an alarm is triggered, the notifications you specify aresent. For details on notifications, refer to Defining Notifications on page 13.

To create, edit, and delete alarms, use the Alarm Definitions menu option in the Monitoringmenu.

2.3 Defining NotificationsNotifications define how CMM users are informed when a threshold value defined for an alarm isreached or exceeded. In the alarm definition, you can assign one or multiple notifications.For a notification, you specify the following elements:• Name. A unique identifier of the notification. The name is offered for selection when defining an

alarm.• Type. Email is the notification method supported by CMM. WebHook and PagerDuty are not

supported.• Address. The email address to be notified when an alarm is triggered.

Note: Generic top-level domains such as business domain names are not supported in emailaddresses (for example, [email protected]).

To create, edit, and delete notifications, use the Notifications menu option in the Monitoringmenu.

2.4 Working with Data VisualizationsThe user interface for monitoring your services and servers integrates with Grafana, an opensource application for visualizing large-scale monitoring data on metrics dashboards. CMM shipswith preconfigured metrics dashboards for operators. As a tenant user, you can configure yourown dashboards as required.Each metrics dashboard is composed of individual panels that are arranged in a number of rows.You can define which content is displayed in which panel and which time range is visualized.



You can drag and drop panels within and between rows. Additional display options enable you tocustomize how your dashboard presents the defined content.In addition to creating your own dashboards, CMM allows you to export and import dashboards.You can also create and save dashboard templates that facilitate customizations. You can sharedashboards with other users, for example, by creating a link to your current dashboard or bycreating a static snapshot.For details on working with the panel editing user interface of the metrics dashboard, refer to theGetting Started tutorial of Grafana.Use the Overview menu option in the Monitoring menu of the OpenStack Horizon dashboard toaccess the CMM metrics dashboard. The options at the top border of the Overview page allowyou to access preconfigured dashboards. Use them as the starting point for creating your owndashboard with the data you want to visualize.

http://docs.grafana.org/v1.9/guides/gettingstarted/

Glossary


GlossaryApplicationA software, including procedures and documentation, which performs productive tasks for users.

CloudA metaphor for the Internet and an abstraction of the underlying infrastructure it conceals.

Cloud ServiceThe availability of services to users on demand via the Internet.Cloud services are designed to provide easy, scalable access to applications, resources, andservices. They can scale dynamically to meet their user's needs. With the service providersupplying the hardware and software necessary for the service, there is no need for users toprovision or deploy their own resources or allocate IT staff to manage the service.

CMM OperatorA person responsible for maintaining and administrating CMM.

ElasticsearchAn open source application that provides a highly scalable full-text search and analytics engine.CMM uses Elasticsearch as the underlying technology for storing, searching, and analyzing bigvolumes of log data.

GrafanaAn open source application for visualizing large-scale measurement data. CMM integrates withGrafana for visualizing the CMM monitoring data.

Infrastructure as a Service (IaaS)The delivery of computer infrastructure (typically a platform virtualization environment) as aservice.

KibanaAn open source analytics and visualization platform designed to work with Elasticsearch. CMMintegrates with Kibana for visualizing the CMM log data.

LogstashAn open source application for receiving, processing, and outputting logs. Logstash provides apipeline for storing, querying, and analyzing logs. It uses Elasticsearch as a back-end data storeand Kibana as a front-end reporting platform.

MetricsSelf-describing data structures that allow for a flexible and concise description of the data to bemonitored. Metrics values represent the actual monitoring data that is collected and presented inCMM.

Glossary


MonascaAn open source Monitoring as a Service solution that integrates with OpenStack. It forms the coreof CMM.

OpenStack OperatorA person responsible for maintaining and administrating OpenStack, the underlying platformtechnology of CMM.

Platform as a Service (PaaS)The delivery of a computing platform and solution stack as a service.

ServiceGenerally, a discretely defined set of contiguous or autonomous business or technical functionality,for example an infrastructure or Web service.

Software as a Service (SaaS)A model of software deployment where a provider licenses an application to customers for use asa service on demand.

Tenant UserA person with limited access to cloud resources in OpenStack.

tenant user's guide · openstack horizon, the user interface visualizes the health and status...

Documents