Extend VLAN Group Scope to Include Virtualization Clusters

[Jan-rockawayx]

NetBox version

v4.2.4

Feature type

Change to existing functionality

Proposed functionality

Currently, VLAN Groups are scoped only to DCIM > Devices, meaning that VLANs assigned to a VLAN Group are visible only to physical devices. However, in many deployments, Clusters in Virtualization share the same infrastructure and should have visibility into the same VLANs.

I propose extending VLAN Group scope to include Virtualization > Clusters, so that VLANs assigned to a VLAN Group are available to both:

Physical devices (DCIM > Devices)
Clusters (Virtualization > Cluster) and their Virtual Machines

Suggested Implementation

Modify VLAN Group scope to allow selecting Virtualization > Cluster in addition to DCIM > Devices.
Ensure VLANs assigned to a VLAN Group are also available to Virtual Machine interfaces when the Cluster belongs to that group.
Update UI and API to reflect the new scope options.

Use case

In environments where Clusters and physical servers share the same rack, the VLAN visibility should be consistent.

This change would ensure that:

Virtual Machines within a Cluster can access the same VLANs as physical servers in the same rack.
Networking policies and VLAN assignments are more unified across physical and virtual infrastructure.

Database changes

No response

External dependencies

No response

[jeremystretch]

Currently, VLAN Groups are scoped only to DCIM > Devices

VLAN groups cannot be scoped to devices.

I propose extending VLAN Group scope to include Virtualization > Clusters

This is already supported in NetBox v4.2, and has been for some time. Are you maybe thinking of a different model, or running an older version of NetBox?

[Jan-rockawayx]

Currently, VLAN Groups are scoped only to DCIM > Devices

VLAN groups cannot be scoped to devices.

I propose extending VLAN Group scope to include Virtualization > Clusters

This is already supported in NetBox v4.2, and has been for some time. Are you maybe thinking of a different model, or running an older version of NetBox?

I apologize for the inaccurate statement.
VLAN groups do not have direct visibility into devices. However, they can see SITES, which allows me to assign VLANs to device interfaces.

VLAN groups can indeed see Virtualization > Clusters, but they cannot be scoped to multiple entities simultaneously. This means a VLAN group can be assigned to either DCIM or Virtualization, but not both at the same time.
I would like VLAN groups to be applicable to multiple entities at once so they can be used in both DCIM > Devices and Virtualization > Clusters -- allowing VM/BM interfaces to properly see the VLAN.

[github-actions]

This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically.

[jeremystretch]

I'm sorry bu the proposed change is not tenable, and would largely defeat the purpose of declaring scope assignments. Instead, you can opt to assign a scope for a group of VLANs that must span multiple domains.