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:
On several occasions, the database behind various services have needed to be "cleaned" to prevent performance degradation. This has applied to CASTOR DBs, FTS, dCache etc. Have all the necessary cleaning operations been performed at CERN and outside sites ready for the multi-VO throughput tests starting March 26th? Should these operations be performed regularly? Automatically?
Also affects ATLAS "Tier1" VO boxes that are being setup / tested at CERN.
5 June - a meeting with CMS computing management has been setup for 19 June to discuss this and other service-related issues. An IT pre-meeting was held 5 June - notes attached.
LFC for LHCb - replication to additional Tier1 sites
We agreed to finish the setup of the LHCb r/o LFC replica at all
LHCb T1 database clusters during the next two weeks. This will allow the LFC teams at T1s to setup the LHCb LFC front-ends independently and connect to the local DB replicas (in the LHCb cluster). Eva will pass around a concrete plan in the next days.
The primary purpose of this item is to bring up any (hopefully rare) issues that are in danger of becoming "hot" if not given attention.
By definition, this must be used sparingly (i.e. not for every single problem seen by an experiment) and experience has shown that these issues should be raised in advance, e.g. the day before (or even earlier if possible...)