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

Platform manufacturer should not depend on hardware manufacturer #5750

New Issue
Closed
opened 2025-12-29 19:32:12 +01:00 by adam · 1 comment
adam commented 2025-12-29 19:32:12 +01:00
Owner
Copy Link

Originally created by @damiankaczkowski on GitHub (Dec 9, 2021).

NetBox version

v3.0.11

Feature type

Change to existing functionality

Proposed functionality

Some devices can be loaded with software (netbox platform) from different manufacturers.

For example Cumulus Linux compatible devices: https://www.nvidia.com/en-us/networking/ethernet-switching/hardware-compatibility-list/

But the list expands for many more devices which can load any x86_64 software like pfsense or any other firewall or similar software.

The same goes for more generic devices like servers which can be loaded with Red Hats RHEL, Canonical Ubuntu, Microsoft Windows and so on.

So in other words Hardware Manufacturer != Software Manufacturer (netbox platform).

Unfortunately netbox limits available platform choices according to selected device manufacturer, which is wrong assumption imo. It works for Cisco, Juniper but not for device vendors that allows the device to be loaded with different vendor software.

NetBox should change behavior and split the hardware to platform manufacturer dependency.

The only way to workaround this right now is to not fill any manufacturer in the platform configuration, which is just .... counter-intuitive imo.

Use case

User is not limited to netbox dependency model and he can create the real life scenarios where for example the Dell device is loaded with NVIDIAs software/platform.

Database changes

No response

External dependencies

No response

Originally created by @damiankaczkowski on GitHub (Dec 9, 2021). ### NetBox version v3.0.11 ### Feature type Change to existing functionality ### Proposed functionality Some devices can be loaded with software (netbox platform) from different manufacturers. For example Cumulus Linux compatible devices: https://www.nvidia.com/en-us/networking/ethernet-switching/hardware-compatibility-list/ But the list expands for many more devices which can load any x86_64 software like pfsense or any other firewall or similar software. The same goes for more generic devices like servers which can be loaded with Red Hats RHEL, Canonical Ubuntu, Microsoft Windows and so on. So in other words Hardware Manufacturer != Software Manufacturer (netbox platform). Unfortunately netbox limits available platform choices according to selected device manufacturer, which is wrong assumption imo. It works for Cisco, Juniper but not for device vendors that allows the device to be loaded with different vendor software. NetBox should change behavior and split the hardware to platform manufacturer dependency. The only way to workaround this right now is to not fill any manufacturer in the platform configuration, which is just .... **counter-intuitive** imo. ### Use case User is not limited to netbox dependency model and he can create the **real life scenarios** where for example the Dell device is loaded with NVIDIAs software/platform. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 19:32:12 +01:00
adam closed this issue 2025-12-29 19:32:12 +01:00
adam commented 2025-12-29 19:32:12 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 9, 2021):

Unfortunately netbox limits available platform choices according to selected device manufacturer, which is wrong assumption imo. It works for Cisco, Juniper but not for device vendors that allows the device to be loaded with different vendor software.

The assignment of a platform to a manufacturer is entirely optional. In such cases, you simply don't make the assignment, and there is no limitation.

@jeremystretch commented on GitHub (Dec 9, 2021): > Unfortunately netbox limits available platform choices according to selected device manufacturer, which is wrong assumption imo. It works for Cisco, Juniper but not for device vendors that allows the device to be loaded with different vendor software. The assignment of a platform to a manufacturer is entirely optional. In such cases, you simply don't make the assignment, and there is no limitation.
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#5750
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?