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 0148141
OR click HERE (Please specify your name & affiliation in the web-interface)
Italy, France and CERN had not validated their ROC reports as of the 14:00 deadline. Reports show no major operational issues encountered during the reporting period, and no points to raise at this meeting.
FZK-LCG2 wishes to convey the following information:
INFO: GridKa is going to move the remaining SL4 worker nodes (WNs) to SL5 starting next Monday (August 24) with the exception of the Babar share. After Friday 28th August SL4 WNs will no longer be available for WLCG VOs at GridKa.
OUTAGE: 24.08.09 7:00 am - 9:00 am UTC
Due to cluster upgrade to SL5 next week two more CEs get configured to point to SL5. The ce-3-fzk and cream-1-fzk will be unavailable in the information system for the time. No jobs will be lost.
OUTAGE: 25.08.09 8:00 am - 8:30 am UTC
Due to a necessary update of the SRM services, atlassrm-fzk.gridka.de and gridka-dCache.fzk.de will be down for up to 30 minutes. This downtime will only affect the *SRM* but no other dCache services!
Last reminder that the default DPM used for SAM tests will be upgraded to SL4, and that sites with obsolete client S/W will start failing tests.
SAM MPI tests will be activated
At the TMB on 05/08/2009 it was agreed that SAM MPI tests should be re-instated and results followed up.
SL5 Rules, OK?
WLCG MB agreed on 4th of August to ask for the SL5 migration at all Sites, including the Tier-2 Sites.
A web page is available to provide pointers to the relevant information to support the migration, including links to the necessary packages. (https://twiki.cern.ch/twiki/bin/view/LCG/SL4toSL5wnMigration).
It is understood that the Experiments are all ready and able to use SL5 resources.