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

Serial number field for Virtual machines #5513

New Issue
Closed
opened 2025-12-29 19:28:51 +01:00 by adam · 7 comments
adam commented 2025-12-29 19:28:51 +01:00
Owner
Copy Link

Originally created by @pmusolino-rms on GitHub (Oct 13, 2021).

Originally assigned to: @arthanson on GitHub.

NetBox version

v3.0.7

Feature type

Data model extension

Proposed functionality

Would it be possible to add a serial number field to virtual machines? I know it could certainly be added as a custom field, but many network devices as they exist in either public/private cloud or vm clusters still retain serial numbers for licensing and seems to be something that could be a standard but not required field.

Use case

Exporting data and inventory/licensing tracking of non physical devices.

Database changes

New field to Virtual machine table

External dependencies

No response

Originally created by @pmusolino-rms on GitHub (Oct 13, 2021). Originally assigned to: @arthanson on GitHub. ### NetBox version v3.0.7 ### Feature type Data model extension ### Proposed functionality Would it be possible to add a serial number field to virtual machines? I know it could certainly be added as a custom field, but many network devices as they exist in either public/private cloud or vm clusters still retain serial numbers for licensing and seems to be something that could be a standard but not required field. ### Use case Exporting data and inventory/licensing tracking of non physical devices. ### Database changes New field to Virtual machine table ### External dependencies _No response_
adam added the status: acceptedtype: featurecomplexity: low labels 2025-12-29 19:28:52 +01:00
adam closed this issue 2025-12-29 19:28:52 +01:00
adam commented 2025-12-29 19:28:52 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 14, 2021):

This doesn't sound quite natural to me. The term "serial" implies a succession of unique identifiers which never get repeated. This is feasible and common for hardware because the manufacturer serves the authority for allocating serial numbers, however there is no such authority for virtual machines and thus no guarantee of order or uniqueness. Curious to hear from others.

@jeremystretch commented on GitHub (Oct 14, 2021): This doesn't sound quite natural to me. The term "serial" implies a succession of unique identifiers which never get repeated. This is feasible and common for hardware because the manufacturer serves the authority for allocating serial numbers, however there is no such authority for virtual machines and thus no guarantee of order or uniqueness. Curious to hear from others.
adam commented 2025-12-29 19:28:52 +01:00
Author
Owner
Copy Link

@ziggekatten commented on GitHub (Oct 14, 2021):

Well, closest thing in the virtual world are the UUID, wich is the unique identifier of a VM and are sometimes of significant importance.

For example, cloning a VM yields a new UUID on the cloned VM.

We use a custom field for this, and it is good enough for our purpouses, ensuring uniqueness in various systems and automation flows.

@ziggekatten commented on GitHub (Oct 14, 2021): Well, closest thing in the virtual world are the UUID, wich is the unique identifier of a VM and are sometimes of significant importance. For example, cloning a VM yields a new UUID on the cloned VM. We use a custom field for this, and it is good enough for our purpouses, ensuring uniqueness in various systems and automation flows.
adam commented 2025-12-29 19:28:52 +01:00
Author
Owner
Copy Link

@rodvand commented on GitHub (Nov 2, 2021):

I can see a use case for this. More and more functionality is moving from hardware appliances to virtual appliances and the vendors tend to stick to their "everything needs a license" model. So my virtual Palo Alto firewall has a serial number, and I can see the value in recording this. Not sure if the use case is "wide" enough to warrant a separate field encompassing all virtual machines, but I've definitely thought about it.

@rodvand commented on GitHub (Nov 2, 2021): I can see a use case for this. More and more functionality is moving from hardware appliances to virtual appliances and the vendors tend to stick to their "everything needs a license" model. So my virtual Palo Alto firewall has a serial number, and I can see the value in recording this. Not sure if the use case is "wide" enough to warrant a separate field encompassing all virtual machines, but I've definitely thought about it.
adam commented 2025-12-29 19:28:53 +01:00
Author
Owner
Copy Link

@aauerswald commented on GitHub (Nov 1, 2022):

Hello,

please add the serial field to virtual machines. At the moment we use a custom field, but this is not searchable.

@aauerswald commented on GitHub (Nov 1, 2022): Hello, please add the serial field to virtual machines. At the moment we use a custom field, but this is not searchable.
adam commented 2025-12-29 19:28:53 +01:00
Author
Owner
Copy Link

@ryanmerolle commented on GitHub (Apr 25, 2023):

This could be a good candidate for 3.6

@ryanmerolle commented on GitHub (Apr 25, 2023): This could be a good candidate for 3.6
adam commented 2025-12-29 19:28:53 +01:00
Author
Owner
Copy Link

@tagur87 commented on GitHub (Aug 13, 2023):

I also agree that this would be a helpful field for virtual machines. We are starting to migrate our VPN devices from physical hardware to virtual appliances. These virtual appliances (Ivanti Connect Secure) have serial numbers that are used for registration with the vendor. We have other vendors that also do this...(kemp, clearpass, etc).

I would be willing to try to add this field, since it seems fairly straightforward to add to the VM model.

@tagur87 commented on GitHub (Aug 13, 2023): I also agree that this would be a helpful field for virtual machines. We are starting to migrate our VPN devices from physical hardware to virtual appliances. These virtual appliances (Ivanti Connect Secure) have serial numbers that are used for registration with the vendor. We have other vendors that also do this...(kemp, clearpass, etc). I would be willing to try to add this field, since it seems fairly straightforward to add to the VM model.
adam commented 2025-12-29 19:28:53 +01:00
Author
Owner
Copy Link

@tagur87 commented on GitHub (Aug 14, 2023):

Anyone opposed to aiming at 3.7 for a milestone? I worked up a simple prototype yesterday mirroring the field used in devices.

Any concerns with me working on that?

@tagur87 commented on GitHub (Aug 14, 2023): Anyone opposed to aiming at 3.7 for a milestone? I worked up a simple prototype yesterday mirroring the field used in devices. Any concerns with me working on that?
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 complexity: low status: accepted 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#5513
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?