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

A way to separate the IPAM Object by environments #7619

New Issue
Closed
opened 2025-12-29 20:26:06 +01:00 by adam · 2 comments
adam commented 2025-12-29 20:26:06 +01:00
Owner
Copy Link

Originally created by @eprothon on GitHub (Feb 8, 2023).

NetBox version

v3.4.4

Feature type

New functionality

Proposed functionality

We need to have a real way to separate the IPAM’s objects between our different environments PROD/STAGING/DEV.

Use case

We use a unique instance of Netbox to configure our different datacenters. Our developers use Netbox also to manage our different isolated environments PROD/STAGING/DEV with overlap of prefix and IP addresses.
In this context, we need to have a real way to separate the IPAM’s objects between the different environments.
We have tried to use tenant-groups and tenants without success. We have also tried VRF as a way to achieve this separation.
However, such VRF is only useful for the user interface in Netbox but is confusing for operators as it does not really represent the reality and they should not configure it.

Database changes

No response

External dependencies

No response

Originally created by @eprothon on GitHub (Feb 8, 2023). ### NetBox version v3.4.4 ### Feature type New functionality ### Proposed functionality We need to have a real way to separate the IPAM’s objects between our different environments PROD/STAGING/DEV. ### Use case We use a unique instance of Netbox to configure our different datacenters. Our developers use Netbox also to manage our different isolated environments PROD/STAGING/DEV with overlap of prefix and IP addresses. In this context, we need to have a real way to separate the IPAM’s objects between the different environments. We have tried to use tenant-groups and tenants without success. We have also tried VRF as a way to achieve this separation. However, such VRF is only useful for the user interface in Netbox but is confusing for operators as it does not really represent the reality and they should not configure it. ### Database changes _No response_ ### External dependencies _No response_
adam closed this issue 2025-12-29 20:26:06 +01:00
adam commented 2025-12-29 20:26:06 +01:00
Author
Owner
Copy Link

@stavr666 commented on GitHub (Feb 8, 2023):

Combination of VRF, VLAN and Tenant does not work for you either? We have no separate dev network right now, but planning to do so.

Can you show example screenshots of artefacts (from Demo), that you experience, when use filters with both Tenant and VRF defined? For operators you can limit visibility by either of this 3 options, afaik.

@stavr666 commented on GitHub (Feb 8, 2023): Combination of VRF, VLAN and Tenant does not work for you either? We have no separate dev network right now, but planning to do so. Can you show example screenshots of artefacts (from Demo), that you experience, when use filters with both Tenant and VRF defined? For operators you can limit visibility by either of this 3 options, afaik.
adam commented 2025-12-29 20:26:07 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 8, 2023):

Converting this to a discussion as no specific implementation has been proposed.

@jeremystretch commented on GitHub (Feb 8, 2023): Converting this to a discussion as no specific implementation has been proposed.
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#7619
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?