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 Tenancy Support to VLAN Group #10605

New Issue
Closed
opened 2025-12-29 21:33:36 +01:00 by adam · 0 comments
adam commented 2025-12-29 21:33:36 +01:00
Owner
Copy Link

Originally created by @sleepinggenius2 on GitHub (Jan 3, 2025).

Originally assigned to: @arthanson on GitHub.

NetBox version

v4.2-beta1

Feature type

Data model extension

Triage priority

N/A

Proposed functionality

Add the tenant field to the VLANGroup model to support tenancy. Ideally, show the tenant with an "*" appended in the Tenant column on the VLAN table for a VLAN that is not explicitly assigned to a Tenant, but inherited from its group, just like is done with the IPAddress table when its Prefix has an assigned Tenant.

Use case

The VLAN model already supports tenancy, so it's curious why the VLANGroup model does not. When using a VLANGroup to document the VLANs on an ENNI, it would be useful to also associate the group to a Tenant and not just the VLAN members under it. This would also allow for additional validation opportunities, like it could be enforced that the Tenant set on the VLAN and VLANGroup match (I think it makes sense to leave this as a custom validation opportunity). We added a custom field for this in our environment today, but that has the limitation that when you go to the details page for a Tenant, it is not listed under the related objects.

Database changes

Add nullable tenant ForeignKey to tenancy.Tenant.

External dependencies

None

Originally created by @sleepinggenius2 on GitHub (Jan 3, 2025). Originally assigned to: @arthanson on GitHub. ### NetBox version v4.2-beta1 ### Feature type Data model extension ### Triage priority N/A ### Proposed functionality Add the `tenant` field to the `VLANGroup` model to support tenancy. Ideally, show the tenant with an "*" appended in the `Tenant` column on the `VLAN` table for a `VLAN` that is not explicitly assigned to a `Tenant`, but inherited from its group, just like is done with the `IPAddress` table when its `Prefix` has an assigned `Tenant`. ### Use case The `VLAN` model already supports tenancy, so it's curious why the `VLANGroup` model does not. When using a `VLANGroup` to document the VLANs on an ENNI, it would be useful to also associate the group to a `Tenant` and not just the `VLAN` members under it. This would also allow for additional validation opportunities, like it could be enforced that the `Tenant` set on the `VLAN` and `VLANGroup` match (I think it makes sense to leave this as a custom validation opportunity). We added a custom field for this in our environment today, but that has the limitation that when you go to the details page for a `Tenant`, it is not listed under the related objects. ### Database changes Add nullable `tenant` ForeignKey to `tenancy.Tenant`. ### External dependencies None
adam added the status: acceptedtype: featurecomplexity: medium labels 2025-12-29 21:33:37 +01:00
adam closed this issue 2025-12-29 21:33:37 +01:00
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 complexity: medium 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#10605
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?