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

VRF/VLAN status and VXLAN field #3384

New Issue
Closed
opened 2025-12-29 18:28:36 +01:00 by adam · 1 comment
adam commented 2025-12-29 18:28:36 +01:00
Owner
Copy Link

Originally created by @tomicke on GitHub (Feb 22, 2020).

Environment

  • Python version: 3.6.9
  • NetBox version: 2.6.7

We have started to test Netbox with our new datacenter currently being deployed and apart from documenting the installation from rack to device and VRF/VLAN/VXLAN we would like to use Netbox to provision VRF and VLAN segments and document allocated VXLAN IDs(VNI).

Proposed Functionality

I'm proposing to add status field to VRFs and complement current status field for VLANs. Currently i'm using the reserved and deprecated status choices. I would love some of the same choices you find under devices/racks.

I also propose to add a separate value field to VRF and VLANs so it is possible to document allocated VNIs

VRF:
Add status field with the following choices

  • Active
  • Planned
  • Decommissioning

VLAN:
Add more choices to current status field

  • Planned
  • Decommissioning

VXLAN:
Add extra value field for VRF/VLANs to document VNIs

Use Case

To make it possible to add/remove planned or decommissioned VRF/VLANs in production with Python/Ansible and to document the VNIs used.

Database Changes

Unknown

External Dependencies

Unknown

Originally created by @tomicke on GitHub (Feb 22, 2020). ### Environment * Python version: 3.6.9 * NetBox version: 2.6.7 We have started to test Netbox with our new datacenter currently being deployed and apart from documenting the installation from rack to device and VRF/VLAN/VXLAN we would like to use Netbox to provision VRF and VLAN segments and document allocated VXLAN IDs(VNI). ### Proposed Functionality I'm proposing to add status field to VRFs and complement current status field for VLANs. Currently i'm using the reserved and deprecated status choices. I would love some of the same choices you find under devices/racks. I also propose to add a separate value field to VRF and VLANs so it is possible to document allocated VNIs VRF: Add status field with the following choices - Active - Planned - Decommissioning VLAN: Add more choices to current status field - Planned - Decommissioning VXLAN: Add extra value field for VRF/VLANs to document VNIs ### Use Case To make it possible to add/remove planned or decommissioned VRF/VLANs in production with Python/Ansible and to document the VNIs used. ### Database Changes Unknown ### External Dependencies Unknown
adam closed this issue 2025-12-29 18:28:36 +01:00
adam commented 2025-12-29 18:28:37 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Feb 22, 2020):

I don't think it makes sense to add a status field to VRF. Neither does it make sense to add the additional status fields for VLAN (Planned, you can use reserved, Decommissioning, you can use Deprecated).

VXLAN has been asked for alot, I could see a use case for it, but if you can build up a better use case (not just "to document" as that can be done with tags) for VXLAN and perhaps flesh out a model (There have been previously discussed VXLAN issues: #3738, #2800, #1800, #1725, #1058, #825, #777) this could be something we could revisit. Keep in mind, we are pretty backlogged with only 4 maintainers with other commitments outside of this.

@DanSheps commented on GitHub (Feb 22, 2020): I don't think it makes sense to add a status field to VRF. Neither does it make sense to add the additional status fields for VLAN (Planned, you can use reserved, Decommissioning, you can use Deprecated). VXLAN has been asked for alot, I could see a use case for it, but if you can build up a better use case (not just "to document" as that can be done with tags) for VXLAN and perhaps flesh out a model (There have been previously discussed VXLAN issues: #3738, #2800, #1800, #1725, #1058, #825, #777) this could be something we could revisit. Keep in mind, we are pretty backlogged with only 4 maintainers with other commitments outside of this.
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#3384
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?