Description
From: David Bouvet - COD-FR
Context: Follow-up of last escalation step by OCC and ROC not correctly done. When last step is reached, as stated in Operational Manual, ROC should normally discuss in private with its site, and then tell at next Weekly Operation meeting if the site should be suspend or not. Most of the time, at Weekly Operation meeting, ROC says that it has too discuss, and then no more news. The site stay in last escalation step during several weeks.
In Operational Manual: "If no progress is made, COD make sure that OMC is informed of the situation, and the site status is set to “suspended” in GOCDB by COD unless OMC say differently."
Proposed solution:As COD has rights to suspend a site, if ROC is not present at Weekly Operation meeting or has not send a mail about that problem, COD suspends the site. If ROC is present and asks for discussion with its site, OCC should put an action on ROC in the list of actions of the Weekly Operation meeting so it will be followed at next meeting. Answer or suspension by ROC should be done within the next 3 days: as acknowledgement, a mail should be sent to both OCC and COD mailing lists. In case not, the site is suspended by COD after these 3 days.
Some example of "long" last step:
* GGUS #40521: RU-Phys-SPbSU (1 month and a half)
o 25/09/2008: last escalation step
o 06/10/2008: raised at WLCG Ops meeting
o 06/11/2008: still in last step and not suspended
o 06/11/2008: Cyril L'Orphelin (COD-FR) send mail to Maite, Steve and Nick
o 06/11/2008: Maite sent mail to Russian ROC
o 06/11/2008: site suspended by Russian ROC
* GGUS #42015: ITPA-LCG2 (4 weeks)
o 24/10/2008: last escalation step
o 27/10/2008: raised at WLCG Ops meeting
o 03/11/2008: raised again at WLCG Ops meeting
o 07/11/2008: still in last step and not suspended
o 10/11/2008: raised again at WLCG Ops meeting
o 17/11/2008: still in last step and not suspended. ROC North is present at WLCG Ops meeting and will check with site.
o 18/11/2008: finally fixed by site
