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:
Progress of Java implementation, feature changes, ...
(Laboratoire de l''Accelerateur Lineaire (LAL) (IN2P3) (LAL))
Marco Emilio Poleggi
Core modules update30m
Status of developments on core modules maintained at CERN
Marco Emilio Poleggi
Quattor developments (cont)
QWG templates update30m
Update on configuration of gLite components, with emphasis on WMS.
Managing Xen with Quattor30m
In this talk, I will describe the development of the ncm-xen
component for managing the configuration of Xen virtual
machines. I will cover pypxeboot, a new tool for simulating
PXE booting for guest VMs and describe the functionality of
ncm-xen itself. Feedback welcome!
AII update and release issues
Latest developments on AII, discussion of change requests.
Luis Fernando Munoz Mejias
(Facultad de Ciencias - Universidad Autonoma de Madrid)
Discuss recent developments (esp. introduction of
namespaces). Review open bugs in Savannah. Plan future
Review open Savannah bugs1h
We will go through the list of bugs in Savannah, and discuss
whether they are assigned to the right person, and decide on
There has been some progress on documentation since the last workshop. In particular, there is now an infrastructure in place for automatically generating component documentation from CVS. We will discuss this, the release page on the wiki and other forms of documentation and try to identify areas for improvement.
Core tools and components
Discussion of the operation of ncm-ncd and ncm-cdispd, in particular how dependencies between components are handled.
Making it easier to write components30m
In this session, we will discuss options for improving the experience of the component writer. This could potentially include improvements to CCM libraries to ease the handling of configuration trees in Perl, discussion of libraries currently in use and suggestions for new ones, ...
Best practice when writing components30m
There has been some discussion of coding style on the mailing list. In this session, we will open up this can of worms! Hints and tips from experienced component writers would be welcome, and we will also examine the existing guidelines and see if they need to be updated.