Closes #5795: Add Virtual Machine Type model #73

New Issue

MrUnknownDE · 2026-04-05T16:21:29+02:00

MrUnknownDE commented

2026-04-05 16:21:29 +02:00

Originally created by @pheus on 3/26/2026

Fixes: #5795

This PR introduces VirtualMachineType to classify virtual machines and provide default values for platform, vCPUs, and memory when a VM is created.

We chose the classification + create-time defaults approach here because it adds practical value beyond metadata alone, while keeping the scope well-defined. It solves the immediate need to model VM types natively in NetBox and avoids overloading Platform, without jumping straight into full DeviceType-style templating for interfaces and disks.

Defaults are only applied at creation time, explicit values on the VM always take precedence, and updating a VirtualMachineType does not retroactively change existing virtual machines.

The implementation includes the new model and its relationship to VirtualMachine, along with support across forms, filtersets, tables, views, the REST API, GraphQL, navigation, search, documentation, and tests.

The design is also intended to leave the door open for a more template-oriented approach in the future if there is a stronger need to model VMInterface and VirtualDisk templates as well.

*Originally created by @pheus on 3/26/2026* ### Fixes: #5795 This PR introduces `VirtualMachineType` to classify virtual machines and provide default values for platform, vCPUs, and memory when a VM is created. We chose the **classification + create-time defaults** approach here because it adds practical value beyond metadata alone, while keeping the scope well-defined. It solves the immediate need to model VM types natively in NetBox and avoids overloading `Platform`, without jumping straight into full `DeviceType`-style templating for interfaces and disks. Defaults are only applied at creation time, explicit values on the VM always take precedence, and updating a `VirtualMachineType` does not retroactively change existing virtual machines. The implementation includes the new model and its relationship to `VirtualMachine`, along with support across forms, filtersets, tables, views, the REST API, GraphQL, navigation, search, documentation, and tests. The design is also intended to leave the door open for a more template-oriented approach in the future if there is a stronger need to model `VMInterface` and `VirtualDisk` templates as well.

MrUnknownDE closed this issue

2026-04-05 16:21:29 +02:00

Sign in to join this conversation.

Branches Tags

main

21455-sql-indexes-audit

21357-register-model-actions

feature

20924-plugin-ui-components

21766-improve-test-coverage-for-sortable-table-columns

21157-export-template-public-models

21025-pre-render-config-contexts

21364-swagger

feature-ip-prefix-link

20911-dropdown-3

fix_module_substitution

21160-filterset

20911-dropdown-2

20044-elevation-stuck-lightmode

7604-filter-modifiers-v3

20660-script-load

19724-graphql

14884-script

19720-macaddress-interface-generic-relation

fix-19669-api-image-download

7604-filter-modifiers

19275-fixes-interface-bulk-edit

fix-17794-get_field_value_return_list

11507-show-aggregate-and-rir-on-api

9583-add_column_specific_search_field_to_tables

No Label

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/netbox#73