GRID monitoring with NetSaint

Transcription

1 GRID monitoring with NetSaint Roberto Barbera Paolo Lo Re Giuseppe Sava Gennaro Tortone Bologna - Datagrid WP7 meeting January 2002

2 Index NetSaint overview Role of NetSaint in GRID monitoring Interesting features of NetSaint for GRID monitoring Addons developed by INFNGRID WP7 group Conclusions A short demo on INFN implementation

3 NetSaint overview 1/2 NetSaint ( is a network monitoring tool developed by Ethan Galstad and designed to run under Linux. Some of its features include: simple plugins design that allows users to easily develop their own service checks monitoring of network services (FTP, HTTP, SSH, ) monitoring of host resources (CPU load, disk usage, ) ability to define network host (or device) hierarchy using parent host, allowing detection and distinction between host that are down and those that are unreachable distributed monitoring: a central NetSaint server obtains check results from one or more NetSaint distributed servers

4 NetSaint overview 2/2 contact notifications when service or host problems occour (via or user defined method) ability to define event handlers to be run during service or host events for proactive problem resolution logging mechanism and automatic log-file rotation optional plugins to send SNMP queries to host or network devices (router, switches, ); web interface for view current network status, notifications and problem history, logfile,

5 Role of NetSaint in GRID monitoring (from Requirement of network monitoring for the GRID - by Robin Tasker) Immediate network monitoring: a single view/access point of the available tools needs to be produced to allow a GRID user access to determine the "health" of the network. Such a snapshot of the network will likely include route information between specified end points; the characterisation of the network using, for example, pathchar; and the means of measuring throughput... The pre-testbed sites are encouraged to develop this concept to demonstrate capability and to allow WP7 to further refine the ideas based upon their experience and input from the users of these products. The idea is to use NetSaint: to view a snapshot of the GRID/Testbed resources status, services availability and network measurements to receive notifications on host or service faults to view graphs of resource monitoring results or network measurements

6 NetSaint is the official choice of INFN Testbed Technical Board for monitoring of INFN Testbed 1 Presently a NetSaint server is installed in Catania and checks approximately 120 services on 35 hosts (user: infn-tb - pass: guest)

7 Interesting features of NetSaint for GRID monitoring 1/3 notifications: it s possible to define a group of users (site admins) to notify when a service (or host) is in critical state event handlers: they are optional commands that are executed whenever a host or service state change occours; an obvious use of event handlers is the ability for NetSaint to proactively fix problems before anyone is notified; another use is to log service or host events to an external database; plugin architecture: NetSaint does not include any internal mechanism to check the status of services (or hosts); instead, NetSaint relies on external programs (plugins) to do all the monitoring activity; this feature allows users to easily develop their own service checks;

8 Interesting features of NetSaint for GRID monitoring 2/3 remote service checks - NRPEP addon: this addon is designed to provide a way for executing plugins on a remote host. The check_nrpe plugin runs on the NetSaint server and is used to send plugin execution requests to the NRPEP agent on the remote host. The nrpe agent will then run an appropriate plugin on the remote host and return the plugin output and return code to the check_nrpe plugin on the NetSaint server. The check_nrpe plugin then passes the remote plugin's output and return code back to NetSaint as if it were its own. All data in transit are in TripleDES encription format; passive checks : NetSaint can process service check results that are submitted by remote hosts through a daemon that runs on the NetSaint server and a client that is executed on remote hosts;

9 Interesting features of NetSaint for GRID monitoring 3/3 distributed monitoring - scalability: a possible usage of NetSaint is to install one NetSaint sensor (in barebone configuration) for each site to collect monitoring results from resources and one main NetSaint collector (in full configuration) to collect groups of monitoring results from sensors; this feature shows the functionality overlap that exists between NetSaint distributed architecture and GIIS/MDS GRID architecture; NetSaint collector site A host monitoring results NetSaint sensor NetSaint sensor monitoring results site B host

10 Addons developed by INFNGRID WP7 group graphs of resources (or network) monitoring results: we have developed a wrapper that parses the output of a plugin execution and insert monitoring values into a RRD (Round Robin Database - An user, from NetSaint web interface, can view daily, weekly, monthly or yearly graphs for a selected resource LDAP based plugins: another thread of development activities is the implementation of plugins that pull information from a MDS server, instead than from resources

11 Conclusions Work in progress: integration of NetSaint layout with MDS information providers of Datagrid WP7 (edg-pinger, edg-iperf, edg-udpmon); the idea is to pull from the MDS (Ftree) server all the network measurements pushed by WP7 information providers and enable graphs and notifications on these attributes; development of LDAP based plugins for all resource monitoring parameters (CPU load, disk usage, ); RPM packaging of NetSaint distribution with all configuration files and plugins for automatic installation by LCFG WP4 tool; possible integration of MapCenter as frontend of NetSaint to display various views of GRIDs with a link (for each host) to NetSaint status page for that host; Ethan Galstad, the author of the program, has been already contacted and he is willing to introduce any change in the NetSaint core logic our developments should need; We are open for any kind of collaboration