Fix rear-face image-only labels, click-to-add units, cable concept devices

- 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>
This commit is contained in:
2026-09-16 10:18:50 +02:00
co-authored by Claude Sonnet 5
parent e4817ea83b
commit 63538c2efe
24 changed files with 1293 additions and 33 deletions
+29
View File
@@ -59,3 +59,32 @@ class WidthFractionChoices(ChoiceSet):
# Least common multiple of all supported denominators. The elevation is laid out
# on this many lanes so that every fraction lands on an integer lane boundary.
LANE_COUNT = 12
class ConceptComponentTypeChoices(ChoiceSet):
"""
The kinds of pluggable component a planned device can carry. One shared model
covers all of them (see ConceptComponent) rather than mirroring dcim's seven
separate component models - a blueprint only needs enough detail to say what a
cable plugs into, not full per-type validation.
"""
TYPE_INTERFACE = 'interface'
TYPE_FRONT_PORT = 'front-port'
TYPE_REAR_PORT = 'rear-port'
TYPE_CONSOLE_PORT = 'console-port'
TYPE_CONSOLE_SERVER_PORT = 'console-server-port'
TYPE_POWER_PORT = 'power-port'
TYPE_POWER_OUTLET = 'power-outlet'
CHOICES = [
(TYPE_INTERFACE, 'Interface', 'blue'),
(TYPE_FRONT_PORT, 'Front port', 'orange'),
(TYPE_REAR_PORT, 'Rear port', 'yellow'),
(TYPE_CONSOLE_PORT, 'Console port', 'teal'),
(TYPE_CONSOLE_SERVER_PORT, 'Console server port', 'cyan'),
(TYPE_POWER_PORT, 'Power port', 'red'),
(TYPE_POWER_OUTLET, 'Power outlet', 'pink'),
]
#: Component types that are pass-through ports and can appear in a ConceptPortMapping.
PATCH_TYPES = (TYPE_FRONT_PORT, TYPE_REAR_PORT)