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:
All sessions should be discussion sessions.
Rather than giving talks, the presenters are asked to briefly describe the issues, questions ect. and open the floor for discussions. If presentations are given, they must not take more than 50% of the allocated time. The session chair should moderate the discussions.
The presenters need to be named by Friday June 11th
Talks need to be available by Wednesday June 23rd
Welcome from local organizers (logistics)
Opening by Frederic Hemmer
Integration & Testing
Initial Experiences with the Implementation of the SCM Plan40m
Goals, problems and lessons learned, procedure for adding new subsystems and components, general guidelines for integration and configuration
The building and packaging system40m
How the build procedure works and how the various types of packages are created and managed with special focus on Ant extensions, RPM and MSI
The Continuous Integration System40m
Organization, configuration and preliminary results, procedures for reacting to bugs that break the periodic builds.
Testing process and plans1h
Testplan and approval mechanisms (Leanne)
Unit Testing coordination and Interface Testing (David)
Tools survey, tools selected and being evaluated, first experiences with the prototype (Diana)
First experiences testing the prototype, experiences with savannah, what works, what does not, etc (Mario)
Leanne Guy, David Collados, Diana Bosio, Mario Reale
* Current GAS status (Pablo)
* Service Controller (Predrag)
Topics to be discussed include:
- How does the GAS work in detail
- What is expected from other components to integrate with it
- play through use cases
Pablo Saiz, Predrag Buncic
Components shared between clusters1h 30m
which common components could the clusters share? (e.g. logging, error reporting, configuration). Is this viable? How do we get organized to deliver these?
There should be short (~10/15 minutes) presentations from people from each cluster on what is available and what would be desired and then we open the floor for discussion.
- Messaging (Kris)
- Java Web Services and their testing (Gavin)
- logger, package mgr, job agent (Predrag)
- logging, messaging (Abdeslem)
Gavin McCance, Krzysztof Nienartowicz, Predrag Buncic, Francesco Prelz, Abdeslem Djaoui