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

Be capable of adding multiple disks to VMs #6732

New Issue
Closed
opened 2025-12-29 19:44:35 +01:00 by adam · 4 comments
adam commented 2025-12-29 19:44:35 +01:00
Owner
Copy Link

Originally created by @Spezi2u on GitHub (Jul 28, 2022).

NetBox version

v3.2.5

Feature type

Data model extension

Proposed functionality

A VM is usually today what Hardware was 10 years ago. So it may have one or more disks and one or more nics. While we are able today to input the later into netbox, we are still fixed on just one storage device.

It would be great if we could add multiple disks each differing in size and quality. The disk size field today could be used a sum field for the total storage.

Maybe it is possible to think about storage devices in general and adding them as for instance components

Use case

Documenting the real world is what netbox does. I know netbox is not fixated on storage but those can be also network devices so why not?

Why would you need this. If you are using netbox to document your real world maybe you want to do capacity planing maybe you want to invoice disksizes with different qualities, etc.

Database changes

probably

External dependencies

none that I know of

Originally created by @Spezi2u on GitHub (Jul 28, 2022). ### NetBox version v3.2.5 ### Feature type Data model extension ### Proposed functionality A VM is usually today what Hardware was 10 years ago. So it may have one or more disks and one or more nics. While we are able today to input the later into netbox, we are still fixed on just one storage device. It would be great if we could add multiple disks each differing in size and quality. The disk size field today could be used a sum field for the total storage. Maybe it is possible to think about storage devices in general and adding them as for instance components ### Use case Documenting the real world is what netbox does. I know netbox is not fixated on storage but those can be also network devices so why not? Why would you need this. If you are using netbox to document your real world maybe you want to do capacity planing maybe you want to invoice disksizes with different qualities, etc. ### Database changes probably ### External dependencies none that I know of
adam added the type: featurestatus: revisions needed labels 2025-12-29 19:44:35 +01:00
adam closed this issue 2025-12-29 19:44:35 +01:00
adam commented 2025-12-29 19:44:36 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 1, 2022):

probably

Please elaborate on what specific implementation you're proposing.

@jeremystretch commented on GitHub (Aug 1, 2022): > probably Please elaborate on what specific implementation you're proposing.
adam commented 2025-12-29 19:44:36 +01:00
Author
Owner
Copy Link

@PieterL75 commented on GitHub (Aug 1, 2022):

looks like #8356 could cover this request

@PieterL75 commented on GitHub (Aug 1, 2022): looks like #8356 could cover this request
adam commented 2025-12-29 19:44:36 +01:00
Author
Owner
Copy Link

@Spezi2u commented on GitHub (Aug 7, 2022):

#8356 is in principal the same thing I want. but as discribed in the ongoing discussion of that same issue, maybe VMs should have their own inventory model. Since if I'm understanding it correctly you are using the device NIC model for VMs today since it doesn't not really change from hw.

@Spezi2u commented on GitHub (Aug 7, 2022): [#8356](https://github.com/netbox-community/netbox/issues/8356) is in principal the same thing I want. but as discribed in the ongoing discussion of that same issue, maybe VMs should have their own inventory model. Since if I'm understanding it correctly you are using the device NIC model for VMs today since it doesn't not really change from hw.
adam commented 2025-12-29 19:44:36 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 10, 2022):

As no further detail has been provided by OP, I'm going to close this out. I invite you to share your use case on #8356 as it seems likely to address your need.

@jeremystretch commented on GitHub (Aug 10, 2022): As no further detail has been provided by OP, I'm going to close this out. I invite you to share your use case on #8356 as it seems likely to address your need.
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 status: revisions needed 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#6732
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?