Repository navigation
ops(lab): rack Dell switch 1 — rails, firmware, initial config, config stored, labels #6073
Description
Parent: #6066 (home lab build-out).
Drew's item (2026-11-04): rack 3 or 4 Dell switches — this is switch 1 of 3 filed (a 4th gets filed identically if it exists; see #6066).
Steps (Drew's per-switch list):
- (a) Build the rails and mount the rails; rack the switch
- (b) Update the firmware; record the firmware version on this ticket
- (c) Ensure everything works (hardware verification: ports/links, fans, management interface alive)
- (d) Build and deploy the initial config
- (e) Ensure the config is stored: switch configs live in the code repo (fleet principle: configs live in code). If no lab switch-config home exists yet, this ticket establishes one (suggested:
lab/switches/<hostname>/in developing-today/code) and records the final path here. Done = the running config is committed there and linked from this ticket - (f) Attach appropriate labels to the physical device with the label maker (hostname + role + management address)
Record on this ticket: switch model, hostname, management address, firmware version, stored-config link.
Acceptance criteria
- Switch racked: rails built and mounted, switch installed.
- Firmware updated; the firmware version recorded on this issue.
- Hardware verified: ports/links, fans, management interface alive.
- Initial config built and deployed; the running config committed to the repo's switch-config home and linked from this issue.
- Physical device labelled (hostname + role + management address); model, hostname, and management address recorded here.
Metadata
Metadata
Assignees
Labels
Infrastructure, deployment, and operationsMedium: expected under 1 day of workRoutine maintenance, housekeeping, dependency hygieneIntake review done: acceptance criteria, links, and normalized labels addedNeeds physical hands on site: build, install, cable, or configure devicesOrdinary priority (the default)Queue or user escalation stateFiled directly by a humanQueue or user escalation stateQueue packet kind: verify, reproduce, and route this itemQueue or user escalation state
Activity
developing-today commentedon Nov 5, 2026
CODE-1736
dezren39 commentedon Nov 5, 2026
Intake review
lab/switches/<hostname>/— if no switch-config home exists yet, this ticket establishes it and the siblings reuse it).dezren39 commentedon Nov 5, 2026
Task 10436 (lane code-s) claimed and assigned to the opencode execution lane. Handed off to the opencode claimant — the bound session drives this task to its terminal state. Parked by this lane per the handoff protocol.