C-COD is a team provided at a global layer for coordination of all RODs and overall coordination of COD services in the long run.
Who?
C-COD will be composed of
- ROD representatives (at least one person from each ROD)
- COD head
- Observers
- e.g. regular COD people willing to get familiar with new model, experts
List of C-COD members
- COD head : Helene Cordier
- AP ROC : Shu-Ting Liao, Jhen-Wei Huang
- CE ROC : Malgorzata Krakowian, Marcin Radecki
- NE ROC : Vera Hansper, Lucas Uljee
- SWE ROC : Kai Neuffer, Marc Rodriguez
- SEE ROC : Ioannis Liabotis (OPM)
- IT ROC : Tiziana Ferrari
C-COD Leader
- C-COD coordinator
- one person from one of R-CODs for a week shift
C-COD leader on Duty rotation
- 5-9.01.2009 CE ROC
- 12-16.01.2009 NE ROC
- 19-23.01.2009 AP ROC
- 26-30.01.2009 SWE ROC
- 2-6.02.2009 CE ROC
- 9-13.02.2009 CE ROC
- 16-20.02.2009 AP ROC
- 23-27.02.2009 SWE ROC
- 2-6.03.2009 NE ROC
- 9-13.03.2009 NE ROC
- 16-20.03.2009 AP ROC
- 23-27.03.2009 SWE ROC
- 30.03-3.04.2009 CE ROC
- 6-10.04.2009 NE ROC
- 13-17.04.2009 AP ROC
- 20-24.04.2009 SWE ROC
- 27.04-1.05.2009 CE ROC
- 4-08.05.2009 NE ROC
- 11-15.05.2009 AP ROC
- 18-22.05.2009 SWE ROC
- 25-29.05.2009 CE ROC
- 1-05.06.2009 NE ROC
- 8-12.06.2009 AP ROC
- 15-19.06.2009 SWE ROC
*end of c-COD * start of GMT
- 15-22.06.2009 SWE ROC
- 22-26.06.2009 CE ROC
- 29.06-03.07.2009 NE ROC
- 6-10.07.2009 FR ROC
- 13-17.07.2009 IT ROC
- 20-24.07.2009 CE ROC
- 27-31.07.2009 NE ROC
- 03-07.08.2009 IT ROC
- 10-14.08.2009 FR ROC
- 24-28.08.2009 CE ROC
- 31.08.2009 - 04.09.2009 NE ROC
- 07-11.09.2009 FR ROC
- 14-18.09.2009 IT ROC
Duties
C-COD team
- Looks into their dashboard for escalated tickets and alarms
- Deal with GGUS tickets assigned to the COD SU
- Watch Operations Meeting actions list for COD assigned actions and take part in Operations Meetings raising issues and reporting progress if needed
- Communicate with all ROD or a given ROD
- Look into global ROD metrics
- Follow-up core matters with the ROD community
- Make recommendations to the knowledge sharing organization (e.g. structure), ensuring convergence of regional contributions
- Upgrade the Operations Procedure Manual in conjunction with the ROD community
- Put a site in SD in agreement with its corresponding ROD for security matters or for critical problems for the operation of infrastructure
- Create tickets to ROD(s) for core or urgent matters
C-COD leader
- Make sure C-COD operations are progressing
- Send a summary (handover) to the C-COD mailing list at the end of the week
- Rises issues at the Operations Meeting and represents C-COD
- Send an email to Operations Meeting people with issues to be raised before the meeting
- Send outcome of operations meetings back to C-COD
- Supervise the work of ROD, look at metrics
Communication
Sites
C-COD is communicating with sites through GGUS tickets
RODs
C-COD can communicate with RODs in two ways. First one is ROD representative in C-COD the second one is an email to ROD mailing list.
RODs mail contact list
Operations Meeting
C-COD send an email to Maite, Nick and Steve to rise an issue at Operations Meetings.
- Maite Barroso Lopez <Maria.Barroso.Lopez@cern.ch>
- Nicholas Thackray <Nicholas.Thackray@cern.ch>
- Steve Traylen <steve.traylen@cern.ch>
ROC Managers
Proper ROD representative in C-COD is responsible to contact with own ROC manager.
C-COD
For internal communication C-COD should use own mailing list:
project-eu-egee-sa1-c-cod-followup@cernNOSPAMPLEASE.ch
How to become a C-COD member
- have a valid certificate
- read Operations Manual
- request 'C-COD staff' role in GOC DB
- sign up to the C-COD mailing list (e.g. send mail to c-cod mailing list to be add)
- choose proper preferences in regional dashboard
Links and documents