Allow cluster to use a VM as a host device #536

New Issue

MrUnknownDE · 2026-04-05T16:40:48+02:00

MrUnknownDE commented

2026-04-05 16:40:48 +02:00

Originally created by @cryptonym64 on 1/18/2026

NetBox version

4.5

Feature type

Change to existing functionality

Proposed functionality

In clusters I cannot add a VM to the cluster as a hosting device. Example, physical hypervisor host(s) with VM's on them that then run docker inside them. If I could create a cluster to represent the docker as a "cluster", I could associate all installed docker compose instances to the docker host VM they are running on. And, as the docker VM is already in the hypervisor cluster assigned to a physical host, I'd have full tracing. As is, I have to choose, a) add the VM as a physical device (it's really a VM) and lose it's traceback to it's hypervisor, or b) not be able to associate the docker VM to the docker cluster as a host and therefore lose traceback on the docker instances assigned to that cluster. Simply allowing clusters to have VMs as "devices" would fix this I believe. Open to any ideas, but having full tracing is important.

Use case

Containerization is quickly accelerating in adoption, leaving NetBox behind in the process. In search of an all knowing system, NetBox is limiting it's uptake by not addressing real world implementations. Absent some modification to track containerized environments (nested) users cannot use this as a source of knowledge.

In truth, above is the most simplistic view. If one extends this to cloud IaaS builds there is a minumum of one or two more nested views.

Database changes

No response

External dependencies

none I can think of

*Originally created by @cryptonym64 on 1/18/2026* ### NetBox version 4.5 ### Feature type Change to existing functionality ### Proposed functionality In clusters I cannot add a VM to the cluster as a hosting device. Example, physical hypervisor host(s) with VM's on them that then run docker inside them. If I could create a cluster to represent the docker as a "cluster", I could associate all installed docker compose instances to the docker host VM they are running on. And, as the docker VM is already in the hypervisor cluster assigned to a physical host, I'd have full tracing. As is, I have to choose, a) add the VM as a physical device (it's really a VM) and lose it's traceback to it's hypervisor, or b) not be able to associate the docker VM to the docker cluster as a host and therefore lose traceback on the docker instances assigned to that cluster. Simply allowing clusters to have VMs as "devices" would fix this I believe. Open to any ideas, but having full tracing is important. ### Use case Containerization is quickly accelerating in adoption, leaving NetBox behind in the process. In search of an all knowing system, NetBox is limiting it's uptake by not addressing real world implementations. Absent some modification to track containerized environments (nested) users cannot use this as a source of knowledge. In truth, above is the most simplistic view. If one extends this to cloud IaaS builds there is a minumum of one or two more nested views. ### Database changes _No response_ ### External dependencies none I can think of

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 complexity: high complexity: high complexity: high complexity: high complexity: high complexity: high complexity: high complexity: high netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/netbox#536