Choose timezone
Your profile timezone:
COD Pole1 - next 3 federations joined
→
Europe/Zurich
EVO (Virtual Meeting)
EVO
Virtual Meeting
Description
Connecting details:
- EVO Title: COD Pole1, Community: UNIVERSE
- EVO by phone call EVO Phone Bridge Telephone Numbers:
- RMS visioconference (backup solution)
-- Title : Pole1_phone_conf_2009_03
-- Date : 2009 April 22
-- Time : 09:00:00 local time
-- Length : 02:00:00
-- Call number :
---- IP : 193.48.95.82
---- ISDN : +33 (0)4 26 68 73 02 ---- TEL : +33 (0)4 26 68 73 02
-- Numeric identifier : 24435 (end by #)
-- PIN code : 1031 (end by #)
Meeting password:pole1
From: 9:00 (meeting starts at 8.30) CEST
To: 11:00 CEST
EVO gate click "Start" and browse the right link in the list ("COD Pole1").
Slovakia (UPJS, Kosice) +421 55 234 2420
Switzerland (CERN, Geneva) +41 22 76 71400
Italy (INFN, several cities) Phone numbers Enter '4000' to access the EVO bridge
Germany (DESY, Hamburg) +49 40 8998 1340
USA (BNL, Upton, NY) +1 631 344 6100
USA (Caltech, Pasadena, CA) +1 626 395 2112
United Kingdom (University of Manchester) +44 161 306 6802
Netherlands (Nikhef, Amsterdam) +31 20 7165293 Dial '2' at the prompt
Phone Bridge identifier:944120 password: 9112
Attendance: (IT) Tiziana Ferrari, Alessandro Paolini, (FR) Helene Cordier, Cyril l'Orphelin, (NE) Vera Hansper, Luuk Uljee, (CE) Malgorzata Krakowian, Marcin Radecki, (RU) Victor Edneral
1. Prioritization of CIC portal tasks.
Material is attached do the agenda, tasks are prioritized there.
CO: some of them already implemented (i.e. 2,5,10,11,13) but are not in production yet.
Discussion on item 14 "comparator tool"
Cyril: there's still a bug in it.
VH: keep it as an "indicator" tool, not take any action regarding that. Agreed by all
Agreed with Cyril that new dashboard features put into production will be announced.
Conclusion: Cyril needs an extra week to implement all requests foreseen for end of April. So around 9th of May portal should be ready. Marcin will organize a teleconference a week later (mid May) to assess the situation.
2. Outcome of watching tickets procedure for CCOD
Procedure announced, concerns about manual steps. One big issue is that operational tickets (generated from CIC portal) are missing the exact error message, this limits their usage if they are supposed to be used as a source for GGUS KB search.
HC: current SAM error message too verbose to be put into the ticket.
CO: even more, there are subtests like Replica Management for which you don't know which one failed.
MR: then it will be the responsibility of ROD, 1st line or site admin to put not only complete final solution but also the error message, problem origin.
Action 1 on Marcin to send out the procedure again, complete with info that pilot + 3 new federations need to be checked out and make sure people either agree or express their complaints about the procedure.
Action 2 on Marcin to check with Emir if nagios is crafted in a way it provides an error message instead of 200kB log in which one has to seek for an exact problem.
2a. CCOD tickets handling (item added by HC)
HC: untill all federations join there will be 2 handovers from COD: regular COD and CCOD, presence of CCOD is necessary.
New CCOD handover page in CIC portal: handover page
Action 3 on Helene to ask if AP,SWE can attend OM regularly, when they were CCOD leader a given week.
3. Knowledge sharing reassessed
Marcin presented the position in CE (see agenda)
TF: we currently exchange info through web pages, done by 1st line, ROD and sometimes by admins. Do we want to have it centrally deployed or regional?
MR: rather centrally, to have one place where one can go for support.
TF: how this relates to GGUS KB thing?
MR: GGUS is using regional wikis as a source. In case of web forum it is good to have it regional, but while need asking support may be difficult to go to regional instances. It will be good to have it central if taken into account exchange between experts from different regions.
TF: need to cross check with GGUS KB.
HC: Shu-Ting should help us with this cross-checking.
Action 4 on Marcin to summarize statement of CE and send out request for position on that topic to 7 federations. We need assessment of needs, possibilities to establish a web forum.
Action 5 on Shu-Ting (to be confirmed) how does this web forum topic fits into plans on GGUS's Knowledge Base.
4. Comments on recent version of ROD metrics
Topic skipped until we have new version of metrics.
5. Comments on tickets numbers and avg. response time
HC: the material will be attached to ROD metrics web page to make it more visible. Metrics are produced by GGUS scripts run monthly, but GGUS is about to provide an interface for generating such things.
HC: need for number of ticket assigned to CCOD SU -> thing to clarify with Cyril.
Conclusion: These metrics looks reasonable for CE and NE and will be something to come up regularly, in parallel with regular ROD metrics.
Action 6 on Helene to ask AP, SWE for comments on the numbers.
8. Feedback from CERN/IT/FR on joining the model (point moved earlier into agenda)
Alessandro: is there a way to switch off all OK alarms?
Cyril: There is a manual way, can add a button for a site to close all OK alarms for a site.
Alessandro: another question on masked alarms. there was a case that old alarm was masking some other and when closed the masking one the others which were masked disappeared.
Cyril: this is a feature implemented into last version.
Action 7 on Alessandro to send an e-mail to Helene to describe the case. Helene will then transform this case into savannah ticket and ask Vera and others for comments there to make sure that Alessandro's request is handled properly and we don't flip-flap with way of implementing things in dashboard.
Action 8 on Cyril (to be confirmed) to register request of a button for closing all OK alarms for a given site. France: nothing particular.
6. Emulation on CCOD role after COD-20
Proposal by Vera to make it an e-mail discussion. Accepted. HC: please focus on:
HC: need to prepare material for mid May.
TF: attendance to USAG needed as they are refining TPM shifts and one point was escalation of tickets especially software bugs, looks similar to CCOD duties.
Action 9 on Vera to kick off a discussion on CCOD role.
Action 10 on Helene, Vera, Tiziana ;-), Marcin to check last USAG group meeting minutes and attend the meeting if possible, represent the CCOD role there.
7. Date for UKI/DECH/RU/SEE to join new model
VH: probably useful to have a training session for them at COD-20. Best would be to have access to new version of dashboard.
HC: DECH requested access to new version of dashboard but it is not possible to operate 2 dashboards at the same time, we can think of giving them readonly access.
HC: need to have a date for new feds to join. Could it be 15.06. but then it means they will stop regular COD and the next day they will start ROD.
MR: may be risky, need to be sure that everything is working for them in advance.
VH: if the same people - not a problem. Victor: will be there in Helsinking with Gregory Spitz (?)
HC: Dashboard manual must be ready by that time, do we need to rearrange CCOD to help new federations?
MR: maybe not, we can do a teleconference to clear all issues as we did today.
Action 11 on Helene to send an e-mail to "last 4" federations asking for a possible date of joining and all materials attached, extending the "readiness" slides of question if this will be the same people doing regular COD and ROD or not.
1. Prioritization of CIC portal tasks.
Material is attached do the agenda, tasks are prioritized there.
CO: some of them already implemented (i.e. 2,5,10,11,13) but are not in production yet.
Discussion on item 14 "comparator tool"
Cyril: there's still a bug in it.
VH: keep it as an "indicator" tool, not take any action regarding that. Agreed by all
Agreed with Cyril that new dashboard features put into production will be announced.
Conclusion: Cyril needs an extra week to implement all requests foreseen for end of April. So around 9th of May portal should be ready. Marcin will organize a teleconference a week later (mid May) to assess the situation.
2. Outcome of watching tickets procedure for CCOD
Procedure announced, concerns about manual steps. One big issue is that operational tickets (generated from CIC portal) are missing the exact error message, this limits their usage if they are supposed to be used as a source for GGUS KB search.
HC: current SAM error message too verbose to be put into the ticket.
CO: even more, there are subtests like Replica Management for which you don't know which one failed.
MR: then it will be the responsibility of ROD, 1st line or site admin to put not only complete final solution but also the error message, problem origin.
Action 1 on Marcin to send out the procedure again, complete with info that pilot + 3 new federations need to be checked out and make sure people either agree or express their complaints about the procedure.
Action 2 on Marcin to check with Emir if nagios is crafted in a way it provides an error message instead of 200kB log in which one has to seek for an exact problem.
2a. CCOD tickets handling (item added by HC)
HC: untill all federations join there will be 2 handovers from COD: regular COD and CCOD, presence of CCOD is necessary.
New CCOD handover page in CIC portal: handover page
Action 3 on Helene to ask if AP,SWE can attend OM regularly, when they were CCOD leader a given week.
3. Knowledge sharing reassessed
Marcin presented the position in CE (see agenda)
TF: we currently exchange info through web pages, done by 1st line, ROD and sometimes by admins. Do we want to have it centrally deployed or regional?
MR: rather centrally, to have one place where one can go for support.
TF: how this relates to GGUS KB thing?
MR: GGUS is using regional wikis as a source. In case of web forum it is good to have it regional, but while need asking support may be difficult to go to regional instances. It will be good to have it central if taken into account exchange between experts from different regions.
TF: need to cross check with GGUS KB.
HC: Shu-Ting should help us with this cross-checking.
Action 4 on Marcin to summarize statement of CE and send out request for position on that topic to 7 federations. We need assessment of needs, possibilities to establish a web forum.
Action 5 on Shu-Ting (to be confirmed) how does this web forum topic fits into plans on GGUS's Knowledge Base.
4. Comments on recent version of ROD metrics
Topic skipped until we have new version of metrics.
5. Comments on tickets numbers and avg. response time
HC: the material will be attached to ROD metrics web page to make it more visible. Metrics are produced by GGUS scripts run monthly, but GGUS is about to provide an interface for generating such things.
HC: need for number of ticket assigned to CCOD SU -> thing to clarify with Cyril.
Conclusion: These metrics looks reasonable for CE and NE and will be something to come up regularly, in parallel with regular ROD metrics.
Action 6 on Helene to ask AP, SWE for comments on the numbers.
8. Feedback from CERN/IT/FR on joining the model (point moved earlier into agenda)
Alessandro: is there a way to switch off all OK alarms?
Cyril: There is a manual way, can add a button for a site to close all OK alarms for a site.
Alessandro: another question on masked alarms. there was a case that old alarm was masking some other and when closed the masking one the others which were masked disappeared.
Cyril: this is a feature implemented into last version.
Action 7 on Alessandro to send an e-mail to Helene to describe the case. Helene will then transform this case into savannah ticket and ask Vera and others for comments there to make sure that Alessandro's request is handled properly and we don't flip-flap with way of implementing things in dashboard.
Action 8 on Cyril (to be confirmed) to register request of a button for closing all OK alarms for a given site. France: nothing particular.
6. Emulation on CCOD role after COD-20
Proposal by Vera to make it an e-mail discussion. Accepted. HC: please focus on:
- CCOD duties list
- how much workload will be needed
- how to handle rota when all feds are in
- what can/must be done centrally, what can/must be distributed
HC: need to prepare material for mid May.
TF: attendance to USAG needed as they are refining TPM shifts and one point was escalation of tickets especially software bugs, looks similar to CCOD duties.
Action 9 on Vera to kick off a discussion on CCOD role.
Action 10 on Helene, Vera, Tiziana ;-), Marcin to check last USAG group meeting minutes and attend the meeting if possible, represent the CCOD role there.
7. Date for UKI/DECH/RU/SEE to join new model
VH: probably useful to have a training session for them at COD-20. Best would be to have access to new version of dashboard.
HC: DECH requested access to new version of dashboard but it is not possible to operate 2 dashboards at the same time, we can think of giving them readonly access.
HC: need to have a date for new feds to join. Could it be 15.06. but then it means they will stop regular COD and the next day they will start ROD.
MR: may be risky, need to be sure that everything is working for them in advance.
VH: if the same people - not a problem. Victor: will be there in Helsinking with Gregory Spitz (?)
HC: Dashboard manual must be ready by that time, do we need to rearrange CCOD to help new federations?
MR: maybe not, we can do a teleconference to clear all issues as we did today.
Action 11 on Helene to send an e-mail to "last 4" federations asking for a possible date of joining and all materials attached, extending the "readiness" slides of question if this will be the same people doing regular COD and ROD or not.
There are minutes attached to this event.
Show them.
