Monitoring System

THIS SECTION OF GCUBE DOCUMENTATION IS CURRENTLY UNDER UPDATE.

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

• Hardware
• Services and Applications
• Collections and Auxiliary Resources

Hardware resources include gLite storage elements and computing nodes as well as gCube hosting nodes (containers), 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 put into gCube Information System (IS) which plays the role of the infrastructure's registry and supports the publishing, discovery and monitoring of all the parts that form the infrastructure. D4Science project offers the Monitoring Portal which is a set of tools which provide quick visualization of the multi-level organization of resources and the relationships among them.

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

Monitor Portal Installation

Once a tomcat instance as been installed the monitor portlet wars have to be putted into the $CATALINA_HOME/webbaps/.

This is the list of monitor portlets war containing the two applications below can be downloaded from here: [| monitoring application WAR(s)]

• Infrastructure Viewer
• Advanced Monitoring

Configuration

Each portlet have 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

Last but certainly not least of the tools provided for monitoring the d4science infrastructure is the Advanced Monitoring. It technical guide can be found here.