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:
PG num not a power of 2 on gabe data pool. It was also far too many for the swift users pool, so I merged that from 1024 to 64 PGs. This exposed yet another osdmap trimming bug: https://tracker.ceph.com/issues/48212
Dan van der Ster
(CERN), Theofilos Mouratidis
cephjim cluster was powered off for switch replacement.
itnfs38b: disk has filled up a few times due to misconfigured MIC user processes writing scratch data to micprojects. Wojciech has today found a culprit. To workaround we had to trim old snapshots which were pointing at 1T of deleted files.
filer-carbon: Someone wrote 30GB of new metrics there on Friday. I added 3x new 100GB io1 volumes to the zpool. Now there is ample space for new metrics.