A way to separate the IPAM Object by environments

[eprothon]

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

[stavr666]

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.

[jeremystretch]

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