summaryrefslogtreecommitdiff
path: root/yang/ietf
AgeCommit message (Collapse)Author
2024-08-18*: Spelling issuesDonald Sharp
Signed-off-by: Donald Sharp <sharpd@nvidia.com>
2024-07-22yang: Added missed prefix to the yang fileY Bharath
Corrected warning by including the module Signed-off-by: y-bharath14 <y.bharath@samsung.com>
2024-03-03yang: modify standard modelChristian Hopps
We need to operate w/o cryptographic algorithm during key creation due to how our legacy CLI works (each command issuing a single YANG modification). Signed-off-by: Christian Hopps <chopps@labn.net>
2024-03-01yang: Add initial model and generated code.Christian Hopps
Signed-off-by: Christian Hopps <chopps@labn.net>
2024-01-31yang: add more ietf modelsIgor Ryzhov
These models are needed to use LYD_PRINT_WD_ALL_TAG flag of libyang. Signed-off-by: Igor Ryzhov <iryzhov@nfware.com>
2021-11-23lib, yang: remove vrf from the interface list keyIgor Ryzhov
This is needed for the following two reasons: 1. To be able to remove the northbound HACK in if_update_to_new_vrf. It is totally wrong to rewrite the configuration datastore when some operational state changes. It is a hard blocker for storing a configuration data in a management daemon which knows nothing about the operational state. 2. To allow changing the VRF of the interface using FRR CLI or any other frontend in the future. If the VRF is a part of the key, it can't be changed. If the VRF is a simple leaf, it becomes possible to change it and thus move the interface between VRFs. For now I mark the leaf as a "config false" as it's not yet possible to control it from FRR. But we can't simply remove the VRF from the key, because it is needed to distinguish interfaces when using netns based VRFs, as it is possible to have multiple interfaces with the same name in different namespaces. To handle this, I came up with an idea to store both VRF and an interface name in the "name" leaf using the pattern "vrfname:ifname". For example, if there's an interface "eth0" in VRF "red" then its "name" leaf will be "red:eth0". Signed-off-by: Igor Ryzhov <iryzhov@nfware.com>
2020-08-14bgpd: yang definationvdhingra
Yang files for bgpd to use northbound APIs Co-authored-by: Santosh P K <sapk@vmware.com> Co-authored-by: vishaldhingra <vdhingra@vmware.com> Signed-off-by: vishaldhingra <vdhingra@vmware.com>
2020-04-16yang: add ietf interface yang modelChirag Shah
Add ietf interface yant model. Also include it in the makefile. Signed-off-by: Chirag Shah <chirag@cumulusnetworks.com>
2020-03-25*: use the current project name (FRRouting)Lou Berger
Signed-off-by: Lou Berger <lberger@labn.net>
2019-10-09yang: add ietf routing types moduleChirag Shah
Signed-off-by: Chirag Shah <chirag@cumulusnetworks.com>
2019-01-18yang: sync the IETF module translator with the latest frr-ripd changesRenato Westphal
Signed-off-by: Renato Westphal <renato@opensourcerouting.org>
2018-10-27yang: add a module translator for ietf-rip.yangRenato Westphal
As it can be seen below, this translator covers only ~13% of the ietf-rip YANG module. Work must be done to increase that number. ripd> en ripd# conf t ripd(config)# yang module-translator load /tmp/frr-ietf-translator.json % Module translator "ietf" loaded successfully. ripd(config)# do show yang module-translator Family Module Deviations Coverage (%) ----------------------------------------------------------------------- ietf ietf-interfaces frr-deviations-ietf-interfaces 3.92 ietf ietf-routing frr-deviations-ietf-routing 1.56 ietf ietf-rip frr-deviations-ietf-rip 13.60 Signed-off-by: Renato Westphal <renato@opensourcerouting.org>