Skip to content

Add Face field for Device components #9263

@sleepinggenius2

Description

@sleepinggenius2

NetBox version

v3.2.2

Feature type

Data model extension

Proposed functionality

Add a Face field like the Rack face field on Racks for Device components and templates. I was originally going to limit this to the Device Bay and Module Bay models and associated templates, but I think it would be really useful for all the device components. Unfortunately, this can't be properly done with a custom field unless #9243 is implemented. The same options that are used for Rack face, Front and Rear, would be sufficient for my immediate use case, but there might be some devices where Top, Bottom, Left, or Right would also be required. Additionally, it could be helpful to change the uniqueness constraint to be [face, name] for at least device and module bays. Having to still name things like Slot 1 (Front) and Slot 1 (Rear) seems like it would be redundant and potentially error prone. I have seen some devices with a midplane that use the same slot numbering on the front and rear.

Use case

When modeling device components, it would be really helpful to be able to specify the face on the device where that component is located. We have a number of devices where modules, interfaces, and ports are located on the front and rear of a device and we are currently doing something like Slot 1 (Rear) to indicate physically where a given module bay is located, for example. Having a standard way to apply this to not just bays, but also interfaces and ports would be very helpful when interfacing with field technicians. I know there are currently front and rear images that can be set on a device type, but it's not always practical to add those images for all device types or produce them at a high enough resolution where text can be read clearly.

This may seem a little redundant for the Front and Rear port models, but would actually be especially useful there, as I often find scenarios where those models need to be used in a particular way because of how the rear and front port models work (one to many breakout) and not because a given port is actually on the front or rear of a device.

Database changes

Add a Face field to the Device component models and templates. Possibly change the uniqueness constraint on at least device and module bays to be [face, name].

External dependencies

None

Metadata

Metadata

Assignees

No one assigned

    Labels

    pending closureRequires immediate attention to avoid being closed for inactivitystatus: under reviewFurther discussion is needed to determine this issue's scope and/or implementationtype: featureIntroduction of new functionality to the application

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions