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

Device platform and device type platform #10128

New Issue
Closed
opened 2025-12-29 21:27:13 +01:00 by adam · 2 comments
adam commented 2025-12-29 21:27:13 +01:00
Owner
Copy Link

Originally created by @lucafabbri365 on GitHub (Aug 21, 2024).

NetBox version

v4.0.9

Feature type

Change to existing functionality

Proposed functionality

  • Assuming a device type ProLiant X from manufacturer HPE
  • Assuming the device platform VMware ESXi Y from manufacturer VMware
  • Assuming a device SRV01 created from the device type ProLiant X
  • Device SRV01 hosts VMware ESXi Y as OS

I cannot assign platform VMware ESXi Y to device SRV01; Error: The assigned platform is limited to VMware device types, but this device's type belongs to HPE.

How about allowing the assignment of a platform from a specific manufacturer (e.g. VMware) to a device created from a device type of another manufacturer (e.g. HPE) ?

Use case

In a real world I could have a device from one manufacturer (e.g. HPE) and an OS (platform) from another manufacturer (e.g. VMware or Microsoft).

Database changes

No response

External dependencies

No response

Originally created by @lucafabbri365 on GitHub (Aug 21, 2024). ### NetBox version v4.0.9 ### Feature type Change to existing functionality ### Proposed functionality - Assuming a device type **ProLiant X** from manufacturer **HPE** - Assuming the device platform **VMware ESXi Y** from manufacturer **VMware** - Assuming a device **SRV01** created from the device type ProLiant X - Device SRV01 hosts VMware ESXi Y as OS I cannot assign platform **VMware ESXi Y** to device **SRV01**; Error: _The assigned platform is limited to VMware device types, but this device's type belongs to HPE._ How about allowing the assignment of a platform from a specific manufacturer (_e.g. VMware_) to a device created from a device type of another manufacturer (_e.g. HPE_) ? ### Use case In a real world I could have a device from one manufacturer (e.g. HPE) and an OS (platform) from another manufacturer (e.g. VMware or Microsoft). ### Database changes _No response_ ### External dependencies _No response_
adam closed this issue 2025-12-29 21:27:13 +01:00
adam commented 2025-12-29 21:27:14 +01:00
Author
Owner
Copy Link

@stavr666 commented on GitHub (Aug 22, 2024):

Platform = Firmware.
We use custom field (Object: Platform type) for described case. But it's kinda inconvenient, since not visible in platform table.

Good way to fix it: add optional "Installed OS" field (like optional OOB IP) for devices with Platform selector without vendor-lock.

@stavr666 commented on GitHub (Aug 22, 2024): Platform = Firmware. We use custom field (Object: Platform type) for described case. But it's kinda inconvenient, since not visible in platform table. Good way to fix it: add optional "Installed OS" field (like optional OOB IP) for devices with Platform selector without vendor-lock.
adam commented 2025-12-29 21:27:14 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 22, 2024):

Per the documentation, the manufacturer field is used to optionally limit the device types on which a platform may be installed. For example, Cisco IOS can only be installed on Cisco devices. If this does not apply to a platform, as in your scenario, simply leave it blank.

This has been discussed in previous issues. Please remember to search closed issues before opening a new one.

@jeremystretch commented on GitHub (Aug 22, 2024): [Per the documentation](https://netboxlabs.com/docs/netbox/en/stable/models/dcim/platform/#manufacturer), the manufacturer field is used to optionally limit the device types on which a platform may be installed. For example, Cisco IOS can only be installed on Cisco devices. If this does not apply to a platform, as in your scenario, simply leave it blank. This has been discussed in previous issues. Please remember to search closed issues before opening a new one.
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
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#10128
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?