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:
VO questionnaire on EMI middleware transition and features
Name of the VO:
Number of users in the VO:
The EMI project would like to move from gLite 3.1 to gLite 3.2 and gradually replace all the 3.1 components with their respective 3.2 version. The transition of gLite grid sites from gLite 3.1 to gLite 3.2 implies an update from Scientific Linux 4 to Scientific Linux 5 on those sites that are still using version 4 of the operating system. Because of the operation system update, grid applications that use dynamically linked shared libraries may need to be recompiled. Do you see any issue with the recompilation of any of the grid applications of your VO?
gLite 3.2 includes CREAM CE, but not LCG-CE service for job execution. Although the two services should be identical for users' jobs, given that the jobs are submitted through Workload Management Service (WMS), do you see the replacement of LCG-CEs with CREAM CEs as an issue?
The European Middleware Initiative project (EMI) is collecting requirements to define the development plans for the ARC, gLite and UNICORE middleware stacks for the first year of EMI. (planned release in April 2011) EMI year 1 developments focus on service enhancements (security, consolidation of services and libraries, usability) not on adding completely new functionalities. The EGI user community is expected to provide input to this plan. Please list and explain what enhancements your VO would like to see in the new middleware release.