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)
Maite Barroso Lopez
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 France to CentralEurope
No log at the time of preparing the meeting (14:20). I see it was inserted later:
Dear NE C-COD,
Last week, there was some work with APEL support on APEL problems detected at ESA-ESAC (GGUS #52012), TW-FTT (#51229) and MY-MIMOS-GC-01 (#51135). But the accounting is still in trouble for these sites.
About GGUS ticket #52012 for APEL problem at ESA-ESAC, I have downgraded it from "Case transfered to C-COD" to "First mail step" as it was escalated while the site was responding and working.
No answer from site IN-DAE-VECC-02 to GGUS ticket #52103 about APEL problem. I have ask AP ROC to see why they are not answering.
David - FR C-COD
FZK-LCG2: One lcg-CE (ce-1-fzk) will be down for a week - from 16th to 23rd of November. We will check the hardware and reinstall the node.
EGEE decision: The decision taken at this week’s SA1 coordination meeting was to request all EGEE sites to deploy a CREAM CE before the end of March 2010, 5 months from now.
The present site availability calculation only takes the LCG CE into account, so this one has to be preserved till the availability is changed to include the CREAM CE. The timeline for this is beginning of 2010 (we will schedule the relevant discussions to validate the changes).
ISSUE: When will be the SL5 port ready? Since the main support platform is SL5 many sites want to deploy the CREAM CE on SL5 to avoid duplicated work.
ANSWER FROM SA3: patch https://savannah.cern.ch/patch/?3260 ; certification will start on Monday
There are still a few RBs and old versions of WMS out there in SWE and SEE: Please check Steve's Page for the details.
1.2.0, HG-01-GRNET, ResourceBroker, rb.isabella.grnet.gr:7772
1.2.0, IFCA-LCG2, ResourceBroker, egeerb01.ifca.es:7772
1.2.0, IFIC-LCG2, ResourceBroker, lcg2rb.ific.uv.es:7772
1.2.0, TR-01-ULAKBIM, ResourceBroker, rb.ulakbim.gov.tr