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

Show available VLAN IDs within a group #775

New Issue
Closed
opened 2025-12-29 16:25:42 +01:00 by adam · 6 comments
adam commented 2025-12-29 16:25:42 +01:00
Owner
Copy Link

Originally created by @ktims on GitHub (Mar 17, 2017).

Feature request to show available VLAN IDs within a group, similar to the way available prefixes are shown in aggregates/parent prefixes. Currently allocating a new VLAN requires manually browsing the list to find an available ID, remembering it, and manually entering in the Add a VLAN form. It would be nice to streamline this.

Originally created by @ktims on GitHub (Mar 17, 2017). Feature request to show available VLAN IDs within a group, similar to the way available prefixes are shown in aggregates/parent prefixes. Currently allocating a new VLAN requires manually browsing the list to find an available ID, remembering it, and manually entering in the Add a VLAN form. It would be nice to streamline this.
adam added the status: acceptedtype: feature labels 2025-12-29 16:25:42 +01:00
adam closed this issue 2025-12-29 16:25:42 +01:00
adam commented 2025-12-29 16:25:42 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 17, 2017):

How would you display this? Could you provide a mock-up?

@jeremystretch commented on GitHub (Mar 17, 2017): How would you display this? Could you provide a mock-up?
adam commented 2025-12-29 16:25:43 +01:00
Author
Owner
Copy Link

@ktims commented on GitHub (Mar 17, 2017):

Sure, I'm imagining something very much like what exists when viewing a prefix on the IP addresses tab. I guess this would involve creating a new view for VLAN groups, rather than just linking to the VLAN search. I've mocked something up based on the mentioned prefix page (my math probably suffers from off-by-one errors). Add a VLAN would default to the first available VLAN ID, and clicking one of the 'available' links would default to the first available ID within that range, like how it works for IPs/prefixes.
netbox-vlans-mockup

@ktims commented on GitHub (Mar 17, 2017): Sure, I'm imagining something very much like what exists when viewing a prefix on the IP addresses tab. I guess this would involve creating a new view for VLAN groups, rather than just linking to the VLAN search. I've mocked something up based on the mentioned prefix page (my math probably suffers from off-by-one errors). Add a VLAN would default to the first available VLAN ID, and clicking one of the 'available' links would default to the first available ID within that range, like how it works for IPs/prefixes. ![netbox-vlans-mockup](https://cloud.githubusercontent.com/assets/1471533/24025607/ac234fca-0a78-11e7-9f81-0a08eeb12fc3.png)
adam commented 2025-12-29 16:25:43 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 17, 2017):

Oh, ok. I thought you were talking about inserting the VLAN list in the form somehow. I like it.

@jeremystretch commented on GitHub (Mar 17, 2017): Oh, ok. I thought you were talking about inserting the VLAN list in the form somehow. I like it.
adam commented 2025-12-29 16:25:43 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 28, 2017):

Thinking about this further, we don't have a view for VLANGroup because it's not a primary object. (It's used only for the organization of primary objects.) Not sure we really want to deviate from that pattern.

@jeremystretch commented on GitHub (Mar 28, 2017): Thinking about this further, we don't have a view for VLANGroup because it's not a primary object. (It's used only for the organization of primary objects.) Not sure we really want to deviate from that pattern.
adam commented 2025-12-29 16:25:43 +01:00
Author
Owner
Copy Link

@Senetus commented on GitHub (Nov 3, 2017):

For auto-allocation it would be awesome to get this info via an API call.

@Senetus commented on GitHub (Nov 3, 2017): For auto-allocation it would be awesome to get this info via an API call.
adam commented 2025-12-29 16:25:44 +01:00
Author
Owner
Copy Link

@mmahacek commented on GitHub (Jul 28, 2018):

How would this know what VLANs to show as available? You assign a group to a VLAN, not the other way around. A VLAN group is for organization inside Netbox and for filtering the drop down lists. There isn't a specific assumption of what VLANS should be in the group to determine what is missing, unless you are checking the site's entered VLANs against all possible VLAN IDs.

@mmahacek commented on GitHub (Jul 28, 2018): How would this know what VLANs to show as available? You assign a group to a VLAN, not the other way around. A VLAN group is for organization inside Netbox and for filtering the drop down lists. There isn't a specific assumption of what VLANS should be in the group to determine what is missing, unless you are checking the site's entered VLANs against all possible VLAN IDs.
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: accepted 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#775
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?