1 module transportpce-portmapping {
3 namespace "http://org/opendaylight/transportpce/portmapping";
4 prefix "org-opendaylight-transportpce-portmapping";
6 import org-openroadm-common-types {
7 prefix org-openroadm-common-types;
8 revision-date 2016-10-14;
14 "transportPCE committers - ODL";
16 "YANG definitions of RPCs supported by OLM.
17 Copyright (c) 2017 AT&T and others. All rights reserved.
18 authors: Dhruv Bhardwaj ( db929a@att.com )
19 Shweta Vachhani ( sv111y@att.com )";
21 revision "2017-02-28" {
22 description "Initial revision of port mapping model";
30 "Unique identifier for node in the network";
33 leaf openroadm-version{
48 type org-openroadm-common-types:node-types;
50 "Identifier for node-type e.g Roadm, xponder";
54 "Mapping for Physical circuit pack/port/parent interfaces
55 corresponding to each logical connection point present in the node.";
56 key logical-connection-point;
57 leaf logical-connection-point{
60 leaf supporting-circuit-pack-name{
63 "Circuit pack where the logical connection point is located";
68 "Port where the logical connection point is located";
73 "OMS interface provisioned on the port";
78 "OTS interface provisioned on the port";
83 "Useful for line port of XPDR, for which there is no
84 indication in its logical-termination-point naming";
89 "Useful to identify from portmapping client from network ports of XPDR";
94 "For XPDR, associate two logical-connection-points
95 from device/connnection-map data";
100 "This mapping helps locate degree number of the circuitpack that does lldp
101 protocol management";
102 key circuit-pack-name;
103 leaf circuit-pack-name{