Tier3 monitoring. Initial issues.

1. Tier3 monitoring. Initial issues. Danila Oleynik. Artem Petrosyan. JINR.

2. What is Tier3 sites. Tier 3 site – is a computing facility, which using some local groups for their analysis work. Working definition • “Non pledged resources” • “Analysis facilities” at Your University/Institute/... Specialty: • Final analysis vs simulation and reconstruction • Local control vs ATLAS central control • Operation load more on local resources (i.e. people) than on the central team (i.e. other people)

3. Types of Tier 3’s • Tier 3 gs (grid services) • Same services as Tier2 • Tier 3 w (workstation) • Interactive workstation with Atlas Software • No batch system • Can submit grid jobs • Data retrieved using client tools (dq2-get)

4. Tier 3G (most common Tier 3) • Interactive nodes • Can submit grid jobs • Batch system • Atlas code available • Client tools used for fetch data (dq2-ls, dq2-get) • Storage can be one of two types: • Located on the worker nodes • Located on dedicated file servers

5. T3g Software Services • Generic Services (services which are used to maintain the cluster) • LDAP is a database, which, in this case, is used to manage the users on the cluster. • Ganglia infrastructure monitoring system. • Web server. • NFS (network file system). • Job submission services • Proof (most common) • Arcond (More exotic) • Distributed Storage Service • XrootD

6. Monitoring issues for Tier3 • Local monitoring • Infrastructure monitoring • Monitoring of Job submission system • Monitoring of Data management (storage) system • Requirements: easy installation and support • Global monitoring (monitoring of all Tier3 activities) • We still have no full picture about which data should be represented on this layer 

7. Local Tier3 Monitoring ‘Ganglia’ and ‘Nagios’ – is a most recommend system for infrastructure monitoring (a lot of Tier3 sites in US already use Ganglia). This system provides wide range of monitoring parameters, significant advantage of this systems that they boiled by plug-in technology and for monitoring specific parameters only sensors needed to be developed. Most of Tier3 sites will use Proof as job management system and xRootd as data management system. This systems has initial interfaces for thus monitoring. Proof and xRootd can be monitored by Monalisa monitoring system, but we collect different views about Monalisa. Monalisa can be very heavy solution for small sites, but we still in investigation.

8. Global Tier3 monitoring • Due to we have no information about data that should be presented in global monitoring from tier3 sites and data flow, we can talk only about initial concepts of this service. • This service should based on agent model. Each agent works with local monitoring system, collect aggregate needful data and send this data to some central monitoring service. In depends from dataflow different technology can be implemented (REST - WebServices, ActiveMQ). Central service should provide possibility to collect and store this information from all sites. Provide different interfaces to data, as human oriented so machine oriented.

9. Interfaces for Monitoring Tier3 system. • Local monitoring system. Ganglia and Nagios provide own web interfaces. All new parameters which can be collected by these systems will be presented through their interfaces. • Global monitoring system. For presentation of monitored data on global level we offer to use web based technology. In development of this application we are ready to use Ajax technology (Jquery) and Jango as data model layer. Integration with other application can be done by using REST protocol.