Name: Operations Management Board
Start: 2010-12-21T10:30:00+01:00
End: 2010-12-21T13:20:00+01:00
Location: No location set

Operations Management Board

Tuesday, 21 December 2010 - 10:30

Monday, 20 December 2010
Tuesday, 21 December 2010
10:30 Introduction - Tiziana Ferrari (EGI.EU)
Introduction
- Tiziana Ferrari (EGI.EU)
10:30 - 10:40
- status of EGI operations wiki - Deliverable to come soon: D4.1 Operations Architecture - next OMB/OTAG: start 24 Jan 11:00, end 25 Tue 17:30 (face to face meeting in Amsterdam) - OMB calendar 2011: . Tue 15 Feb (phone), Tue 22 Mar (phone), Thu 14 Apr (face-to-face, colocated with EGI User Forum - Vilnius, day is now tentative and depends on room availability)
10:40 Update from last OMB: terminology and OLA - Tiziana Ferrari (EGI.EU) Dimitris Zilaskos (Technical staff)
Update from last OMB: terminology and OLA
- Tiziana Ferrari (EGI.EU)
- Dimitris Zilaskos (Technical staff)
10:40 - 10:50
- New Nagios terminology is approved: CRITICAL/AVAILABILITY/OPERATIONS PROBE - Site OLA
10:50 DTEAM: mandatory support: (APPROVED). DTEAM Migration Status. - Tiziana Ferrari (EGI.EU) Dimitris Zilaskos (Technical staff)
DTEAM: mandatory support: (APPROVED). DTEAM Migration Status.
- Tiziana Ferrari (EGI.EU)
- Dimitris Zilaskos (Technical staff)
10:50 - 10:55
After the Nov OMB, he Nordic cuntries (Denmark, Finland, Norway and Sweden)have been consulted and after discussion they agree to the mandatory support of DTEAM by production sites. The OMB APPROVES the MANDATORY SUPPORT of DTEAM by all production EGI NGIs. Proposal: Use cases, usage and status will be reviewed in 12 months (Dec 2011).
10:55 EGI Operations requirement gathering process - Tiziana Ferrari (EGI.EU)
EGI Operations requirement gathering process
- Tiziana Ferrari (EGI.EU)
10:55 - 11:25
Information on requirements gathering procedures, timeline for requirements gathering for EMI 2.0, survey of requirements for EMI 1.0
11:25 Managing VO name changes - Goncalo Borges (LIP)
Managing VO name changes
- Goncalo Borges (LIP)
11:25 - 11:40
Discussion points: 1. a requirement to EMI enabling data movement between VOs (either at user level or at any other level); 2. the establishment of an operation procedure for VO end-of-support at the site level and at the infrastructure level.
11:40 Single EGI monitoring VO - Emir Imamagic (SRCE)
Single EGI monitoring VO
- Emir Imamagic (SRCE)
11:40 - 12:00
12:00 GGUS SU restructuring: update on status - Torsten Antoni (Karlsruhe Institute of Technology)
GGUS SU restructuring: update on status
- Torsten Antoni (Karlsruhe Institute of Technology)
12:00 - 12:15
12:15 Staged Rollout Metrics - Goncalo Borges (LIP)
Staged Rollout Metrics
- Goncalo Borges (LIP)
12:15 - 12:35
12:35 AOB - Tiziana Ferrari (EGI.EU) Vera Hansper (CSC)
AOB
- Tiziana Ferrari (EGI.EU)
- Vera Hansper (CSC)
12:35 - 12:45
- requests for training at EGI User Forum - EGI User Forum call for abstracts (https://www.egi.eu/indico/conferenceCFA.py?confId=207), deadline 24 Dec 2010: 1. Management and/or exploitation of emerging computing technologies (desktops, virtualisation, clouds) 2. Integration, sharing and exploitation of national and international e-Infrastructure 3. Delivery of operational e-Infrastructure services to its users - APEL Active MQ migration. REMINDER: upgrade requested by 31 Jan 2011!! 4. Change to org.apel.APEL-pub: 16/12/2010 > COD team received from IT NGI ROD request to change the threshold for > switching org.apel.APEL-pub results from warning to critical state in > NAGIOS. > > Currently RODs have to wait 30 days in warning status before it is > flagged as critical. > This affects the possibility to have alarms into operational dashboard > because the dashboard itself raises alarms only for critical status. > > Hence, suggestion would be to modify the old threshold decreasing > it to 7 days.