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

Virtualisation Clusters not matching Scope for VLAN Groups #4858

New Issue
Closed
opened 2025-12-29 19:21:20 +01:00 by adam · 3 comments
adam commented 2025-12-29 19:21:20 +01:00
Owner
Copy Link

Originally created by @maznu on GitHub (May 2, 2021).

NetBox version

v2.11.2

Python version

3.7

Steps to Reproduce

  1. Create a Region "UK"
  2. Create a VLAN Group "UK" with scope "UK"
  3. Create a Virtualisation Cluster in Region "UK"
  4. Look at how your Virtualisation Cluster doesn't have a Region (because they can only be in a Location)
  5. Be sad that you can't assign Interfaces on VMs in the Cluster to VLANs from the "UK" VLAN Group

Expected Behavior

  • scope a Virtualisation Cluster to a Region (not just a Location)
  • subsequently be able to choose VLANs from Groups in that Region

Observed Behavior

  • Virtualisation Cluster did not belong to any Region
  • couldn't choose VLANs from Groups in that Region (in our case, actually had no VLANs to choose from when setting VM Interfaces as Access/Tagged)
Originally created by @maznu on GitHub (May 2, 2021). ### NetBox version v2.11.2 ### Python version 3.7 ### Steps to Reproduce 1. Create a Region "UK" 2. Create a VLAN Group "UK" with scope "UK" 3. Create a Virtualisation Cluster in Region "UK" 4. Look at how your Virtualisation Cluster doesn't have a Region (because they can only be in a Location) 5. Be sad that you can't assign Interfaces on VMs in the Cluster to VLANs from the "UK" VLAN Group ### Expected Behavior * scope a Virtualisation Cluster to a Region (not just a Location) * subsequently be able to choose VLANs from Groups in that Region ### Observed Behavior * Virtualisation Cluster did not belong to any Region * couldn't choose VLANs from Groups in that Region (in our case, actually had no VLANs to choose from when setting VM Interfaces as Access/Tagged)
adam added the type: bug label 2025-12-29 19:21:20 +01:00
adam closed this issue 2025-12-29 19:21:20 +01:00
adam commented 2025-12-29 19:21:20 +01:00
Author
Owner
Copy Link

@maznu commented on GitHub (May 2, 2021):

Of course, VLAN Groups can be assigned the scope of a Virtualisation Cluster (or Cluster Group) but then:

  • that VLAN Group isn't usable by any physical infrastructure (can't blend Devices and VMs)
  • the Devices of the Cluster cannot have Interfaces which have Access/Tagged for those VLANs

Therefore would it not be more flexible to have the Scoping work the other way around? That is to say, associate the Virtualisation Cluster with a Region/Location/SIte; and associate VLAN Groups with Region/Location/Site; and then VLAN selection for Virtual Machines (within a Cluster) is the same as for Devices?

@maznu commented on GitHub (May 2, 2021): Of course, VLAN Groups _can_ be assigned the scope of a Virtualisation Cluster (or Cluster Group) but then: * that VLAN Group isn't usable by any physical infrastructure (can't blend Devices and VMs) * the Devices of the Cluster cannot have Interfaces which have Access/Tagged for those VLANs Therefore would it not be more flexible to have the Scoping work the other way around? That is to say, associate the Virtualisation Cluster with a Region/Location/SIte; and associate VLAN Groups with Region/Location/Site; and then VLAN selection for Virtual Machines (within a Cluster) is the same as for Devices?
adam commented 2025-12-29 19:21:21 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 3, 2021):

Look at how your Virtualisation Cluster doesn't have a Region (because they can only be in a Location)

Clusters can't be assigned only to sites. The region dropdown is present only to assist in the selection of a site. This is expected behavior.

scope a Virtualisation Cluster to a Region (not just a Location)

Please submit a feature request proposing this citing your specific use case.

@jeremystretch commented on GitHub (May 3, 2021): > Look at how your Virtualisation Cluster doesn't have a Region (because they can only be in a Location) Clusters can't be assigned only to sites. The region dropdown is present only to assist in the selection of a site. This is expected behavior. > scope a Virtualisation Cluster to a Region (not just a Location) Please submit a feature request proposing this citing your specific use case.
adam commented 2025-12-29 19:21:21 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 4, 2021):

Closing this out since there's nothing to under the context of a bug report, but like I said please feel free to open a FR for the proposed change.

@jeremystretch commented on GitHub (May 4, 2021): Closing this out since there's nothing to under the context of a bug report, but like I said please feel free to open a FR for the proposed change.
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: bug
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#4858
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?