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 Central Europe to Northern Europe
From last week left only issues concerning APEL test (sites are working on the problem) and some alarms not handled by AP ROD (ROD asked for action and explanation).
I would like to remind that C-COD started not only ask RODs for action but also for explanation why issues were not handled according to procedure. We need that to know how to read metrics.
CREAM CE on SL5 still not released: https://savannah.cern.ch/patch/?3260
SAM tests: available for viewing in Production (https://lcg-sam.cern.ch:8443/sam/sam.py). Only CEs that publish "production" tag are visible. Need to define when tests can be set to critical in order for alarms to be generated.
Various tidbits gleaned from the CIC portal:
New version of Operations Dashboard available tomorrow
CREAM CE in SAMAP available since Thursday
New EGEE SA1 NAGIOS Update - Addition of MYEGEE portal.