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

Inherit VRF for child prefix from parent prefix #6012

Closed
Ordauq opened this issue Mar 18, 2021 · 3 comments
Closed

Inherit VRF for child prefix from parent prefix #6012

Ordauq opened this issue Mar 18, 2021 · 3 comments
Assignees
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@Ordauq
Copy link

Ordauq commented Mar 18, 2021

NetBox version

v2.10.6

Feature type

Change to existing functionality

Proposed functionality

When adding new child prefixes inherit VRF from parent prefix (/ipam/prefixes/add/?prefix=192.168.0.0/30)

Use case

In my environment we have many parent prefixes (container type) each of which is in different VRF.
When I or my colleagues creating new child prefix (for example /30 child in /24 parent prefix) VRF field is not inherited from parent which leads to inconsistency.
We need manually to choose right VRF for every child, otherwise it land to Global default VRF.

Database changes

I believe it not needed

External dependencies

No response

@Ordauq Ordauq added the type: feature Introduction of new functionality to the application label Mar 18, 2021
@jeremystretch
Copy link
Member

When adding new child prefixes inherit VRF from parent prefix (/ipam/prefixes/add/?prefix=192.168.0.0/30)

This is already the case when clicking the "add prefix" button when viewing a prefix within the NetBox UI: The link automatically sets the parent's VRF.

@Ordauq
Copy link
Author

Ordauq commented Mar 25, 2021

You are right, if I'm clicking on this button everything working as expected. (first available prefix is chose)
Thanks for pointing this out.

But if I'm choosing specific prefix from list it don't work.
For example, first available network is /29 (add prefix button action) but I'm want to create subnet with size /28 or more, so I'm need to find this network manually (url - /ipam/prefixes/add/?prefix=availiable_prefix/28)

@jeremystretch
Copy link
Member

This sounds similar to #5703 then.

@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application and removed type: feature Introduction of new functionality to the application labels Mar 25, 2021
@jeremystretch jeremystretch self-assigned this Mar 25, 2021
jeremystretch added a commit that referenced this issue Mar 25, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 24, 2021
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: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

No branches or pull requests

2 participants