INFSO-RI Enabling Grids for E-sciencE 1 Downtime Process Author : Osman AIDEL Hélène Cordier

INFSO-RI Enabling Grids for E-sciencE 2 Current downtime process - 2 actions are needed : publication in the GOC db + broadcast from CIC Portal - there are still an issue to define the relevant broadcast targets and not to forget some political instances - The Broadcast Tool only informs the political instances - The broadcast outcome through only is not enough: notification cannot trigger any automatic actions.

INFSO-RI Enabling Grids for E-sciencE 3 CIC Portal Proposal 1- One action only to declare and broadcast downtimes: the publication downtime in the GOC interface triggers a notification system 2 – the broadcast targets definition is systematized : Mandatory s are derived from Nick's document 3 – Any user can subscribe to one or several types of downtime publication 4 - Two notification methods are enabled : customized subscription to and RSS flow

Enabling Grids for E-sciencE INFSO-RI Downtime notification service CIC Application GOC Portal: Downtime Interface [Nick's template] GOC Portal: Downtime Interface [Nick's template] Mandatory RSS Flow to the political Instances (Nick's document) SD description Any users Manage r New Downtime Process

INFSO-RI Enabling Grids for E-sciencE 5 Implementation 1 - Data gathering from the BDII ( nodes / services / VOs ) 2 - Definition of the new GOC interface 3 - Definition of the interface between the CIC and GOC Portal 4 – Implementation of a management component ( Log + rules ) 5 – Integration of a broadcast component

Enabling Grids for E-sciencE INFSO-RI GOC Portal: Downtime Interface [Nick's template] GOC Portal: Downtime Interface [Nick's template] SD description Manage r GOC db BDII Data Collector CIC db Technical schema CIC Application

INFSO-RI Enabling Grids for E-sciencE 7 Implementation 1 - Data gathering from the BDII ( nodes / services / VOs ) 2 - Definition of the new GOC interface 3 - Definition of the interface between the CIC and GOC Portal 4 – Implementation of a management component ( Log + rules ) 5 – Integration of a broadcast component

Enabling Grids for E-sciencE INFSO-RI GOC Portal: Downtime Interface [Nick's template] GOC Portal: Downtime Interface [Nick's template] SD description Manage r GOC db BDII Data Collector CIC db Technical schema CIC Application

INFSO-RI Enabling Grids for E-sciencE 9 Implementation 1 - Data gathering from the BDII ( nodes / services / VOs ) 2 - Definition of the new GOC interface 3 - Definition of the interface between the CIC and GOC Portal 4 – Implementation of a management component ( Log + rules ) 5 – Integration of a broadcast component

Enabling Grids for E-sciencE INFSO-RI GOC Portal: Downtime Interface [Nick's template] GOC Portal: Downtime Interface [Nick's template] SD description Manage r GOC db BDII Data Collector CIC db Downtime Listener Technical schema

INFSO-RI Enabling Grids for E-sciencE 11 Implementation 1 - Data gathering from the BDII ( nodes / services / VOs ) 2 - Definition of the new GOC interface 3 - Definition of the interface between the CIC and GOC Portal 4 – Implementation of a management component ( Log + rules ) 5 – Integration of a broadcast component

Enabling Grids for E-sciencE INFSO-RI GOC Portal: Downtime Interface [Nick's template] GOC Portal: Downtime Interface [Nick's template] SD description Manage r GOC db BDII Data Collector CIC db Downtime Listener Supervisor Rules Technical schema Redo log CIC Application CIC db User subscription

INFSO-RI Enabling Grids for E-sciencE 13 Implementation 1 - Data gathering from the BDII ( nodes / services / VOs ) 2 - Definition of the new GOC interface 3 - Definition of the interface between the CIC and GOC Portal 4 – Implementation of a management component ( Log + rules ) 5 – Integration of a broadcast component

Enabling Grids for E-sciencE INFSO-RI GOC Portal: Downtime Interface [Nick's template] GOC Portal: Downtime Interface [Nick's template] SD description Manage r GOC db BDII Data Collector CIC db Downtime Listener Supervisor Rules Broadcast SenderRSS Sender Technical schema Redo log CIC Application CIC db

Enabling Grids for E-sciencE INFSO-RI GOC Portal: Downtime Interface [Nick's template] SD description Manage r GOC db BDII Data Collector CIC db Downtime Listener Supervisor Rules Broadcast SenderRSS Sender Technical schema Redo log CIC db Step 1Step 2 Step 3 Step 4 Step 5

Enabling Grids for E-sciencE INFSO-RI Questions ?

INFSO-RI Enabling Grids for E-sciencE 17 Description - Users will announce their downtimes via the GOC interface - the GOC will notify the CIC application throught a XML flow [ proposal RSS flow]. - the CIC application will search the political instances impacted and users that are subscribed to “the downtime notification” service. - the CIC application will broadcast the announcement to people found in the preceding step :. The political instance will be mandatory informed by as described in the nick's document.. users that are subscribed to the downtime notification” service will be notified either or RSS flow

INFSO-RI Enabling Grids for E-sciencE 18 Downtime interface to implement the interface, the GOC and CIC will need to discuss together. At current, the CIC is defining the fields which will be necessary for the global working. To conceive it, we will base on the Nick and Helene 's document.

INFSO-RI Enabling Grids for E-sciencE 19 Downtime Notification Service This service will be implemented so that any users can be notified about downtimes. The benefit of this feature is users will be able to filter downtimes in function of a region/site/node/service or VO. For instance, if a user wants to be informed for all downtimes concerning a specific VO, he will just need to subscribe to the Downtime Notification Service defining the appropriated scope.. Scope will be setting up on the CIC portal and will be composed on 4 fields : scope level, scope name, service and VO. By default, each field will be configured to ALL. If we come back to our example, the scope value would be : scopelevel =ALL {region,site,node,ALL} and scopename=ALL and service=ALL and VO =atlas Thanks to these fields, users will receive only the downtimes they wants.

INFSO-RI Enabling Grids for E-sciencE 20 Downtime Notification Service In addition, we will implement 2 notification methods : and RSS Flow. The first one will generally be used by the political people and the second one rather by the technical user. Notification To subscribe to the notification, users will have to record themselves on the CIC Portal thanks to a web interface, which will allow to define the right scope and user . RSS Notification The RSS Flow is a way that will be implemented for technical users as site administrators. The main idea is to enable to administrators triggering any actions after a RSS notification. For example, at the IN2P3-CC, our FTS administrator would like to manage the FTS configuration in function of SE downtime announced in order to close the involved channels.

INFSO-RI Enabling Grids for E-sciencE 21 Downtime Notification Service RSS Notification To subscribe to this service, users will just need to record in their RSS client the appropriated url. Indeed, m any RSS flows will be proposed on the CIC Portal. There will be a RSS flow for each scope. Of course, a web interface will be available so that helping users to find the right url. Below, you find the pattern of the url: =ALL {region,site,node,ALL} and scopename=ALL and service=ALL and VO =atlas

INFSO-RI Enabling Grids for E-sciencE 22 Conclusion - Broadcast targets definition is systematized - Notification by subscription - Possibility to filter the downtime broadcast - 2 Notification methods : and RSS Flow