In order to enable an iCal export link, your account needs to have an API key created. This key enables other applications to access data from within Indico even when you are neither using nor logged into the Indico system yourself with the link provided. Once created, you can manage your key at any time by going to 'My Profile' and looking under the tab entitled 'HTTP API'. Further information about HTTP API keys can be found in the Indico documentation.
Additionally to having an API key associated with your account, exporting private event information requires the usage of a persistent signature. This enables API URLs which do not expire after a few minutes so while the setting is active, anyone in possession of the link provided can access the information. Due to this, it is extremely important that you keep these links private and for your use only. If you think someone else may have acquired access to a link using this key in the future, you must immediately create a new key pair on the 'My Profile' page under the 'HTTP API' and update the iCalendar links afterwards.
Permanent link for public information only:
Permanent link for all public and protected information:
28-R-15 (CERN conferencing service (joining details below))
CERN conferencing service (joining details below)
firstname.lastname@example.org Weekly OSG, EGEE, WLCG 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
OSG operations team
EGEE operations team
EGEE ROC managers
WLCG coordination representatives
WLCG Tier-1 representatives
other site representatives (optional)
To dial in to the conference:
a. Dial +41227676000
b. Enter access code 0140768
NB: Reports were not received in advance of the meeting from:
Feedback on last meeting's minutes
<big> Grid-Operator-on-Duty handover </big>
From: Italy / SW Europe
To: Central Europe / France
Issues from SW Europe COD:
No major issues to raise.
Issues from Italian COD:
No major issues to raise.
<big> PPS Report & Issues </big>
PPS reports were not received from these ROCs:
Issues from EGEE ROCs:
<big> EGEE issues coming from ROC reports </big>
(ROC CE): It looks we have a central problem with accounting data. Listing of sites not publishing accounting data contains about 40 sites which suddenly stopped publishing in Dec 2007: http://www3.egee.cesga.es/acctenfor/nodata.php Some sites in CE reported problems with APEL similar to a bug: https://savannah.cern.ch/bugs/?32435 Could APEL people comment on that?
(ROC CE): When could we expect MON BOX on SL(C)4? For sites using SL4 this is one of SL3 dependencies.
<big> gLite Release News</big>
<big> WLCG issues coming from ROC reports </big>
<big>WLCG Service Interventions (with dates / times where known) </big>
rfio problems at CNAF (and now also at RAL). The problem (hanging connection in case the file on the SE is read from the WN using rfio protocol) is under investigation by CASTOR people with support of CNAF people. However being CNAF out of the production mask since months now (suffering the accounting) we are looking for the shortest way to get it fixed: accessing files through rootd rather than through rfiod. This has been proved to work at CERN (where it is happily used).
I'd like to remind with this report this issue (that heavily penalizes computing mask of LHCb) and to set some actions that should be
CASTOR people + CNAF people to debug the rfio problem
CNAF people (to install,configure and test rootd). They got the support from FIO and CASTOR people at CERN and it should foreseen for this week.
In case the recipe works at CNAF involve RAL people for the point 2.