Hi all,

We worked with the OSUOSL admins to get the new sourceware-builder3
server at OSUOSL 2x28 cores (2x56 threads), 768GB RAM and 2 x NVMe M.2
1TB online. It replaces the two (much smaller) sourceware-builder1 and
sourceware-builder2 servers, which have been turned off now.

The machine has been partitioned into four VMs:

- sw3bb1: 40 vcpus, 256GB mem, 500GB disk
- sw3bb2: 16 vcpus,  96GB mem, 420GB disk
- sw3runner1: 40 vcpus, 256GB mem, 500GB disk
- sw3runner2: 16 vcpus,  96GB mem, 420GB disk

The buildbot worker tasks and containers can be configured through the
builder project: https://sourceware.org/cgit/builder
For projects with user branches (like binutils, gdb, libabigail,
elfutils, valgrind) it can also be used for pre-commit CI with try
branches: https://sourceware.org/binutils/wiki/Buildbot
For questions please join the mailinglist:
https://sourceware.org/mailman/listinfo/buildbot

The forge workflows can be configured through your projects
.forgejo/workflows/ actions (you can also enable actions on your
personal forks). For workflows that need to run on sw3runner1 use the
sourceware-large-runner label. See also the forge project on
https://forge.sourceware.org/forge/ or join the mailinglist:
https://sourceware.org/mailman/listinfo/forge

Please support the OSUOSL! Their data center migration is in full swing
(all our servers have already moved) and they have an update and a
fundraising event:

  https://osuosl.org/blog/data-center-migration-update-fundraising/

Please donate if you can, or ask your company to support OSUOSL, this
will not only help Sourceware but also the GCC Compile Farm and many,
many, many other Free Software projects:

  https://www.beavsgive.org/organizations/open-source-lab

This also finalizes our hardware refresh cycle and moving all services
off bare metal servers onto VMs (at least for all the x86_64 hardware)
which greatly simplifies backups, redundancy and moving services
around. For hardware we should be good for the next couple of years now
and thanks to your generous donations our hardware refresh fund is back
up strenght so we are able to replace any server in case it might
break. https://sourceware.org/donate.html

And we are still moving more services into separate VMs, creating
public setup and Ansible provisioning and configuration management
scripts to untangle dependencies and improve isolation:
https://sourceware.org/sourceware-security-vision.html

Thanks from the Sourceware Project Leadership Committee
https://sourceware.org/mission.html#plc

Frank Ch. Eigler, Ian Kelling, Ian Lance Taylor, Tom Tromey, Jon
Turney, Mark J. Wielaard and Elena Zannoni

Reply via email to