-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add multitenancy support #16
Comments
Just merged #393, which implements tenancy assignment for:
I have intentionally omitted prefixes and IP addresses, as adding explicit tenant assignment for these objects could be tedious and confusing. For example if I assign a VRF to each of my customers, I don't want to also assign each prefix and IP address within those VRFs to customers. That would be redundant and error-prone. That said, it would be great if prefixes and IPs could inherit the tenant from their parent VRF (if the VRF has been assigned a tenant). More research is needed to determine whether the overhead required to support this is acceptable. |
Extended tenancy support to Prefixes and IPAddresses in e6c06b3. The inheritance seems to work well but needs additional testing. |
Many entities which might use NetBox, particularly service providers, manage networks for many different customers. Currently, NetBox does not have any concept of distinct customers or organizations. This makes it very difficult to track which devices and other resources belong to which customer.
It should be fairly easy to extend NetBox's schema to include a Tenant object. Devices, Prefixes, and other objects could then optionally be associated with a Tenant via a ForeignKey field to track multitenant installations.
The text was updated successfully, but these errors were encountered: