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

Inventory for Device Types #1070

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

Originally created by @MrEsL on GitHub (Jul 2, 2017).

Hello,

We have lots of Chassis servers that are "parents" and we attach to their device bays servers that are configured as children.

Our problem is that we would like to add information to each of the children (cpu,ram,disks), the only way to do that is through adding inventory to each individual server.

Is there a way to add inventory to Device Types? that way each child will inherit the proper inventory.

Edit: On another topic.. I saw a issue someone opened regarding editing device types and it not updating current devices. Is this planned to be an option in the near future?

It doesn't make sense to build 100+ devices then adding an interface or the likes in the device type, and having to update each device individually.

Thank you.

Originally created by @MrEsL on GitHub (Jul 2, 2017). Hello, We have lots of Chassis servers that are "parents" and we attach to their device bays servers that are configured as children. Our problem is that we would like to add information to each of the children (cpu,ram,disks), the only way to do that is through adding inventory to each individual server. Is there a way to add inventory to Device Types? that way each child will inherit the proper inventory. Edit: On another topic.. I saw a issue someone opened regarding editing device types and it not updating current devices. Is this planned to be an option in the near future? It doesn't make sense to build 100+ devices then adding an interface or the likes in the device type, and having to update each device individually. Thank you.
adam closed this issue 2025-12-29 16:28:31 +01:00
adam commented 2025-12-29 16:28:31 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 5, 2017):

Our problem is that we would like to add information to each of the children (cpu,ram,disks), the only way to do that is through adding inventory to each individual server.

NetBox isn't designed to function as an asset management system. While it has the ability to track device components for inventory purposes, it is primarily an IPAM/DCIM application. The inventory data is intended to be populated programmatically via the API or other means. It wouldn't make sense to define components like CPUs and hard disks under the device type, because you'll still need to glean unique data from each individual device.

It doesn't make sense to build 100+ devices then adding an interface or the likes in the device type, and having to update each device individually.

It does make sense. You define all built-in console/power/interface components on the device type, which serves as a template for instantiating real devices. Then you can add removable components to those individual devices as appropriate. Also note that you can add components to devices in bulk.

@jeremystretch commented on GitHub (Jul 5, 2017): > Our problem is that we would like to add information to each of the children (cpu,ram,disks), the only way to do that is through adding inventory to each individual server. NetBox isn't designed to function as an asset management system. While it has the ability to track device components for inventory purposes, it is primarily an IPAM/DCIM application. The inventory data is intended to be populated programmatically via the API or other means. It wouldn't make sense to define components like CPUs and hard disks under the device type, because you'll still need to glean unique data from each individual device. > It doesn't make sense to build 100+ devices then adding an interface or the likes in the device type, and having to update each device individually. It does make sense. You define all built-in console/power/interface components on the device type, which serves as a template for instantiating real devices. Then you can add removable components to those individual devices as appropriate. Also note that you can add components to devices in bulk.
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#1070
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?