Fix wrong SR-NAI type for Path Computation 93/91093/4
authorOlivier Dugeon <olivier.dugeon@orange.com>
Fri, 10 Jul 2020 13:53:02 +0000 (15:53 +0200)
committerRobert Varga <nite@hq.sk>
Fri, 17 Jul 2020 10:19:24 +0000 (10:19 +0000)
commit7292b55abe58b83bdf76a49cc4b4bfecce9c7ffc
treec6a9154b95d88fb2a943f879f8057affc6452bef
parent4f9ccb2926ae1fafda9ca8c7b62076fcd68f08cf
Fix wrong SR-NAI type for Path Computation

When computing a segment path for PcInitiate message, the Path Computation
Algorithms produce an SR-ERO composed by Node-SIDs (NAI Type = 1 or 2).
However, routers expect a SR-ERO composed by Adjacency-SIDs
(NAI Type = 3 or 4) with M-Flag set to 1. Indeed, Node SID NAI is only valid
for loose path while Path Computation determines strict path.

This patch set change NAI (1/2) by NAI (3/4) in the SR-ERO computed by the
Path Computation Algorithms.

JIRA: BGPCEP-913

Signed-off-by: Olivier Dugeon <olivier.dugeon@orange.com>
Change-Id: Ia57b0475d764830a671f785e7444aaf37007adeb
algo/algo-api/src/main/yang/path-computation.yang
algo/algo-impl/src/main/java/org/opendaylight/algo/impl/AbstractPathComputation.java
pcep/server/server-provider/src/main/java/org/opendaylight/bgpcep/pcep/server/provider/MessagesUtil.java