-
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
Interface to VRF Associations #7852
Comments
We probably don't want to enforce any validation around this, especially since it would prevent users from assigning any VRF IPs to an interface until that interface has been assigned to a VRF. I also imagine some users will prefer to assign only IPs or only interfaces to VRFs. Also custom validation is an option now for users who may want to enforce this. |
I agree with your logic. |
Closes #7852: Interface VRF assignment
NetBox version
v3.0.10
Feature type
Data model extension
Proposed functionality
Enable interface to VRF mapping.
Use case
Generally NetBox should support most base functions an interface supports. One obvious function missing in the current model is the ability to map interfaces to a VRF.
I do not know we can rush in to this without first discussing if and how should IP assignment be limited be associated to an interface only if they are both in the same VRF. This constraint could be challenging to implement given the current IP model. I think at the very least the MVP would just allow interfaces to be associated to a VRF without any constraints on IP assignments.
Database changes
No response
External dependencies
No response
The text was updated successfully, but these errors were encountered: