Skip to content

Move the Hives to the Spindle VPS if there is headroom #340

Open

Description

@hanthor

Follow-up to #337 (Spindle VPS). If the Oracle A1 host has headroom once Spindle is measured, move the Hives there too instead of keeping them off.

What ran on the AWS cluster (from cluster-state, 2026-10-25)

  • Namespaces hive, hive-hanthor, hive-reef, hive-hub, hive-contributors, hive-system (operator). CRs: 1 HiveRelease, 3 HiveSpokes (hanthor, reef, school), usage pools for anthropic/google/kiro/meta/openai.
  • Requests (memory / cpu): 3 Hives at 1 Gi / 300m each (limit 4 Gi each), 3 contributors at ~0.5 Gi / 250m (limit 2 Gi), operator 128 Mi, hub, console, ccleft and discord-realtime (limit 4 Gi each, no requests). Roughly 5-6 GiB requested; 12 GiB+ if every limit is hit. Spindle itself requested 4 Gi with an 11 Gi limit.
  • Data (all in ~/backups/tunaos-aws-2026-10-25 on himachal-1): hive_hive-data 16 GiB, hive-reef_hive-data 15 GiB, hive-hanthor_hive-data 12 GiB, plus hub, discord-reports and hive-ops-state. NOT exported: contributor homes, hive-shared-auth and the shared-claude/codex/gemini PVCs, so provider logins must be redone (or served by the omp auth broker).
  • Needs Kubernetes (the operator and CRDs): k3s on the VPS, or rewrite as compose. The manifests are in talos-k8s/hive/ and the CRs are in cluster-state.

Decide first

  • Measure real Spindle + MAS memory on the VPS for a few days (docker stats); only proceed if 24 GB leaves at least ~10 GiB free.
  • The tenancy's Always Free allowance may be 2 OCPU / 12 GB (see feat(spindle-vps): run matrix.reilly.asia on an Oracle Always Free VPS #337 README); in that case the Hives do not fit with Spindle and need another host.
  • Note the home region is Sydney (ap-sydney-1); Always Free compute must be in the home region.

To do

  • k3s on the VPS (or compose), restore the three Hive data tarballs, apply the CRDs and CRs from cluster-state (secrets rendered at deploy time, never committed), re-create ghcr-auth pull secrets.
  • Tailscale operator is not needed if the VPS is on the tailnet itself; the old tailnet device names (hive, hive-auth-egress-*) can be retired with scripts/tailnet.py (feat(tailnet): gc, rename and inventory alignment (scripts/tailnet.py) #333).
  • Re-point hive.reilly.asia, school.tunaos.org, reef.tunaos.org, hub.tunaos.org (Cloudflare-proxied) at the new origin.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    stage/010-actionableTriaged; eligible for the hive to pick up

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions