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:
CI/CD Testing?: offloading quality/functionality checks to automated pipelines for container images and helm charts.
Needs process for out of band changes.
Is there a threshold consideration
Agreed: MRs come with require approver. Can uncheck for emergency (can the runner notify on that?). We need a bot for open reqs. Need agreement with HPCers for bi. Protect QA & Master. Features should be tickets if you can't describe them in basically the commit message.
BBC-2109: Migration to CC7 (50%):
Only ~500 cores (CMS T0) pending in gva_project_004 (networking issues in OpenStack).
BBC-2028: Provisioning more 24cpu nodes in Geneva Project 041 (BE-ABP).
A total of 2400 cores is desired.
Using standard naming convention.
Testing Terraform on mixed flavor environments.
build some new 32 cores bigmcore.
create a new wholemachine, fullnode hostgroup to consolidate sixteen and bigmcore: a hostgroup that only accepts full node jobs. This requires as well doing magic to convert user jobs to right sizes (18->16, 28->24, 48->32).
New version almost ready. They were running for the last days succesfully sending data to fifecarbon02 (test graphite instance).