starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Add generic device in rack (cable managers, covers, etc) #10234

New Issue
Closed
opened 2025-12-29 21:28:42 +01:00 by adam · 5 comments
adam commented 2025-12-29 21:28:42 +01:00
Owner
Copy Link

Originally created by @Etibru on GitHub (Sep 12, 2024).

NetBox version

v4.0

Feature type

New functionality

Proposed functionality

It would be interesting to be able to add equipment to the Racks that are neither devices nor reservations. For example, grommet, cable Managers, covers, etc.
This would provide a better representation of the reality of datacenter racks

Use case

On a rack to occupy rack Units (U) but without unique modeling as could be done with devices or rack reservations.

Database changes

No response

External dependencies

No response

Originally created by @Etibru on GitHub (Sep 12, 2024). ### NetBox version v4.0 ### Feature type New functionality ### Proposed functionality It would be interesting to be able to add equipment to the Racks that are neither devices nor reservations. For example, grommet, cable Managers, covers, etc. This would provide a better representation of the reality of datacenter racks ### Use case On a rack to occupy rack Units (U) but without unique modeling as could be done with devices or rack reservations. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 21:28:42 +01:00
adam closed this issue 2025-12-29 21:28:42 +01:00
adam commented 2025-12-29 21:28:42 +01:00
Author
Owner
Copy Link

@ghost commented on GitHub (Sep 12, 2024):

you can already do that. you just create a device and leave it unnamed.
That is how we do wire managers, blanking panels, and drawers.

@ghost commented on GitHub (Sep 12, 2024): you can already do that. you just create a device and leave it unnamed. That is how we do wire managers, blanking panels, and drawers.
adam commented 2025-12-29 21:28:43 +01:00
Author
Owner
Copy Link

@Etibru commented on GitHub (Sep 12, 2024):

Yes, you're right, it can be a functional model, but from my point of view, a blanking panel, drawer or cable manager isn't really a device. Despite that, i think it's the only way to model it effectively.

@Etibru commented on GitHub (Sep 12, 2024): Yes, you're right, it can be a functional model, but from my point of view, a blanking panel, drawer or cable manager isn't really a device. Despite that, i think it's the only way to model it effectively.
adam commented 2025-12-29 21:28:43 +01:00
Author
Owner
Copy Link

@ghost commented on GitHub (Sep 12, 2024):

Yes, you're right, it can be a functional model, but from my point of view, a blanking panel, drawer or cable manager isn't really a device. Despite that, i think it's the only way to model it effectively.

https://demo.netbox.dev/static/docs/core-functionality/devices/

Every piece of hardware which is installed within a site or rack exists in NetBox as a device.

Not saying your point of view is wrong, but NetBox's point of view is clear.

@ghost commented on GitHub (Sep 12, 2024): > Yes, you're right, it can be a functional model, but from my point of view, a blanking panel, drawer or cable manager isn't really a device. Despite that, i think it's the only way to model it effectively. https://demo.netbox.dev/static/docs/core-functionality/devices/ > Every piece of hardware which is installed within a site or rack exists in NetBox as a device. Not saying your point of view is wrong, but NetBox's point of view is clear.
adam commented 2025-12-29 21:28:43 +01:00
Author
Owner
Copy Link

@alehaa commented on GitHub (Sep 12, 2024):

I think this was already discussed in https://github.com/netbox-community/netbox/issues/16308.

@alehaa commented on GitHub (Sep 12, 2024): I think this was already discussed in https://github.com/netbox-community/netbox/issues/16308.
adam commented 2025-12-29 21:28:43 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 13, 2024):

It has been raised several times. As has been discussed in previous issues, there is no substantial difference between the cited objects and other devices. They can be modeled in NetBox as unnamed devices quite easily.

@jeremystretch commented on GitHub (Sep 13, 2024): It has been raised several times. As has been discussed in previous issues, there is no substantial difference between the cited objects and other devices. They can be modeled in NetBox as unnamed devices quite easily.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#10234
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?