Skip to content

ops(lab): cluster interconnect — connect the dozen cluster machines + 2–3 mini PCs #6077

Open

Description

@dezren39

Parent: #6066 (home lab build-out).

Drew's item (2026-11-04): connect all the machines in the Kubernetes cluster — a dozen machines, plus the two or three mini PCs. This is the physical/network bring-up that the cluster setup depends on (#1086 TALM + Talos bootstrap, #1087 Cozystack platform).

  • Physical links: every cluster machine + mini PC cabled (to the new Dell switches where relevant); switch port recorded per machine
  • Addressing: IP plan for the cluster segment recorded here or linked to where it is stored
  • Switch ports configured for the cluster segment (VLAN / speed as designed)
  • Verification: every node reaches every other node — a full-mesh reachability pass, results recorded here

Machine count as stated by Drew: a dozen cluster machines + 2–3 mini PCs (exact inventory firms up on this ticket; cf. #1810 hardware inventory).

Sequencing: after the Dell switch tickets, BEFORE #1086 / #1087 cluster bring-up (see #6066).

Acceptance criteria

  • Every cluster machine and mini PC is physically cabled, with the switch port recorded per machine.
  • The IP plan for the cluster segment is recorded on this issue or linked to where it is stored.
  • Switch ports are configured for the cluster segment (VLAN / speed as designed).
  • A full-mesh reachability pass (every node reaches every other node) is run and the results recorded here.

Activity

  1. added
    kind/choreRoutine maintenance, housekeeping, dependency hygiene
    area/infraInfrastructure, deployment, and operations
    on Nov 5, 2026
  2. developing-today commented on Nov 5, 2026

    @developing-today
    Contributor
  3. added
    priority/normalOrdinary priority (the default)
    effort/lLarge: multi-day or open-ended; expect staged check-ins
    source/humanFiled directly by a human
    meta/enrichedIntake review done: acceptance criteria, links, and normalized labels added
    on Nov 5, 2026
  4. dezren39 commented on Nov 5, 2026

    @dezren39
    MemberAuthor

    Intake review

  5. added
    queue/queuedHas a queued task in the Supabase agent queue
    task/triageQueue packet kind: verify, reproduce, and route this item
    work/assignedQueue worker lifecycle state
    queue/claimedQueue worker lifecycle state
    and removed
    queue/queuedHas a queued task in the Supabase agent queue
    on Nov 5, 2026
  6. 9 remaining items

  7. developing-today commented on Nov 5, 2026

    @developing-today
    Contributor

    🤖 Agent note · handed off

  8. dezren39 commented on Nov 5, 2026

    @dezren39
    MemberAuthor

    Agent note - handed off

  9. dezren39 commented on Nov 5, 2026

    @dezren39
    MemberAuthor

    Triage — live physical dependency; keep parked

    Fresh check (2026-11-05): issue #6077 is still OPEN, has no linked PR, and all four acceptance items remain unrecorded. Checked against current �[1morigin/main�[0m �[1m8d82b73fce2edacd55fecc04effc5e5ffa9c2036�[0m: �[1mplanning/roadmaps/basement-cluster.md�[0m still marks the network fabric planned and cluster bootstrap later; �[1minfra/cluster/README.md�[0m says bare-metal work is gated on hardware inventory #1810. No evidence this interconnect work is already done or superseded.

    Scoped path: retain this as one physical bring-up ticket (no code fix or split now). Before execution, firm the host list / NICs / selected first nodes from #1810/#1080, complete the three Dell switch tickets (#6073 is blocked; #6074 and #6075 are parked), and settle the cluster segment's addressing, VLAN and link-speed design through network-fabric #1084 / NIC facts #1097. Then record a host↔NIC↔switch-port↔IP matrix, configure the ports to that design, cable the listed nodes, and attach an all-to-all reachability matrix here. Do not reuse the torn-down v1.9 address layout as the new plan.

    Ordering/blockers: #6066 sequences racking → Dell switches (#6073–#6075) → edge routing/mesh (#6067/#6068) → this interconnect → #1086 TALM/Talos and #1087 Cozystack. #1810/#1080 and #1097 are still open/blocked on hardware facts or physical access; #1084 is still open/planned. Therefore keep #6077 OPEN and parked until those prerequisites and Drew's on-site cabling/configuration window are ready. The existing intake suggestion (plan first, then cable switch-by-switch, then mesh verification) remains the right execution order.

  10. added
    queue/claimedQueue worker lifecycle state
    and removed
    queue/parkedQueue task is parked (waiting on CI, time, or an event)
    status/parkedDeliberately paused with a recorded resume condition
    on Nov 5, 2026
  11. dezren39 commented on Nov 5, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · handed off

  12. added
    queue/parkedQueue task is parked (waiting on CI, time, or an event)
    status/parkedDeliberately paused with a recorded resume condition
    and removed
    queue/claimedQueue worker lifecycle state
    on Nov 5, 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-inskind/choreRoutine maintenance, housekeeping, dependency hygienemeta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedpriority/normalOrdinary priority (the default)queue/parkedQueue task is parked (waiting on CI, time, or an event)source/humanFiled directly by a humanstatus/parkedDeliberately paused with a recorded resume conditiontask/triageQueue packet kind: verify, reproduce, and route this itemwork/assignedQueue worker lifecycle state

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions