[ODTN]Fix indentation for Yang files
It is change only in appearance.
Change-Id: I09cbf6d3a47b2d6f1ea8c2504f0a1cbde7ce126f
diff --git a/models/tapi/src/main/yang/tapi-virtual-network@2018-10-16.yang b/models/tapi/src/main/yang/tapi-virtual-network@2018-10-16.yang
old mode 100644
new mode 100755
index 6e87288..8ab1bb4
--- a/models/tapi/src/main/yang/tapi-virtual-network@2018-10-16.yang
+++ b/models/tapi/src/main/yang/tapi-virtual-network@2018-10-16.yang
@@ -32,28 +32,28 @@
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>";
- reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model
+ 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-03-07 {
- description "ONF Transport API version 2.0.2
- This YANG module has been generated from the TAPI UML Model using the IISOMI-Eagle xmi2yang mapping tool.
+ description "ONF Transport API version 2.0.2
+ This YANG module has been generated from the TAPI UML Model using the IISOMI-Eagle xmi2yang mapping tool.
Changes in this revision: <https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.0.2.md>";
- reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 6020, RFC 6087 and ONF TAPI UML model
+ reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 6020, RFC 6087 and ONF TAPI UML model
<https://github.com/OpenNetworkingFoundation/TAPI/tree/v2.0.2/UML>";
}
revision 2018-02-16 {
- description "ONF Transport API version 2.0.1
- This YANG module has been generated from the TAPI UML Model using the IISOMI-Eagle xmi2yang mapping tool.
+ description "ONF Transport API version 2.0.1
+ This YANG module has been generated from the TAPI UML Model using the IISOMI-Eagle xmi2yang mapping tool.
Changes in this revision: <https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.0.1.md>";
- reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 6020, RFC 6087 and ONF TAPI UML model
+ reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 6020, RFC 6087 and ONF TAPI UML model
<https://github.com/OpenNetworkingFoundation/TAPI/tree/v2.0.1/UML>";
}
revision 2018-01-02 {
- description "ONF Transport API version 2.0.0
- This YANG module has been generated from the TAPI UML Model using the IISOMI-Eagle xmi2yang mapping tool.
+ description "ONF Transport API version 2.0.0
+ This YANG module has been generated from the TAPI UML Model using the IISOMI-Eagle xmi2yang mapping tool.
Changes in this revision: <https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.0.0.md>";
- reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 6020, RFC 6087 and ONF TAPI UML model
+ reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 6020, RFC 6087 and ONF TAPI UML model
<https://github.com/OpenNetworkingFoundation/TAPI/tree/v2.0.0/UML>";
}
augment "/tapi-common:context" {
@@ -63,9 +63,10 @@
}
description "Augments the base TAPI Context with VirtualNetworkService information";
}
- /*************************
+
+ /**************************
* definitions of refrences
- *************************/
+ **************************/
grouping virtual-nw-service-ref {
leaf virtual-nw-service-uuid {
type leafref {
@@ -75,193 +76,192 @@
}
description "none";
}
-
- /***********************
- * package object-classes
- **********************/
- grouping virtual-network-constraint {
- container src-service-end-point {
- uses tapi-common:service-interface-point-ref;
- config false;
- description "none";
- }
- container sink-service-end-point {
- uses tapi-common:service-interface-point-ref;
- config false;
- description "none";
- }
- list diversity-exclusion {
- uses virtual-nw-service-ref;
- key 'virtual-nw-service-uuid';
- config false;
- description "none";
- }
- container requested-capacity {
- uses tapi-common:capacity;
- description "none";
- }
- leaf service-level {
- type string;
- description "An abstract value the meaning of which is mutually agreed – typically represents metrics such as - Class of service, priority, resiliency, availability";
- }
- leaf-list service-layer {
- type tapi-common:layer-protocol-name;
- description "none";
- }
- list cost-characteristic {
- key 'cost-name';
- uses tapi-topology:cost-characteristic;
- description "The list of costs where each cost relates to some aspect of the TopologicalEntity.";
- }
- list latency-characteristic {
- key 'traffic-property-name';
- uses tapi-topology:latency-characteristic;
- description "The effect on the latency of a queuing process. This only has significant effect for packet based systems and has a complex characteristic.";
- }
- uses tapi-common:local-class;
- description "none";
- }
- grouping virtual-network-service {
- container topology {
- uses tapi-topology:topology-ref;
- config false;
- description "none";
- }
- list end-point {
- key 'local-id';
- min-elements 2;
- uses virtual-network-service-end-point;
- description "none";
- }
- list vnw-constraint {
- key 'local-id';
- min-elements 1;
- uses virtual-network-constraint;
- description "none";
- }
- leaf schedule {
- type string;
- description "none";
- }
- container state {
- uses tapi-common:admin-state-pac;
- description "none";
- }
- leaf-list layer-protocol-name {
- type tapi-common:layer-protocol-name;
- min-elements 1;
- description "none";
- }
- uses tapi-common:service-spec;
- description "The ForwardingConstruct (FC) object class models enabled potential for forwarding between two or more LTPs and like the LTP supports any transport protocol including all circuit and packet forms.
- At the lowest level of recursion, a FC represents a cross-connection within an NE.";
- }
- grouping virtual-network-service-end-point {
- container service-interface-point {
- uses tapi-common:service-interface-point-ref;
- config false;
- description "none";
- }
- leaf role {
- type tapi-common:port-role;
- config false;
- description "Each EP of the FC has a role (e.g., working, protection, protected, symmetric, hub, spoke, leaf, root) in the context of the FC with respect to the FC function. ";
- }
- leaf direction {
- type tapi-common:port-direction;
- config false;
- description "The orientation of defined flow at the EndPoint.";
- }
- leaf service-layer {
- type tapi-common:layer-protocol-name;
- config false;
- description "none";
- }
- uses tapi-common:local-class;
- description "The association of the FC to LTPs is made via EndPoints.
- The EndPoint (EP) object class models the access to the FC function.
- The traffic forwarding between the associated EPs of the FC depends upon the type of FC and may be associated with FcSwitch object instances.
- In cases where there is resilience the EndPoint may convey the resilience role of the access to the FC.
- It can represent a protected (resilient/reliable) point or a protecting (unreliable working or protection) point.
- The EP replaces the Protection Unit of a traditional protection model.
- The ForwadingConstruct can be considered as a component and the EndPoint as a Port on that component";
- }
- grouping virtual-network-context {
- list virtual-nw-service {
- key 'uuid';
- uses virtual-network-service;
- description "none";
- }
- description "none";
- }
- /***********************
- * package interfaces
- **********************/
- rpc create-virtual-network-service {
- description "none";
- input {
- list sep {
- key 'local-id';
- min-elements 2;
- uses virtual-network-service-end-point;
- description "none";
- }
- container vnw-constraint {
- uses virtual-network-constraint;
- description "none";
- }
- leaf conn-schedule {
- type string;
- description "none";
- }
- }
- output {
- container service {
- uses virtual-network-service;
- description "none";
- }
- }
- }
- rpc delete-virtual-network-service {
- description "none";
- input {
- leaf service-id-or-name {
- type string;
- description "none";
- }
- }
- output {
- container service {
- uses virtual-network-service;
- description "none";
- }
- }
- }
- rpc get-virtual-network-service-details {
- description "none";
- input {
- leaf service-id-or-name {
- type string;
- description "none";
- }
- }
- output {
- container service {
- uses virtual-network-service;
- description "none";
- }
- }
- }
- rpc get-virtual-network-service-list {
- description "none";
- output {
- list service {
- key 'uuid';
- uses virtual-network-service;
- description "none";
- }
- }
- }
+ /**************************
+ * package object-classes
+ **************************/
+ grouping virtual-network-constraint {
+ container src-service-end-point {
+ uses tapi-common:service-interface-point-ref;
+ config false;
+ description "none";
+ }
+ container sink-service-end-point {
+ uses tapi-common:service-interface-point-ref;
+ config false;
+ description "none";
+ }
+ list diversity-exclusion {
+ uses virtual-nw-service-ref;
+ key 'virtual-nw-service-uuid';
+ config false;
+ description "none";
+ }
+ container requested-capacity {
+ uses tapi-common:capacity;
+ description "none";
+ }
+ leaf service-level {
+ type string;
+ description "An abstract value the meaning of which is mutually agreed – typically represents metrics such as - Class of service, priority, resiliency, availability";
+ }
+ leaf-list service-layer {
+ type tapi-common:layer-protocol-name;
+ description "none";
+ }
+ list cost-characteristic {
+ key 'cost-name';
+ uses tapi-topology:cost-characteristic;
+ description "The list of costs where each cost relates to some aspect of the TopologicalEntity.";
+ }
+ list latency-characteristic {
+ key 'traffic-property-name';
+ uses tapi-topology:latency-characteristic;
+ description "The effect on the latency of a queuing process. This only has significant effect for packet based systems and has a complex characteristic.";
+ }
+ uses tapi-common:local-class;
+ description "none";
+ }
+ grouping virtual-network-service {
+ container topology {
+ uses tapi-topology:topology-ref;
+ config false;
+ description "none";
+ }
+ list end-point {
+ key 'local-id';
+ min-elements 2;
+ uses virtual-network-service-end-point;
+ description "none";
+ }
+ list vnw-constraint {
+ key 'local-id';
+ min-elements 1;
+ uses virtual-network-constraint;
+ description "none";
+ }
+ leaf schedule {
+ type string;
+ description "none";
+ }
+ container state {
+ uses tapi-common:admin-state-pac;
+ description "none";
+ }
+ leaf-list layer-protocol-name {
+ type tapi-common:layer-protocol-name;
+ min-elements 1;
+ description "none";
+ }
+ uses tapi-common:service-spec;
+ description "The ForwardingConstruct (FC) object class models enabled potential for forwarding between two or more LTPs and like the LTP supports any transport protocol including all circuit and packet forms.
+ At the lowest level of recursion, a FC represents a cross-connection within an NE.";
+ }
+ grouping virtual-network-service-end-point {
+ container service-interface-point {
+ uses tapi-common:service-interface-point-ref;
+ config false;
+ description "none";
+ }
+ leaf role {
+ type tapi-common:port-role;
+ config false;
+ description "Each EP of the FC has a role (e.g., working, protection, protected, symmetric, hub, spoke, leaf, root) in the context of the FC with respect to the FC function. ";
+ }
+ leaf direction {
+ type tapi-common:port-direction;
+ config false;
+ description "The orientation of defined flow at the EndPoint.";
+ }
+ leaf service-layer {
+ type tapi-common:layer-protocol-name;
+ config false;
+ description "none";
+ }
+ uses tapi-common:local-class;
+ description "The association of the FC to LTPs is made via EndPoints.
+ The EndPoint (EP) object class models the access to the FC function.
+ The traffic forwarding between the associated EPs of the FC depends upon the type of FC and may be associated with FcSwitch object instances.
+ In cases where there is resilience the EndPoint may convey the resilience role of the access to the FC.
+ It can represent a protected (resilient/reliable) point or a protecting (unreliable working or protection) point.
+ The EP replaces the Protection Unit of a traditional protection model.
+ The ForwadingConstruct can be considered as a component and the EndPoint as a Port on that component";
+ }
+ grouping virtual-network-context {
+ list virtual-nw-service {
+ key 'uuid';
+ uses virtual-network-service;
+ description "none";
+ }
+ description "none";
+ }
+ /**************************
+ * package interfaces
+ **************************/
+ rpc create-virtual-network-service {
+ description "none";
+ input {
+ list sep {
+ key 'local-id';
+ min-elements 2;
+ uses virtual-network-service-end-point;
+ description "none";
+ }
+ container vnw-constraint {
+ uses virtual-network-constraint;
+ description "none";
+ }
+ leaf conn-schedule {
+ type string;
+ description "none";
+ }
+ }
+ output {
+ container service {
+ uses virtual-network-service;
+ description "none";
+ }
+ }
+ }
+ rpc delete-virtual-network-service {
+ description "none";
+ input {
+ leaf service-id-or-name {
+ type string;
+ description "none";
+ }
+ }
+ output {
+ container service {
+ uses virtual-network-service;
+ description "none";
+ }
+ }
+ }
+ rpc get-virtual-network-service-details {
+ description "none";
+ input {
+ leaf service-id-or-name {
+ type string;
+ description "none";
+ }
+ }
+ output {
+ container service {
+ uses virtual-network-service;
+ description "none";
+ }
+ }
+ }
+ rpc get-virtual-network-service-list {
+ description "none";
+ output {
+ list service {
+ key 'uuid';
+ uses virtual-network-service;
+ description "none";
+ }
+ }
+ }
}