yang: add vrf model #5492
yang: add vrf model #5492
Conversation
module: frr-vrf
+--rw lib
+--rw vrf* [name]
+--rw name string
+--rw id? uint32
Signed-off-by: Chirag Shah <chirag@cumulusnetworks.com>
💚 Basic BGPD CI results: SUCCESS, 0 tests failedResults table
For details, please contact louberger |
| @@ -0,0 +1,50 @@ | |||
| module frr-vrf { | |||
| yang-version 1.1; | |||
There was a problem hiding this comment.
As part of #5492 it is defined yang/frr-vrf.yang as it was missing. Also it seems you have raised PR against master but we are using nb_conversions branch to commit all NB changes for now.
There was a problem hiding this comment.
Created a new PR-5501 against nb_conversions brnach.
Continuous Integration Result: SUCCESSFULCongratulations, this patch passed basic tests Tested-by: NetDEF / OpenSourceRouting.org CI System CI System Testrun URL: https://ci1.netdef.org/browse/FRR-FRRPULLREQ-9977/ This is a comment from an automated CI system. clang_check |
| } | ||
| description | ||
| "VRF Id."; | ||
| } |
There was a problem hiding this comment.
I think an additional identifier could inform which vrf backend it is.
a leaf named ns_name optional, which is a string big enough to contain the path of the ns : eg: /var/run/netns/.
There was a problem hiding this comment.
I have added ns_name optional field to check if netns feature is enabled.
|
PR-5501 is created to develop in |
module: frr-vrf
+--rw lib
+--rw vrf* [name]
+--rw name string
+--rw id? uint32
Signed-off-by: Chirag Shah chirag@cumulusnetworks.com