Difference between revisions of "Monitoring System"

Revision as of 09:07, 24 July 2013

A gCube infrastructure manages various types of resources, such as:

• Hardware
• Services and Applications
• Collections and Auxiliary Resources

Hardware resources include gCube hosting nodes (containers) as well as gLite storage elements, computing and Cloud nodes, while gCube services and external software fall into the second category type. Collections and auxiliary resources can be data, metadata, indices, schemas or transformation utilities, among others.

All these resource information are collected by the gCube Information System (IS) which plays the role of the infrastructure's registry and supports the publishing, discovery and monitoring of all the resources belonging the infrastructure. In addition, gCube offers a set of tools providing different orthogonal views of resources and their relationships: these tools are available in the Monitoring Portal.

The rest of this section explains the installation process for the Monitoring Portal and then describes the each tools that come with it, separately.

Monitor Portal Installation

The monitoring tools run on [Tomcat 6.x], therefore the first step is to install and start a Tomcat instance.

The, the following monitor portlets has to be downloaded from the gCube website (Download area):

• Infrastructure Viewer
• Advanced Monitoring

Finally, their respective WARs (available in the downloaded archive) have to be deployed into the $CATALINA_HOME/webbaps/.

Configuration

Each portlet has a configuration file where the Infrastructures VO are specified.

Configuring Infrastructure Viewer

The configuration file path is {applicationFolder}/XML/scopedata.xml.

The scopedata file have this structure:

<?xml version="1.0" encoding="UTF-8"?>
<infrastructures>
  <infrastructure>
    <name>d4science</name>
    <vos>
      <vo>
        <name>d4science</name>
        <src>ServiceMap_d4science.research-infrastructures.eu.xml</src>
        <scope>/d4science.research-infrastructures.eu</scope>
      </vo>
    </vos>
  </infrastructure>
<infrastructures>

Tags:

• infrastructures: the infrastructures list.
  • infrastructure: a single infrastructure.
    • name: the infrastructure name (like gcube or d4science)
    • vos: the vo list.
      • vo: a single vo.
        • name: the vo name.
        • src: the vo ServiceMap file (located in $GLOBUS_LOCATION/config dir).
        • scope: the vo scope.

Here a complete sample.

When a new VO is added, a new vo tag is needed. The VRE are discovered automatically.

Configuring Advanced Monitoring

You can refer to the Infrastructure Viewer guide for the setting of the Infrastructure / VO(s). You should also edit another configuration file which is located {applicationFolder}/config/config.properties.

ONLY the default scope property MUST be changed.

Guide

Infrastructure Viewer

The interface of the tool is directly provided at Infrastructure Viewer. Currently, it is also the default tool at which the user is redirected by following the general URL of the Monitoring Portal. The report concerning this tool can be found here.

Live Monitoring

The Live Monitoring can be found at the Live Monitoring. A sample screenshot is shown below. Functionality is described here. This guide can also be found by following the "Help" link at the top right hand corner of the portlet itself.

Advanced Monitoring

The last tool developed for monitoring the gCube infrastructure is the Advanced Monitoring. Under special user privileges, it also allows to take corrective actions on resources. Detailed information are available in its technical guide.