- Fix "images only" leaving plain labels visible on faces where a
device has no image for that side (e.g. no rear_image set): the
view selector now hides every plain label outright in that mode,
not just the ones an image happens to sit on top of.
- Remove the "Add planned device" button from the elevation card.
Empty units are now click targets themselves - clicking one opens
the add-device form pre-filled with that position and face, exactly
like a real rack's elevation. Occupancy is computed per unit per
face from the existing device blocks.
- Add cabling for concept devices: ConceptComponent (interfaces,
front/rear ports, power ports/outlets, console ports) and
ConceptCable (a connection between two components, restricted to
devices in the same concept). components.sync_components()
populates a device's components from its device type's templates,
including the front/rear port pass-through mapping copied from
DeviceType.port_mappings - so a device with front/rear port
templates (a patch panel being the common case) behaves exactly
like a real one, without hardcoding anything role-specific.
Placeholder devices without a device type get components added by
hand. Full CRUD views, tables, filtersets, API endpoints and a
"Connect" action wired in from the device detail page.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Introduces a NetBox 4.6 plugin for planning rack layouts (RackConcept,
ConceptDevice) without creating real dcim.Rack/dcim.Device objects, so
blueprints never appear in rack/device lists, utilization reports, or
IPAM.
Features:
- Copy paths: real rack -> concept, concept -> concept (clone), and
concept -> one or more real racks (deploy, with name patterning and
dry-run support)
- Manual concept creation via a dedicated "Rack Concepts" nav menu
- Tenant and tenant group assignment on concepts and planned devices
- Partial-width device placement (1/1-1/4) with slot-based collision
detection, matching netbox_utilities' partial-width feature
- Custom drag-and-drop elevation (netbox-reorder-rack operates on real
Device querysets, which concepts don't have) with server-side
validation of every move
- Full REST API, filtering, CSV import, bulk edit, search integration
- Optional, config-driven interop with netbox_utilities (partial-width
field mapping) and netbox-reorder-rack, degrading gracefully when
either plugin is absent
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
MrBlakeandClaude Sonnet 5