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:
EGI - possible directions and scenarios - the EGI Design Study15m
(INFN & EGI_DS/WP3)
Operations Review - hot topics from recent months15m
WLCG Requirements - what do we need for 2008 and beyond?30m
Robust Services & 24x725m
Effective PPS - how to make the PPS more effective for the experiments20m
This includes providing an environment where the experiment-specific "Critical Services" can be tested
Experiment Operations1h 30m
What is it that the experiments hate most about the current operations setup?
What explicitly is missing from the point of view of the experiments?
What can be done better? What (perhaps?) should not be done at all?
Should we somehow integrate global / experiment operations? e.g. via repeat consoles in the various operations rooms?
CMS Centers for Control, Monitoring, Offline Operations and Analysis25m
The CMS experiment is about to embark on its first physics run at the LHC. To maximize the effectiveness of physicists and technical experts at CERN and worldwide and to facilitate their communications, CMS has established several dedicated and inter-connected operations and monitoring centers. These include a traditional “Control Room” at the CMS site in France, a “CMS Centre” for up to fifty people on the CERN main site in Switzerland, and remote operations centers, such as the “LHC@FNAL” center at Fermilab. We describe how this system of centers coherently supports the following activities: (1) CMS data quality monitoring, prompt sub-detector calibrations, and time-critical data analysis of express-line and calibration streams; and (2) operation of the CMS computing systems for processing, storage and distribution of real CMS data and simulated data, both at CERN and at offsite centers. We describe the physical infrastructure that has been established, the computing and software systems, the operations model, and the communications systems that are necessary to make such a distributed system coherent and effective.