Description
We are currently doing this in network-pcep-topology-config.yang:
augment "/nt:network-topology/nt:topology" {
when "nt:topology-types/pn:topology-pcep";
ext:augment-identifier pcep-topology-type-config;
description "Augment Pcep topology with session config";
uses pdc:pcep-config;
}
This adds the configuration as an optional thing, where as we really want to make it required – which means it should be part of network-topology-pcep.yang's 'topology-pcep'.
Since topology-pcep is a presence container, it forms a mandatory leaf validation root, and therefore we can express exactly what we mean: things like listen-address etc. are mandatory and it is invalid to try to have a pcep-topology without those knobs.
This will simplify a lot of logic, as we can rely on datastore to enforce this invariant.
Attachments
Issue Links
- relates to
-
BGPCEP-962 Remove blueprint from pcep-impl
-
- Resolved
-
| # | Subject | Branch | Project | Status | CR | V |
|---|---|---|---|---|---|---|
| 98726,8 | Eliminate network-pcep-topology-config | master | bgpcep | Status: MERGED | +2 | +1 |
| 102407,3 | Update the payload of network-topology-pcep node | master | integration/test | Status: MERGED | +2 | +1 |