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)
CERN, France, DECH, NE, ROC_LA, Russia and UKI had not validated their production reports by 14:00. This is not good (6 had, 7 hadn't).
From ROC Italy:
Top-bdii core service for IT-ROC has been migrated to gLite 3.2 on SL5 x86_64 and we observed an improvement of the performance.
What about the migration to gLite 3.2 for the site-bdii service? Is there any known blocking issue? We think that migration for both top-bdii and site-bdii services should be recommended for the considerable performance improvement.
This weekend we’ve seen further important progress with beam commissioning in the LHC at 450 GeV. On Friday evening, 4 December, beam circulated with more than one proton bunch for the first time. This was another significant step towards running at useful beam intensities.
Then in the early hours of Sunday, the operators succeeded in circulating four bunches in each of the LHC’s two beams and announced stable beams for the experiments. On Sunday evening there was further stable running with higher-intensity bunches. All six LHC experiments have observed collisions and collected useful quantities of data. They were able immediately to begin checking the operation of their detectors, with excellent results that augur well for the future.
Also, some information from the WLCG Daily meeting: