This should have been added in the HTTP/3 commits[2][3], but it was my
understanding that it was not supported by Hetzner DNS. It apparently is
supported but not documented.

Cloudflare has a blog post[4] explaining how this speeds up HTTP/3
negotiation. Basically, the clients can connect over HTTP/3 right away,
rather than having to connect with an older protocol (probably HTTP/2 in
our case) and then upgrade to HTTP/3 (based on the Alt-Svc header).

Our domains are HSTS preloaded[1], so it would not speed up HTTPS
negotiation in most cases.

[1] https://datatracker.ietf.org/doc/html/rfc9460
[2] 8dfa7e8c ("nginx: Add plumbing for enabling HTTP/3 conditionally")
[3] 28e0f03c ("Enable HTTP/3 for {,aur.,wiki.}archlinux.org")
[4] https://blog.cloudflare.com/speeding-up-https-and-http-3-negotiation-with-dns
[5] https://hstspreload.org/

Ref #606

CPX51 is a bit expensive (€54.4/mo) and based on performance monitoring
the CX52 should accomplish the same job at a much lower cost (€31.9/mo).

Starting September 2024 the lower pricing on our grandfathered CX11
cloud server will go away. Thus, the price will be the same as CX22.

CX11  -> CX22: Same price and better specs!
CX21  -> CX22: Cheaper price and same specs!
CX31  -> CX32: Cheaper price and better specs!
CPX11 -> CX22: Same price and similar spec! (for consistency)
CPX21 -> CX32: Cheaper price and better specs!
CPX41 -> CX42: Cheaper price and similar specs!

Some of the CX11 servers are not rescaled as they are on older, cheaper
grandfathered plans.

[1] https://www.hetzner.com/news/new-cx-plans/

See https://lists.archlinux.org/archives/list/arch-mirrors@lists.archlinux.org/thread/TZJGUW52AHGUNCK6DHUAJFX7OLN6VQXW/ for more details.

Related to #531



Co-authored-by: Kristian Klausen <kristian@klausen.dk>
Signed-off-by: Christian Heusel <christian@heusel.eu>

The server was created on 2023-05-27 with tf and announced the next
day[1]. It is becoming annoying to keep a unstaged change around, so new
tf changes can be deployed, so let's just commit the change.

[1] #257 (comment 96721)

Requested by Allan on IRC (-devops).

New server; same CPU and RAM as previous one, hopefully more stable.

As announced[2][3] the bugtracker has been migrated to gitlab, so
bugs.a.o can be decommissioned and replaced with a static copy[1](to
avoid link rot).

[1] https://gitlab.archlinux.org/archlinux/bugs-archive/
[2] https://archlinux.org/news/bugtracker-migration-to-gitlab-completed/
[3] https://lists.archlinux.org/hyperkitty/list/arch-dev-public@lists.archlinux.org/thread/WYXDTJ3TR2DWRQCDZK44BQDH67IDVGTS/

Fix #550
Fix #551

Requested by @anthraxx 

The servers have been configured with the common and firewalld roles.

It was not supposed to go in the commit and it will be added at later
date, when it is ready(ish).

Fixes: 122eb202 ("Add dedicated Fastly billing account")

I don't expect more GitHub Pages to be set up, so using a explict
resource instead of abstracting it, is fine I think.

[1] https://github.com/archlinux/archinstall/issues/2098

The role has been renamed[1], so rename the bylaw subdomain.

tu-bylaws.aur.a.o will be kept around for some time redirecting to
package-maintainer-bylaws.aur.a.o.

[1] rfcs!7

Ref #533

The VMs created in the Hetzner cloud sandbox project must be accessible
with a DNS name. This creates a dedicated DNS zone for this purpose.

For now this zone will only be used by the aurweb project, so it can
create DNS records for the VMs it creates. This is needed so the dynamic
created environment can be accessed over HTTPS.

[1] https://docs.gitlab.com/ee/ci/review_apps/

Bugbuddy is the upcoming tool for assigning package bugs to the proper
folks. The bugbuddy role will be created at a later date when the tool
is ready.

We are not sure where this CNAME was originally used. DNS records were
transferred to Terraform sometime in 2020 so we lack history for them.

[1] archlinux/alpm/alpm-types#36

Until we get our situation with uptimerobot fixed, we are redirecting
status.archlinux.org to the standard uptimerobot URL, that is provided
with their free plan. Once/if we re-gain our premium access, we can
simply revert this MR.

Initial setup bootstrapped from arch-boxes repo [1], default user 'arch'
removed after.

https://gitlab.archlinux.org/archlinux/arch-boxes/-/jobs/157024/artifacts/browse/output



Signed-off-by: Leonidas Spyropoulos <artafinde@archlinux.org>

With rsync.sandbox being gone from archlinux_org_cname, the indentation
needs to be adjusted.

This has moved to production.

GitLab is configured to use OpenSearch from its admin panel[2].

[1] https://docs.gitlab.com/ee/user/search/advanced_search.html
[2] https://docs.gitlab.com/ee/integration/advanced_search/elasticsearch.html#enable-advanced-search

Fix #159

New feature by Hetzner, primary IPs are a way to manage addresses
assigned to each cloud server. This allows having IPv6-only boxes.

Signed-off-by: Leonidas Spyropoulos <artafinde@archlinux.org>

It looks more professional and we can move it to a dedicated box if the
load increases.

Chonky packages are chonky. The extra 25G should last us 6-12 months.

Enabling debug packages by default has resulted in more debug packages.

Nobody could have foreseen this.

When debuginfod processes big debug packages it can run out of memory
and get killed. Then, it gets restarted by systemd only to OOM again.

Let's try doubling the memory to ~4G.

Equinix's AMS1 DC is being shut down so we need to recreate this box.

For Geo variety, this one is created in Frankfurt instead of Amsterdam.

Ref #495

Equinix's AMS1 DC is being shut down so we need to recreate this box.

Ref #495

We've been seeing CPU spikes that a single vCPU can't handle, resulting
in alerts about high CPU usage. Let's try two cores to see how they do.

For the upcoming "Git packaging sources"[1], we need a shadow copy of
repos.archlinux.org we can test stuff on (Ansible roles, packaging
workflow etc.). We still have repos-git.archlinux.org, but that box is
more of a POC box allocated to anthraxx for his MRs related to the git
migration.

More details on how the box was setup can be found in[2]. Only the
terraform code is committed to the master branch, as it is annoying
having the server in the state without the corresponding IaC code
comitted.

This was deployed Fri Dec 16 01:10:15 2022 +0100.

[1] https://lists.archlinux.org/archives/list/arch-dev-public@lists.archlinux.org/thread/YKKYBXQL62U5RTYIRI2NT2I3EG7V63HT/
[2] archlinux/infrastructure!665

Fix #479

As announced on the mailing list[2] pacman has been migrated to gitlab
and there is no real use for patchwork left, so it can be
decommissioned. A static copy[1] is kept around for the time being to
avoid link rot.

[1] https://gitlab.archlinux.org/archlinux/patchwork-archive
[2] https://lists.archlinux.org/archives/list/arch-dev-public@lists.archlinux.org/message/7B6R5HVEC67U7B2VQ3SKUVXU4RDCRRMM/

Fix #487

We currently have 23G of debug packages and soon expect quite a bit more
since the debug option is being enabled by default in devtools 20230105.

Ref: archlinux/rfcs!15

With the final lists migrated to mailman3[1], the mailman2 server can
finally be killed.

When the mailman3 server was initially setup[2], it was done on a
separate server because the mailman and mailman3 packages conflicted,
and the traffic was routed over wireguard (HTTP, LMTP and SMTP).

Instead of installing mailman3 on the original lists.al.org server and
transferring the data, it was easier just to install the missing pieces
(basically Postfix and adjusting the Nginx configuration) on the ml3
server and move the IPs (to keep the IP mail reputation).

So basically the following was done:
- The IPs for the original lists.al.org was moved to the mailman3.al.org
  server
- The mailman2 datadir was transferred to mailman3.al.org server, so we
  can keep the pipermail links alive, and import missing mails if needed
- The original lists.al.org server was decommissioned
- The mailman3.al.org server was renamed to lists.al.org
- The missing pieces was added to the mailman3 role (basically Postfix +
  Nginx adjustments)
- The mailman role was deleted and the mailman3 role renamed to mailman

[1] 75ac7d09 ("mailman: Fourth and final batch of mailman3 migrated lists")
[2] 9294828f ("Setup mailman3 server")

Fix #59

Going to be served by all our Geo boxes under riscv.mirror.pkgbuild.com.