CI Level 3¶
There is a number of dedicated CI worker nodes that are managed by the HPC Operations team. The following node configurations are available:
Name | Hardware/Features | Available |
---|---|---|
uc2-ci-intel-bw | Intel Broadwell Xeon (CPU-only) | |
uc2-ci-intel-cl | Intel Cascade Lake Xeon (CPU-only) | |
hk-ci-intel-il | Intel Ice Lake Xeon (CPU-only) | |
hk-ci-intel-ila100 | Intel Ice Lake Xeon CPU + 1x NVIDIA A100 | |
ftp-ci-intel-clv100 | Intel Cascade Lake Xeon CPU + 1x NVIDIA V100 | |
ftp-ci-amdmi100 | AMD EPYC Rome/Milan CPU + 1x AMD MI100 | |
ftp-ci-a64fx | Fujitsu ARM64FX CPU-only |
Dedicated CI Workers Management¶
A single gitlab-runner
instance will run on each of the dedicated CI nodes. Choose one of the dedicated worker nodes and send the name of the node, the Gitlab instance URL, the CI runner token and the desired settings for ,,executor'' and ,,tags'' to the CI Operations team via the support channels.
You can find the instance URL in the GitLab Web interface in the Your Project → Settings menu → CI / CD
sub menu by selecting Runners → Specific runners sub section → Set up a specific runner manually
, and the token can be found in the same GitLab Web interface in the Your Project → Settings menu → CI / CD
sub menu by selecting Runners → Specific runners sub section → Set up a specific runner manually
.
The Operations team will then set up the configuration on the dedicated CI worker.