forked from cisagov/Malcolm
-
Notifications
You must be signed in to change notification settings - Fork 59
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
use prefix.description instead of VRF for identifying subnets in NetBox #280
Comments
mmguero
added a commit
to mmguero-dev/Malcolm
that referenced
this issue
Oct 31, 2023
…ox (idaholab#280); needs testing
mmguero
added a commit
to mmguero-dev/Malcolm
that referenced
this issue
Nov 1, 2023
mmguero
added a commit
to mmguero-dev/Malcolm
that referenced
this issue
Nov 16, 2023
…me to ipam_prefix.description
mmguero
added a commit
to mmguero-dev/Malcolm
that referenced
this issue
Nov 16, 2023
…me to ipam_prefix.description (todo, need to do it in regular startup)
mmguero
added a commit
to mmguero-dev/Malcolm
that referenced
this issue
Nov 22, 2023
This was referenced Dec 4, 2023
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
My original understanding of what a VRF is was incorrect, and I now think that using it as the way to tie a name to a Prefix was a mistake.
I think it would be better to use just the ipam/prefixes data model and to use
description
to store the name rather than do what we're currently doing.This will inconvenience some existing users as they'll have to go fill in the prefix descriptions. Perhaps on initialization we could do that for them manually, though, if a prefix exists, its description is empty, and it has a VRF associated with it.
The text was updated successfully, but these errors were encountered: