The EGI Operations Portal

Cyril L'Orphelin – CNRS/CCIN2P3

GDB Meeting

June 9th 20101

EGI-InSPIRE – GDB Meeting Cyril L’Orphelin

2

Plan

- History

- Overview of the portal

- Objectives of the coming year

- Presentation of the features interesting for WLCG

EGI-InSPIRE – GDB Meeting Cyril L’Orphelin

3

History

• The Operations Portal has been developed during EGEE I-II and III at IN2P3-CC in SA1 activity

• The historical portal namely “CIC Portal”– http://cic.gridops.org

• This portal is migrated step by step to Operations Portal– https://operations-portal.in2p3.fr

• The dashboard is the first module we have migrated .

• Since early May we are involved in the JRA1 activity of EGI.

EGI-InSPIRE – GDB Meeting Cyril L’Orphelin

4

The operations portal proposes :

• Tools for operations

• Tools for communication

• Tools to manage VO informations

For different actors:

• Site administrators

• Regional Managers

• Vo Managers

• End Users

OperationsPortal

Communication tools

REGIONAL CENTER

SITE

USER

OPERATOR

Monitoring tools

VO info

User Support

Site info

VO Managers

Overview

EGI-InSPIRE – GDB Meeting Cyril L’Orphelin

5

Overview: Architecture

EGI-InSPIRE – GDB Meeting Cyril L’Orphelin

6

Objectives

• Our objectives in the coming year

– Migrate all features under Symfony in the new Operations Portal and follow the previous architecture

– Improve the regional package– Integrate new information resources– Propose programmatic interfaces (xml , json )

EGI-InSPIRE – GDB Meeting Cyril L’Orphelin

7

The dashboard for Operations

The dashboard is a tool designed to follow and track problems on sites.

In summary you track problem with the different results from Monitoring Tools ( Nagios , Gstat) and you can open and update trouble ticket in GGUS directly in the dashboard. We use also GOC DB and BDII to consolidate monitoring informations with downtime information and dynamic statuses .

This tool is currently used by Regional (NGI) and Central Operators .

Next step : Extend the tools to other VO than OPS with :

• the possibility to open tickets with the VO specific tests coming from SAM

• the use of results coming from Nagios boxes dedicated to specific VOs

EGI-InSPIRE – GDB Meeting Cyril L’Orphelin

8

VO ID CARD new generation

New “feel and look” of the features revisited for EGI scope– Registration of a new VO– VO Update

• New work-flows defined by NA4/SA1– Yearly renewal – Deletion

• All VO Information, metrics available in standard format– Distribution of resources / VO– Global Information / VO

• Available on HTML , RSS , XML– Statistics and metrics

The development is not finished . We are still waiting the validation by the project .

If you have specific needs or ideas to improve this feature , you are welcome !

• Release Date : 3 weeks after the validation by the project

EGI-InSPIRE – GDB Meeting Cyril L’Orphelin

9

Broadcast tool new generation

• New “feel and look” but same principle :– Select different targets (VO Managers , Site managers , ngi

managers...)– Send a email to all targets

• What's new :

– Define your own list of targets

– Define your own predefined categories ( template + list )

– Add an attachment to the mail

- We can add new targets before starting to put it in production if you have specific needs , don’t hesitate !

- Release date : current July

EGI-InSPIRE – GDB Meeting Cyril L’Orphelin

10

Downtimes notifications

Goal : delivering emails about (un)scheduled downtimes to the concerned people by using different information:– Downtimes (GOC DB)– VO information (CIC DB)– Publication data (BDII)

• This feature has encountered some troubles the last months (Oracle problem) . The system is stable now and we want to extend this feature in the future with programmatic interfaces (for external applications).

• Release Date : End of the year

EGI-InSPIRE – GDB Meeting Cyril L’Orphelin

11

Downtime Overview

We provide a graphical overview of downtimes with a customized selection of sites and time scale .

We want to extend this feature with an overview of downtimes which are impacting the selected Vos.

EGI-InSPIRE – GDB Meeting Cyril L’Orphelin

12

Resources Distribution

The goal is to propose synthetic view of the geographical distribution of the resources and services offered to a VO, by crossing information from :

– GOC DB (sites , NGI , ROC infos)

– BDII (services , CPU info , Storage Info)

• Next steps :– improve ergonomics . – propose programmatic interfaces– Propose a summary at each level (site / NGI / EGI)

• Release Date : End of the year – Under study

EGI-InSPIRE – GDB Meeting Cyril L’Orphelin

13

Regionalisation

Goal : distribute the different features / modules present into the Central Operations Portal into a regional package for NGIs to cope with NGI needs.

- Release of the first production package with the dashboard module: June 8 th

- Package and documentation distributed via SVN

- Next steps : Upgrade this package to add the other features integrated step by step into the Central Instance.

EGI-InSPIRE – GDB Meeting Cyril L’Orphelin

14

New information resources

• With the use of the Web Service Lavoisier it is easy to exploit information from a new data source.

• With the use of plug-ins we ensure the flexibility and the robustness of the application.

• New potential data sources should be :

– New monitoring system

– Evolution of existing monitoring system ( Nagios Boxes for specific VO tests)

– New middleware components

– External applications

EGI-InSPIRE – GDB Meeting Cyril L’Orphelin

15

Programmatic Interfaces

- Currently the information is accessible via :- Html interfaces- some rss feeds for specifics services (notifications)

- We want to generalize and standardized the access to information :

- Via Html interfaces- Via rss - Via xml - Via json

- The aim is to propose a panel of services usable by external applications (like VO dashboard)

EGI-InSPIRE – GDB Meeting Cyril L’Orphelin

16

The link with the LHC community

• We are providing services for VO , and sites representatives, end users …

• We will continue to improve these services and we need feedback to cope with the needs of these actors.

• The architecture of the portal has been built in order to extend the number of data sources, and to propose a standard access to information.

• LHC community have some specific needs and certainly also specific information providers .

• We are ready to provide either user friendly interfaces to access such information (eventually consolidated with other information) either APIs for external applications.