From ac2ccf54b97bdf48afae2108f1f9a48a231c1ef7 Mon Sep 17 00:00:00 2001 From: Karthik Sethuraman Date: Mon, 10 Dec 2018 15:25:36 -0500 Subject: [PATCH] Renamed YANG, TREE & OAS files with 2.1.1 revision date @2018-12-10 --- ...10-16.yaml => tapi-common@2018-12-10.yaml} | 0 ...yaml => tapi-connectivity@2018-12-10.yaml} | 0 ...18-10-16.yaml => tapi-dsr@2018-12-10.yaml} | 0 ...18-10-16.yaml => tapi-eth@2018-12-10.yaml} | 0 ...yaml => tapi-notification@2018-12-10.yaml} | 0 ...18-10-16.yaml => tapi-oam@2018-12-10.yaml} | 0 ...18-10-16.yaml => tapi-odu@2018-12-10.yaml} | 0 ... => tapi-path-computation@2018-12-10.yaml} | 0 ...ml => tapi-photonic-media@2018-12-10.yaml} | 0 ...-16.yaml => tapi-topology@2018-12-10.yaml} | 0 ...l => tapi-virtual-network@2018-12-10.yaml} | 0 RI/README.md | 2 +- .../OpenInterfaceModelProfile/.project | 11 ------ UML/UmlProfiles/OpenModelProfile/.project | 11 ------ .../ProfileLifecycleProfile/.project | 11 ------ YANG/config-xmi2yang.json | 9 ++++- ...10-16.tree => tapi-common@2018-12-10.tree} | 0 ...10-16.yang => tapi-common@2018-12-10.yang} | 34 ++++++++++------- ...tree => tapi-connectivity@2018-12-10.tree} | 0 ...yang => tapi-connectivity@2018-12-10.yang} | 31 ++++++++++------ ...18-10-16.tree => tapi-dsr@2018-12-10.tree} | 0 ...18-10-16.yang => tapi-dsr@2018-12-10.yang} | 37 ++++++++++++------- ...18-10-16.tree => tapi-eth@2018-12-10.tree} | 0 ...18-10-16.yang => tapi-eth@2018-12-10.yang} | 31 ++++++++++------ ...tree => tapi-notification@2018-12-10.tree} | 0 ...yang => tapi-notification@2018-12-10.yang} | 31 ++++++++++------ ...18-10-16.tree => tapi-oam@2018-12-10.tree} | 0 ...18-10-16.yang => tapi-oam@2018-12-10.yang} | 31 ++++++++++------ ...18-10-16.tree => tapi-odu@2018-12-10.tree} | 0 ...18-10-16.yang => tapi-odu@2018-12-10.yang} | 31 ++++++++++------ ... => tapi-path-computation@2018-12-10.tree} | 0 ... => tapi-path-computation@2018-12-10.yang} | 31 ++++++++++------ ...ee => tapi-photonic-media@2018-12-10.tree} | 0 ...ng => tapi-photonic-media@2018-12-10.yang} | 31 ++++++++++------ ...-16.tree => tapi-topology@2018-12-10.tree} | 0 ...-16.yang => tapi-topology@2018-12-10.yang} | 31 ++++++++++------ ...e => tapi-virtual-network@2018-12-10.tree} | 0 ...g => tapi-virtual-network@2018-12-10.yang} | 31 ++++++++++------ 38 files changed, 223 insertions(+), 171 deletions(-) rename OAS/{tapi-common@2018-10-16.yaml => tapi-common@2018-12-10.yaml} (100%) rename OAS/{tapi-connectivity@2018-10-16.yaml => tapi-connectivity@2018-12-10.yaml} (100%) rename OAS/{tapi-dsr@2018-10-16.yaml => tapi-dsr@2018-12-10.yaml} (100%) rename OAS/{tapi-eth@2018-10-16.yaml => tapi-eth@2018-12-10.yaml} (100%) rename OAS/{tapi-notification@2018-10-16.yaml => tapi-notification@2018-12-10.yaml} (100%) rename OAS/{tapi-oam@2018-10-16.yaml => tapi-oam@2018-12-10.yaml} (100%) rename OAS/{tapi-odu@2018-10-16.yaml => tapi-odu@2018-12-10.yaml} (100%) rename OAS/{tapi-path-computation@2018-10-16.yaml => tapi-path-computation@2018-12-10.yaml} (100%) rename OAS/{tapi-photonic-media@2018-10-16.yaml => tapi-photonic-media@2018-12-10.yaml} (100%) rename OAS/{tapi-topology@2018-10-16.yaml => tapi-topology@2018-12-10.yaml} (100%) rename OAS/{tapi-virtual-network@2018-10-16.yaml => tapi-virtual-network@2018-12-10.yaml} (100%) delete mode 100644 UML/UmlProfiles/OpenInterfaceModelProfile/.project delete mode 100644 UML/UmlProfiles/OpenModelProfile/.project delete mode 100644 UML/UmlProfiles/ProfileLifecycleProfile/.project rename YANG/{tapi-common@2018-10-16.tree => tapi-common@2018-12-10.tree} (100%) rename YANG/{tapi-common@2018-10-16.yang => tapi-common@2018-12-10.yang} (92%) rename YANG/{tapi-connectivity@2018-10-16.tree => tapi-connectivity@2018-12-10.tree} (100%) rename YANG/{tapi-connectivity@2018-10-16.yang => tapi-connectivity@2018-12-10.yang} (92%) rename YANG/{tapi-dsr@2018-10-16.tree => tapi-dsr@2018-12-10.tree} (100%) rename YANG/{tapi-dsr@2018-10-16.yang => tapi-dsr@2018-12-10.yang} (75%) rename YANG/{tapi-eth@2018-10-16.tree => tapi-eth@2018-12-10.tree} (100%) rename YANG/{tapi-eth@2018-10-16.yang => tapi-eth@2018-12-10.yang} (95%) rename YANG/{tapi-notification@2018-10-16.tree => tapi-notification@2018-12-10.tree} (100%) rename YANG/{tapi-notification@2018-10-16.yang => tapi-notification@2018-12-10.yang} (88%) rename YANG/{tapi-oam@2018-10-16.tree => tapi-oam@2018-12-10.tree} (100%) rename YANG/{tapi-oam@2018-10-16.yang => tapi-oam@2018-12-10.yang} (90%) rename YANG/{tapi-odu@2018-10-16.tree => tapi-odu@2018-12-10.tree} (100%) rename YANG/{tapi-odu@2018-10-16.yang => tapi-odu@2018-12-10.yang} (92%) rename YANG/{tapi-path-computation@2018-10-16.tree => tapi-path-computation@2018-12-10.tree} (100%) rename YANG/{tapi-path-computation@2018-10-16.yang => tapi-path-computation@2018-12-10.yang} (87%) rename YANG/{tapi-photonic-media@2018-10-16.tree => tapi-photonic-media@2018-12-10.tree} (100%) rename YANG/{tapi-photonic-media@2018-10-16.yang => tapi-photonic-media@2018-12-10.yang} (93%) rename YANG/{tapi-topology@2018-10-16.tree => tapi-topology@2018-12-10.tree} (100%) rename YANG/{tapi-topology@2018-10-16.yang => tapi-topology@2018-12-10.yang} (92%) rename YANG/{tapi-virtual-network@2018-10-16.tree => tapi-virtual-network@2018-12-10.tree} (100%) rename YANG/{tapi-virtual-network@2018-10-16.yang => tapi-virtual-network@2018-12-10.yang} (83%) diff --git a/OAS/tapi-common@2018-10-16.yaml b/OAS/tapi-common@2018-12-10.yaml similarity index 100% rename from OAS/tapi-common@2018-10-16.yaml rename to OAS/tapi-common@2018-12-10.yaml diff --git a/OAS/tapi-connectivity@2018-10-16.yaml b/OAS/tapi-connectivity@2018-12-10.yaml similarity index 100% rename from OAS/tapi-connectivity@2018-10-16.yaml rename to OAS/tapi-connectivity@2018-12-10.yaml diff --git a/OAS/tapi-dsr@2018-10-16.yaml b/OAS/tapi-dsr@2018-12-10.yaml similarity index 100% rename from OAS/tapi-dsr@2018-10-16.yaml rename to OAS/tapi-dsr@2018-12-10.yaml diff --git a/OAS/tapi-eth@2018-10-16.yaml b/OAS/tapi-eth@2018-12-10.yaml similarity index 100% rename from OAS/tapi-eth@2018-10-16.yaml rename to OAS/tapi-eth@2018-12-10.yaml diff --git a/OAS/tapi-notification@2018-10-16.yaml b/OAS/tapi-notification@2018-12-10.yaml similarity index 100% rename from OAS/tapi-notification@2018-10-16.yaml rename to OAS/tapi-notification@2018-12-10.yaml diff --git a/OAS/tapi-oam@2018-10-16.yaml b/OAS/tapi-oam@2018-12-10.yaml similarity index 100% rename from OAS/tapi-oam@2018-10-16.yaml rename to OAS/tapi-oam@2018-12-10.yaml diff --git a/OAS/tapi-odu@2018-10-16.yaml b/OAS/tapi-odu@2018-12-10.yaml similarity index 100% rename from OAS/tapi-odu@2018-10-16.yaml rename to OAS/tapi-odu@2018-12-10.yaml diff --git a/OAS/tapi-path-computation@2018-10-16.yaml b/OAS/tapi-path-computation@2018-12-10.yaml similarity index 100% rename from OAS/tapi-path-computation@2018-10-16.yaml rename to OAS/tapi-path-computation@2018-12-10.yaml diff --git a/OAS/tapi-photonic-media@2018-10-16.yaml b/OAS/tapi-photonic-media@2018-12-10.yaml similarity index 100% rename from OAS/tapi-photonic-media@2018-10-16.yaml rename to OAS/tapi-photonic-media@2018-12-10.yaml diff --git a/OAS/tapi-topology@2018-10-16.yaml b/OAS/tapi-topology@2018-12-10.yaml similarity index 100% rename from OAS/tapi-topology@2018-10-16.yaml rename to OAS/tapi-topology@2018-12-10.yaml diff --git a/OAS/tapi-virtual-network@2018-10-16.yaml b/OAS/tapi-virtual-network@2018-12-10.yaml similarity index 100% rename from OAS/tapi-virtual-network@2018-10-16.yaml rename to OAS/tapi-virtual-network@2018-12-10.yaml diff --git a/RI/README.md b/RI/README.md index 483726b9..79b14889 100644 --- a/RI/README.md +++ b/RI/README.md @@ -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/ diff --git a/UML/UmlProfiles/OpenInterfaceModelProfile/.project b/UML/UmlProfiles/OpenInterfaceModelProfile/.project deleted file mode 100644 index 7519bd9c..00000000 --- a/UML/UmlProfiles/OpenInterfaceModelProfile/.project +++ /dev/null @@ -1,11 +0,0 @@ - - - OpenInterfaceModelProfile - - - - - - - - diff --git a/UML/UmlProfiles/OpenModelProfile/.project b/UML/UmlProfiles/OpenModelProfile/.project deleted file mode 100644 index 632ad928..00000000 --- a/UML/UmlProfiles/OpenModelProfile/.project +++ /dev/null @@ -1,11 +0,0 @@ - - - OpenModelProfile - - - - - - - - diff --git a/UML/UmlProfiles/ProfileLifecycleProfile/.project b/UML/UmlProfiles/ProfileLifecycleProfile/.project deleted file mode 100644 index 5c85be2a..00000000 --- a/UML/UmlProfiles/ProfileLifecycleProfile/.project +++ /dev/null @@ -1,11 +0,0 @@ - - - ProfileLifecycleProfile - - - - - - - - diff --git a/YANG/config-xmi2yang.json b/YANG/config-xmi2yang.json index 9961c549..bbf5b3c4 100644 --- a/YANG/config-xmi2yang.json +++ b/YANG/config-xmi2yang.json @@ -2,12 +2,17 @@ "tapi":{ "namespace":"urn:onf:otcc:yang:", "organization":"ONF OTCC (Open Transport Configuration & Control) Project", - "contact":"\r\n Project Web: \r\n Project List: \r\n Editor: Karthik Sethuraman\r\n\t\t ", + "contact":"\r\n Project Web: \r\n Project List: \r\n Editor: Karthik Sethuraman\r\n ", "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 \r\n and further edited manually to comply with the [ONF IISOMI UML2YANG mapping guidelines]\r\n \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 .\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 ", + "reference":"ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model\n " + }, { "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\r\n\tand further edited manually to comply with the [ONF IISOMI UML2YANG mapping guidelines]\r\n\t\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 .\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", + "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 \r\n and further edited manually to comply with the [ONF IISOMI UML2YANG mapping guidelines]\r\n \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 .\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 ", "reference":"ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model\n " }, { diff --git a/YANG/tapi-common@2018-10-16.tree b/YANG/tapi-common@2018-12-10.tree similarity index 100% rename from YANG/tapi-common@2018-10-16.tree rename to YANG/tapi-common@2018-12-10.tree diff --git a/YANG/tapi-common@2018-10-16.yang b/YANG/tapi-common@2018-12-10.yang similarity index 92% rename from YANG/tapi-common@2018-10-16.yang rename to YANG/tapi-common@2018-12-10.yang index d526a7ab..b5fecaa9 100755 --- a/YANG/tapi-common@2018-10-16.yang +++ b/YANG/tapi-common@2018-12-10.yang @@ -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] + + and further edited manually to comply with the [ONF IISOMI UML2YANG mapping 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 . + 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 + "; + reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model + "; + } 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] - - and further edited manually to comply with the [ONF IISOMI UML2YANG mapping 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 . - 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 - "; + Changes included in this TAPI release (v2.1.0) are listed in + "; reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model "; } diff --git a/YANG/tapi-connectivity@2018-10-16.tree b/YANG/tapi-connectivity@2018-12-10.tree similarity index 100% rename from YANG/tapi-connectivity@2018-10-16.tree rename to YANG/tapi-connectivity@2018-12-10.tree diff --git a/YANG/tapi-connectivity@2018-10-16.yang b/YANG/tapi-connectivity@2018-12-10.yang similarity index 92% rename from YANG/tapi-connectivity@2018-10-16.yang rename to YANG/tapi-connectivity@2018-12-10.yang index 755eb2ef..5b798c7b 100755 --- a/YANG/tapi-connectivity@2018-10-16.yang +++ b/YANG/tapi-connectivity@2018-12-10.yang @@ -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] + + and further edited manually to comply with the [ONF IISOMI UML2YANG mapping 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 . + 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 + "; + reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model + "; + } 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] - - and further edited manually to comply with the [ONF IISOMI UML2YANG mapping 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 . - 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 - "; + Changes included in this TAPI release (v2.1.0) are listed in + "; reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model "; } diff --git a/YANG/tapi-dsr@2018-10-16.tree b/YANG/tapi-dsr@2018-12-10.tree similarity index 100% rename from YANG/tapi-dsr@2018-10-16.tree rename to YANG/tapi-dsr@2018-12-10.tree diff --git a/YANG/tapi-dsr@2018-10-16.yang b/YANG/tapi-dsr@2018-12-10.yang similarity index 75% rename from YANG/tapi-dsr@2018-10-16.yang rename to YANG/tapi-dsr@2018-12-10.yang index 545f5855..77f5a8b5 100755 --- a/YANG/tapi-dsr@2018-10-16.yang +++ b/YANG/tapi-dsr@2018-12-10.yang @@ -10,21 +10,32 @@ module tapi-dsr { Project List: Editor: Karthik Sethuraman "; - 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] + + and further edited manually to comply with the [ONF IISOMI UML2YANG mapping 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 . + 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 + "; + reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model + "; + } 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] - - and further edited manually to comply with the [ONF IISOMI UML2YANG mapping 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 . - 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 - "; + Changes included in this TAPI release (v2.1.0) are listed in + "; reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model "; } diff --git a/YANG/tapi-eth@2018-10-16.tree b/YANG/tapi-eth@2018-12-10.tree similarity index 100% rename from YANG/tapi-eth@2018-10-16.tree rename to YANG/tapi-eth@2018-12-10.tree diff --git a/YANG/tapi-eth@2018-10-16.yang b/YANG/tapi-eth@2018-12-10.yang similarity index 95% rename from YANG/tapi-eth@2018-10-16.yang rename to YANG/tapi-eth@2018-12-10.yang index 383558eb..953affaf 100755 --- a/YANG/tapi-eth@2018-10-16.yang +++ b/YANG/tapi-eth@2018-12-10.yang @@ -21,22 +21,29 @@ module tapi-eth { "; description "This module contains TAPI ETH Model definitions. Source: TapiEth.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] + + and further edited manually to comply with the [ONF IISOMI UML2YANG mapping 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 . + 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 + "; + reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model + "; + } 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] - - and further edited manually to comply with the [ONF IISOMI UML2YANG mapping 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 . - 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 - "; + Changes included in this TAPI release (v2.1.0) are listed in + "; reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model "; } diff --git a/YANG/tapi-notification@2018-10-16.tree b/YANG/tapi-notification@2018-12-10.tree similarity index 100% rename from YANG/tapi-notification@2018-10-16.tree rename to YANG/tapi-notification@2018-12-10.tree diff --git a/YANG/tapi-notification@2018-10-16.yang b/YANG/tapi-notification@2018-12-10.yang similarity index 88% rename from YANG/tapi-notification@2018-10-16.yang rename to YANG/tapi-notification@2018-12-10.yang index 2885abc4..28071af0 100755 --- a/YANG/tapi-notification@2018-10-16.yang +++ b/YANG/tapi-notification@2018-12-10.yang @@ -13,22 +13,29 @@ module tapi-notification { description " This module contains TAPI Notification Model definitions. Source: TapiNotification.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] + + and further edited manually to comply with the [ONF IISOMI UML2YANG mapping 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 . + 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 + "; + reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model + "; + } 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] - - and further edited manually to comply with the [ONF IISOMI UML2YANG mapping 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 . - 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 - "; + Changes included in this TAPI release (v2.1.0) are listed in + "; reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model "; } diff --git a/YANG/tapi-oam@2018-10-16.tree b/YANG/tapi-oam@2018-12-10.tree similarity index 100% rename from YANG/tapi-oam@2018-10-16.tree rename to YANG/tapi-oam@2018-12-10.tree diff --git a/YANG/tapi-oam@2018-10-16.yang b/YANG/tapi-oam@2018-12-10.yang similarity index 90% rename from YANG/tapi-oam@2018-10-16.yang rename to YANG/tapi-oam@2018-12-10.yang index 143b7901..5410ba45 100755 --- a/YANG/tapi-oam@2018-10-16.yang +++ b/YANG/tapi-oam@2018-12-10.yang @@ -19,22 +19,29 @@ module tapi-oam { description " This module contains TAPI OAM Model definitions. Source: TapiOam.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] + + and further edited manually to comply with the [ONF IISOMI UML2YANG mapping 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 . + 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 + "; + reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model + "; + } 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] - - and further edited manually to comply with the [ONF IISOMI UML2YANG mapping 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 . - 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 - "; + Changes included in this TAPI release (v2.1.0) are listed in + "; reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model "; } diff --git a/YANG/tapi-odu@2018-10-16.tree b/YANG/tapi-odu@2018-12-10.tree similarity index 100% rename from YANG/tapi-odu@2018-10-16.tree rename to YANG/tapi-odu@2018-12-10.tree diff --git a/YANG/tapi-odu@2018-10-16.yang b/YANG/tapi-odu@2018-12-10.yang similarity index 92% rename from YANG/tapi-odu@2018-10-16.yang rename to YANG/tapi-odu@2018-12-10.yang index d927fddd..8d104b90 100755 --- a/YANG/tapi-odu@2018-10-16.yang +++ b/YANG/tapi-odu@2018-12-10.yang @@ -25,22 +25,29 @@ module tapi-odu { description " This module contains TAPI Odu Model definitions. Source: TapiOdu.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] + + and further edited manually to comply with the [ONF IISOMI UML2YANG mapping 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 . + 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 + "; + reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model + "; + } 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] - - and further edited manually to comply with the [ONF IISOMI UML2YANG mapping 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 . - 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 - "; + Changes included in this TAPI release (v2.1.0) are listed in + "; reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model "; } diff --git a/YANG/tapi-path-computation@2018-10-16.tree b/YANG/tapi-path-computation@2018-12-10.tree similarity index 100% rename from YANG/tapi-path-computation@2018-10-16.tree rename to YANG/tapi-path-computation@2018-12-10.tree diff --git a/YANG/tapi-path-computation@2018-10-16.yang b/YANG/tapi-path-computation@2018-12-10.yang similarity index 87% rename from YANG/tapi-path-computation@2018-10-16.yang rename to YANG/tapi-path-computation@2018-12-10.yang index ba6173d3..eeae3e27 100755 --- a/YANG/tapi-path-computation@2018-10-16.yang +++ b/YANG/tapi-path-computation@2018-12-10.yang @@ -16,22 +16,29 @@ module tapi-path-computation { description " This module contains TAPI Path Computation Model definitions. Source: TapiPathComputation.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] + + and further edited manually to comply with the [ONF IISOMI UML2YANG mapping 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 . + 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 + "; + reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model + "; + } 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] - - and further edited manually to comply with the [ONF IISOMI UML2YANG mapping 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 . - 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 - "; + Changes included in this TAPI release (v2.1.0) are listed in + "; reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model "; } diff --git a/YANG/tapi-photonic-media@2018-10-16.tree b/YANG/tapi-photonic-media@2018-12-10.tree similarity index 100% rename from YANG/tapi-photonic-media@2018-10-16.tree rename to YANG/tapi-photonic-media@2018-12-10.tree diff --git a/YANG/tapi-photonic-media@2018-10-16.yang b/YANG/tapi-photonic-media@2018-12-10.yang similarity index 93% rename from YANG/tapi-photonic-media@2018-10-16.yang rename to YANG/tapi-photonic-media@2018-12-10.yang index 5ae8fe1c..dc69c768 100755 --- a/YANG/tapi-photonic-media@2018-10-16.yang +++ b/YANG/tapi-photonic-media@2018-12-10.yang @@ -19,22 +19,29 @@ module tapi-photonic-media { description " This module contains TAPI PhotonicMedia Model definitions. Source: TapiPhotonicMedia.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] + + and further edited manually to comply with the [ONF IISOMI UML2YANG mapping 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 . + 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 + "; + reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model + "; + } 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] - - and further edited manually to comply with the [ONF IISOMI UML2YANG mapping 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 . - 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 - "; + Changes included in this TAPI release (v2.1.0) are listed in + "; reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model "; } diff --git a/YANG/tapi-topology@2018-10-16.tree b/YANG/tapi-topology@2018-12-10.tree similarity index 100% rename from YANG/tapi-topology@2018-10-16.tree rename to YANG/tapi-topology@2018-12-10.tree diff --git a/YANG/tapi-topology@2018-10-16.yang b/YANG/tapi-topology@2018-12-10.yang similarity index 92% rename from YANG/tapi-topology@2018-10-16.yang rename to YANG/tapi-topology@2018-12-10.yang index df459aae..0d35d859 100755 --- a/YANG/tapi-topology@2018-10-16.yang +++ b/YANG/tapi-topology@2018-12-10.yang @@ -13,22 +13,29 @@ module tapi-topology { description " This module contains TAPI Topology Model definitions. Source: TapiTopology.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] + + and further edited manually to comply with the [ONF IISOMI UML2YANG mapping 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 . + 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 + "; + reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model + "; + } 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] - - and further edited manually to comply with the [ONF IISOMI UML2YANG mapping 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 . - 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 - "; + Changes included in this TAPI release (v2.1.0) are listed in + "; reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model "; } diff --git a/YANG/tapi-virtual-network@2018-10-16.tree b/YANG/tapi-virtual-network@2018-12-10.tree similarity index 100% rename from YANG/tapi-virtual-network@2018-10-16.tree rename to YANG/tapi-virtual-network@2018-12-10.tree diff --git a/YANG/tapi-virtual-network@2018-10-16.yang b/YANG/tapi-virtual-network@2018-12-10.yang similarity index 83% rename from YANG/tapi-virtual-network@2018-10-16.yang rename to YANG/tapi-virtual-network@2018-12-10.yang index 8ab1bb47..e6ed2446 100755 --- a/YANG/tapi-virtual-network@2018-10-16.yang +++ b/YANG/tapi-virtual-network@2018-12-10.yang @@ -16,22 +16,29 @@ module tapi-virtual-network { description " This module contains TAPI Virtual Network Model definitions. Source: TapiVirtualNetwork.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] + + and further edited manually to comply with the [ONF IISOMI UML2YANG mapping 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 . + 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 + "; + reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model + "; + } 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] - - and further edited manually to comply with the [ONF IISOMI UML2YANG mapping 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 . - 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 - "; + Changes included in this TAPI release (v2.1.0) are listed in + "; reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model "; }