Hey all,
Let's re-start the bi-weekly meetings to sync up on the state of things,
on Thursday 20:00 CEST.
# Topics
- Leftover migration ToDo's
- Closing Flyspray
- Gitlab package related topics
Detailed agenda: https://md.archlinux.org/kF4a9cx2Sqe5ESusZw85zg?both
Greetings,
GitLab's SSH clone URLs no longer require port 222. This matches the
structure used by most GitLab instances. Previous clone URLs (which
include port 222) will continue to work for the foreseeable future.
The host's SSH port has been changed to 2222 and Ansible will use it
automatically.
Arch DevOps will also need to: ssh-keygen -R gitlab.archlinux.org
Credits go to Kristian for suggesting and implementing this
quality-of-life improvement:
https://gitlab.archlinux.org/archlinux/infrastructure/-/merge_requests/716
Dear Arch DevOps Team,
Following the migration of our GitLab instance from a cloud server to a
new dedicated box, you will need to remove the old host keys from your
$HOME/.ssh/known_hosts file. For this please do:
ssh-keygen -R gitlab.archlinux.org
After the above, when you attempt to connect to gitlab.archlinux.org,
you will be prompted to accept a new host key. Please find below the
new host key fingerprints:
SHA256:ZHy7zbNNwKHukTEyFcAT2Ns+mT/wlc2vAjJULnlOroE (ECDSA)
SHA256:KD3Og7bPg9glmODrqUKN0r3Jl18pQ0OVp2MT7xv/bm8 (ED25519)
SHA256:2R7QoVWeZ2DpKEsZBgVKUieM+9TQu6g9N62CIJCyVtc (RSA)
Please note that this change only affects the host machine and not
GitLab itself. Git clones from the latter will work without change.
Stay safe and frosty!
Hi all,
we already seem to have a quite high base load on our current VPS
instance for our GitLab. We see some periodic soft lockups for git and
UI operations when resource hungry tasks are performed, like Linux
kernel mirror operations or GitLab housekeeping.
Soon we will have Git packaging sources on our GitLab as well, which
will increase the baseline usage against our GitLab quite noticeably. We
really want to avoid to cheap out on this crucial and central part of
our infra. As we already sort of maxed out on the VPS capabilities, we'd
proceed and move the GitLab box to a bare metal system. The best bang
for the bucks seems to be the AX52 [0], which will give us a spicy and
more responsive GitLab instance.
Cheers,
Levente
[0] https://www.hetzner.com/de/dedicated-rootserver/ax52