Skip to content

Commit 5efb50e

Browse files
nigel-r-davisnigel-r-davis
authored
Merge pull request #664 from nigel-r-davis/tapi-2_5_0-fixes
Ready for TAPI v2.5.2 delivery.
2 parents fe4d0f5 + e9529b4 commit 5efb50e

29 files changed

Lines changed: 14578 additions & 14169 deletions

‎YANG/TapiTree.tree‎

Lines changed: 14232 additions & 13943 deletions
Large diffs are not rendered by default.

‎YANG/tapi-common.yang‎

Lines changed: 23 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -2,30 +2,38 @@ module tapi-common {
22
yang-version "1.1";
33
namespace "urn:onf:otcc:yang:tapi-common";
44
prefix tapi-common;
5-
organization "ONF OTCC (Open Transport Configuration & Control) Project";
5+
organization "Linux Foundation ONMI (Open Network Modeling and Interfaces) Project";
66
contact "
7-
Project Web: <https://wiki.opennetworking.org/display/OTCC/TAPI>
8-
Project List: <mailto:transport-api@opennetworking.org>
9-
Editor: Karthik Sethuraman <mailto:karthik.sethuraman@necam.com>
10-
Andrea Mazzini <mailto:andrea.mazzini@nokia.com>
11-
Arturo Mayoral <mailto:arturo.mayoral@telefonica.com>
12-
Nigel Davis <mailto:ndavis@ciena.com>
7+
Project Web: <https://github.com/Open-Network-Models-and-Interfaces-ONMI/onmi-home/wiki>
8+
Project List: <mailto:onmi-tapi@googlegroups.com>
9+
Editor: Nigel Davis <mailto:ndavis@ciena.com>
10+
Arturo Mayoral <mailto:amayoral@telecominfraproject.com>
1311
Ramon Casellas <mailto:ramon.casellas@cttc.es>";
1412
description "
1513
This module contains TAPI Common Model definitions.
1614
Source: TapiCommon.uml
1715
- The TAPI YANG models included in this TAPI release are a *normative* part of the TAPI SDK.
18-
- The YANG specifications have been generated from the corresponding UML model using the [ONF EAGLE UML2YANG mapping tool]
19-
<https://github.com/OpenNetworkingFoundation/EagleUmlYang>
20-
and further edited manually to comply with the [ONF IISOMI UML2YANG mapping guidelines]
21-
<https://wiki.opennetworking.org/display/OIMT/IISOMI+Deliverables>
16+
- The YANG specifications have been generated from the corresponding UML model using the [EAGLE UML2YANG mapping tool]
17+
<https://github.com/Open-Network-Models-and-Interfaces-ONMI/onmi-iisomi-uml-yang>
18+
and further edited manually to comply with the [ONMI IISOMI UML2YANG mapping guidelines]
19+
<https://github.com/Open-Network-Models-and-Interfaces-ONMI/onmi-iisomi-home>
2220
- Status of YANG model artifacts can be determined by referring to the corresponding UML artifacts.
2321
As described in the UML models, some artifacts are considered *experimental*, and thus the corresponding YANG artifacts.
24-
- The ONF TAPI release process does not guarantee backward compatibility of YANG models across major versions of TAPI releases.
22+
- The LF ONMI TAPI release process does not guarantee backward compatibility of YANG models across major versions of TAPI releases.
2523
The YANG model backward compatibility criteria are outlined in section 11 of <https://tools.ietf.org/html/rfc7950>.
26-
YANG models included in this release may not be backward compatible with previous TAPI releases.
27-
Copyright (c) 2023 Open Networking Foundation (ONF). All rights reserved.
24+
YANG models included in this release may not be backward compatible with some previous TAPI releases.
25+
- Previous revisions can now be found at https://github.com/Open-Network-Models-and-Interfaces-ONMI/TAPI under the
26+
appropriate tag and, where relevant, fixes to those revisions can be found under the corresponding branches. The documentation for
27+
each significant revision is found at https://github.com/Open-Network-Models-and-Interfaces-ONMI/TAPI-Documentation under the
28+
appropriate tag and, where relevant, fixes to those revisions can be found under the corresponding branches.
2829
License: This module is distributed under the Apache License 2.0.";
30+
revision 2025-12-31 {
31+
description "LF ONMI Transport API version 2.5.2
32+
Changes included in this TAPI release (v2.5.2) are listed in
33+
<https://github.com/Open-Network-Models-and-Interfaces-ONMI/TAPI-Documentation/tree/v2.5.2/DeltaDocument>";
34+
reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and LF ONMI TAPI UML model
35+
<https://github.com/Open-Network-Models-and-Interfaces-ONMI/TAPI/tree/v2.5.2/UML>";
36+
}
2937
revision 2023-10-10 {
3038
description "ONF Transport API version 2.5.0.
3139
Changes included in this TAPI release (v2.5.0) are listed in
@@ -145,6 +153,7 @@ module tapi-common {
145153
leaf service-interface-point-uuid {
146154
type leafref {
147155
path '/tapi-common:context/tapi-common:service-interface-point/tapi-common:uuid';
156+
require-instance false;
148157
}
149158
description "none";
150159
}

‎YANG/tapi-connectivity.tree‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
1-
21
module: tapi-connectivity
2+
33
augment /tapi-common:context:
44
+--rw connectivity-context
55
+--rw connectivity-service* [uuid]

‎YANG/tapi-connectivity.yang‎

Lines changed: 22 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -17,30 +17,38 @@ module tapi-connectivity {
1717
import tapi-notification {
1818
prefix tapi-notification;
1919
}
20-
organization "ONF OTCC (Open Transport Configuration & Control) Project";
20+
organization "Linux Foundation ONMI (Open Network Modeling and Interfaces) Project";
2121
contact "
22-
Project Web: <https://wiki.opennetworking.org/display/OTCC/TAPI>
23-
Project List: <mailto:transport-api@opennetworking.org>
24-
Editor: Karthik Sethuraman <mailto:karthik.sethuraman@necam.com>
25-
Andrea Mazzini <mailto:andrea.mazzini@nokia.com>
26-
Arturo Mayoral <mailto:arturo.mayoral@telefonica.com>
27-
Nigel Davis <mailto:ndavis@ciena.com>
22+
Project Web: <https://github.com/Open-Network-Models-and-Interfaces-ONMI/onmi-home/wiki>
23+
Project List: <mailto:onmi-tapi@googlegroups.com>
24+
Editor: Nigel Davis <mailto:ndavis@ciena.com>
25+
Arturo Mayoral <mailto:amayoral@telecominfraproject.com>
2826
Ramon Casellas <mailto:ramon.casellas@cttc.es>";
2927
description "
3028
This module contains TAPI Connectivity Model definitions.
3129
Source: TapiConnectivity.uml
3230
- The TAPI YANG models included in this TAPI release are a *normative* part of the TAPI SDK.
33-
- The YANG specifications have been generated from the corresponding UML model using the [ONF EAGLE UML2YANG mapping tool]
34-
<https://github.com/OpenNetworkingFoundation/EagleUmlYang>
35-
and further edited manually to comply with the [ONF IISOMI UML2YANG mapping guidelines]
36-
<https://wiki.opennetworking.org/display/OIMT/IISOMI+Deliverables>
31+
- The YANG specifications have been generated from the corresponding UML model using the [EAGLE UML2YANG mapping tool]
32+
<https://github.com/Open-Network-Models-and-Interfaces-ONMI/onmi-iisomi-uml-yang>
33+
and further edited manually to comply with the [ONMI IISOMI UML2YANG mapping guidelines]
34+
<https://github.com/Open-Network-Models-and-Interfaces-ONMI/onmi-iisomi-home>
3735
- Status of YANG model artifacts can be determined by referring to the corresponding UML artifacts.
3836
As described in the UML models, some artifacts are considered *experimental*, and thus the corresponding YANG artifacts.
39-
- The ONF TAPI release process does not guarantee backward compatibility of YANG models across major versions of TAPI releases.
37+
- The LF ONMI TAPI release process does not guarantee backward compatibility of YANG models across major versions of TAPI releases.
4038
The YANG model backward compatibility criteria are outlined in section 11 of <https://tools.ietf.org/html/rfc7950>.
41-
YANG models included in this release may not be backward compatible with previous TAPI releases.
42-
Copyright (c) 2023 Open Networking Foundation (ONF). All rights reserved.
39+
YANG models included in this release may not be backward compatible with some previous TAPI releases.
40+
- Previous revisions can now be found at https://github.com/Open-Network-Models-and-Interfaces-ONMI/TAPI under the
41+
appropriate tag and, where relevant, fixes to those revisions can be found under the corresponding branches. The documentation for
42+
each significant revision is found at https://github.com/Open-Network-Models-and-Interfaces-ONMI/TAPI-Documentation under the
43+
appropriate tag and, where relevant, fixes to those revisions can be found under the corresponding branches.
4344
License: This module is distributed under the Apache License 2.0.";
45+
revision 2025-12-31 {
46+
description "LF ONMI Transport API version 2.5.2
47+
Changes included in this TAPI release (v2.5.2) are listed in
48+
<https://github.com/Open-Network-Models-and-Interfaces-ONMI/TAPI-Documentation/tree/v2.5.2/DeltaDocument>";
49+
reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and LF ONMI TAPI UML model
50+
<https://github.com/Open-Network-Models-and-Interfaces-ONMI/TAPI/tree/v2.5.2/UML>";
51+
}
4452
revision 2023-10-10 {
4553
description "ONF Transport API version 2.5.0.
4654
Changes included in this TAPI release (v2.5.0) are listed in

‎YANG/tapi-digital-otn.tree‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
1-
21
module: tapi-digital-otn
2+
33
augment /tapi-common:context/tapi-topology:topology-context/tapi-topology:topology/tapi-topology:node/tapi-topology:owned-node-edge-point/tapi-connectivity:cep-list/tapi-connectivity:connection-end-point:
44
+--ro odu-connection-end-point-spec
55
+--ro odu-common

‎YANG/tapi-digital-otn.yang‎

Lines changed: 22 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -17,30 +17,38 @@ module tapi-digital-otn {
1717
import tapi-dsr {
1818
prefix tapi-dsr;
1919
}
20-
organization "ONF OTCC (Open Transport Configuration & Control) Project";
20+
organization "Linux Foundation ONMI (Open Network Modeling and Interfaces) Project";
2121
contact "
22-
Project Web: <https://wiki.opennetworking.org/display/OTCC/TAPI>
23-
Project List: <mailto:transport-api@opennetworking.org>
24-
Editor: Karthik Sethuraman <mailto:karthik.sethuraman@necam.com>
25-
Andrea Mazzini <mailto:andrea.mazzini@nokia.com>
26-
Arturo Mayoral <mailto:arturo.mayoral@telefonica.com>
27-
Nigel Davis <mailto:ndavis@ciena.com>
22+
Project Web: <https://github.com/Open-Network-Models-and-Interfaces-ONMI/onmi-home/wiki>
23+
Project List: <mailto:onmi-tapi@googlegroups.com>
24+
Editor: Nigel Davis <mailto:ndavis@ciena.com>
25+
Arturo Mayoral <mailto:amayoral@telecominfraproject.com>
2826
Ramon Casellas <mailto:ramon.casellas@cttc.es>";
2927
description "
3028
This module contains TAPI Digital OTN Model definitions.
3129
Source: TapiDigitalOtn.uml
3230
- The TAPI YANG models included in this TAPI release are a *normative* part of the TAPI SDK.
33-
- The YANG specifications have been generated from the corresponding UML model using the [ONF EAGLE UML2YANG mapping tool]
34-
<https://github.com/OpenNetworkingFoundation/EagleUmlYang>
35-
and further edited manually to comply with the [ONF IISOMI UML2YANG mapping guidelines]
36-
<https://wiki.opennetworking.org/display/OIMT/IISOMI+Deliverables>
31+
- The YANG specifications have been generated from the corresponding UML model using the [EAGLE UML2YANG mapping tool]
32+
<https://github.com/Open-Network-Models-and-Interfaces-ONMI/onmi-iisomi-uml-yang>
33+
and further edited manually to comply with the [ONMI IISOMI UML2YANG mapping guidelines]
34+
<https://github.com/Open-Network-Models-and-Interfaces-ONMI/onmi-iisomi-home>
3735
- Status of YANG model artifacts can be determined by referring to the corresponding UML artifacts.
3836
As described in the UML models, some artifacts are considered *experimental*, and thus the corresponding YANG artifacts.
39-
- The ONF TAPI release process does not guarantee backward compatibility of YANG models across major versions of TAPI releases.
37+
- The LF ONMI TAPI release process does not guarantee backward compatibility of YANG models across major versions of TAPI releases.
4038
The YANG model backward compatibility criteria are outlined in section 11 of <https://tools.ietf.org/html/rfc7950>.
41-
YANG models included in this release may not be backward compatible with previous TAPI releases.
42-
Copyright (c) 2023 Open Networking Foundation (ONF). All rights reserved.
39+
YANG models included in this release may not be backward compatible with some previous TAPI releases.
40+
- Previous revisions can now be found at https://github.com/Open-Network-Models-and-Interfaces-ONMI/TAPI under the
41+
appropriate tag and, where relevant, fixes to those revisions can be found under the corresponding branches. The documentation for
42+
each significant revision is found at https://github.com/Open-Network-Models-and-Interfaces-ONMI/TAPI-Documentation under the
43+
appropriate tag and, where relevant, fixes to those revisions can be found under the corresponding branches.
4344
License: This module is distributed under the Apache License 2.0.";
45+
revision 2025-12-31 {
46+
description "LF ONMI Transport API version 2.5.2
47+
Changes included in this TAPI release (v2.5.2) are listed in
48+
<https://github.com/Open-Network-Models-and-Interfaces-ONMI/TAPI-Documentation/tree/v2.5.2/DeltaDocument>";
49+
reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and LF ONMI TAPI UML model
50+
<https://github.com/Open-Network-Models-and-Interfaces-ONMI/TAPI/tree/v2.5.2/UML>";
51+
}
4452
revision 2023-10-10 {
4553
description "ONF Transport API version 2.5.0.
4654
Changes included in this TAPI release (v2.5.0) are listed in

‎YANG/tapi-dsr.yang‎

Lines changed: 22 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -5,30 +5,38 @@ module tapi-dsr {
55
import tapi-common {
66
prefix tapi-common;
77
}
8-
organization "ONF OTCC (Open Transport Configuration & Control) Project";
8+
organization "Linux Foundation ONMI (Open Network Modeling and Interfaces) Project";
99
contact "
10-
Project Web: <https://wiki.opennetworking.org/display/OTCC/TAPI>
11-
Project List: <mailto:transport-api@opennetworking.org>
12-
Editor: Karthik Sethuraman <mailto:karthik.sethuraman@necam.com>
13-
Andrea Mazzini <mailto:andrea.mazzini@nokia.com>
14-
Arturo Mayoral <mailto:arturo.mayoral@telefonica.com>
15-
Nigel Davis <mailto:ndavis@ciena.com>
10+
Project Web: <https://github.com/Open-Network-Models-and-Interfaces-ONMI/onmi-home/wiki>
11+
Project List: <mailto:onmi-tapi@googlegroups.com>
12+
Editor: Nigel Davis <mailto:ndavis@ciena.com>
13+
Arturo Mayoral <mailto:amayoral@telecominfraproject.com>
1614
Ramon Casellas <mailto:ramon.casellas@cttc.es>";
1715
description "
1816
This module contains TAPI Digital Signal Rate Model definitions.
1917
Source: TapiDsr.uml
2018
- The TAPI YANG models included in this TAPI release are a *normative* part of the TAPI SDK.
21-
- The YANG specifications have been generated from the corresponding UML model using the [ONF EAGLE UML2YANG mapping tool]
22-
<https://github.com/OpenNetworkingFoundation/EagleUmlYang>
23-
and further edited manually to comply with the [ONF IISOMI UML2YANG mapping guidelines]
24-
<https://wiki.opennetworking.org/display/OIMT/IISOMI+Deliverables>
19+
- The YANG specifications have been generated from the corresponding UML model using the [EAGLE UML2YANG mapping tool]
20+
<https://github.com/Open-Network-Models-and-Interfaces-ONMI/onmi-iisomi-uml-yang>
21+
and further edited manually to comply with the [ONMI IISOMI UML2YANG mapping guidelines]
22+
<https://github.com/Open-Network-Models-and-Interfaces-ONMI/onmi-iisomi-home>
2523
- Status of YANG model artifacts can be determined by referring to the corresponding UML artifacts.
2624
As described in the UML models, some artifacts are considered *experimental*, and thus the corresponding YANG artifacts.
27-
- The ONF TAPI release process does not guarantee backward compatibility of YANG models across major versions of TAPI releases.
25+
- The LF ONMI TAPI release process does not guarantee backward compatibility of YANG models across major versions of TAPI releases.
2826
The YANG model backward compatibility criteria are outlined in section 11 of <https://tools.ietf.org/html/rfc7950>.
29-
YANG models included in this release may not be backward compatible with previous TAPI releases.
30-
Copyright (c) 2023 Open Networking Foundation (ONF). All rights reserved.
27+
YANG models included in this release may not be backward compatible with some previous TAPI releases.
28+
- Previous revisions can now be found at https://github.com/Open-Network-Models-and-Interfaces-ONMI/TAPI under the
29+
appropriate tag and, where relevant, fixes to those revisions can be found under the corresponding branches. The documentation for
30+
each significant revision is found at https://github.com/Open-Network-Models-and-Interfaces-ONMI/TAPI-Documentation under the
31+
appropriate tag and, where relevant, fixes to those revisions can be found under the corresponding branches.
3132
License: This module is distributed under the Apache License 2.0.";
33+
revision 2025-12-31 {
34+
description "LF ONMI Transport API version 2.5.2
35+
Changes included in this TAPI release (v2.5.2) are listed in
36+
<https://github.com/Open-Network-Models-and-Interfaces-ONMI/TAPI-Documentation/tree/v2.5.2/DeltaDocument>";
37+
reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and LF ONMI TAPI UML model
38+
<https://github.com/Open-Network-Models-and-Interfaces-ONMI/TAPI/tree/v2.5.2/UML>";
39+
}
3240
revision 2023-10-10 {
3341
description "ONF Transport API version 2.5.0.
3442
Changes included in this TAPI release (v2.5.0) are listed in

‎YANG/tapi-equipment.tree‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
1-
21
module: tapi-equipment
2+
33
augment /tapi-common:context:
44
+--rw physical-context
55
+--ro device* [uuid]

0 commit comments

Comments
 (0)