Skip to content

epic(cluster): network fabric #1084

New issue
New issue
Open
Open
epic(cluster): network fabric#1084
Assignees
dezren39
Labels
area/infraInfrastructure, deployment, and operationseffort/lLarge: multi-day or open-ended; expect staged check-insepicMeta-issue grouping multiple items (org Project Type=Epic)meta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedmode/hybridOnline work plus a physical step (power, cabling, KVM access to a real device)source/creatorFiled by the new-issue-creator jobtask/triageQueue packet kind: verify, reproduce, and route this item

Description

@dezren39
dezren39
opened on Oct 27, 2026

Network fabric

Purpose

A documented, declarative network design sized for the cluster: fast east-west between nodes, scarce egress managed deliberately.

Scope

Switching and addressing plan replacing the torn-down v1.9 test layout (doc/talos-addresses.md is historical only). Confirm the exact high-speed NIC spec on core machines and the switch gear between them (needed to sanity-check LINSTOR/DRBD replication traffic). Management network for BMC/KVM. Edge: 2 Gbps symmetric Brightspeed fiber; egress strategy (tunnels to Cloudflare/Turso/Tailscale, compression) documented as design constraints. Existing notes: doc/network-topology.md, doc/inventory/routing-and-switching.md.

Execution mode

Hybrid: design and config online; cabling, switch install, and link verification physical.

Dependencies

Depends on epic 1 (NIC inventory). Gates epic 6 bootstrap.

Acceptance

Addressing + VLAN/segmentation plan committed; NIC/switch facts verified against hardware; management network reachable for every first-node machine.

Structure

Part of the basement cluster program. Project home: planning/roadmaps/basement-cluster.md in this repo. Full program register: goal workspace files/idea-register-2026-10-20.md (Muse goal goal_ba17a5777c21). Detailed task issues are filed as sub-issues of this epic; dependencies use blocks / blocked-by links.

Hard rules for the whole program: no HashiCorp anything; everything bootstrappable from config, no hand-built state.

Activity

  1. dezren39
    added
    status/needs-triageNot yet triaged; needs a first look
    area/infraInfrastructure, deployment, and operations
    epicMeta-issue grouping multiple items (org Project Type=Epic)
    effort/lLarge: multi-day or open-ended; expect staged check-ins
    meta/enrichedIntake review done: acceptance criteria, links, and normalized labels added
    mode/hybridOnline work plus a physical step (power, cabling, KVM access to a real device)
    on Oct 27, 2026

  2. developing-today commented on Oct 27, 2026

    @developing-today
    developing-todayBot
    on Oct 27, 2026 – with developing.today
    Contributor

    CODE-225

  3. github-actions
    assigned
    dezren39
    on Oct 27, 2026

  4. dezren39 commented on Oct 27, 2026

    @dezren39
    dezren39
    on Oct 27, 2026
    MemberAuthor

    Epic map — basement cluster program

    # Epic Issue
    1 Hardware inventory & first-node selection #1080
    2 Firmware / BIOS / BMC audit #1081
    3 Basement power & space #1083
    4 Network fabric #1084
    5 Storage assembly & validation #1085
    6 TALM + Talos bootstrap #1086
    7 Cozystack platform #1087
    8 Platform services #1088
    9 Observability, backup & recovery #1090
    10 Cloud extension (OCI & egress) #1091
    11 First workload: ID app #1092
    12 ESP32 wing #1093

    This epic: #1084 — Network fabric
    Dependencies: Blocked by #1080 (NIC facts); gates #1086

    Filed in the 2026-10-26 cluster seed. Project home: planning/roadmaps/basement-cluster.md.

  5. dezren39
    marked this as blocked on Nov 1, 2026
  6. dezren39
    marked this as blocking on Nov 1, 2026

  7. dezren39 commented on Nov 3, 2026

    @dezren39
    dezren39
    on Nov 3, 2026
    MemberAuthor

    agent-note:v1
    state: triaged (coverage pass)
    Coverage pass 2026-11-03: reviewed in the fleet-wide per-issue pass (drift / overlap / already-handled / stale / blockers / ordering). Verdict: still live; queued in repo-health-code-pilot as triage at priority 30 (priority/none). If this is already handled at current main, the triage closes it with evidence; if it needs splitting, the triage files the split.
    Found via: coverage pass 2026-11-03

  8. dezren39 commented on Nov 3, 2026

    @dezren39
    dezren39
    on Nov 3, 2026
    MemberAuthor

    🤖 Agent note · triaged (epic live; one acceptance half is gated, the design half is not)

    • Agent: queue worker (repo-worker-code), OpenChamber scheduled lane ec118cad
    • Session / ID: queue task 7644
    • Fresh state at origin/main: epic(cluster): network fabric #1084 OPEN, no sub-issues (subIssuesSummary: 0/0), roadmap row planning/roadmaps/basement-cluster.md:21 lists it as planned. Source docs are on main: doc/network-topology.md, doc/inventory/routing-and-switching.md, doc/talos-addresses.md (historical only, as the issue says).

    Dependency, named: #1097 task(cluster): verify NIC and switch-gear facts is OPEN. That gates the hardware-verification half of the acceptance criterion ("NIC/switch facts verified against hardware"); it does not gate the design deliverables — the issue's hybrid execution mode says design/config are online while cabling, switch install and link verification are physical.

    Scope worth splitting (the epic has no children yet):

    1. Addressing + VLAN/segmentation plan — the committed-plan deliverable; can start now from doc/network-topology.md + doc/inventory/routing-and-switching.md.
    2. Management network (BMC/KVM) reachability — "reachable for every first-node machine"; depends on task(cluster): verify NIC and switch-gear facts #1097's verified inventory.
    3. Egress strategy as design constraints — 2 Gbps symmetric Brightspeed edge; tunnels (Cloudflare/Turso/Tailscale) and compression documented as constraints, not implementation.
    4. Physical verification — cabling, switch install, link checks; gated on task(cluster): verify NIC and switch-gear facts #1097 and on hardware in hand.

    Verdict: keep open as the epic tracker; no fix packet is appropriate while the hardware facts are unverified. When it is scheduled, items 1 and 3 are safely workable now; items 2 and 4 start after #1097. No production code is involved. No labels were in-flight, so none were changed beyond the triage state.

  9. dezren39
    added
    queue/queuedHas a queued task in the Supabase agent queue
    source/creatorFiled by the new-issue-creator job
    task/triageQueue packet kind: verify, reproduce, and route this item
    and removed
    status/needs-triageNot yet triaged; needs a first look
    on Nov 3, 2026

  10. dezren39 commented on Nov 3, 2026

    @dezren39
    dezren39
    on Nov 3, 2026
    MemberAuthor

    agent-note:v1
    state: triaged (coverage pass)
    Coverage pass 2026-11-03: reviewed in the fleet-wide per-issue pass (drift / overlap / already-handled / stale / blockers / ordering). Verdict: still live; queued in repo-health-code-pilot as triage at priority 30 (priority/none). If this is already handled at current main, the triage closes it with evidence; if it needs splitting, the triage files the split.
    Found via: coverage pass 2026-11-03

  11. dezren39
    added
    work/assignedQueue worker lifecycle state
    queue/claimedQueue worker lifecycle state
    status/in-progressQueue worker lifecycle state
    and removed
    queue/queuedHas a queued task in the Supabase agent queue
    on Nov 4, 2026

  12. dezren39 commented on Nov 4, 2026

    @dezren39
    dezren39
    on Nov 4, 2026
    MemberAuthor

    🤖 Agent note · triaged

  13. dezren39
    removed
    status/in-progressQueue worker lifecycle state
    queue/claimedQueue worker lifecycle state
    work/assignedQueue worker lifecycle state
    on Nov 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area/infraInfrastructure, deployment, and operationseffort/lLarge: multi-day or open-ended; expect staged check-insepicMeta-issue grouping multiple items (org Project Type=Epic)meta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedmode/hybridOnline work plus a physical step (power, cabling, KVM access to a real device)source/creatorFiled by the new-issue-creator jobtask/triageQueue packet kind: verify, reproduce, and route this item

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions