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:
S3 account migration/removal campaign has started, will send reminder this week.
Filer Migration, CephFS/Manila status and plans.
Dan van der Ster
Incident INC1973961: itnfs30 was not allowing OpenShift to mount anything. Loadavg was normal and zfs looked fine. Tons of processes of 'osadmin'. ~1000 zfs filesystems, which is abnormal. Alex Lossent found that a process on their side had created 800 volumes in a loop. He manually removed them, I restarted nfs-server, and things recovered.
User issue from HPC:
I have, however, observed that the modification time of some data files remains unchanged when small amounts of data are appended to them. The modification time reported to the user stays the same even after days of running.
In the cases where this occured, the simulation program opened the data file with fopen() in "ab" mode, writes a few numbers and closes the file with fclose(). One can see that the file grows and it is possible to check that the data are correctly stored.
The same does not happen when larger amounts of data (a few KB at least) are appended. And it did not happen before the software update. There is no indication of data losses or data corruption.