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

Allow VLAN Group hierarchy with specific scopes #7849

New Issue
Closed
opened 2025-12-29 20:28:59 +01:00 by adam · 2 comments
adam commented 2025-12-29 20:28:59 +01:00
Owner
Copy Link

Originally created by @BrunoBlanes on GitHub (Apr 1, 2023).

NetBox version

v3.4.5

Feature type

Change to existing functionality

Proposed functionality

Propose to expand the current VLAN Group model to allow nesting to itself given specific scopes. See Use case section for better understanding.

Use case

We as an ISP have VLAN Groups for dedicated link clients. We use this group throughout our network in all of our sites therefore it is scoped to the major region that we cover. However, within this region and group, we have subsets of VLAN Groups specific to the sites present in this region.

Consider the VLAN Group A being scoped to region USA and having a range set as 1000-2000. This range is only to be used for dedicated link clients in major cities. This range is then subdivided into smaller ranges for each major city.

I'd like to be able to create a VLAN Group B that belongs to group A and is instead scoped to a site or region belonging to the region USA or to some region that has a child relationship with the USA region, i.e. Florida, and has a range that is limited, but not necessarily equal to, its parent range, i.e. 2100-2050.

Database changes

Unsure, but definitely some major relationship additions, it shouldn't break any existing ones or be a breaking change.

External dependencies

No response

Originally created by @BrunoBlanes on GitHub (Apr 1, 2023). ### NetBox version v3.4.5 ### Feature type Change to existing functionality ### Proposed functionality Propose to expand the current VLAN Group model to allow nesting to itself given specific scopes. See *Use case* section for better understanding. ### Use case We as an ISP have VLAN Groups for dedicated link clients. We use this group throughout our network in all of our sites therefore it is scoped to the major region that we cover. However, within this region and group, we have subsets of VLAN Groups specific to the sites present in this region. Consider the VLAN Group `A` being scoped to region `USA` and having a range set as `1000-2000`. This range is only to be used for dedicated link clients in major cities. This range is then subdivided into smaller ranges for each major city. I'd like to be able to create a VLAN Group `B` that belongs to group `A` and is instead scoped to a site or region belonging to the region `USA` or to some region that has a child relationship with the `USA` region, i.e. `Florida`, and has a range that is limited, but not necessarily equal to, its parent range, i.e. `2100-2050`. ### Database changes Unsure, but definitely some major relationship additions, it shouldn't break any existing ones or be a breaking change. ### External dependencies _No response_
adam added the type: featurestatus: revisions needed labels 2025-12-29 20:28:59 +01:00
adam closed this issue 2025-12-29 20:28:59 +01:00
adam commented 2025-12-29 20:28:59 +01:00
Author
Owner
Copy Link

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

Unsure, but definitely some major relationship additions, it shouldn't break any existing ones or be a breaking change.

I'm sorry but you're going to need to provide much more detail about the proposed implementation. A use case alone is not sufficient. If you're unsure of what to propose, please consider closing this FR and starting a discussion instead to collaborate with others who may be able to help devise an implementation.

@jeremystretch commented on GitHub (May 4, 2023): > Unsure, but definitely some major relationship additions, it shouldn't break any existing ones or be a breaking change. I'm sorry but you're going to need to provide much more detail about the proposed implementation. A use case alone is not sufficient. If you're unsure of what to propose, please consider closing this FR and starting a [discussion](https://github.com/netbox-community/netbox/discussions/new/choose) instead to collaborate with others who may be able to help devise an implementation.
adam commented 2025-12-29 20:28:59 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 25, 2023):

This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.

@jeremystretch commented on GitHub (Jul 25, 2023): This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.
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 status: revisions needed 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#7849
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?