Closes #12024: Allow Virtual Machines to be assigned directly to Devices #101

New Issue

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

MrUnknownDE commented

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

Originally created by @pheus on 3/23/2026

Fixes: #12024

Summary

This PR allows virtual machines to be assigned directly to a standalone device, without requiring a cluster. Previously, a VM could only be placed on a site or within a cluster (with an optional device pin). This adds a third placement mode: direct assignment to a device that doesn't belong to any cluster.

Changes

Model (VirtualMachine)

A VM can now be assigned to a site, a cluster, a standalone device, or a combination (e.g. cluster + device pin)
Site is automatically inherited from the assigned cluster or device when not explicitly set
If a device belongs to a cluster, the cluster must still be specified on the VM
Added device-scoped uniqueness constraints (name must be unique per device and tenant for standalone assignments)

Forms

Updated VirtualMachineForm, VirtualMachineImportForm, and VirtualMachineBulkEditForm with descriptive help texts for the site, cluster, and device fields

Documentation

Updated model docstring, virtualmachine.md model docs, and virtualization.md feature page to describe all three placement modes
Added "New in NetBox v4.6" callout for the standalone device feature

Tests

Added comprehensive test coverage for all valid and invalid placement combinations, standalone device assignment, name uniqueness per device, site auto-inheritance, tenant scoping, and case-insensitive name checks

*Originally created by @pheus on 3/23/2026* ### Fixes: #12024 ### Summary This PR allows virtual machines to be assigned directly to a standalone device, without requiring a cluster. Previously, a VM could only be placed on a site or within a cluster (with an optional device pin). This adds a third placement mode: direct assignment to a device that doesn't belong to any cluster. ### Changes **Model (`VirtualMachine`)** - A VM can now be assigned to a site, a cluster, a standalone device, or a combination (e.g. cluster + device pin) - Site is automatically inherited from the assigned cluster or device when not explicitly set - If a device belongs to a cluster, the cluster must still be specified on the VM - Added device-scoped uniqueness constraints (name must be unique per device and tenant for standalone assignments) **Forms** - Updated `VirtualMachineForm`, `VirtualMachineImportForm`, and `VirtualMachineBulkEditForm` with descriptive help texts for the site, cluster, and device fields **Documentation** - Updated model docstring, `virtualmachine.md` model docs, and `virtualization.md` feature page to describe all three placement modes - Added "New in NetBox v4.6" callout for the standalone device feature **Tests** - Added comprehensive test coverage for all valid and invalid placement combinations, standalone device assignment, name uniqueness per device, site auto-inheritance, tenant scoping, and case-insensitive name checks

MrUnknownDE closed this issue

2026-04-05 16:21:41 +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#101