yang: support BFD session profiles

Allow sessions to use BFD profile configurations instead of having to
clone the configuration per peer.

If using a profile and setting a peer configuration, the peer
configuration will take precedence over the profile.

Signed-off-by: Rafael Zalamena <rzalamena@opensourcerouting.org>
This commit is contained in:
Rafael Zalamena 2020-05-15 17:35:42 -03:00
parent c9157c0115
commit abf1ba08e3

View File

@ -139,6 +139,21 @@ module frr-bfdd {
}
}
typedef profile-name {
type string {
length "1..64";
}
description "Profile name format";
}
typedef profile-ref {
type leafref {
path "/frr-bfdd:bfdd/frr-bfdd:bfd/frr-bfdd:profile/frr-bfdd:name";
require-instance false;
}
description "Reference to a BFD profile";
}
/*
* Shared BFD items.
*/
@ -337,6 +352,19 @@ module frr-bfdd {
container bfd {
presence "Present if the BFD protocol is enabled";
list profile {
key "name";
description "BFD pre configuration profiles";
leaf name {
type profile-name;
description "Profile name";
}
uses session-common;
uses session-echo;
}
container sessions {
list single-hop {
key "dest-addr interface vrf";
@ -364,6 +392,11 @@ module frr-bfdd {
description "Local IP address";
}
leaf profile {
type profile-ref;
description "Override defaults with profile.";
}
uses session-common;
uses session-echo;
@ -399,6 +432,11 @@ module frr-bfdd {
description "Virtual Routing Domain name";
}
leaf profile {
type profile-ref;
description "Override defaults with profile.";
}
uses session-common;
container stats {