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

Add the ability to map VLANs to clusters #1797

New Issue
Closed
opened 2025-12-29 17:19:11 +01:00 by adam · 1 comment
adam commented 2025-12-29 17:19:11 +01:00
Owner
Copy Link

Originally created by @kasimon on GitHub (Jun 18, 2018).

Issue type

[X] Feature request
[ ] Bug report
[ ] Documentation

Environment

  • Python version: 2.7.13
  • NetBox version: 2.3.3

Description

In order to keep track about which vlans are available on which clusters, a mapping vlans <-> clusters would be very helpful. We are using a lot of vlans to separate subnets (several hundreds) and these are connected to different clusters. So in case there is more demand for this feature, we certainly would appreciate it.

Originally created by @kasimon on GitHub (Jun 18, 2018). ### Issue type [X] Feature request <!-- An enhancement of existing functionality --> [ ] Bug report <!-- Unexpected or erroneous behavior --> [ ] Documentation <!-- A modification to the documentation --> ### Environment * Python version: 2.7.13 * NetBox version: 2.3.3 ### Description In order to keep track about which vlans are available on which clusters, a mapping vlans <-> clusters would be very helpful. We are using a lot of vlans to separate subnets (several hundreds) and these are connected to different clusters. So in case there is more demand for this feature, we certainly would appreciate it.
adam closed this issue 2025-12-29 17:19:11 +01:00
adam commented 2025-12-29 17:19:12 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 30, 2018):

I'm going to close this out as, although it appears to be popular, there hasn't been any discussion regarding the proposed data model changes. Please feel free to resubmit this issue if you'd like to propose a detailed schema change.

@jeremystretch commented on GitHub (Nov 30, 2018): I'm going to close this out as, although it appears to be popular, there hasn't been any discussion regarding the proposed data model changes. Please feel free to resubmit this issue if you'd like to propose a detailed schema 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
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#1797
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?