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:
ALICE is basically querying CREAM CEs and ARC CEs BDIIs. Changing CREAM CE ldapsearch queries to consume GLUE 2.0 information should be pretty easy, while for ARC CEs it still needs to be understood whether all the needed information is properly published in GLUE 2.0. The presentation will report about the status of this activity.
AGIS plans to move to GLUE 2.0 and simplify interactions with IS25m
This presentation will give an update of AGIS plans to change AGIS collectors to query GLUE 2 information. It will also explain how the current set of interactions with GOCDB, OIM, REBUS and BDII could be simplified.
AGIS is implementing some changes to become a less ATLAS specific tool and be suitable also for other LHC experiments. This presentation will explain how this is being implemented and how the support from ATLAS Novosibirsk group will be provided.
(Budker Institute of Nuclear Physics (RU))
CMS future use cases for the information system15m
During the CMS offline and computing week, the CMS information system was reviewed and discussed. This presentation will summarise the future use cases that emerged also during subsequent discussions with key experts.
LHCb actions to move to GLUE 2.0 and simplify interactions with the IS10m
LHCb is preparing to support GLUE 2.0, and is also collecting more information from GOCDB. This talk will outline these developments, and report on a prototype using the URL field in GOCDB to discover resource BDIIs directly. Information can then be collected from the resource BDIIs themselves. Services which publish GLUE 2.0 information as JSON over HTTPS can also be discovered using this approach.
Vcycle and Vac support for GLUE 2.0 publishing via JSON/HTTPS15m
Currently there is no way to query the state of VM-based resources managed by Vcycle and Vac. GridPP is prototyping publishing the state of tenancies and VMs on OpenStack etc which are managed by Vcycle, using the JSON representation of GLUE 2.0. This talk will outline how Vcycle’s concepts of spaces and machinetypes have been mapped to GLUE 2.0 ComputingServices, ComputingShares etc, and represented in JSON documents.