Skip to content
Permalink
Browse files

Renamed YANG, TREE & OAS files with 2.1.1 revision date @2018-12-10

  • Loading branch information...
karthik-sethuraman committed Dec 10, 2018
1 parent b9caaad commit ac2ccf54b97bdf48afae2108f1f9a48a231c1ef7
Showing with 223 additions and 171 deletions.
  1. 0 OAS/{tapi-common@2018-10-16.yaml → tapi-common@2018-12-10.yaml}
  2. 0 OAS/{tapi-connectivity@2018-10-16.yaml → tapi-connectivity@2018-12-10.yaml}
  3. 0 OAS/{tapi-dsr@2018-10-16.yaml → tapi-dsr@2018-12-10.yaml}
  4. 0 OAS/{tapi-eth@2018-10-16.yaml → tapi-eth@2018-12-10.yaml}
  5. 0 OAS/{tapi-notification@2018-10-16.yaml → tapi-notification@2018-12-10.yaml}
  6. 0 OAS/{tapi-oam@2018-10-16.yaml → tapi-oam@2018-12-10.yaml}
  7. 0 OAS/{tapi-odu@2018-10-16.yaml → tapi-odu@2018-12-10.yaml}
  8. 0 OAS/{tapi-path-computation@2018-10-16.yaml → tapi-path-computation@2018-12-10.yaml}
  9. 0 OAS/{tapi-photonic-media@2018-10-16.yaml → tapi-photonic-media@2018-12-10.yaml}
  10. 0 OAS/{tapi-topology@2018-10-16.yaml → tapi-topology@2018-12-10.yaml}
  11. 0 OAS/{tapi-virtual-network@2018-10-16.yaml → tapi-virtual-network@2018-12-10.yaml}
  12. +1 −1 RI/README.md
  13. +0 −11 UML/UmlProfiles/OpenInterfaceModelProfile/.project
  14. +0 −11 UML/UmlProfiles/OpenModelProfile/.project
  15. +0 −11 UML/UmlProfiles/ProfileLifecycleProfile/.project
  16. +7 −2 YANG/config-xmi2yang.json
  17. 0 YANG/{tapi-common@2018-10-16.tree → tapi-common@2018-12-10.tree}
  18. +20 −14 YANG/{tapi-common@2018-10-16.yang → tapi-common@2018-12-10.yang}
  19. 0 YANG/{tapi-connectivity@2018-10-16.tree → tapi-connectivity@2018-12-10.tree}
  20. +19 −12 YANG/{tapi-connectivity@2018-10-16.yang → tapi-connectivity@2018-12-10.yang}
  21. 0 YANG/{tapi-dsr@2018-10-16.tree → tapi-dsr@2018-12-10.tree}
  22. +24 −13 YANG/{tapi-dsr@2018-10-16.yang → tapi-dsr@2018-12-10.yang}
  23. 0 YANG/{tapi-eth@2018-10-16.tree → tapi-eth@2018-12-10.tree}
  24. +19 −12 YANG/{tapi-eth@2018-10-16.yang → tapi-eth@2018-12-10.yang}
  25. 0 YANG/{tapi-notification@2018-10-16.tree → tapi-notification@2018-12-10.tree}
  26. +19 −12 YANG/{tapi-notification@2018-10-16.yang → tapi-notification@2018-12-10.yang}
  27. 0 YANG/{tapi-oam@2018-10-16.tree → tapi-oam@2018-12-10.tree}
  28. +19 −12 YANG/{tapi-oam@2018-10-16.yang → tapi-oam@2018-12-10.yang}
  29. 0 YANG/{tapi-odu@2018-10-16.tree → tapi-odu@2018-12-10.tree}
  30. +19 −12 YANG/{tapi-odu@2018-10-16.yang → tapi-odu@2018-12-10.yang}
  31. 0 YANG/{tapi-path-computation@2018-10-16.tree → tapi-path-computation@2018-12-10.tree}
  32. +19 −12 YANG/{tapi-path-computation@2018-10-16.yang → tapi-path-computation@2018-12-10.yang}
  33. 0 YANG/{tapi-photonic-media@2018-10-16.tree → tapi-photonic-media@2018-12-10.tree}
  34. +19 −12 YANG/{tapi-photonic-media@2018-10-16.yang → tapi-photonic-media@2018-12-10.yang}
  35. 0 YANG/{tapi-topology@2018-10-16.tree → tapi-topology@2018-12-10.tree}
  36. +19 −12 YANG/{tapi-topology@2018-10-16.yang → tapi-topology@2018-12-10.yang}
  37. 0 YANG/{tapi-virtual-network@2018-10-16.tree → tapi-virtual-network@2018-12-10.tree}
  38. +19 −12 YANG/{tapi-virtual-network@2018-10-16.yang → tapi-virtual-network@2018-12-10.yang}
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
@@ -13,7 +13,7 @@ Currently the RI includes following implementations:
These implementations have been tested on [Ubuntu 18.04.1 LTS](https://www.ubuntu.com/download/desktop).

## Coverage
For this release (TAPI 2.1.1), the [tapi-photonic-media OpenAPI file](https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/OAS/tapi-photonic-media@402018-10-16.yaml) has been used to generate the server stubs.
For this release (TAPI 2.1.1), the [tapi-photonic-media OpenAPI file](https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/OAS/tapi-photonic-media@402018-12-10.yaml) has been used to generate the server stubs.

Only a limited set of following APIs have been implemented in this release:
* _GET_ /data/context/

This file was deleted.

This file was deleted.

This file was deleted.

@@ -2,12 +2,17 @@
"tapi":{
"namespace":"urn:onf:otcc:yang:",
"organization":"ONF OTCC (Open Transport Configuration & Control) Project",
"contact":"\r\n Project Web: <https://wiki.opennetworking.org/display/OTCC/TAPI>\r\n Project List: <mailto:transport-api@opennetworking.org>\r\n Editor: Karthik Sethuraman\r\n\t\t <mailto:karthik.sethuraman@necam.com>",
"contact":"\r\n Project Web: <https://wiki.opennetworking.org/display/OTCC/TAPI>\r\n Project List: <mailto:transport-api@opennetworking.org>\r\n Editor: Karthik Sethuraman\r\n <mailto:karthik.sethuraman@necam.com>",
"withSuffix":false,
"revision": [
{
"date":"2018-12-10",
"description":"ONF Transport API version 2.1.1.\r\n - The TAPI YANG models included in this TAPI release (v2.1.1) are a *normative* part of the TAPI SDK.\r\n - The YANG specifications have been generated from the corresponding UML model using the [ONF EAGLE UML2YANG mapping tool]\r\n <https://github.com/OpenNetworkingFoundation/EagleUmlYang>\r\n and further edited manually to comply with the [ONF IISOMI UML2YANG mapping guidelines]\r\n <https://wiki.opennetworking.org/display/OIMT/UML+-+YANG+Guidelines>\r\n - Status of YANG model artifacts can be determined by referring to the corresponding UML artifacts.\r\n As described in the UML models, some artifacts are considered *experimental*, and thus the corresponding YANG artifacts.\r\n - The ONF TAPI release process does not guarantee backward compatibility of YANG models across major versions of TAPI releases.\r\n The YANG model backward compatibility criteria are outlined in section 11 of <https://tools.ietf.org/html/rfc7950>.\r\n YANG models included in this release are not backward compatible with previous TAPI releases.\r\n - Changes included in this TAPI release (v2.1.1) are listed in\r\n <https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.1.md>",
"reference":"ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model\n <https://github.com/OpenNetworkingFoundation/TAPI/tree/v2.1.0/UML>"
},
{
"date":"2018-10-16",
"description":"ONF Transport API version 2.1.0.\r\n - The TAPI YANG models included in this TAPI release (v2.1.0) are a *normative* part of the TAPI SDK.\r\n - The YANG specifications have been generated from the corresponding UML model using the [ONF EAGLE UML2YANG mapping tool]\r\n\t<https://github.com/OpenNetworkingFoundation/EagleUmlYang>\r\n\tand further edited manually to comply with the [ONF IISOMI UML2YANG mapping guidelines]\r\n\t<https://wiki.opennetworking.org/display/OIMT/UML+-+YANG+Guidelines>\r\n - Status of YANG model artifacts can be determined by referring to the corresponding UML artifacts.\r\n\tAs described in the UML models, some artifacts are considered *experimental*, and thus the corresponding YANG artifacts.\r\n - The ONF TAPI release process does not guarantee backward compatibility of YANG models across major versions of TAPI releases.\r\n\tThe YANG model backward compatibility criteria are outlined in section 11 of <https://tools.ietf.org/html/rfc7950>.\r\n\tYANG models included in this release are not backward compatible with previous TAPI releases.\r\n - Changes included in this TAPI release (v2.1.0) are listed in\r\n\t<https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.0.md>",
"description":"ONF Transport API version 2.1.0.\r\n - The TAPI YANG models included in this TAPI release (v2.1.0) are a *normative* part of the TAPI SDK.\r\n - The YANG specifications have been generated from the corresponding UML model using the [ONF EAGLE UML2YANG mapping tool]\r\n <https://github.com/OpenNetworkingFoundation/EagleUmlYang>\r\n and further edited manually to comply with the [ONF IISOMI UML2YANG mapping guidelines]\r\n <https://wiki.opennetworking.org/display/OIMT/UML+-+YANG+Guidelines>\r\n - Status of YANG model artifacts can be determined by referring to the corresponding UML artifacts.\r\n As described in the UML models, some artifacts are considered *experimental*, and thus the corresponding YANG artifacts.\r\n - The ONF TAPI release process does not guarantee backward compatibility of YANG models across major versions of TAPI releases.\r\n The YANG model backward compatibility criteria are outlined in section 11 of <https://tools.ietf.org/html/rfc7950>.\r\n YANG models included in this release are not backward compatible with previous TAPI releases.\r\n - Changes included in this TAPI release (v2.1.0) are listed in\r\n <https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.0.md>",
"reference":"ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model\n <https://github.com/OpenNetworkingFoundation/TAPI/tree/v2.1.0/UML>"
},
{
File renamed without changes.
@@ -10,23 +10,29 @@ module tapi-common {
description "
This module contains TAPI Common Model definitions.
Source: TapiCommon.uml
- The TAPI YANG models included in this TAPI release are a *normative* part of the TAPI SDK.
- The YANG specifications have been generated from the corresponding UML model using the [ONF EAGLE UML2YANG mapping tool]
<https://github.com/OpenNetworkingFoundation/EagleUmlYang>
and further edited manually to comply with the [ONF IISOMI UML2YANG mapping guidelines]
<https://wiki.opennetworking.org/display/OIMT/UML+-+YANG+Guidelines>
- Status of YANG model artifacts can be determined by referring to the corresponding UML artifacts.
As described in the UML models, some artifacts are considered *experimental*, and thus the corresponding YANG artifacts.
- The ONF TAPI release process does not guarantee backward compatibility of YANG models across major versions of TAPI releases.
The YANG model backward compatibility criteria are outlined in section 11 of <https://tools.ietf.org/html/rfc7950>.
YANG models included in this release may not be backward compatible with previous TAPI releases.
Copyright (c) 2018 Open Networking Foundation (ONF). All rights reserved.
License: This module is distributed under the Apache License 2.0
";
License: This module is distributed under the Apache License 2.0";
revision 2018-12-10 {
description "ONF Transport API version 2.1.1.
Changes included in this TAPI release (v2.1.1) are listed in
<https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.1.md>";
reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model
<https://github.com/OpenNetworkingFoundation/TAPI/tree/v2.1.0/UML>";
}
revision 2018-10-16 {
description "ONF Transport API version 2.1.0.
- The TAPI YANG models included in this TAPI release (v2.1.0) are a *normative* part of the TAPI SDK.
- The YANG specifications have been generated from the corresponding UML model using the [ONF EAGLE UML2YANG mapping tool]
<https://github.com/OpenNetworkingFoundation/EagleUmlYang>
and further edited manually to comply with the [ONF IISOMI UML2YANG mapping guidelines]
<https://wiki.opennetworking.org/display/OIMT/UML+-+YANG+Guidelines>
- Status of YANG model artifacts can be determined by referring to the corresponding UML artifacts.
As described in the UML models, some artifacts are considered *experimental*, and thus the corresponding YANG artifacts.
- The ONF TAPI release process does not guarantee backward compatibility of YANG models across major versions of TAPI releases.
The YANG model backward compatibility criteria are outlined in section 11 of <https://tools.ietf.org/html/rfc7950>.
YANG models included in this release are not backward compatible with previous TAPI releases.
- Changes included in this TAPI release (v2.1.0) are listed in
<https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.0.md>";
Changes included in this TAPI release (v2.1.0) are listed in
<https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.0.md>";
reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model
<https://github.com/OpenNetworkingFoundation/TAPI/tree/v2.1.0/UML>";
}
File renamed without changes.
@@ -19,22 +19,29 @@ module tapi-connectivity {
description "
This module contains TAPI Connectivity Model definitions.
Source: TapiConnectivity.uml
- The TAPI YANG models included in this TAPI release are a *normative* part of the TAPI SDK.
- The YANG specifications have been generated from the corresponding UML model using the [ONF EAGLE UML2YANG mapping tool]
<https://github.com/OpenNetworkingFoundation/EagleUmlYang>
and further edited manually to comply with the [ONF IISOMI UML2YANG mapping guidelines]
<https://wiki.opennetworking.org/display/OIMT/UML+-+YANG+Guidelines>
- Status of YANG model artifacts can be determined by referring to the corresponding UML artifacts.
As described in the UML models, some artifacts are considered *experimental*, and thus the corresponding YANG artifacts.
- The ONF TAPI release process does not guarantee backward compatibility of YANG models across major versions of TAPI releases.
The YANG model backward compatibility criteria are outlined in section 11 of <https://tools.ietf.org/html/rfc7950>.
YANG models included in this release may not be backward compatible with previous TAPI releases.
Copyright (c) 2018 Open Networking Foundation (ONF). All rights reserved.
License: This module is distributed under the Apache License 2.0";
revision 2018-12-10 {
description "ONF Transport API version 2.1.1.
Changes included in this TAPI release (v2.1.1) are listed in
<https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.1.md>";
reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model
<https://github.com/OpenNetworkingFoundation/TAPI/tree/v2.1.0/UML>";
}
revision 2018-10-16 {
description "ONF Transport API version 2.1.0.
- The TAPI YANG models included in this TAPI release (v2.1.0) are a *normative* part of the TAPI SDK.
- The YANG specifications have been generated from the corresponding UML model using the [ONF EAGLE UML2YANG mapping tool]
<https://github.com/OpenNetworkingFoundation/EagleUmlYang>
and further edited manually to comply with the [ONF IISOMI UML2YANG mapping guidelines]
<https://wiki.opennetworking.org/display/OIMT/UML+-+YANG+Guidelines>
- Status of YANG model artifacts can be determined by referring to the corresponding UML artifacts.
As described in the UML models, some artifacts are considered *experimental*, and thus the corresponding YANG artifacts.
- The ONF TAPI release process does not guarantee backward compatibility of YANG models across major versions of TAPI releases.
The YANG model backward compatibility criteria are outlined in section 11 of <https://tools.ietf.org/html/rfc7950>.
YANG models included in this release are not backward compatible with previous TAPI releases.
- Changes included in this TAPI release (v2.1.0) are listed in
<https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.0.md>";
Changes included in this TAPI release (v2.1.0) are listed in
<https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.0.md>";
reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model
<https://github.com/OpenNetworkingFoundation/TAPI/tree/v2.1.0/UML>";
}
File renamed without changes.
@@ -10,21 +10,32 @@ module tapi-dsr {
Project List: <mailto:transport-api@opennetworking.org>
Editor: Karthik Sethuraman
<mailto:karthik.sethuraman@necam.com>";
description "none";
description "
This module contains TAPI DSR Model definitions.
Source: TapiDsr.uml
- The TAPI YANG models included in this TAPI release are a *normative* part of the TAPI SDK.
- The YANG specifications have been generated from the corresponding UML model using the [ONF EAGLE UML2YANG mapping tool]
<https://github.com/OpenNetworkingFoundation/EagleUmlYang>
and further edited manually to comply with the [ONF IISOMI UML2YANG mapping guidelines]
<https://wiki.opennetworking.org/display/OIMT/UML+-+YANG+Guidelines>
- Status of YANG model artifacts can be determined by referring to the corresponding UML artifacts.
As described in the UML models, some artifacts are considered *experimental*, and thus the corresponding YANG artifacts.
- The ONF TAPI release process does not guarantee backward compatibility of YANG models across major versions of TAPI releases.
The YANG model backward compatibility criteria are outlined in section 11 of <https://tools.ietf.org/html/rfc7950>.
YANG models included in this release may not be backward compatible with previous TAPI releases.
Copyright (c) 2018 Open Networking Foundation (ONF). All rights reserved.
License: This module is distributed under the Apache License 2.0";
revision 2018-12-10 {
description "ONF Transport API version 2.1.1.
Changes included in this TAPI release (v2.1.1) are listed in
<https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.1.md>";
reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model
<https://github.com/OpenNetworkingFoundation/TAPI/tree/v2.1.0/UML>";
}
revision 2018-10-16 {
description "ONF Transport API version 2.1.0.
- The TAPI YANG models included in this TAPI release (v2.1.0) are a *normative* part of the TAPI SDK.
- The YANG specifications have been generated from the corresponding UML model using the [ONF EAGLE UML2YANG mapping tool]
<https://github.com/OpenNetworkingFoundation/EagleUmlYang>
and further edited manually to comply with the [ONF IISOMI UML2YANG mapping guidelines]
<https://wiki.opennetworking.org/display/OIMT/UML+-+YANG+Guidelines>
- Status of YANG model artifacts can be determined by referring to the corresponding UML artifacts.
As described in the UML models, some artifacts are considered *experimental*, and thus the corresponding YANG artifacts.
- The ONF TAPI release process does not guarantee backward compatibility of YANG models across major versions of TAPI releases.
The YANG model backward compatibility criteria are outlined in section 11 of <https://tools.ietf.org/html/rfc7950>.
YANG models included in this release are not backward compatible with previous TAPI releases.
- Changes included in this TAPI release (v2.1.0) are listed in
<https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.0.md>";
Changes included in this TAPI release (v2.1.0) are listed in
<https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.0.md>";
reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model
<https://github.com/OpenNetworkingFoundation/TAPI/tree/v2.1.0/UML>";
}
File renamed without changes.

0 comments on commit ac2ccf5

Please sign in to comment.
You can’t perform that action at this time.