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)
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 ROC DECH:
LCG2-FZK Service Incident:
Planned downtime affecting ATLAS:
OUTAGE 2010-02-01 8:00 to 2010-02-05 15:00 (UTC)
The dCache instance for atlas (atlassrm-fzk.gridka.de) will be migrated to Chimera.
From ROC Russia:
Wrong version detection command for the LB service. https://savannah.cern.ch/bugs/?61586 . This bug duplicate https://savannah.cern.ch/bugs/?55482 from 2009-09-09 09:59. So it is not corrected during 3(!) months.
fixing MPI sites (from the MPI WG)15m
Dear Maite (CC. Steven)
It seems that already today some sites are starting to fix their MPI
We also got a few reactions wondering about this sudden urge to fix MPI site
It would certainly help if the the ROCs receive an explanatory e-mail about
the MPI Task Force mission, containing also the link with to the official
documentation to MPI Support in EGEE, meaning this one:
that each ROC should distribute it to their sites.
Many people is concerned because they have followed some documentation which
is also online coming from SEE Grid, and particular to certain cluster in
There are reasons today for being optimistic, because people are fixing the
issues, and mpi-start continues to work without any problem in the CREAM CE
However, in the timelife of EGEE we can probably only fix the current sites,
and arrange properly the documentation. Any other thing like new features of
the middleware will have to waitt for future developments. See here for
status of mpi-start:
More information about the MPI knowledge DB:
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, here: https://twiki.cern.ch/twiki/bin/view/EGEE/SupportedServiceVersions