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

Extend VLAN Group Scope to Include Virtualization Clusters #10860

New Issue
Closed
opened 2025-12-29 21:36:51 +01:00 by adam · 4 comments
adam commented 2025-12-29 21:36:51 +01:00
Owner
Copy Link

Originally created by @Jan-rockawayx on GitHub (Mar 7, 2025).

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

Originally created by @Jan-rockawayx on GitHub (Mar 7, 2025). ### 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_
adam added the type: feature label 2025-12-29 21:36:51 +01:00
adam closed this issue 2025-12-29 21:36:51 +01:00
adam commented 2025-12-29 21:36:51 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 13, 2025):

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?

@jeremystretch commented on GitHub (Mar 13, 2025): > 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?
adam commented 2025-12-29 21:36:52 +01:00
Author
Owner
Copy Link

@Jan-rockawayx commented on GitHub (Mar 14, 2025):

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.

@Jan-rockawayx commented on GitHub (Mar 14, 2025): > > 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.
adam commented 2025-12-29 21:36:52 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Mar 22, 2025):

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.

@github-actions[bot] commented on GitHub (Mar 22, 2025): 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.
adam commented 2025-12-29 21:36:52 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 24, 2025):

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.

@jeremystretch commented on GitHub (Mar 24, 2025): 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.
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 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#10860
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?