EGEE-III INFSO-RI Enabling Grids for E-sciencE EGEE and gLite are registered trademarks LHCOPN Ops WG Act 4 – Conclusion Guillaume Cessieux (FR IN2P3-CC, EGEE SA2) CERN

Enabling Grids for E-sciencE LHCOPN Ops meeting 4, CERN, GCX Twiki not designed to be a database –But previously really convenient  Lot of work to switch – currently kept – Process to review information to be proposed  Assign informational tickets to sites with all links into Responsibilities and validations –Long term  Switch to a real constrained database  Implement proper AuthN and AuthZ –Template for backup tests to be more constrained FAQ –Primary link down: Connectivity vs performance - Unclear –Precise how and where updating all required information on twiki 2

Enabling Grids for E-sciencE LHCOPN Ops meeting 4, CERN, GCX Webcalendar –Lot of event but only past – should not be so disturbing  Potential wish list Timezone handling (Filter events by sites) Hyperlinks on processes’ picture –Very good idea, sadly not technically currently achievable  Long term… 3

Enabling Grids for E-sciencE LHCOPN Ops meeting 4, CERN, GCX Around GGUS –Ask them for possible automatic twiki update on change management  Could not CMDB be only a particular view of change’s tickets? We have no longer change tickets – tick a box to request info stored Avoid duplicating information Might require migrating CMDB somewhere else –Downtimes of TTS to be handled with informational tickets  No notification to sites only for the record –Keep ENOC/DANTE notification fields –Ask details to TW-ASGC for their requested monthly report –Notifications to be tested every 3 months  Also access to information repositories: twiki, monitoring information etc. –Timezone: Enable submitting in the timezone you want  Long term: User based timezone preference for everything –Level of support to be discussed with them to arbitrate our requests  Separate bugs resolutions from enhancement requests –Could we ensure maintenance delay windows are respected? –New possible status “escalated” needed on tickets 4

Enabling Grids for E-sciencE LHCOPN Ops meeting 4, CERN, GCX T1-T1 issues –Put and document responsibilities on T1-T1 links  Even arbitral to start What is a LHCOPN links –Part of “network specifically put in place to allow distribution of data from T0/T1” – dedicated links only –Each sites to monitor its flows to ensure LHCOPN is not bypassed or misused 5

Enabling Grids for E-sciencE LHCOPN Ops meeting 4, CERN, GCX Security –Existing security groups to be involved  What are traffic patterns to be allowed on the LHCOPN  How to handle security events - Is our model fine and enough? –If filtering to be set up better before LHC start-up...  Firewalling complex (and expensive) Unexpected events –Any event with an impact on the service should be reported and followed  1 ticket per issue not per event  Having complicated links is not an excuse :) 6

Enabling Grids for E-sciencE LHCOPN Ops meeting 4, CERN, GCX Create fake event if no events to test ops processes –But not affecting services –“Unexpected backup tests” Process to put links in production to be shortly documented –Best practice only, not rules enforced –1 week monitoring before claiming production quality seems reasonable 7

Enabling Grids for E-sciencE LHCOPN Ops meeting 4, CERN, GCX KPIs (1/2) KPIs for operation, not infrastructure quality Two kind of KPIs 1.We want to measure way processes are implemented  Pure ops KPI  Beware processes are not only tickets 2.And to correlate what we handle with what really occurs  Correlated KPI  Need data from monitoring View per sites needed –Then where to account T1-T1 things? Problems –Tools not constrained enough to provide really meaningful indicators –We only measure what we see... 8

Enabling Grids for E-sciencE LHCOPN Ops meeting 4, CERN, GCX KPIs (2/2) 1.Pure ops KPIs –Problems durations –Number of reported problems lasting more than one week –Are maintenance delays respected 2.Correlated KPIs –Provide a mapping of link status and tickets on a timeline  Per linkID  Need monitoring information available in a exploitable format Beginning with low granularity –No in-depth analysis –Will be improved in the future with more details 9

Enabling Grids for E-sciencE LHCOPN Ops meeting 4, CERN, GCX Periodical ops phoneconf –Review infrastructure and ops behaviour  Goal: To improve ops and infrastructure –Focus on issues –CH-CERN to support that –15:30 UTC seems most convenient  Site unable to attend welcome to submit through –TBD during next LHCOPN meeting Enforcement of backup test –Now ideally before service challenge in June... –Backup link of UK-T1-RAL should hopefully appear before –3 months left before stressing the infrastructure 10

Enabling Grids for E-sciencE LHCOPN Ops meeting 4, CERN, GCX Ops WG meetings –Why not more involvement from sites?  Is this only travelling issues?  TDB at next LHCOPN meeting –What about doing them before LHCOPN meetings  Also mixing f2f and phoneconf meetings DEISA – PRACE etc. –Investigate collaboration LHCOPN meeting –No possible convenient location for everyone :( 11

Enabling Grids for E-sciencE LHCOPN Ops meeting 4, CERN, GCX Conclusion Lot of things discussed –Lot of things put in “long term requirements”  Maybe we miss some short term improvements Ops should be ready for service challenge in June! See you in Amsterdam! 12