Adapt PCE code for OTN services
[transportpce.git] / api / src / main / yang / service_path / transportpce-renderer-device@2017-02-28.yang
1 module transportpce-device-renderer {
2   namespace "http://org/opendaylight/transportpce/renderer/device";
3   prefix "org-opendaylight-transportpce-renderer-device";
4
5   import transportpce-common-types {
6       prefix org-transportpce-common-types;
7       revision-date 2017-09-07;
8   }
9
10   organization
11        "transportPCE";
12      contact
13        "transportPCE committers - ODL";
14      description
15        "YANG definitions of RPCs supported by renderer.
16         Copyright (c) 2017 AT&T and others.  All rights reserved.
17         authors: Dhruv Bhardwaj ( db929a@att.com )
18                  Shweta Vachhani ( sv111y@att.com )";
19
20   revision "2017-02-28" {
21     description "Initial revision of renderer model version 1.5";
22   }
23
24   rpc service-path {
25     input {
26       leaf modulation-format {
27           type string;
28       }
29       leaf operation {
30         type enumeration {
31           enum "create" {
32             value 1;
33           }
34           enum "delete" {
35             value 2;
36           }
37         }
38       }
39       uses org-transportpce-common-types:olm-renderer-input;
40     }
41     output{
42       leaf success {
43         type boolean;
44       }
45       leaf result {
46         type string;
47       }
48       uses org-transportpce-common-types:node-interfaces;
49     }
50   }
51
52   rpc renderer-rollback {
53     input {
54       uses org-transportpce-common-types:node-interfaces;
55     }
56     output {
57       leaf success {
58         type boolean;
59       }
60       list failed-to-rollback {
61         key node-id;
62         leaf node-id {
63           type string;
64         }
65         leaf-list interface {
66           type string;
67         }
68       }
69     }
70   }
71
72   rpc create-ots-oms {
73     input {
74       leaf node-id {
75         type string;
76       }
77       leaf logical-connection-point {
78         type string;
79       }
80     }
81     output {
82       leaf success {
83         type boolean;
84       }
85       leaf result {
86         type string;
87       }
88     }
89   }
90 }