5 Commits

Include renames

Author	SHA1	Message	Date
jaredandClaude Opus 5.5	f655836446	Add a rack drawing (/rack) ... The rack front is drawn from the rack units on cutsheet items. Switches with a faceplate use it, with live port state; patch panels get a generic panel with port labels; everything else is a labelled plate. Each documented port shows its cutsheet state, and hovering a port lights up every port on the same cable run (through patch panels) and names the cables. Clicking opens the switch port or the cable. Overlapping items and items past the top of the rack are listed instead of drawn over another; where two claim the same top unit, the first one recorded wins. rack.units sets the height (default 42). /api/rack builds on the cutsheet view; cutsheet.rack_layout and cutsheet.port_marks hold the placement and per-port logic. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-10 20:59:30 -05:00
jaredandClaude Opus 5.5	c262e5ecc8	Inventory links, cutsheet marks on faceplates, and single page titles ... Device pages get an Inventory button: it opens the device's HomeBox record once an admin pastes its URL (stored in the new device_links table; only URLs on inventory.base_url are accepted), and searches the inventory for the model until then. Tickets link the record too. Faceplate ports with a documented cable get a corner dot: green matches, red mismatch, grey documented but unconfirmed. The port's tooltip names the cable, and a legend toggle (remembered per browser) hides them. Page titles no longer repeat GANDALF ("Alert History - GANDALF - GANDALF"). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-10 20:47:14 -05:00
jaredandClaude Opus 5.5	86aa29b378	Cutsheet trace mode and mismatch alerts ... Trace a cord: pick a panel port, press Start, and unplug the cord at the panel. The page polls a new admin-only endpoint that reads every switch port's state from UniFi (cached 2 s), shows the one port that dropped with a button to record the cable, and confirms when it's plugged back in. Several ports dropping at once, or none within 3 minutes, is explained rather than guessed at. Mismatch alerts: the monitor runs the cutsheet check every poll. Each mismatched installed run (wrong neighbor, no link, missing port, port conflict) keeps one cable_mismatch event on its switch, resolved when fixed, and opens a P4 ticket after cutsheet.mismatch_ticket_hours (default 24, 0 never). Suppressing the switch or port stops the ticket. Also fixes buttons with the hidden attribute still showing, which left a Delete button on the new-cable form. Closes #12 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-10 16:54:57 -05:00
jaredandClaude Opus 5.5	52cfea5439	Cutsheet: show the next free cable ID as a hint, not a placeholder ... A placeholder of C01 in the empty ID field looked like a real value. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-10 16:10:51 -05:00
jaredandClaude Opus 5.5	b9412ff6ba	Add cutsheets: planned cabling checked against discovery ... A new Cutsheet page records where every cable is meant to go and compares it with what Gandalf discovers. - Inventory for what discovery can't see: patch panels, wall jacks, shelves and rack positions. Panels and jacks pass through front to rear. - Cables with two endpoints, ID, type, length, color, status (planned, installed, dark, retired) and notes; the far end may be unterminated. - Each cable's full run is traced through panels and jacks, and runs ending on a switch port are checked against its discovered neighbor (LLDP, client table, or a DAC serial seen at both ends): matches, wrong neighbor, no link, missing port, port conflict, unverified, idle. - Undocumented links: live switch ports no cable mentions, one click to add with what Gandalf already knows. Port panels show the planned cable. - Labels to make: cable IDs and panel-port labels not yet applied, with a print view, for a handheld label maker. - CSV export, and all-or-nothing import that upserts by cable ID. - Cables, panels and jacks appear in the dashboard search. Editing needs the admin group and a JSON request body. Every change is written to cutsheet_history in the same transaction. Tables are created on first use. Refs #12 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-10 16:05:08 -05:00