28-R-15 (CERN conferencing service (joining details below))
CERN conferencing service (joining details below)
email@example.com Weekly EGEE infrastructure coordination meeting.
We discuss the weekly running of the production grid infrastructure based on weekly reports from the attendees. The reported issues are discussed, assigned to the relevant teams, followed up and escalated when needed. The meeting is also the forum for the sites to get a summary of the weekly WLCG activities and plans
EGEE operations team
EGEE ROC managers
site representatives (optional)
To dial in to the conference:
a. Dial +41227676000
b. Enter access code 0148141
AND click HERE (Please specify your name & affiliation in the web-interface)
From Central Europe to Northern Europe
RODs are highly unresponsive to C-COD request. Even after third reminder there was no reply.
Unresponsive RODs: Canada, Cern, Asia Pacific CERN apologises for unresponsiveness: Reported tickets are now being handed
two tickets not handled:
CA-SCINET-T2 - GGUS 54764 Expiration date 2010-01-21
CA-ALBERTA-WESTGRID-T2 - GGUS 54707 Expiration date 2010-01-19
Update received from Isabel Campos (MPI Task Force) here summarised.
Last week (4th Feb) over the 2/3 limit of MPI sites passing the SAM tests. Comment:
Today the situation is confirmed (67 out of 94 CEs passing the SAM tests)
Isabel suggested to wait another week to get over the 2/3 in a more stable
way, and have some graphics about the historical data from SAM to show the
stability of the service.
Documentation for MPI Support in EGEE: https://twiki.cern.ch/twiki/bin/view/EGEE/MpiTools
More information about errors in the MPI knowledge DB: http://wiki.ifca.es/e-ciencia/index.php/MPI_Errors
Instances of out of date services in the grid15m
Attached you can find a list of instances of services that are “out-of-date” according to the “list of supported service versions" wiki page.
This list will be published every fourth week and the ROCs will be given one week to react (either to upgrade the services at the sites or to explain why not). From the current list please disregard instances reported running version 220.127.116.11 . That's a known issue in the info provider currently being fixed
Next list will be published by the 22nd of February 2010.