Skip to content
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

Closed
ryanmerolle opened this issue Nov 17, 2021 · 2 comments
Closed

Interface to VRF Associations #7852

ryanmerolle opened this issue Nov 17, 2021 · 2 comments
Assignees
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Milestone

Comments

@ryanmerolle
Copy link
Contributor

ryanmerolle commented Nov 17, 2021

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

@ryanmerolle ryanmerolle added the type: feature Introduction of new functionality to the application label Nov 17, 2021
@jeremystretch
Copy link
Member

jeremystretch commented Nov 17, 2021

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.

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.

@jeremystretch jeremystretch added the needs milestone Awaiting prioritization for inclusion with a future NetBox release label Nov 17, 2021
@ryanmerolle
Copy link
Contributor Author

I agree with your logic.

@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation and removed needs milestone Awaiting prioritization for inclusion with a future NetBox release labels Dec 8, 2021
@jeremystretch jeremystretch added this to the v3.2 milestone Dec 8, 2021
@jeremystretch jeremystretch self-assigned this Jan 6, 2022
jeremystretch added a commit that referenced this issue Jan 7, 2022
This was referenced Apr 5, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 8, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Projects
None yet
Development

No branches or pull requests

2 participants