Repository navigation
Open
Labels
area/infraInfrastructure, deployment, and operationsInfrastructure, deployment, and operationseffort/lLarge: multi-day or open-ended; expect staged check-insLarge: multi-day or open-ended; expect staged check-inskind/choreRoutine maintenance, housekeeping, dependency hygieneRoutine maintenance, housekeeping, dependency hygienemeta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedIntake review done: acceptance criteria, links, and normalized labels addedpriority/normalOrdinary priority (the default)Ordinary priority (the default)queue/parkedQueue task is parked (waiting on CI, time, or an event)Queue task is parked (waiting on CI, time, or an event)source/humanFiled directly by a humanFiled directly by a humanstatus/parkedDeliberately paused with a recorded resume conditionDeliberately paused with a recorded resume conditiontask/triageQueue packet kind: verify, reproduce, and route this itemQueue packet kind: verify, reproduce, and route this itemwork/assignedQueue worker lifecycle stateQueue worker lifecycle state
Description
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.
Metadata
Metadata
Assignees
Labels
area/infraInfrastructure, deployment, and operationsInfrastructure, deployment, and operationseffort/lLarge: multi-day or open-ended; expect staged check-insLarge: multi-day or open-ended; expect staged check-inskind/choreRoutine maintenance, housekeeping, dependency hygieneRoutine maintenance, housekeeping, dependency hygienemeta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedIntake review done: acceptance criteria, links, and normalized labels addedpriority/normalOrdinary priority (the default)Ordinary priority (the default)queue/parkedQueue task is parked (waiting on CI, time, or an event)Queue task is parked (waiting on CI, time, or an event)source/humanFiled directly by a humanFiled directly by a humanstatus/parkedDeliberately paused with a recorded resume conditionDeliberately paused with a recorded resume conditiontask/triageQueue packet kind: verify, reproduce, and route this itemQueue packet kind: verify, reproduce, and route this itemwork/assignedQueue worker lifecycle stateQueue worker lifecycle state
Activity
developing-today commentedon Nov 5, 2026
CODE-1740
dezren39 commentedon Nov 5, 2026
Intake review
9 remaining items
developing-today commentedon Nov 5, 2026
🤖 Agent note · handed off
dezren39 commentedon Nov 5, 2026
Agent note - handed off
ses_e5e5361a3feffek2o0GPyQH7QTdezren39 commentedon Nov 5, 2026
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.
dezren39 commentedon Nov 5, 2026
🤖 Agent note · handed off
opencodebyfleet queue lane; handed off to the opencode claimant, which launches the bound session. This lane does not work the task directly.