* Sourceware Open Office, virtual machines, virtual communities, Fri 16:00 UTC
@ 2026-02-12 17:58 Mark Wielaard
2026-02-14 0:21 ` Mark Wielaard
2026-02-27 13:40 ` Sourceware/OSUOSL upgraded buildbot CI and forgejo runner workflow server Mark Wielaard
0 siblings, 2 replies; 3+ messages in thread
From: Mark Wielaard @ 2026-02-12 17:58 UTC (permalink / raw)
To: overseers; +Cc: gcc, libc-alpha, binutils, gdb
Second Friday of the month, second Sourceware Open Office of 2026!
Friday Feb 13, from 16:00 to 17:00 UTC
At #overseers on irc.libera.chat
$ date -d "Fri Feb 13 16:00 UTC 2026"
More hardware, going full VM-only, moving our security isolation
and automating, testing and actions stories forward.
This month server2 and server3 joined the (new) server1 in the new
RH datacenter. And both are now also setup to only run services in
separate VMs. This completes our bare-metal to VM-only transition.
Also new disks have been delivered to OSUOSL for sourceware-builder3
(2x28 core, 112 thread, 768GB RAM, 2TB SSDs) adding VMs and
containers for buildbot builders and forgejo action runners, which
should come online any day now.
Come and discuss the next steps. Putting more services into their own
dedicated VMs, deciding on how we are going to use the new build server
(in a way that provides Freedom to all). Also the Sourceware PLC is
working on a budget for more paid staff/contractors, what should our
priorities be? See the Plans under Sourceware infrastructure security:
https://sourceware.org/sourceware-security-vision.html
Speaking of data center moves, the OSUOSL one is in full swing now 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
Sourceware relies on cooperation among a broad diversity of core
toolchain and developer tool projects, hackers, organizations,
ideas, and communication styles. The monthly Sourceware Open Office
meetings are one way of coming together as a community and discuss
our shared development infrastructure. For other ways to participate
see https://sourceware.org/mission.html#organization
Keep Sourceware worry-free, friendly and independent by donating
https://sourceware.org/donate.html support our fiscal sponser SFC
https://sfconservancy.org/sustainer and/or support OSUOSL for
hosting Free Software projects https://osuosl.org/donate/
Do you or your company want to sponsor Sourceware plans financially
https://sourceware.org/sourceware-security-vision.html#plans
donate hardware or services then contact us at sponsor@sourceware.org
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Sourceware Open Office, virtual machines, virtual communities, Fri 16:00 UTC
2026-02-12 17:58 Sourceware Open Office, virtual machines, virtual communities, Fri 16:00 UTC Mark Wielaard
@ 2026-02-14 0:21 ` Mark Wielaard
2026-02-27 13:40 ` Sourceware/OSUOSL upgraded buildbot CI and forgejo runner workflow server Mark Wielaard
1 sibling, 0 replies; 3+ messages in thread
From: Mark Wielaard @ 2026-02-14 0:21 UTC (permalink / raw)
To: overseers; +Cc: gcc, libc-alpha, binutils, gdb
Hi all,
For those that missed the meeting...
On Thu, Feb 12, 2026 at 06:58:42PM +0100, Mark Wielaard wrote:
> Second Friday of the month, second Sourceware Open Office of 2026!
> [...]
> More hardware, going full VM-only, moving our security isolation
> and automating, testing and actions stories forward.
> [...]
> Come and discuss the next steps. Putting more services into their own
> dedicated VMs, deciding on how we are going to use the new build server
> (in a way that provides Freedom to all). Also the Sourceware PLC is
> working on a budget for more paid staff/contractors, what should our
> priorities be? See the Plans under Sourceware infrastructure security:
> https://sourceware.org/sourceware-security-vision.html
- Unfortunately Bradley couldn't attend. And Mark didn't have a copy
of the Fosdem notes about the budget. The budget talks we had was
simply going over the Plans at the end of the Sourceware Security
document https://sourceware.org/sourceware-security-vision.html and
assuming we would let payed staff/consultants do everything. How do
you estimate that realistically. We'll continue that conversation
with the PLC next and publish.
- server2 and server3 where moved to the new datacenter. Frank made
sure they are also setup as VM-first machines (no services running
on the bare-metal, everything in VMs). The intention is to configure
a VM on server2 as warm backup for sourceware, periodically
copying over the VM lvm snapshot. server3 would also be available
for random new workloads (also VMs). As both server2 and server3
also have raid5 setups we'd have pretty good redundancy in case of
many-disk failures. The limiting factor at the moment is external IP
addresses, we have 8 (can be freely assigned to any VM on any of the
3 servers), but are already using 4.
- forge now also has a VM on server1 (vm02), data has been migrated
(but needs a new resync now of course), Claudio has given Mark a
walkthrough of the ansible setup. We could setup a hot backup for
that too on server3 (48GB mem, 16 cores, 200GB lv)
- Next vms (https://sourceware.org/sourceware-wiki/OpenHouse2025/)
would be inbox, patchwork, buildbot, bunsen (and maybe cygwin,
gitweb/cgit, bugzilla, dwarfstd, valgrind). All these should be
Ansible managed too. We'll start with one public sourceware-admin
git repo for all configuration. But given the recent talks about
"control", we might split that later into separate per
service/project admin git repos that can be maintained separately.
- Claudio has been doing some work on the forge to convert a pull
request to an email containing all discussions. There are some
examples on https://inbox.sourceware.org/test-list/ They need some
TLC and most importantly: when should it trigger? When someone hits
/submit and when someone approves a pull request using the approve
button? Joseph like to see them each time someone reviews / comments
on a PR in the forge (not just a bot message), that should go to the
mailing list at the time. The point is that people should be able to
join in the discussion at any point if they see something of
interest to them, so waiting until the end of the discussion is much
too late. Frank suggests to also allow "incoming" emails. But that
still has to be setup:
https://forgejo.org/docs/latest/admin/advanced/incoming-email/
- The new sourceware-builder3 server at OSUOSL will have 2x28 cores
(2x56 threads), 768GB RAM and 2 x NVMe M.2 1TB. It will replace the
two sourceware-builder1 and sourceware-builder2 servers that do the
buildbot x86_64 container runs. It isn't online yet. But we got an
email from Lance saying: Lance saying: I have them [the new ssd
disks] here next to me in my office! I'm heading to the new DC and
will hopefully get these installed (the server is already in the new
data center). We will partition it into a big and small buildbot
container runners and a big and small forge runner.
Please don't forget to support the OSUOSL!
> Speaking of data center moves, the OSUOSL one is in full swing now 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
Also please note the OSUOSL network switchover on Tues 17 Feb. Impact
should be low, just a few minutes network downtime:
https://inbox.sourceware.org/overseers/20260213210117.GL8940@gnu.wildebeest.org
Cheers,
Mark
^ permalink raw reply [flat|nested] 3+ messages in thread
* Sourceware/OSUOSL upgraded buildbot CI and forgejo runner workflow server
2026-02-12 17:58 Sourceware Open Office, virtual machines, virtual communities, Fri 16:00 UTC Mark Wielaard
2026-02-14 0:21 ` Mark Wielaard
@ 2026-02-27 13:40 ` Mark Wielaard
1 sibling, 0 replies; 3+ messages in thread
From: Mark Wielaard @ 2026-02-27 13:40 UTC (permalink / raw)
To: overseers; +Cc: gcc, libc-alpha, binutils, gdb
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2026-02-27 13:40 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2026-02-12 17:58 Sourceware Open Office, virtual machines, virtual communities, Fri 16:00 UTC Mark Wielaard
2026-02-14 0:21 ` Mark Wielaard
2026-02-27 13:40 ` Sourceware/OSUOSL upgraded buildbot CI and forgejo runner workflow server Mark Wielaard
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).