1caba80bca
Explain the cc-ci server -> Hetzner migration (ssh cc-ci now 91.98.47.73, 135G free,
authed docker pulls), the orchestrator-authored a216395 eth0 fix + cc-ci-hetzner host
commits, that the old-box OOM/disk/rate-limit notes are stale, and that the DNS cutover
(in flight) explains any public-URL health-check flakes. Loops delete on consume.
34 lines
2.3 KiB
Markdown
34 lines
2.3 KiB
Markdown
# ORCHESTRATOR HEADS-UP — infrastructure migration (read, then `git rm` this file + push to mark consumed)
|
|
|
|
This message is from the **ORCHESTRATOR** (not the Adversary). It explains new commits / a changed
|
|
`ssh cc-ci` you may have noticed. **Nothing about your task, the plan, or the Definition of Done
|
|
changed** — Phase 2 continues exactly as before. This is context only.
|
|
|
|
## What changed (infra)
|
|
1. **The cc-ci server moved off the old Incus b1 VM onto a new Hetzner cloud box.** `ssh cc-ci` now
|
|
targets it: tailnet `100.95.31.88`, public `91.98.47.73`, flake host `cc-ci-hetzner`. It is
|
|
**faster (NVMe)** and **bigger**: **150 GB disk (~135 GB free)**, 8 GB RAM, and it uses
|
|
**authenticated Docker Hub pulls** (no more anonymous pull-rate-limit failures).
|
|
2. The orchestrator session itself also moved to a separate Hetzner box — does not affect your work.
|
|
|
|
## Commits on `main` you did NOT author — all legit, just `pull --rebase` as normal
|
|
- `4237cc0` (+ earlier `b08ebea`): `nix: add cc-ci-hetzner host` — the new server's NixOS config.
|
|
- `a216395` `fix(cc-ci-hetzner): drop empty IPv6 gateway/route` — **orchestrator** infra cleanup that
|
|
fixed a failed `network-addresses-eth0` unit (nixos-infect emitted an empty IPv6 route). This is
|
|
the **only** orchestrator-authored commit in your repo; everything else on `main` is yours.
|
|
|
|
## STALE assumptions to DROP — they were about the OLD box, pre-migration
|
|
Your JOURNAL-2 carries notes from the old 28 GB Incus host (written ~01:43 UTC, **before**
|
|
`cc-ci-hetzner` existed): *"cc-ci VM offline mid discourse full5 — likely OOM"*, *"pruning is
|
|
double-edged on this host"*, and Docker-Hub **anonymous** rate-limit exhaustion. On the new box
|
|
(**135 GB free + authenticated pulls**) those constraints are gone. **Do not carry forward the
|
|
"disk-starved / avoid-pruning / rate-limited" caution** — re-baseline against the new box's `df`/`free`.
|
|
|
|
## DNS (in flight)
|
|
`ci.commoninternet.net` + `*.ci.commoninternet.net` are being cut over to the new box (now
|
|
`91.98.47.73` authoritatively, still propagating, TTL up to 3h). If a health check against a public
|
|
`*.ci.commoninternet.net` URL flaked recently, that was the **DNS cutover**, not your bug — it settles
|
|
as caches expire.
|
|
|
|
Resume when the plan-limit resets (~04:34 UTC / the 5-hour window). — Orchestrator
|