14 Commits

Include renames

Author	SHA1	Message	Date
jaredandClaude Opus 5.5	7408b1feca	Rack: Sliger fronts in red, white and blue, and the UniFi brush panel ... From the rack photo on the wiki, the three Sligers have their coloured perforated fronts fitted, not the faceplate-off view: Front drawings "Sliger CX4712 4U, red/white/blue front" draw the hex-perforated panel (about 20 rows of holes, the drive cages faint behind it), black rack ears, the power button with Gandalf's status ring, and the USB recess. UniFi UACC-Rack-Panel-Brush-1U is drawn from Ubiquiti's product images: silver face, ear plates with rounded slots, a recessed chamfered frame and two rows of bristles meeting at a seam. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-11 01:51:29 -05:00
jaredandClaude Opus 5.5	3bc8df6dc7	Tests: wrap a long line ... Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-11 01:08:52 -05:00
jaredandClaude Opus 5.5	d8e827c88b	Rack: gear resting on other gear, and live desk switches on shelves ... A USW Flex Mini lies on top of the NVR. A shelf item with Front drawing "No shelf: gear resting on what is below" draws no tray or ears, so its contents sit directly on the item under it. UniFi desk switches on a shelf (Flex Mini, Flex) are drawn with their live faceplate, scaled to their real width from Ubiquiti's tech specs (107 mm and 122.5 mm), with working ports. faceplateSvg() returns a faceplate's SVG on its own so it can be placed inside the shelf drawing. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-11 01:08:42 -05:00
jared	0243b23732	Merge remote-tracking branch 'origin/main' into zimaboard-and-facing ... # Conflicts: # static/style.css # tests/test_cutsheet.py	2026-11-11 00:46:13 -05:00
jaredandClaude Opus 5.5	a9de175d90	Rack: ports-facing separate from posts, three views, ZimaBoard 832 shelves to scale ... Gear on the rear posts usually still faces the front (the StarTech's RPDU and ZimaBoard shelf), so "which posts" and "which way the ports face" are now separate fields (mount, facing). The page has three views: Front (front posts), Rear posts (rear-post gear seen from the front, i.e. what is behind the front gear) and Rear (from behind). An item seen from the side it doesn't face shows its back. Facing defaults to front, so existing items keep their meaning. Shelves are drawn at true scale with their contents ordered by a new "Position on shelf". The IceWhale ZimaBoard 832 is traced from IceWhale's labelled photo of its port end (ZimaDocs): Mini-DP, two RJ45-over-USB 3.0 stacks with link/activity LEDs, DC jack, gunmetal case, gold PCB edge and black base. Its RJ45 link lights follow the host's physical NICs and the status glow follows the host. New cutsheet_items columns facing and slot, added on first use. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-11 00:12:07 -05:00
jaredandClaude Opus 5.5	ce12dede5f	Faceplates: USW Pro Max 24 PoE and 48 PoE ... Both laid out from the CC0 NetBox devicetype-library images, with jack centres measured from them: the 24 has one row of 24 RJ45 in groups of 8 (17-24 at 2.5G) and 2 SFP+; the 48 has two rows, odd ports on top, in groups of 16 (33-48 at 2.5G) and 4 SFP+ (49-52). The "2.5G" and "10G" bars under the faster ports are drawn too (fpSpeedBar). Registered as USPM24P/USPM48P with USPM24/USPM48 aliases, and as Front drawing options so the new switch draws on the rack before it is adopted. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-11 00:01:12 -05:00
jaredandClaude Opus 5.5	50db56cdcb	Rack: draw the UniFi UACC blank 24-port keystone patch panel ... Front drawing "UniFi Patch Panel Blank 24" draws the real panel, laid out from the CC0 NetBox devicetype-library image: grey steel face, darker ears with oval holes, 24 keystone openings with the cable-support bar behind them, and a cable slot at each end. Ports with a documented cable get a keystone jack; cutsheet marks, port labels and run highlighting work as on the generic panel. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-10 23:39:27 -05:00
jaredandClaude Opus 5.5	619a2c913d	Remove em and en dashes from the UI, code and docs ... Page titles read "Rack | GANDALF", ranges use a hyphen (U26-42, 1-100 of 300), empty cells show "-", and dash-separated phrases use a colon, comma or full stop. In the shared base.js only the on-screen strings changed (boot line, placeholders, offline banner and toast). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-10 23:37:56 -05:00
jaredandClaude Opus 5.5	0f4e129c20	Rack: drawn fronts for the NVR and server cases ... Items Gandalf has no live faceplate for can pick a Front drawing: the UniFi NVR Pro (drawn from the CC0 NetBox devicetype-library image), the Sliger CX4712 4U and Rosewill RSV-L4500U 4U cases (from driveAtlas's layouts), and generic 1U/2U/4U servers. The power light shows the linked device's live status. They export with the rest of the rack. New cutsheet_items column chassis, added on first use. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-10 23:25:02 -05:00
jaredandClaude Opus 5.5	c50e1f8322	Rack: front and rear mounting, rack settings in the page ... Items are mounted from the front, the rear, or full depth. On a 4-post rack a front and a rear item can share a unit; a full-depth one takes both sides, and the rear view shows its back. Overlaps are checked per side. Shelf contents take the shelf's side. A Front / Rear switch flips the drawing. Racks are saved in Gandalf (new cutsheet_racks table) and edited on the rack page by admins: name, height, notes, add and delete. Renaming moves the rack's items; saving the first rack carries over the items of the config default it replaces. Config racks remain the fallback. Faceplates are stretched to the full width only when the drawing is close to the slot's proportions, so the PDU is not squashed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-10 22:35:37 -05:00
jaredandClaude Opus 5.5	bdd68a397d	Rack: link items to devices, shelves, several racks, export; fix layout and light mode ... Cutsheet items gain a "Gandalf device" link, so an item named after the product (UDM-Pro) shows the live device's faceplate, ports and status. Cable checks, suggestions, tickets and the device page treat an item and its linked device as one. Without this, product-named items drew as bare name plates. Items can sit on a shelf instead of a rack unit; the shelf draws what is on it with live status. Items have a rack, the page shows a tab per rack (config "racks"), and a rack can be downloaded as SVG or PNG. The rack is centred, long runs of empty units fold into one band (with a toggle), every device fills the 19" width, the UPS shows its front only, and the rack keeps its own palette so it reads in light mode. New cutsheet_items columns rack, shelf and device are added on first use. Deleting a shelf, or making it something else, is refused while it holds items; renaming it carries over. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-10 21:44:59 -05:00
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	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	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