Add VLAN and VLAN Group to Config Context Form

[i3D-RyanHamel]

NetBox version

3.3.10

Feature type

Data model extension

Proposed functionality

Add VLAN and VLAN group fields to the Config Context creation form, to narrow down the scope of where overrides or specific configuration need to be, and not worth adding custom metadata fields to VLANs.

Use case

For my employer, it would provide more granularity in enforcing specific limitations on VLANs like IPv6 neighbor limits, VXLAN MAC IP table limits (Junos bug), for customers that have a history of abusing and taking up TCAM on a router.

The idea here is using NetBox as a UI to allow engineers to write up a set of rules for our Ansible automation to take into consideration, allowing the automation team to write a framework once in processing these rules, instead of writing edge cases into various Jinja templates or playbooks.

Database changes

Requires adding VLAN and VLAN Group fields.

External dependencies

No response

[DanSheps]

This might be blocked by #14451, depending on specifics around implementation as there is nothing currently directly linking a device to a vlan. You would need to operate on either making broad assumptions about what VLAN is on a specific device or look at all vlans tagged and untagged on a device.

[i3D-RyanHamel]

You would need to operate on either making broad assumptions about what VLAN is on a specific device or look at all vlans tagged and untagged on a device.

For my environment, it would be limited to a cluster and device role ("Core Router" for example) which would shrink the scope quite significantly.

[jeremystretch]

Blocked by #14451