1 module transportpce-renderer {
2 namespace "http://org/opendaylight/transportpce/renderer";
3 prefix org-opendaylight-transportpce-renderer;
5 import org-openroadm-common-service-types {
6 prefix org-openroadm-common-service-types;
8 import transportpce-common-service-path-types {
9 prefix transportpce-common-service-path-types;
11 import org-openroadm-topology {
12 prefix org-openroadm-topology;
14 import transportpce-pathDescription {
15 prefix transportpce-pathDescription;
17 import transportpce-common-types {
18 prefix org-transportpce-common-types;
24 "transportPCE committers - ODL";
26 "YANG definitions of C interface (transportPCE). Adapted from service definition (openroadm)
27 Copyright © 2017 Orange, Inc. and others. All rights reserved.
30 Copyright of the Members of the Open ROADM MSA Agreement dated (c) 2016,
31 AT&T Intellectual Property. All other rights reserved.
33 Redistribution and use in source and binary forms, with or without modification,
34 are permitted provided that the following conditions are met:
36 * Redistributions of source code must retain the above copyright notice, this
37 list of conditions and the following disclaimer.
38 * Redistributions in binary form must reproduce the above copyright notice,
39 this list of conditions and the following disclaimer in the documentation and/or
40 other materials provided with the distribution.
41 * Neither the Members of the Open ROADM MSA Agreement nor the names of its
42 contributors may be used to endorse or promote products derived from this software
43 without specific prior written permission.
45 THIS SOFTWARE IS PROVIDED BY THE MEMBERS OF THE OPEN ROADM MSA AGREEMENT ''AS IS''
46 AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
47 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
48 IN NO EVENT THE MEMBERS OF THE OPEN ROADM MSA AGREEMENT BE LIABLE FOR ANY DIRECT,
49 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
50 NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA,
51 OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
52 WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
53 ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
54 POSSIBILITY OF SUCH DAMAGE";
59 Add list of link-id to the notification";
64 Add optical-renderer-nodes to the notification";
80 "Initial revision of renderer model version 1.5";
83 grouping link-for-notif {
85 "In most of the cases, only 2 link-termination-points exists.
86 It reveals that the service is supported by a single otn-link
87 to configure. Its properties can be easily transmited by this way.";
88 container a-termination {
96 container z-termination {
106 rpc service-implementation-request {
112 "Identifier for the service to be created in
113 the ROADM network, e.g., CLFI, CLCI, etc. This is reported against the service, but may not get reflected in the service in the network.";
115 leaf connection-type {
116 type org-openroadm-common-service-types:connection-type;
118 uses transportpce-common-service-path-types:service-handler-header;
119 container service-a-end {
120 uses transportpce-common-service-path-types:service-endpoint-sp;
122 container service-z-end {
123 uses transportpce-common-service-path-types:service-endpoint-sp;
125 container path-description {
126 uses transportpce-pathDescription:path-description;
130 uses org-openroadm-common-service-types:configuration-response-common;
140 "Identifier for the service to be created in
141 the ROADM network, e.g., CLFI, CLCI, etc. This is reported against the service, but may not get reflected in the service in the network.";
143 uses transportpce-common-service-path-types:service-handler-header;
146 uses org-openroadm-common-service-types:configuration-response-common;
150 notification renderer-rpc-result-sp {
152 "This Notification indicates result of renderer RPC and provides the topology";
153 leaf notification-type {
154 type transportpce-common-service-path-types:service-path-notification-types;
156 container path-topology {
157 uses org-openroadm-topology:topology;
159 uses transportpce-pathDescription:path-description;
160 uses transportpce-common-service-path-types:rpc-response-status-ex;
161 uses org-openroadm-common-service-types:service-notification-result;
168 "when more than 2 link-termination-points exists,
169 it reveals that the service is supported by multiple
170 links (typically, OTU4). In such a case, it is more appropriated
171 to transmit the list of supported links with their link-id";