OpenWrt Infrastructure Meeting
Date: July 14 2026
Present: Baptiste, Paul, lynxis, Ted, Zoltan, Ansuel
Motivation for the meetings
Infra overview
Share an overview of the current infra so that we all have the same understanding
-
Question for the full group: Is patchwork still actively “moderated” i.e. merged patches are closed?
ToDo lynxis: Remove Thomas as admin everywhere (hasn't been active for over two years)
Add tags on the DO droplets to identify who are the main admins
Identify current costs, available budget, infra providers
ToDo lynxis: Ask who owns our domain. Should be SFC. → Done: it is SFC
ToDo Paul: Add Hetzner servers to infra page
ToDo Baptiste: Update finance part
ToDo Paul: Check with John what the “Archive” server does (sb59)
ToDo Paul: Check with Jo about old download server
DO is paid for by SFC
Hetzner as well
We are paying OSUOSL for buildbot workers
Work out a plan for the obsolete or unmaintained parts of the infra
util-01: managing email (critical for outgoing forum email + incoming email for forum + forwarding for openwrt.org + a few technical mailboxes) and Let's Encrypt
DNS challenges.
Handles how many mails per day? probably hundreds/thousands
Either upgrade it, or switch to a managed service
ToDo Ted: will upgrade it
test-01: Debian 11, running freescout. Managed by stintel.
ToDo Baptiste: ask stintel if he is upgrading the
OS
git-01: not used anymore (moved to git-03) but generating traffic.
ToDo Ted: snapshot the droplet and delete it
git-01 snapshot taken and will be preserved on DO until explicitly deleted (~$5/mo)
git-01 will be destroyed tomorrow (15-Jul-2026)
git-archive-01:
forum: reasonably up-to-date, Ted is running it, it's a bit custom (plugins, external storage). We continue to self-host.
wiki: Ted does the minimal required to keep it running, but we need a new maintainer. We also need people to validate the accounts.
Discussion about exposing services with their internal names (git-01, mirror-03, etc). It works, and people+bots seem to rely on it, but we don't want to maintain that eternally.
Identify services that are not managed by the core infra group
(i.e. outside of Ansible)
Discuss setting up a monitoring system
Prototype demonstrated by Baptiste with VictoriaMetrics and Grafana, running on a Hetzner VM
Full monitoring access will be limited to OpenWrt member group, however dashboards/stats of public interest (downloads, sysupgrade server usage etc) will be published on a case-by-case basis
ToDo Baptiste: close the full Grafana dashboards by default
ToDo Baptiste & Paul: deploy monitoring on more servers (starting with sysupgrade)
Discuss the disk space issue on the download server
We are getting tight on disk space on the download server, and we can't allocate more disk space.
We host all releases since 17.01
Proposal: remove everything from 17.01 to 23.05 (end of life releases)
We should document the process so that we archive/remove old releases regularly
Zoltan asks for staged redirect (redirect one major release at a time) to avoid melting the archive server
Group discussion and next meeting
We will create a Signal group for coordination in the group. It is aimed at concrete discussions for people actively doing actions on the OpenWrt infra. Decisions and important information should be discussed on the openwrt-adm mailing list or in group meetings. The Signal group will be open to all OpenWrt voting members.
Next meeting: 26 August 16:00 UTC to 17:30 UTC
ToDo Baptiste: send an invite
We plan regular meetings at a fixed day (every month or every 2 months)
Other topics
Jonas as new admin — Not discussed