-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Router pim config #16269
Router pim config #16269
Conversation
oh god that diff size T_T … |
pimd/pim_cmd_common.h
Outdated
* that VTY_CURR_XPATH is correct and/or uses relative paths, and at | ||
* the end vty is moved back to the original node and xpath popped | ||
*/ | ||
#define START_PIM_DEPRECATED(clinode) \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When and how are we going to get rid of this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, it could go away now, but I'd say once it's been long enough that no body remembers the previous PIM syntax then this stuff can be removed.
|
||
if (pim->vrf->vrf_id == VRF_DEFAULT) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is the indentation off now, for router pim blocks inside VRFs?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
VRF-aware PIM configuration is also at the top level.
router pim
...
router pim vrf blue
...
Yeah. I tried different ways to ALIAS the commands but couldn't get it to work so I essentially had to duplicate all of the global PIM commands. Also all of the pim global xpath's have been touched, since now the current XPath is set and commands use relative paths. |
Documentation needs to be updated to reflect the new syntax. |
fb6fb8e
to
f6ab303
Compare
cce7ba2
to
91c3882
Compare
Fixed these warnings now. |
pimd/pim_cmd_common.c
Outdated
continue; | ||
|
||
snprintfrr(framestr, sizeof(framestr), "router pim%s", | ||
(PIM_AF == AF_INET6 ? "6" : "")); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Common code between pim and pim6. PIM_AF == AF_INET6
triggers
WARNING: Comparisons should place the constant on the right side of the test
The warning is trigged regardless of the order, a rare use case.
848eb56
to
6776a28
Compare
Moved all existing global/vrf PIM config to the new subnode. Existing configuration updated to be hidden and deprecated. Both versions of configuration still work together. Signed-off-by: Nathan Bahr <[email protected]>
41409c2
to
ffbc081
Compare
Fix load from file in frr-reload to detect and convert legacy pim configuration so that the tool can continue to be used with legacy configurations. Signed-off-by: Nathan Bahr <[email protected]>
Document 'router pim[6] [vrf NAME]' configuration. All the commands are basically the same, just dropped the 'ip pim[6]' prefix and document them under the router pim block. Signed-off-by: Nathan Bahr <[email protected]>
ffbc081
to
b58592d
Compare
Added a fix to frr-reload to detect and convert legacy pim configuration so that the tool works as expected. I reverted the changes to topotests so they are all back to using the legacy pim configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good
Added new 'router pim[6] [vrf NAME]' config node.
Moved all existing global/vrf PIM configs to the new subnode and the existing configuration was set to be hidden and deprecated.
Both versions of the configuration still work together for the time being until they can be safely removed.
PIM now always writes out configuration in the "router pim" syntax so ,in order to support frr-reload, the JSON based configuration in the PIM topotests also needs to generate configuration in the same syntax.
Config file style tests are left in the global pim configuration syntax for now as a test of backwards compatibility.
Fixes #16196