1 module transportpce-pce {
2 namespace "http://org/opendaylight/transportpce/pce";
3 prefix org-opendaylight-transportpce-pce;
5 import transportpce-routing-constraints {
6 prefix transportpce-routing-constraints;
8 import org-openroadm-common-service-types {
9 prefix org-openroadm-common-service-types;
10 revision-date 2019-05-31;
12 import transportpce-common-service-path-types {
13 prefix transportpce-common-service-path-types;
15 import transportpce-pathDescription {
16 prefix transportpce-pathDescription;
18 import gnpy-path-computation-simplified {
25 "transportPCE committers - ODL";
27 "YANG definitions of B interface (transportPCE). Adapted from service definition (openroadm)
28 Copyright © 2017 Orange, Inc. and others. All rights reserved.
31 Copyright of the Members of the Open ROADM MSA Agreement dated (c) 2016,
32 AT&T Intellectual Property. All other rights reserved.
34 Redistribution and use in source and binary forms, with or without modification,
35 are permitted provided that the following conditions are met:
37 * Redistributions of source code must retain the above copyright notice, this
38 list of conditions and the following disclaimer.
39 * Redistributions in binary form must reproduce the above copyright notice,
40 this list of conditions and the following disclaimer in the documentation and/or
41 other materials provided with the distribution.
42 * Neither the Members of the Open ROADM MSA Agreement nor the names of its
43 contributors may be used to endorse or promote products derived from this software
44 without specific prior written permission.
46 THIS SOFTWARE IS PROVIDED BY THE MEMBERS OF THE OPEN ROADM MSA AGREEMENT ''AS IS''
47 AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
48 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
49 IN NO EVENT THE MEMBERS OF THE OPEN ROADM MSA AGREEMENT BE LIABLE FOR ANY DIRECT,
50 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
51 NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA,
52 OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
53 WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
54 ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
55 POSSIBILITY OF SUCH DAMAGE";
74 grouping stubpce-path-description {
79 "Identifier for the pathDescription to be created in the ROADM
80 network, e.g., CLFI, CLCI, etc.";
82 uses transportpce-pathDescription:path-description;
99 "true : feasible path / False : non-feasible.";
101 choice response-type {
106 uses gnpypc:no-path-info;
110 "Path computation service.";
111 uses path-performance;
117 grouping path-performance {
119 "TE generic path properties grouping";
120 container path-properties {
123 "The TE path properties";
127 "TE path metric type";
130 base gnpypc:path-metric-type;
133 leaf accumulative-value {
142 rpc path-computation-request {
148 "Identifier for the service to be created in the ROADM network,
149 e.g., CLFI, CLCI, etc. This is reported against the service, but
150 may not get reflected in the service in the network.";
152 leaf resource-reserve {
156 "indicates if resources (from local PCE topology) must be reserved
157 until further notice (cancel-resource-reserve or topology update)";
159 uses transportpce-common-service-path-types:service-handler-header;
160 container service-a-end {
161 uses transportpce-common-service-path-types:service-endpoint-sp;
163 container service-z-end {
164 uses transportpce-common-service-path-types:service-endpoint-sp;
166 uses transportpce-routing-constraints:routing-constraints-sp;
167 uses org-openroadm-common-service-types:routing-metric;
170 uses org-openroadm-common-service-types:configuration-response-common;
171 uses transportpce-common-service-path-types:response-parameters-sp;
176 rpc cancel-resource-reserve {
182 uses transportpce-common-service-path-types:service-handler-header;
185 uses org-openroadm-common-service-types:configuration-response-common;
189 notification service-path-rpc-result {
191 "This Notification indicates result of service RPC";
192 leaf notification-type {
193 type transportpce-common-service-path-types:service-path-notification-types;
195 container path-description {
196 uses transportpce-pathDescription:path-description;
198 uses transportpce-common-service-path-types:rpc-response-status-ex;
199 uses org-openroadm-common-service-types:service-notification-result;
200 uses org-openroadm-common-service-types:routing-metric;
203 container path-description-list {
205 "List of pathDescription. Can only be created, deleted, modified,
206 etc. using special RPCs.";
207 list pathDescriptions {
209 uses stubpce-path-description;