1 module transportpce-pce {
2 namespace "http://org/opendaylight/transportpce/pce";
3 prefix org-opendaylight-transportpce-pce;
5 import ietf-yang-types {
8 import transportpce-routing-constraints {
9 prefix transportpce-routing-constraints;
11 import org-openroadm-common-service-types {
12 prefix org-openroadm-common-service-types;
14 import transportpce-common-service-path-types {
15 prefix transportpce-common-service-path-types;
17 import transportpce-pathDescription {
18 prefix transportpce-pathDescription;
20 import gnpy-path-computation-simplified {
27 "transportPCE committers - ODL";
29 "YANG definitions of B interface (transportPCE). Adapted from service definition (openroadm)
30 Copyright © 2017 Orange, Inc. and others. All rights reserved.
33 Copyright of the Members of the Open ROADM MSA Agreement dated (c) 2016,
34 AT&T Intellectual Property. All other rights reserved.
36 Redistribution and use in source and binary forms, with or without modification,
37 are permitted provided that the following conditions are met:
39 * Redistributions of source code must retain the above copyright notice, this
40 list of conditions and the following disclaimer.
41 * Redistributions in binary form must reproduce the above copyright notice,
42 this list of conditions and the following disclaimer in the documentation and/or
43 other materials provided with the distribution.
44 * Neither the Members of the Open ROADM MSA Agreement nor the names of its
45 contributors may be used to endorse or promote products derived from this software
46 without specific prior written permission.
48 THIS SOFTWARE IS PROVIDED BY THE MEMBERS OF THE OPEN ROADM MSA AGREEMENT ''AS IS''
49 AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
50 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
51 IN NO EVENT THE MEMBERS OF THE OPEN ROADM MSA AGREEMENT BE LIABLE FOR ANY DIRECT,
52 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
53 NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA,
54 OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
55 WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
56 ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
57 POSSIBILITY OF SUCH DAMAGE";
76 grouping stubpce-path-description {
81 "Identifier for the pathDescription to be created in the ROADM
82 network, e.g., CLFI, CLCI, etc.";
84 uses transportpce-pathDescription:path-description;
101 "true : feasible path / False : non-feasible.";
103 choice response-type {
108 uses gnpypc:no-path-info;
112 "Path computation service.";
113 uses path-performance;
119 grouping path-performance {
121 "TE generic path properties grouping";
122 container path-properties {
125 "The TE path properties";
129 "TE path metric type";
132 base gnpypc:path-metric-type;
135 leaf accumulative-value {
144 rpc path-computation-request {
150 "Identifier for the service to be created in the ROADM network,
151 e.g., CLFI, CLCI, etc. This is reported against the service, but
152 may not get reflected in the service in the network.";
154 leaf resource-reserve {
158 "indicates if resources (from local PCE topology) must be reserved
159 until further notice (cancel-resource-reserve or topology update)";
161 uses transportpce-common-service-path-types:service-handler-header;
162 container service-a-end {
163 uses transportpce-common-service-path-types:service-endpoint-sp;
165 container service-z-end {
166 uses transportpce-common-service-path-types:service-endpoint-sp;
168 uses transportpce-routing-constraints:routing-constraints-sp;
169 uses org-openroadm-common-service-types:routing-metric;
172 uses org-openroadm-common-service-types:configuration-response-common;
173 uses transportpce-common-service-path-types:response-parameters-sp;
178 rpc cancel-resource-reserve {
184 uses transportpce-common-service-path-types:service-handler-header;
187 uses org-openroadm-common-service-types:configuration-response-common;
191 notification service-path-rpc-result {
193 "This Notification indicates result of service RPC";
194 leaf notification-type {
195 type transportpce-common-service-path-types:service-path-notification-types;
197 container path-description {
198 uses transportpce-pathDescription:path-description;
200 uses transportpce-common-service-path-types:rpc-response-status-ex;
201 uses org-openroadm-common-service-types:service-notification-result;
202 uses org-openroadm-common-service-types:routing-metric;
205 container path-description-list {
207 "List of pathDescription. Can only be created, deleted, modified,
208 etc. using special RPCs.";
209 list pathDescriptions {
211 uses stubpce-path-description;