1 module GENERIC-RESOURCE-API {
\r
3 namespace "org:onap:sdnc:northbound:generic-resource";
\r
5 prefix generic-resource-api;
\r
7 import ietf-inet-types { prefix "inet"; revision-date "2013-07-15"; }
\r
9 import ietf-yang-types { prefix yang; }
\r
11 revision "2017-08-24" {
\r
13 "ONAP Amsterdam version";
\r
16 grouping service-model-infrastructure {
\r
18 key "service-instance-id";
\r
19 leaf service-instance-id {
\r
20 description "Keep as M";
\r
25 uses service-status;
\r
28 grouping service-data {
\r
29 container service-data {
\r
30 uses service-operation-information;
\r
31 uses service-topology;
\r
32 uses service-level-oper-status;
\r
33 container networks {
\r
42 container network-data {
\r
43 uses network-operation-information;
\r
44 uses network-topology;
\r
45 container network-provided-allotted-resources {
\r
46 leaf-list network-provided-ar-id {
\r
47 description "List of allotted resources using capacity from this network";
\r
54 uses network-level-oper-status;
\r
65 container pnf-data {
\r
66 uses pnf-operation-information;
\r
68 uses pnf-level-oper-status;
\r
81 container vnf-data {
\r
82 uses vnf-operation-information;
\r
84 container vnf-network-collections {
\r
85 uses vnf-network-collection;
\r
87 container vnf-sub-interface-groups {
\r
88 uses vnf-sub-interface-group;
\r
90 container vnf-provided-allotted-resources {
\r
91 leaf-list vnf-provided-ar-id {
\r
92 description "List of allotted resources using capacity from this vnf";
\r
99 uses vnf-level-oper-status;
\r
100 container vf-modules {
\r
102 key "vf-module-id";
\r
103 leaf vf-module-id {
\r
109 container vf-module-data {
\r
110 uses vf-module-operation-information;
\r
111 uses vf-module-topology;
\r
112 uses vf-module-level-oper-status;
\r
119 container consumed-allotted-resources {
\r
120 list consumed-allotted-resource {
\r
121 key "allotted-resource-id";
\r
122 uses allotted-resource-info;
\r
125 container provided-allotted-resources {
\r
126 list provided-allotted-resource {
\r
127 key "allotted-resource-id";
\r
128 uses allotted-resource-info;
\r
131 container provided-configurations {
\r
132 list provided-configuration {
\r
133 key "configuration-id";
\r
134 uses configuration-info;
\r
137 container vnfc-instance-groups {
\r
138 uses vnfc-instance-group;
\r
140 container network-instance-groups {
\r
141 uses network-instance-group;
\r
143 container forwarding-paths {
\r
144 list forwarding-path {
\r
145 key "forwarding-path-id";
\r
146 leaf forwarding-path-id {
\r
147 description "Generated by SDNC";
\r
153 uses forwarding-path-information;
\r
158 grouping service-status {
\r
159 container service-status {
\r
160 leaf response-code {
\r
165 leaf response-message {
\r
170 leaf final-indicator {
\r
175 leaf request-status {
\r
177 enum "synccomplete";
\r
178 enum "asynccomplete";
\r
179 enum "notifycomplete";
\r
183 description "value would one of possible request-actions; match the list in service-data oper-status";
\r
194 description "this is the svc-action from the incoming request";
\r
205 leaf response-timestamp {
\r
212 grouping service-operation-information {
\r
213 uses sdnc-request-header;
\r
214 uses request-information;
\r
215 uses service-information;
\r
216 uses service-request-input;
\r
218 grouping service-request-input {
\r
219 container service-request-input {
\r
220 leaf service-instance-name {
\r
225 container service-input-parameters {
\r
230 grouping service-topology {
\r
231 container service-topology {
\r
232 uses service-topology-identifier;
\r
233 uses onap-model-information;
\r
234 uses service-assignments;
\r
235 uses service-parameters;
\r
238 grouping service-topology-identifier {
\r
239 container service-topology-identifier {
\r
240 leaf service-instance-id {
\r
241 description "repeated";
\r
246 leaf service-type {
\r
247 description "tag labeled subscription-service-type in the service-information input";
\r
253 description "from MSO input on STO assign";
\r
258 leaf service-instance-name {
\r
259 description "optionally comes from service-request-input container or is assigned by sdn-c";
\r
264 leaf global-customer-id {
\r
271 grouping service-assignments {
\r
272 container service-assignments {
\r
275 grouping service-parameters {
\r
276 container service-parameters {
\r
277 list service-parameter {
\r
278 key "service-parameter-name";
\r
279 leaf service-parameter-name {
\r
284 leaf service-parameter-value {
\r
286 length "0..20000" ;
\r
292 grouping service-level-oper-status {
\r
293 container service-level-oper-status {
\r
294 uses oper-status-data;
\r
297 grouping network-operation-information {
\r
298 uses sdnc-request-header;
\r
299 uses request-information;
\r
300 uses service-information;
\r
301 uses network-information;
\r
302 uses network-request-input;
\r
304 grouping network-information {
\r
305 container network-information {
\r
311 leaf network-type {
\r
316 leaf network-technology {
\r
321 leaf from-preload {
\r
322 description "Indicates if source is preload data";
\r
325 uses onap-model-information;
\r
328 grouping network-request-input {
\r
329 container network-request-input {
\r
330 leaf network-name {
\r
335 uses region-identifier;
\r
336 container network-input-parameters {
\r
339 leaf network-instance-group-id {
\r
340 description "When network has instance-group role in service model";
\r
347 grouping network-topology {
\r
348 container network-topology {
\r
349 uses network-topology-identifier-structure;
\r
350 uses region-identifier;
\r
351 uses onap-model-information;
\r
352 uses network-assignments;
\r
353 uses network-parameters;
\r
356 grouping network-topology-identifier-structure {
\r
357 container network-topology-identifier-structure {
\r
363 leaf network-name {
\r
368 leaf network-role {
\r
373 leaf network-type {
\r
378 leaf network-instance-group-id {
\r
379 description "When network is part of network instance-Group-data & instance Group in A&AI";
\r
384 leaf network-technology {
\r
389 leaf eipam-v4-address-plan {
\r
394 leaf eipam-v6-address-plan {
\r
402 leaf segmentation-id {
\r
407 container related-networks {
\r
408 uses related-network;
\r
412 grouping network-assignments {
\r
413 container network-assignments {
\r
416 grouping network-parameters {
\r
417 container network-parameters {
\r
418 list network-parameter {
\r
419 key "network-parameter-name";
\r
420 leaf network-parameter-name {
\r
425 leaf network-parameter-value {
\r
433 grouping network-instance-group {
\r
434 list network-instance-group {
\r
435 key "network-instance-group-id";
\r
436 leaf network-instance-group-id {
\r
437 description "Also a Key in Network Instance Group in A&AI";
\r
443 leaf network-instance-group-function {
\r
448 leaf service-instance-id {
\r
453 uses onap-model-information;
\r
454 container subnet-assignment-policy {
\r
456 description "Current valid values - unique, shared (default)";
\r
462 container vpn-binding-policy {
\r
478 leaf vpn-platform {
\r
483 leaf global-route-target {
\r
488 leaf route-target-role {
\r
494 container aggregate-route-policy {
\r
495 leaf aggregate-route-policy-name {
\r
500 leaf ipv4-aggregate-route-level {
\r
505 leaf ipv6-aggregate-route-level {
\r
511 uses aggregate-routes;
\r
513 leaf subnet-key-value {
\r
514 description "key-value provided to IPAM when creating shared subnet";
\r
519 container networks {
\r
523 description "Index into network-topology-identifier structure";
\r
529 leaf neutron-network-id {
\r
530 description "Neutron-network-id assigned by PO/RO";
\r
539 leaf network-status {
\r
540 description "assigned, unassigned";
\r
545 container customer-bonding-requests {
\r
546 list customer-bonding-request {
\r
547 key "configuration-id";
\r
548 leaf configuration-id {
\r
549 description "e.g. vlan network receptor configuration id";
\r
560 grouping network-level-oper-status {
\r
561 container network-level-oper-status {
\r
562 uses oper-status-data;
\r
565 grouping pnf-operation-information {
\r
566 uses sdnc-request-header;
\r
567 uses request-information;
\r
568 uses service-information;
\r
570 uses pnf-request-input;
\r
572 grouping pnf-details {
\r
573 container pnf-details {
\r
575 description "pnfId*Identifier of this Pnf information element. CORRELATIONID = PNF-NAME (A&AI)";
\r
580 description "pnfType (template)*Type of Resource. NEW type: PNF (pre-defined in SDC)";
\r
586 uses onap-model-information;
\r
589 grouping pnf-request-input {
\r
590 container pnf-request-input {
\r
591 leaf request-version {
\r
592 description "keep this? e.g. 1702";
\r
598 uses region-identifier;
\r
599 container pnf-input-parameters {
\r
604 grouping pnf-topology {
\r
605 container pnf-topology {
\r
606 uses pnf-topology-identifier-structure;
\r
607 uses region-identifier;
\r
608 uses onap-model-information;
\r
609 container pnf-parameters-data {
\r
612 leaf sdnc-generated-cloud-resources {
\r
613 description "Indicate if source is sdnc generated cloud param.When true, the parameters are literal HEAT template parameter names;When false, the parameters need to be converted to HEAT format";
\r
618 grouping pnf-topology-identifier-structure {
\r
619 container pnf-topology-identifier-structure {
\r
624 description "In preload tree, this label is used for the vf-module-type";
\r
628 description "optionally comes from pnf-request-input container or is assigned by sdn-c";
\r
633 grouping pnf-level-oper-status {
\r
634 container pnf-level-oper-status {
\r
635 uses oper-status-data;
\r
638 grouping vnf-operation-information {
\r
639 uses sdnc-request-header;
\r
640 uses request-information;
\r
641 uses service-information;
\r
642 uses vnf-information;
\r
643 uses vnf-request-input;
\r
644 uses license-information;
\r
646 grouping vnf-information {
\r
647 container vnf-information {
\r
663 uses onap-model-information;
\r
666 grouping vnf-request-input {
\r
667 container vnf-request-input {
\r
668 leaf request-version {
\r
669 description "keep this? e.g. 1702";
\r
679 uses region-identifier;
\r
680 container vnf-networks {
\r
682 key "network-role";
\r
683 uses vnf-network-data;
\r
686 list vnf-network-instance-group-ids {
\r
687 key "vnf-network-instance-group-id";
\r
688 leaf vnf-network-instance-group-id {
\r
689 description "List of vnf network-instance-group";
\r
695 container vnf-input-parameters {
\r
700 grouping vnf-topology {
\r
701 container vnf-topology {
\r
702 uses vnf-topology-identifier-structure;
\r
703 uses region-identifier;
\r
704 uses onap-model-information;
\r
705 uses vnf-resource-assignments;
\r
706 container vnf-parameters-data {
\r
709 leaf sdnc-generated-cloud-resources {
\r
710 description "Indicate if source is sdnc generated cloud param. When true, the parameters are literal HEAT template parameter names;When false, the parameters need to be converted to HEAT format";
\r
715 grouping vnf-topology-identifier-structure {
\r
716 container vnf-topology-identifier-structure {
\r
723 description "In preload tree, this label is used for the vf-module-type";
\r
742 description "used in vnf naming";
\r
748 description "optionally comes from vnf-request-input container or is assigned by sdn-c";
\r
755 grouping vnf-resource-assignments {
\r
756 container vnf-resource-assignments {
\r
758 description "Orchestration status from AAI - to be set by SDNC";
\r
763 container availability-zones {
\r
764 leaf-list availability-zone {
\r
765 description "Openstack availability zone name or UUID";
\r
772 description "From the TOSCA data. Indicates the largest availability zone count needed by any vf-module in the VNF.";
\r
776 container vnf-networks {
\r
778 key "network-role";
\r
779 uses vnf-network-data;
\r
784 grouping vnf-network-data {
\r
785 leaf network-role {
\r
786 description "A Network Role to which a VNF must connect";
\r
791 leaf network-name {
\r
792 description "Unique Neutron UUID of an instance of the network role ";
\r
798 description "Unique Neutron UUID of an instance of the network role ";
\r
804 description "Unique Neutron UUID of an instance of the network role ";
\r
809 leaf contrail-network-fqdn {
\r
810 description "contrail network policy object";
\r
815 container subnets-data {
\r
817 key "sdnc-subnet-id";
\r
818 leaf sdnc-subnet-id {
\r
819 description "Unique SDNC generated UUID of the subnet. Key into A&AI instance.This maps to ipv4-key-subnet-id and ipv6-key-subnet-id in VNF-API";
\r
825 description "Subnet Role for the subnet";
\r
831 description "Populated for preload only";
\r
837 description "Should be ipv4 or ipv6";
\r
843 description "subnet UUID to be passed into the HEAT template";
\r
848 leaf dhcp-enabled {
\r
849 description "Indicator to use this subnet for DHCP ";
\r
855 leaf network-start-address {
\r
856 description "start-address of the subnet";
\r
857 type inet:ip-address;
\r
859 leaf gateway-address {
\r
860 description "subnet gateway address";
\r
861 type inet:ip-address;
\r
864 description "cidr mask";
\r
874 leaf segmentation-id {
\r
879 container related-networks {
\r
880 uses related-network;
\r
883 grouping vnf-level-oper-status {
\r
884 container vnf-level-oper-status {
\r
885 uses oper-status-data;
\r
888 grouping vf-module-operation-information {
\r
889 uses sdnc-request-header;
\r
890 uses request-information;
\r
891 uses service-information;
\r
892 uses vnf-information;
\r
893 uses vf-module-information;
\r
894 uses vf-module-request-input;
\r
896 grouping vf-module-information {
\r
897 container vf-module-information {
\r
898 leaf vf-module-id {
\r
903 leaf vf-module-type {
\r
908 leaf from-preload {
\r
909 description "Indicates if source is preload data";
\r
912 uses onap-model-information;
\r
915 grouping vf-module-request-input {
\r
916 container vf-module-request-input {
\r
917 leaf request-version {
\r
918 description "keep this?";
\r
923 leaf vf-module-name {
\r
928 uses region-identifier;
\r
929 container vf-module-input-parameters {
\r
934 grouping vf-module-topology {
\r
935 container vf-module-topology {
\r
936 uses vf-module-topology-identifier;
\r
937 uses region-identifier;
\r
938 uses onap-model-information;
\r
939 uses vf-module-assignments;
\r
940 container vf-module-parameters {
\r
943 leaf sdnc-generated-cloud-resources {
\r
944 description "Indicate if source is sdnc-generated-cloud-resources.When true, the parameters are literal HEAT template parameter names;When false, the parameters need to be converted to HEAT format";
\r
949 grouping vf-module-topology-identifier {
\r
950 container vf-module-topology-identifier {
\r
951 leaf vf-module-id {
\r
952 description "vf-module id";
\r
957 leaf vf-module-name {
\r
958 description "vf-module-name";
\r
963 leaf vf-module-type {
\r
970 grouping vf-module-assignments {
\r
971 container vf-module-assignments {
\r
972 leaf vf-module-status {
\r
973 description "Orchestration status from AAI";
\r
981 uses vm-topology-data;
\r
984 uses vlan-vnfc-instance-groups;
\r
985 container dhcp-subnet-assignments {
\r
986 list dhcp-subnet-assignment {
\r
987 key "neutron-subnet-id";
\r
988 leaf neutron-subnet-id {
\r
989 description "Same as subnet-id in subnet-data structure";
\r
995 leaf network-role {
\r
1009 grouping vm-topology-data {
\r
1016 uses onap-model-information;
\r
1017 leaf nfc-naming-code {
\r
1018 description "used in vm naming(draft 29: changed from nfc-code)";
\r
1023 leaf vm-type-tag {
\r
1024 description "from tosca data on vfc";
\r
1032 container vm-names {
\r
1033 leaf-list vm-name {
\r
1046 container vnfc-networks {
\r
1047 uses vnfc-network-data;
\r
1051 container vm-networks {
\r
1053 key "network-role";
\r
1054 uses vm-network-data;
\r
1058 grouping vnfc-network-data {
\r
1059 list vnfc-network-data {
\r
1060 key "vnfc-network-role";
\r
1061 leaf vnfc-network-role {
\r
1072 uses connection-point;
\r
1073 container vnfc-ports {
\r
1075 key "vnfc-port-id";
\r
1076 leaf vnfc-port-id {
\r
1077 description "Port(s) with a given network-role are assigned vnfc-port-id from series - 01, 02, 03 ...Example: VM with two ports with network-role =X and another 2 ports with network-role=Y vnfc-port-ids:01 - 1st port with network-role=X02 - 2nd port with network-role=X01 - 1st port with network-role=Y02 - 2nd port with network-role=Y";
\r
1083 leaf common-sub-interface-role {
\r
1084 description "If sub-interfaces have common interface role (network role)";
\r
1089 container vnic-sub-interfaces {
\r
1090 uses sub-interface-network-data;
\r
1094 list vnfc-subnet {
\r
1095 key "vnfc-subnet-role";
\r
1096 leaf vnfc-subnet-role {
\r
1097 description "Default value if subnet role is not defined.";
\r
1103 list vnfc-ip-assignments {
\r
1104 key "vnfc-address-family";
\r
1105 leaf vnfc-address-family {
\r
1106 description "indicates if this is IpV4 or IpV6";
\r
1107 type enumeration {
\r
1112 leaf vnfc-subnet-dhcp {
\r
1113 description "Indicator to use DHCP for IP assignment. Unless dhcp=N, we wouldnt have any IPs here, since they would not be SDNC assigned ";
\r
1114 type enumeration {
\r
1119 leaf vnfc-subnet-ip-count {
\r
1120 description "The number of IP addresses to be assigned per vnfc for this subnet role";
\r
1123 list vnfc-subnet-ip {
\r
1124 key "vnfc-ip-address";
\r
1125 leaf vnfc-ip-address {
\r
1126 description "Either IpV4 IP or IpV6 IP address should be present";
\r
1127 type inet:ip-address;
\r
1129 leaf vnfc-client-key {
\r
1135 description "Capture what type of IP this is, if is virtual IP (AKA, floating IP) or Fixed IP. ";
\r
1136 type enumeration {
\r
1146 grouping vm-network-data {
\r
1147 leaf network-role {
\r
1148 description "network (identified by role) that this VM connects to. Should also be included in the vnf-networks for the containing VNF";
\r
1154 leaf network-role-tag {
\r
1159 container network-information-items {
\r
1160 list network-information-item {
\r
1163 description "Use ipv4 or ipv6";
\r
1169 description "Indicator to use DHCP on this network for this VM";
\r
1170 type enumeration {
\r
1176 description "The number of ip addresses to be assigned per vm for this network role";
\r
1179 container network-ips {
\r
1180 leaf-list network-ip {
\r
1181 description "List of assigned ip addresses of type ip-version on a network";
\r
1190 container mac-addresses {
\r
1191 leaf-list mac-address {
\r
1192 description "List of network assignments for this vm-type";
\r
1199 container floating-ips {
\r
1200 leaf-list floating-ip-v4 {
\r
1201 description "Floating ipv4 for VMs of a given type on this network";
\r
1202 type inet:ip-address;
\r
1205 leaf-list floating-ip-v6 {
\r
1206 description "Floating ipv6 for VMs of a given type on this network";
\r
1207 type inet:ipv6-address;
\r
1211 container interface-route-prefixes {
\r
1212 leaf-list interface-route-prefix {
\r
1213 description "ordered-by: user";
\r
1218 container sriov-parameters {
\r
1219 container heat-vlan-filters {
\r
1220 leaf-list heat-vlan-filter {
\r
1225 container application-tags {
\r
1226 container c-tags {
\r
1234 container s-tags {
\r
1247 leaf segmentation-id {
\r
1252 container related-networks {
\r
1253 uses related-network;
\r
1256 grouping vf-module-level-oper-status {
\r
1257 container vf-module-level-oper-status {
\r
1258 uses oper-status-data;
\r
1261 grouping allotted-resource-info {
\r
1262 leaf allotted-resource-id {
\r
1267 leaf allotted-resource-type {
\r
1268 description "Not an enum, but expected values are contrail-route and security-zone.";
\r
1273 leaf allotted-resource-pointer {
\r
1274 description "Pointer to the allotted-resources topology";
\r
1280 grouping forwarding-path-operation-information {
\r
1281 uses sdnc-request-header;
\r
1282 uses request-information;
\r
1283 uses service-information;
\r
1284 uses forwarding-path-request-input;
\r
1286 grouping forwarding-path-request-input {
\r
1287 container forwarding-path-request-input {
\r
1288 list forwarding-paths {
\r
1289 key "forwarding-path-name";
\r
1290 leaf forwarding-path-name {
\r
1291 description "Forwarding-path-name from tosca-model. ";
\r
1297 uses onap-model-information;
\r
1301 grouping forwarding-path-information {
\r
1302 leaf forwarding-path-name {
\r
1303 description "Fowarding-path name from TOSCA model, or name generated by SDNC";
\r
1308 leaf forwarding-path-type {
\r
1309 description "Based on MySQL Forwarding_Path tables path_type value from related TOSCA model";
\r
1310 type enumeration {
\r
1315 uses onap-model-information;
\r
1316 container service-paths {
\r
1317 list service-path {
\r
1318 key "service-path-instance-id";
\r
1319 uses service-path-information;
\r
1323 grouping service-path-information {
\r
1324 leaf service-path-instance-id {
\r
1325 description "Service path instance ID generated by SDNC. Identifies a service-path-instance within a forwarding-path definition";
\r
1330 leaf service-path-instance-name {
\r
1331 description "A unique name generated by SDNC ( forwarding-path-name + service-path-instance-id )";
\r
1337 description "Only one version of the service-path-instance data will be available in MD-SAL. version will be updated when the service-path-instance is reevaluated ";
\r
1343 key "service-instance-id";
\r
1344 leaf service-instance-id {
\r
1345 description "service-instance-id of each service-instance in the service-path-instance";
\r
1350 leaf service-path-sequence-id {
\r
1351 description "e.g. S1S2S3S5seq id=1 S1-S2seq id=2 S2S3seq id=3 S3S5Incremental integer value";
\r
1356 key "vnf-instance-id";
\r
1357 uses vnf-path-information;
\r
1362 grouping vnf-path-information {
\r
1363 leaf vnf-instance-id {
\r
1364 description "VNF instance ID in the path";
\r
1369 leaf vnf-path-sequence-id {
\r
1370 description "Sequence ID at the VNF instance levele.g. e.g. V1V2V3V5V6seq id=1 V1-V2seq id=2 V2V3seq id=3 V3V5seq id=4 V5V6incremental integer value.";
\r
1373 leaf left-network-name {
\r
1374 description "Every VNF instance in the path is connected to one or two VNFs.";
\r
1379 leaf left-network-role {
\r
1384 leaf right-network-name {
\r
1389 leaf right-network-role {
\r
1394 container vf-module-instance {
\r
1395 leaf vf-module-id {
\r
1400 leaf vf-module-name {
\r
1407 grouping forwarding-path-level-oper-status {
\r
1408 container forwarding-path-level-oper-status {
\r
1409 uses oper-status-data;
\r
1412 grouping configuration-info {
\r
1413 leaf configuration-id {
\r
1418 leaf configuration-type {
\r
1419 description "Not an enum, but expected values are port-mirror-configuration, , vlan-network-receptor";
\r
1424 leaf configuration-sub-type {
\r
1425 description "Not an enum, but expected values are vprobe and pprobe";
\r
1430 leaf configuration-topology-link {
\r
1431 description "Pointer to the configurations topology";
\r
1437 grouping vnfc-instance-group {
\r
1438 list vnfc-instance-group {
\r
1439 key "instance-group-role nfc-naming-code configuration-id";
\r
1440 leaf instance-group-role {
\r
1441 description "i.e.TSBC_VNFC_group";
\r
1447 leaf nfc-naming-code {
\r
1448 description "Set to nfc-naming-code from A&AI";
\r
1454 leaf configuration-id {
\r
1461 description " port-mirror-source or port-mirror-dest";
\r
1466 uses vnfc-objects;
\r
1469 grouping vnfc-objects {
\r
1470 container vnfc-objects {
\r
1471 list vnfc-object {
\r
1479 description "Vnfc name as key in A&AI";
\r
1494 leaf vserver-name {
\r
1506 key "vnic-port-name";
\r
1507 leaf vnic-port-name {
\r
1512 leaf vnic-port-id {
\r
1517 container capacity {
\r
1518 leaf vnic-capacity {
\r
1521 leaf used-capacity {
\r
1522 description "Updated for destination port when source port is mapped/unmapped.";
\r
1526 container vnic-ip-addresses {
\r
1527 uses ip-addresses;
\r
1539 description "Vnfc name as key in A&AI";
\r
1544 leaf vserver-name {
\r
1561 key "vnic-port-name";
\r
1562 leaf vnic-port-name {
\r
1567 leaf vnic-port-id {
\r
1572 uses sub-interfaces;
\r
1576 grouping sub-interfaces {
\r
1577 container sub-interfaces {
\r
1578 list sub-interface {
\r
1579 key "sub-interface-port-name";
\r
1580 leaf sub-interface-port-name {
\r
1585 leaf sub-interface-port-id {
\r
1590 container sub-interface-ip-addresses {
\r
1591 uses ip-addresses;
\r
1594 container sub-interface-network {
\r
1595 leaf network-name {
\r
1606 leaf sub-interface-status {
\r
1607 description "NULL, unassigned, assigned";
\r
1615 grouping vlan-tags {
\r
1616 container vlan-tags {
\r
1617 leaf vlan-interface {
\r
1618 description "A&AI Key";
\r
1623 leaf upper-tag-id {
\r
1624 description "aka outer tag";
\r
1627 leaf lower-tag-id {
\r
1628 description "aka inner tag";
\r
1636 grouping vlan-vnfc-instance-groups {
\r
1637 container vlan-vnfc-instance-groups {
\r
1638 list vlan-vnfc-instance-group {
\r
1639 key "instance-group-id";
\r
1640 leaf instance-group-id {
\r
1641 description "A&AI ID";
\r
1647 leaf instance-group-function {
\r
1671 grouping vnic-groups {
\r
1672 container vnic-groups {
\r
1674 key "vnic-interface-role";
\r
1675 leaf vnic-interface-role {
\r
1676 description "Same as network-role of network where vnic is connected";
\r
1682 leaf network-instance-group-function {
\r
1683 description "network-instance-Group-function for network collection where vnics with vnic-interface-role will connect";
\r
1688 leaf vlan-assignment-policy-name {
\r
1689 description "Policy name in ASDC model & policy definition in Policy Engine";
\r
1694 leaf vlan-tag-index-next {
\r
1695 description "Next tag to be assigned";
\r
1698 container vlan-common-ip-addresses {
\r
1699 uses ip-addresses;
\r
1701 container vlan-vnics {
\r
1703 key "vnic-port-id";
\r
1704 leaf vnic-port-id {
\r
1710 container vnic-sub-interfaces {
\r
1711 uses sub-interface-network-data;
\r
1718 grouping vnf-cloud-param {
\r
1719 leaf service-instance-id {
\r
1724 leaf service-instance-name {
\r
1743 key "vf-module-id";
\r
1744 leaf vf-module-id {
\r
1753 grouping vnf-network-collection {
\r
1754 list vnf-network-collection {
\r
1755 key "network-instance-group-function";
\r
1756 leaf network-instance-group-function {
\r
1757 description "Network Instance-Group function in A&AI";
\r
1763 leaf network-instance-group-id {
\r
1764 description "Network Instance-Group id in A&AI";
\r
1769 leaf network-collection-service-instance-id {
\r
1770 description "Service-instance-id of service that created the network collection";
\r
1775 leaf network-collection-customization-uuid {
\r
1776 description "network-collection-customization-uuid stored in Network IsntanceGroup.customization-uuid in A&AI";
\r
1781 container networks {
\r
1785 description "Index into network-topology-identifier structure";
\r
1791 leaf neutron-network-id {
\r
1792 description "Neutron-network-id assigned by PO/RO";
\r
1799 container vnf-floating-ip {
\r
1800 uses ip-addresses;
\r
1804 grouping vnf-sub-interface-group {
\r
1805 list vnf-sub-interface-group {
\r
1806 key "vnfc-instance-group-function network-instance-group-function parent-port-role";
\r
1807 leaf vnfc-instance-group-function {
\r
1813 leaf network-instance-group-function {
\r
1819 leaf parent-port-role {
\r
1826 container customer-bonding-requests {
\r
1827 list customer-bonding-request {
\r
1828 key "configuration-id";
\r
1829 leaf configuration-id {
\r
1830 description "e.g. vlan network receptor configuration id";
\r
1839 grouping sub-interface-network-data {
\r
1840 list sub-interface-network-data {
\r
1843 description "Subinterface network id (UUID in A&AI)";
\r
1849 leaf neutron-network-id {
\r
1850 description "Neutron network id assigned by PO/RP";
\r
1855 leaf network-name {
\r
1856 description "Subinterface network name";
\r
1859 leaf vlan-tag-id {
\r
1860 description "Vlan tag assigned to subinterface port";
\r
1863 leaf network-role {
\r
1864 description "e.g. untrusted ";
\r
1869 leaf network-role-tag {
\r
1870 description "Assuming HEAT template network role tag parameter - not used";
\r
1875 container network-information-items {
\r
1876 list network-information-item {
\r
1879 description "Use ipv4 or ipv6";
\r
1885 description "Indicator to use DHCP on this network for this VM - set to N for Vlan tagging";
\r
1886 type enumeration {
\r
1892 description "The number of ip addresses to be assigned per vm for this network role";
\r
1895 container network-ips {
\r
1896 leaf-list network-ip {
\r
1897 description "List of assigned ip addresses of type ip-version on a network.";
\r
1898 type inet:ip-address;
\r
1904 container floating-ips {
\r
1905 leaf-list floating-ip-v4 {
\r
1906 description "Floating ipv4 for VMs of a given type on this network";
\r
1907 type inet:ip-address;
\r
1910 leaf-list floating-ip-v6 {
\r
1911 description "Floating ipv6 for VMs of a given type on this network";
\r
1912 type inet:ipv6-address;
\r
1918 grouping vnf-get-resource-request-input-data {
\r
1927 key "vf-module-id";
\r
1928 leaf vf-module-id {
\r
1936 grouping license-information {
\r
1937 container license-information {
\r
1938 list entitlement-pool-list {
\r
1939 key "entitlement-pool-uuid action";
\r
1940 leaf entitlement-pool-uuid {
\r
1952 leaf entitlement-pool-invariant-uuid {
\r
1957 leaf entitlement-uuid {
\r
1958 description "assigned by ALTS";
\r
1964 list license-key-group-list {
\r
1965 key "license-key-group-uuid action";
\r
1966 leaf license-key-group-uuid {
\r
1978 leaf license-key-group-invariant-uuid {
\r
1983 leaf license-key {
\r
1984 description "assigned by ALTS";
\r
1989 leaf license-uuid {
\r
1990 description "assigned by ALTS";
\r
1998 grouping related-network {
\r
1999 list related-network {
\r
2002 description "Key to l3-network object";
\r
2007 leaf network-role {
\r
2015 grouping connection-point {
\r
2016 container connection-point {
\r
2017 leaf connection-point-id {
\r
2018 description "Key to CP object in A&AI";
\r
2024 description "port-index when multiple CPs connect to same network. Default zero (0)";
\r
2032 description "Key to vlan-tag uuid object in A&AI Generated by vlan mS";
\r
2037 leaf vlan-tag-id {
\r
2042 leaf vlan-tag-description {
\r
2048 description "Inner/Outer roles";
\r
2056 grouping aggregate-routes {
\r
2057 list aggregate-routes {
\r
2060 description "Unique id";
\r
2065 leaf start-address {
\r
2066 type inet:ip-address;
\r
2074 description "Use values 4 or 6.";
\r
2081 grouping pnf-information {
\r
2082 container pnf-information {
\r
2084 description "Key for A&AI query";
\r
2094 uses onap-model-information;
\r
2097 grouping contrail-route-operation-information {
\r
2098 uses sdnc-request-header;
\r
2099 uses request-information;
\r
2100 uses service-information;
\r
2101 uses allotted-resource-information;
\r
2102 uses contrail-route-request-input;
\r
2104 grouping contrail-route-request-input {
\r
2105 container contrail-route-request-input {
\r
2106 container source-network {
\r
2107 uses network-info;
\r
2109 container dest-network {
\r
2110 uses network-info;
\r
2112 container contrail-applied-service-info {
\r
2113 leaf service-instance-id {
\r
2114 description "The service-instance-id of the service in which the resource(s) providing the applied-service are. For vIPR, this is the service-instance-id of the vIPR-ATM service in which the vIPR-ATM VNF Contrail service is the applied service. MSO will populate with the input data.";
\r
2119 leaf contrail-fqdn {
\r
2120 description "For future use by MSO on input; MSO not expected to populate in 1707. If MSO can identify the contrail-fqdn of the Contrail applied service for this contrail-route, then it would be specified here on input. Otherwise, SDN-C will look it up by the vIPR-ATM VNF in the service-instance-id of the contrail-applied-service-info grouing.";
\r
2126 container contrail-route-input-parameters {
\r
2131 grouping network-info {
\r
2137 leaf network-role {
\r
2143 grouping contrail-route-topology {
\r
2144 container contrail-route-topology {
\r
2145 uses allotted-resource-identifiers;
\r
2146 uses onap-model-information;
\r
2147 uses contrail-route-assignments;
\r
2148 container contrail-route-parameters {
\r
2153 grouping contrail-route-assignments {
\r
2154 container contrail-route-assignments {
\r
2156 description "The Contrail fq-name of the network policy";
\r
2161 leaf contrail-id {
\r
2162 description "The ID assigned by Contrail to the network-policy (one for one with the fq-name)";
\r
2167 container source-network {
\r
2168 uses network-info;
\r
2170 container dest-network {
\r
2171 uses network-info;
\r
2173 container contrail-applied-service {
\r
2174 leaf service-instance-id {
\r
2175 description "The service-instance-id of the vnf from which the contrail applied service is coming";
\r
2181 description "The vnf representing the contrail applied service";
\r
2186 leaf contrail-fqdn {
\r
2187 description "This is the fq-name of the Contrail service instance through which the route is passing.";
\r
2194 description "Contrail-assigned vlan-tag to the vipr vm interface for this route.";
\r
2201 grouping security-zone-operation-information {
\r
2202 uses sdnc-request-header;
\r
2203 uses request-information;
\r
2204 uses service-information;
\r
2205 uses allotted-resource-information;
\r
2206 uses security-zone-request-input;
\r
2208 grouping security-zone-request-input {
\r
2209 container security-zone-request-input {
\r
2215 leaf trusted-network-role {
\r
2216 description "In the case of vIPR, this is the landing networks network-role; used in naming";
\r
2221 leaf untrusted-network-role {
\r
2222 description "In the case of vIPR, this is the tenant oam networks network-role; used in naming";
\r
2227 container security-zone-input-parameters {
\r
2232 grouping security-zone-topology {
\r
2233 container security-zone-topology {
\r
2234 uses allotted-resource-identifiers;
\r
2235 uses onap-model-information;
\r
2236 uses security-zone-assignments;
\r
2237 container security-zone-parameters {
\r
2242 grouping security-zone-assignments {
\r
2243 container security-zone-assignments {
\r
2244 leaf trusted-network-role {
\r
2245 description "In the case of vIPR, this is the landing networks network-role; used in naming";
\r
2250 leaf security-zone-name-trusted {
\r
2255 leaf untrusted-network-role {
\r
2256 description "In the case of vIPR, this is the tenant oam networks network-role; used in naming";
\r
2261 leaf security-zone-name-untrusted {
\r
2266 leaf security-zone-service-instance-id {
\r
2267 description "Will be the same as the parent-service-instance-id";
\r
2272 leaf security-zone-vnf-id {
\r
2273 description "Selected by SDNC from the security-zone-service-instance-id";
\r
2285 grouping port-mirror-topology-operation-information {
\r
2286 uses sdnc-request-header;
\r
2287 uses request-information;
\r
2288 uses service-information;
\r
2289 uses configuration-information;
\r
2290 uses port-mirror-configuration-request-input;
\r
2292 grouping port-mirror-configuration-request-input {
\r
2293 container port-mirror-configuration-request-input {
\r
2294 container source-port {
\r
2296 leaf source-port-id {
\r
2297 description "needed for srv-action=disable/enable";
\r
2303 container dest-port {
\r
2306 uses region-identifier;
\r
2307 container port-mirror-configuration-input-parameters {
\r
2312 grouping port-info {
\r
2313 leaf service-instance-id {
\r
2314 description "May not be need.";
\r
2319 uses pnf-information;
\r
2320 uses vnf-information;
\r
2322 grouping port-mirror-configuration-topology {
\r
2323 container port-mirror-configuration-topology {
\r
2324 uses configuration-identifiers;
\r
2325 uses onap-model-information;
\r
2326 uses port-mirror-configuration-assignments;
\r
2327 container port-mirror-configuration-parameters {
\r
2332 grouping port-mirror-configuration-assignments {
\r
2333 container port-mirror-configuration-assignments {
\r
2334 container contrail-vmi-params {
\r
2337 leaf vnics-group-id {
\r
2342 leaf owning-entity {
\r
2347 leaf tenant-context {
\r
2348 description "From tenant object in A&AI";
\r
2354 description "Tenant name from A&AI for source VNF";
\r
2360 description "tenant-id from A&AI for source VNF";
\r
2365 leaf dest-tenant {
\r
2366 description "Tenant name from A&AI for destination VNF";
\r
2371 leaf dest-tenant-id {
\r
2372 description "tenant-id from A&AI for destination VNF";
\r
2377 leaf cloud-region-id {
\r
2382 leaf cloud-owner {
\r
2387 leaf dest-network-fqdn {
\r
2392 leaf source-network-fqdn {
\r
2397 leaf source-capacity {
\r
2398 description "Source port pps (packets per second) rating from tosca model";
\r
2401 leaf source-vnf-id {
\r
2406 leaf dest-vnf-id {
\r
2407 description "For vProbe";
\r
2412 leaf dest-pnf-name {
\r
2413 description "For pProbe";
\r
2418 leaf dest-p-interface {
\r
2419 description "For pProbe; from policy manager";
\r
2424 leaf dest-pnf-port-policy-name {
\r
2425 description "For pProbe; from tosca model";
\r
2431 description "vprobe or pprobe; derived from configuration-information.configuration-sub-type";
\r
2436 leaf route-allotted-resource-id {
\r
2437 description "For vProbe";
\r
2442 container source-vnfc-instance-group-id {
\r
2443 leaf service-instance-id {
\r
2448 leaf nfc-naming-code {
\r
2449 description "Set to nfc-naming-code";
\r
2454 leaf instance-group-role {
\r
2459 leaf configuration-id {
\r
2465 container dest-vnfc-instance-group-id {
\r
2466 leaf service-instance-id {
\r
2471 leaf nfc-naming-code {
\r
2472 description "Set to nfc-naming-code";
\r
2477 leaf instance-group-role {
\r
2482 leaf configuration-id {
\r
2488 container source-to-dest-maps {
\r
2489 list source-to-dest-map {
\r
2490 key "source-port-id";
\r
2491 leaf source-port-id {
\r
2497 leaf source-port-name {
\r
2502 leaf source-vserver-id {
\r
2507 leaf dest-vserver-id {
\r
2512 leaf dest-port-id {
\r
2517 leaf dest-port-name {
\r
2527 container dest-ip-addresses {
\r
2528 uses ip-addresses;
\r
2534 grouping gc-topology-operation-information {
\r
2535 uses sdnc-request-header;
\r
2536 uses request-information;
\r
2537 uses service-information;
\r
2538 uses configuration-information;
\r
2539 uses gc-request-input;
\r
2541 grouping gc-request-input {
\r
2542 container gc-request-input {
\r
2548 leaf vf-module-id {
\r
2549 description "This is mandatory in case of rebuild";
\r
2554 container input-parameters {
\r
2558 description "Value will indicate what to rebuild";
\r
2563 list configuration-ids {
\r
2564 key "configuration-id";
\r
2565 leaf configuration-id {
\r
2573 grouping vnr-parameters {
\r
2574 container vnr-parameters {
\r
2580 leaf vf-module-id {
\r
2581 description "This is mandatory in case of rebuild";
\r
2586 leaf vnf-service-instance-id {
\r
2591 leaf network-collection-service-instance-id {
\r
2592 description "service instance id that created network-collection";
\r
2597 leaf network-instance-group-id {
\r
2607 leaf vnfc-instance-group-function {
\r
2612 leaf network-instance-group-function {
\r
2617 leaf parent-port-role {
\r
2622 leaf upper-tag-id {
\r
2625 leaf lower-tag-id {
\r
2630 grouping tunnelxconn-operation-information {
\r
2631 uses sdnc-request-header;
\r
2632 uses request-information;
\r
2633 uses service-information;
\r
2634 uses allotted-resource-information;
\r
2635 uses tunnelxconn-request-input;
\r
2637 grouping tunnelxconn-request-input {
\r
2639 container tunnelxconn-request-input {
\r
2640 leaf brg-wan-mac-address {
\r
2645 grouping tunnelxconn-topology {
\r
2646 container tunnelxconn-topology {
\r
2647 uses allotted-resource-identifiers;
\r
2648 uses onap-model-information;
\r
2649 uses tunnelxconn-assignments;
\r
2650 container tunnelxconn-parameters {
\r
2655 grouping tunnelxconn-assignments {
\r
2656 container tunnelxconn-assignments {
\r
2658 description "The Network Controller will assign a VNI value from the associated vGMUX VNI pool";
\r
2661 leaf vgmux-bearer-ip {
\r
2662 description "The Network Controller will look up the vgmux bearer ip from the vgmux vf module";
\r
2663 type inet:ip-address;
\r
2665 leaf vgmux-lan-ip {
\r
2666 description "The Network Controller will look up the vgmux lan ip from the vgmux vg module";
\r
2667 type inet:ip-address;
\r
2670 description "The Network Controller will assign the VG IP address from local inventory";
\r
2671 type inet:ip-address;
\r
2675 grouping brg-operation-information {
\r
2676 uses sdnc-request-header;
\r
2677 uses request-information;
\r
2678 uses service-information;
\r
2679 uses allotted-resource-information;
\r
2680 uses brg-request-input;
\r
2682 grouping brg-request-input {
\r
2683 container brg-request-input {
\r
2684 leaf vgmux-bearer-ip {
\r
2685 type inet:ip-address;
\r
2690 leaf brg-wan-mac-address {
\r
2695 grouping brg-topology {
\r
2696 container brg-topology {
\r
2697 uses allotted-resource-identifiers;
\r
2698 uses onap-model-information;
\r
2699 uses brg-assignments;
\r
2700 container brg-parameters {
\r
2705 grouping brg-assignments {
\r
2706 container brg-assignments {
\r
2707 leaf vbrg-wan-ip {
\r
2708 type inet:ip-address;
\r
2712 grouping connection-attachment-operation-information {
\r
2713 uses sdnc-request-header;
\r
2714 uses request-information;
\r
2715 uses service-information;
\r
2716 uses allotted-resource-information;
\r
2717 uses connection-attachment-request-input;
\r
2720 grouping connection-attachment-request-input {
\r
2721 container connection-attachment-request-input {
\r
2726 grouping connection-attachment-topology {
\r
2727 container connection-attachment-topology {
\r
2728 uses allotted-resource-identifiers;
\r
2729 uses onap-model-information;
\r
2730 uses connection-attachment-assignments;
\r
2731 container connection-attachment-parameters {
\r
2737 grouping connection-attachment-assignments {
\r
2738 container connection-attachment-assignments {
\r
2742 grouping vnf-vnr-rebuild-data {
\r
2743 container vnf-vnr-rebuild-data {
\r
2749 leaf vnf-service-instance-id {
\r
2755 key "configuration-id";
\r
2756 leaf configuration-id {
\r
2761 leaf network-instance-group-id {
\r
2771 leaf vnfc-instance-group-function {
\r
2776 leaf network-instance-group-function {
\r
2781 leaf parent-port-role {
\r
2786 leaf upper-tag-id {
\r
2789 leaf lower-tag-id {
\r
2795 grouping allotted-resource-information {
\r
2796 container allotted-resource-information {
\r
2797 leaf allotted-resource-id {
\r
2802 leaf allotted-resource-type {
\r
2803 description "Not an enum, but expected values are contrail-route and security-zone.";
\r
2808 leaf parent-service-instance-id {
\r
2809 description "Service-instance-id of the parent service to which this allotted resource belongs.";
\r
2814 uses onap-model-information;
\r
2817 grouping allotted-resource-identifiers {
\r
2818 container allotted-resource-identifiers {
\r
2819 leaf allotted-resource-id {
\r
2824 leaf allotted-resource-name {
\r
2825 description "For a contrail-route, the network policy name.";
\r
2830 leaf allotted-resource-type {
\r
2831 description "(Added in draft 32)Expected to be contrail-route or security-zone.";
\r
2836 leaf consuming-service-instance-id {
\r
2837 description "The service-instance-id of the consuming service of this allotted resource";
\r
2842 leaf parent-service-instance-id {
\r
2843 description "Service-instance-id of the parent service to which this allotted resource belongs.";
\r
2850 grouping allotted-resource-oper-status {
\r
2851 container allotted-resource-oper-status {
\r
2852 uses oper-status-data;
\r
2855 grouping allotted-resource-status {
\r
2856 container allotted-resource-status {
\r
2857 leaf response-code {
\r
2862 leaf response-message {
\r
2867 leaf final-indicator {
\r
2872 leaf request-status {
\r
2873 type enumeration {
\r
2874 enum "synccomplete";
\r
2875 enum "asynccomplete";
\r
2876 enum "notifycomplete";
\r
2880 description "value would one of possible request-actions; match the list in service-data oper-status";
\r
2891 description "this is the svc-action from the incoming request";
\r
2892 type enumeration {
\r
2898 enum "deactivate";
\r
2901 leaf response-timestamp {
\r
2908 grouping configuration-information {
\r
2909 container configuration-information {
\r
2910 leaf configuration-id {
\r
2915 leaf configuration-name {
\r
2920 leaf configuration-type {
\r
2921 description "Not an enum, but expected values are port-mirror-configuration, vlan-network-receptor";
\r
2926 leaf configuration-sub-type {
\r
2927 description "e.g. vprobe and pprobe when configuration-type=port-mirror-configuration";
\r
2932 uses onap-model-information;
\r
2935 grouping configuration-identifiers {
\r
2936 container configuration-identifiers {
\r
2937 leaf configuration-id {
\r
2942 leaf configuration-name {
\r
2947 leaf configuration-type {
\r
2948 description "Not an enum, but expected values are port-mirror-configuration.";
\r
2953 leaf configuration-sub-type {
\r
2954 description " vprobe and pprobe";
\r
2959 leaf parent-service-instance-id {
\r
2960 description "Service-instance-id of the parent service to which this resource belongs.";
\r
2967 grouping configuration-oper-status {
\r
2968 container configuration-oper-status {
\r
2969 uses oper-status-data;
\r
2972 grouping configuration-status {
\r
2973 container configuration-status {
\r
2974 leaf response-code {
\r
2979 leaf response-message {
\r
2984 leaf final-indicator {
\r
2989 leaf request-status {
\r
2990 type enumeration {
\r
2991 enum "synccomplete";
\r
2992 enum "asynccomplete";
\r
2993 enum "notifycomplete";
\r
2997 description "value would one of possible request-actions; match the list in service-data oper-status";
\r
3008 description "this is the svc-action from the incoming request";
\r
3009 type enumeration {
\r
3017 enum "deactivate";
\r
3020 leaf response-timestamp {
\r
3027 grouping topology-response-common {
\r
3028 leaf svc-request-id {
\r
3029 description "the request id from the request message for which this is the responseKeep as M";
\r
3034 leaf response-code {
\r
3035 description "a success code or an defined error codeKeep as M";
\r
3040 leaf response-message {
\r
3041 description "message included for error code";
\r
3046 leaf ack-final-indicator {
\r
3047 description "Expected to be Y or N.";
\r
3053 grouping sdnc-request-header {
\r
3054 container sdnc-request-header {
\r
3055 leaf svc-request-id {
\r
3056 description "Uniquely generated by calling system (e.g. MSO or SDN-GP)";
\r
3062 description "This is the rpcAction";
\r
3063 type enumeration {
\r
3068 enum "changeassign";
\r
3069 enum "changedelete";
\r
3071 enum "deactivate";
\r
3077 enum "reoptimize";
\r
3081 leaf svc-notification-url {
\r
3082 description "Contains URL for asynchronous response";
\r
3089 grouping request-information {
\r
3090 container request-information {
\r
3092 description "Request ID generated upstream of MSO";
\r
3097 leaf request-action {
\r
3098 description "still need to work Disconnect";
\r
3099 type enumeration {
\r
3100 enum "CreateNetworkInstance";
\r
3101 enum "ActivateNetworkInstance";
\r
3102 enum "DeActivateNetworkInstance";
\r
3103 enum "CreateServiceInstance";
\r
3104 enum "DeleteServiceInstance";
\r
3105 enum "DeleteNetworkInstance";
\r
3106 enum "CreateVnfInstance";
\r
3107 enum "ActivateVnfInstance";
\r
3108 enum "DeleteVnfInstance";
\r
3109 enum "CreatePnfInstance";
\r
3110 enum "ActivatePnfInstance";
\r
3111 enum "DeletePnfInstance";
\r
3112 enum "CreateVfModuleInstance";
\r
3113 enum "ActivateVfModuleInstance";
\r
3114 enum "DeleteVfModuleInstance";
\r
3115 enum "CreateContrailRouteInstance";
\r
3116 enum "DeleteContrailRouteInstance";
\r
3117 enum "CreateSecurityZoneInstance";
\r
3118 enum "DeleteSecurityZoneInstance";
\r
3119 enum "ActivateDCINetworkInstance";
\r
3120 enum "DeActivateDCINetworkInstance";
\r
3121 enum "CreateTunnelXConnInstance";
\r
3122 enum "DeleteTunnelXConnInstance";
\r
3123 enum "CreateBRGInstance";
\r
3124 enum "DeleteBRGInstance";
\r
3125 enum "CreateSOTNConnectivityInstance";
\r
3126 enum "ActivateSOTNConnectivityInstance";
\r
3127 enum "DeactivateSOTNConnectivityInstance";
\r
3128 enum "DeleteSOTNConnectivityInstance";
\r
3129 enum "CreateSOTNAttachmentInstance";
\r
3130 enum "ActivateSOTNAttachmentInstance";
\r
3131 enum "DeactivateSOTNAttachmentInstance";
\r
3132 enum "DeleteSOTNAttachmentInstance";
\r
3133 enum "CreateSiteInstance";
\r
3134 enum "ActivateSiteInstance";
\r
3135 enum "DeactivateSiteInstance";
\r
3136 enum "DeleteSiteInstance";
\r
3137 enum "CreatePortMirrorConfigurationInstance";
\r
3138 enum "DeletePortMirrorConfigurationInstance";
\r
3139 enum "ChangePortMirrorConfigurationInstance";
\r
3140 enum "CreateGenericConfigurationInstance";
\r
3141 enum "RebuildGenericConfigurationInstance";
\r
3142 enum "DeleteGenericConfigurationInstance";
\r
3143 enum "PreloadVfModuleRequest";
\r
3144 enum "DeletePreloadVfModuleRequest";
\r
3145 enum "PreloadNetworkRequest";
\r
3146 enum "DeletePreloadNetworkRequest";
\r
3147 enum "CreateForwardingPathInstance";
\r
3148 enum "DeleteForwardingPathInstance";
\r
3149 enum "UpdateForwardingPathInstance";
\r
3150 enum "CreateSDWANDeviceInstance";
\r
3151 enum "ActivateSDWANDeviceInstance";
\r
3152 enum "DeactivateSDWANDeviceInstance";
\r
3153 enum "DeleteSDWANDeviceInstance";
\r
3154 enum "CreateSDWANPortInstance";
\r
3155 enum "ActivateSDWANPortInstance";
\r
3156 enum "DeactivateSDWANPortInstance";
\r
3157 enum "DeleteSDWANPortInstance";
\r
3158 enum "ReoptimizeSOTNInstance";
\r
3159 enum "CreateSDWANLanPortInstance";
\r
3160 enum "ActivateSDWANLanPortInstance";
\r
3161 enum "DeactivateSDWANLanPortInstance";
\r
3162 enum "DeleteSDWANLanPortInstance";
\r
3163 enum "CreateSDWANVpnInstance";
\r
3164 enum "ActivateSDWANVpnInstance";
\r
3165 enum "DeactivateSDWANVpnInstance";
\r
3166 enum "DeleteSDWANVpnInstance";
\r
3167 enum "CreateSDWANSiteInstance";
\r
3168 enum "ActivateSDWANSiteInstance";
\r
3169 enum "DeactivateSDWANSiteInstance";
\r
3170 enum "DeleteSDWANSiteInstance";
\r
3171 enum "SdwanBandwidthChange";
\r
3172 enum "CreateAccessConnectivityInstance";
\r
3173 enum "DeleteAccessConnectivityInstance";
\r
3174 enum "CreateInternetProfileInstance";
\r
3175 enum "ChangeInternetProfileInstance";
\r
3176 enum "DeleteInternetProfileInstance";
\r
3177 enum "CreateSOTNUnderlayInstance";
\r
3178 enum "ActivateSOTNUnderlayInstance";
\r
3179 enum "DeactivateSOTNUnderlayInstance";
\r
3180 enum "DeleteSOTNUnderlayInstance";
\r
3181 enum "CreateSOTNUniInstance";
\r
3182 enum "ActivateSOTNUniInstance";
\r
3183 enum "DeactivateSOTNUniInstance";
\r
3184 enum "DeleteSOTNUniInstance";
\r
3185 enum "CreateSOTNL2VpnInstance";
\r
3186 enum "ActivateSOTNL2VpnInstance";
\r
3187 enum "DeactivateSOTNL2VpnInstance";
\r
3188 enum "DeleteSOTNL2VpnInstance";
\r
3189 enum "AllocateTransportSliceInstance";
\r
3190 enum "ActivateTransportSliceInstance";
\r
3191 enum "DeactivateTransportSliceInstance";
\r
3192 enum "DeleteTransportSliceInstance";
\r
3193 enum "ModifyTransportSliceInstance";
\r
3194 enum "CreateCloudLeasedLineInstance";
\r
3195 enum "ModifyCloudLeasedLineInstance";
\r
3196 enum "DeleteCloudLeasedLineInstance";
\r
3204 leaf notification-url {
\r
3209 leaf order-number {
\r
3214 leaf order-version {
\r
3221 grouping service-information {
\r
3222 container service-information {
\r
3224 description "This maps to the product-family-id in A&AI";
\r
3229 leaf subscription-service-type {
\r
3230 description "used to reference a&ai subscription-service-type. For example, we show as vIPR-ATM in example.";
\r
3235 uses onap-model-information;
\r
3236 leaf service-instance-id {
\r
3241 leaf global-customer-id {
\r
3242 description "need for put of data to AnAI (MSO provides)";
\r
3247 leaf subscriber-name {
\r
3248 description "Would not be expected for vIPR-ATM or mobility services.";
\r
3255 grouping onap-model-information {
\r
3256 container onap-model-information {
\r
3257 leaf model-invariant-uuid {
\r
3258 description "identifies the invariant uuid for this service or resource";
\r
3263 leaf model-customization-uuid {
\r
3264 description "customized resource for use within a given service.Would not be present at the service level but would be present for the resource level";
\r
3270 description "identifies the uuid for this service or resource, which is version specific";
\r
3275 leaf model-version {
\r
3287 grouping region-identifier {
\r
3293 leaf aic-cloud-region {
\r
3294 description "The AIC cloud region which maps to contrail versions";
\r
3297 leaf cloud-owner {
\r
3303 description "Not expected to be used";
\r
3319 length "0..20000";
\r
3322 container resource-resolution-data {
\r
3323 list resource-key {
\r
3332 length "0..20000";
\r
3337 description "SUCCESS, FAILED, or PENDING - RA returned data as capability";
\r
3342 leaf capability-name {
\r
3343 description "Resource assignment resolution Capability name";
\r
3354 grouping ip-addresses {
\r
3355 container ip-addresses {
\r
3356 leaf ipv4-address {
\r
3357 type inet:ip-address;
\r
3359 leaf ipv6-address {
\r
3360 type inet:ip-address;
\r
3362 leaf vipv4-address {
\r
3363 description "Virtual v4";
\r
3364 type inet:ip-address;
\r
3366 leaf vipv6-address {
\r
3367 description "Virtual v6";
\r
3368 type inet:ip-address;
\r
3372 grouping instance-reference {
\r
3373 leaf instance-id {
\r
3378 leaf object-path {
\r
3379 description "restconf retrieval path to this particular objectE.g. restconf/config/GENERIC-RESOURCE-API:services/service/$service-instance-id/service-data/service-topology/";
\r
3385 grouping oper-status-data {
\r
3386 leaf order-status {
\r
3387 description "TBD - do we need Request failed statuses? RequestFailed | InProgressTimeout";
\r
3388 type enumeration {
\r
3390 enum "PendingAssignment";
\r
3391 enum "PendingCreate";
\r
3392 enum "PendingUpdate";
\r
3393 enum "PendingDelete";
\r
3398 leaf last-rpc-action {
\r
3399 type enumeration {
\r
3404 enum "deactivate";
\r
3406 enum "changeassign";
\r
3407 enum "reoptimize";
\r
3410 leaf last-action {
\r
3411 description "should be list of possible request-actions";
\r
3412 type enumeration {
\r
3413 enum "CreateNetworkInstance";
\r
3414 enum "ActivateNetworkInstance";
\r
3415 enum "DeActivateNetworkInstance";
\r
3416 enum "DeleteNetworkInstance";
\r
3417 enum "CreateServiceInstance";
\r
3418 enum "DeleteServiceInstance";
\r
3419 enum "CreateVnfInstance";
\r
3420 enum "ActivateVnfInstance";
\r
3421 enum "DeleteVnfInstance";
\r
3422 enum "CreatePnfInstance";
\r
3423 enum "ActivatePnfInstance";
\r
3424 enum "DeletePnfInstance";
\r
3425 enum "CreateVfModuleInstance";
\r
3426 enum "ActivateVfModuleInstance";
\r
3427 enum "DeleteVfModuleInstance";
\r
3428 enum "CreateContrailRouteInstance";
\r
3429 enum "DeleteContrailRouteInstance";
\r
3430 enum "CreateSecurityZoneInstance";
\r
3431 enum "DeleteSecurityZoneInstance";
\r
3432 enum "ActivateDCINetworkInstance";
\r
3433 enum "DeActivateDCINetworkInstance";
\r
3434 enum "CreateTunnelXConnInstance";
\r
3435 enum "DeleteTunnelXConnInstance";
\r
3436 enum "CreateBRGInstance";
\r
3437 enum "DeleteBRGInstance";
\r
3438 enum "CreateSOTNConnectivityInstance";
\r
3439 enum "ActivateSOTNConnectivityInstance";
\r
3440 enum "DeactivateSOTNConnectivityInstance";
\r
3441 enum "DeleteSOTNConnectivityInstance";
\r
3442 enum "CreateSOTNAttachmentInstance";
\r
3443 enum "ActivateSOTNAttachmentInstance";
\r
3444 enum "DeactivateSOTNAttachmentInstance";
\r
3445 enum "DeleteSOTNAttachmentInstance";
\r
3446 enum "CreateSiteInstance";
\r
3447 enum "ActivateSiteInstance";
\r
3448 enum "DeactivateSiteInstance";
\r
3449 enum "DeleteSiteInstance";
\r
3450 enum "CreatePortMirrorConfigurationInstance";
\r
3451 enum "DeletePortMirrorConfigurationInstance";
\r
3452 enum "ChangePortMirrorConfigurationInstance";
\r
3453 enum "CreateGenericConfigurationInstance";
\r
3454 enum "DeleteGenericConfigurationInstance";
\r
3455 enum "PreloadVfModuleRequest";
\r
3456 enum "DeletePreloadVfModuleRequest";
\r
3457 enum "PreloadNetworkRequest";
\r
3458 enum "DeletePreloadNetworkRequest";
\r
3459 enum "CreateForwardingPathInstance";
\r
3460 enum "DeleteForwardingPathInstance";
\r
3461 enum "UpdateForwardingPathInstance";
\r
3462 enum "CreateSDWANDeviceInstance";
\r
3463 enum "ActivateSDWANDeviceInstance";
\r
3464 enum "DeactivateSDWANDeviceInstance";
\r
3465 enum "DeleteSDWANDeviceInstance";
\r
3466 enum "CreateSDWANPortInstance";
\r
3467 enum "ActivateSDWANPortInstance";
\r
3468 enum "DeactivateSDWANPortInstance";
\r
3469 enum "DeleteSDWANPortInstance";
\r
3470 enum "ReoptimizeSOTNInstance";
\r
3471 enum "CreateSDWANLanPortInstance";
\r
3472 enum "ActivateSDWANLanPortInstance";
\r
3473 enum "DeactivateSDWANLanPortInstance";
\r
3474 enum "DeleteSDWANLanPortInstance";
\r
3475 enum "CreateSDWANVpnInstance";
\r
3476 enum "ActivateSDWANVpnInstance";
\r
3477 enum "DeactivateSDWANVpnInstance";
\r
3478 enum "DeleteSDWANVpnInstance";
\r
3479 enum "CreateSDWANSiteInstance";
\r
3480 enum "ActivateSDWANSiteInstance";
\r
3481 enum "DeactivateSDWANSiteInstance";
\r
3482 enum "DeleteSDWANSiteInstance";
\r
3483 enum "SdwanBandwidthChange";
\r
3484 enum "CreateAccessConnectivityInstance";
\r
3485 enum "DeleteAccessConnectivityInstance";
\r
3486 enum "CreateInternetProfileInstance";
\r
3487 enum "ChangeInternetProfileInstance";
\r
3488 enum "DeleteInternetProfileInstance";
\r
3489 enum "CreateSOTNUnderlayInstance";
\r
3490 enum "ActivateSOTNUnderlayInstance";
\r
3491 enum "DeactivateSOTNUnderlayInstance";
\r
3492 enum "DeleteSOTNUnderlayInstance";
\r
3493 enum "CreateSOTNUniInstance";
\r
3494 enum "ActivateSOTNUniInstance";
\r
3495 enum "DeactivateSOTNUniInstance";
\r
3496 enum "DeleteSOTNUniInstance";
\r
3497 enum "CreateSOTNL2VpnInstance";
\r
3498 enum "ActivateSOTNL2VpnInstance";
\r
3499 enum "DeactivateSOTNL2VpnInstance";
\r
3500 enum "DeleteSOTNL2VpnInstance";
\r
3501 enum "AllocateTransportSliceInstance";
\r
3502 enum "ActivateTransportSliceInstance";
\r
3503 enum "DeactivateTransportSliceInstance";
\r
3504 enum "DeleteTransportSliceInstance";
\r
3505 enum "ModifyTransportSliceInstance";
\r
3506 enum "CreateCloudLeasedLineInstance";
\r
3507 enum "ModifyCloudLeasedLineInstance";
\r
3508 enum "DeleteCloudLeasedLineInstance";
\r
3511 leaf last-svc-request-id {
\r
3512 description "Not currently populated in service data.";
\r
3517 leaf last-order-status {
\r
3518 type enumeration {
\r
3520 enum "PendingAssignment";
\r
3521 enum "PendingCreate";
\r
3522 enum "PendingUpdate";
\r
3523 enum "PendingDelete";
\r
3528 leaf create-timestamp {
\r
3529 description "Not currently populated in service data.";
\r
3534 leaf modify-timestamp {
\r
3540 grouping service-response-information {
\r
3541 container service-response-information {
\r
3542 uses instance-reference;
\r
3545 grouping network-response-information {
\r
3546 container network-response-information {
\r
3547 uses instance-reference;
\r
3550 grouping vnf-response-information {
\r
3551 container vnf-response-information {
\r
3552 uses instance-reference;
\r
3555 grouping vf-module-response-information {
\r
3556 container vf-module-response-information {
\r
3557 uses instance-reference;
\r
3560 grouping pnf-response-information {
\r
3561 container pnf-response-information {
\r
3562 uses instance-reference;
\r
3565 grouping contrail-route-response-information {
\r
3566 container contrail-route-response-information {
\r
3567 uses instance-reference;
\r
3570 grouping security-zone-response-information {
\r
3571 container security-zone-response-information {
\r
3572 uses instance-reference;
\r
3575 grouping getpathsegment-response-information {
\r
3576 container getpathsegment-response-information {
\r
3577 uses instance-reference;
\r
3580 grouping port-mirror-response-information {
\r
3581 container port-mirror-response-information {
\r
3582 uses instance-reference;
\r
3585 grouping gc-response-information {
\r
3586 container gc-response-information {
\r
3587 uses instance-reference;
\r
3590 grouping tunnelxconn-response-information {
\r
3591 container tunnelxconn-response-information {
\r
3592 uses instance-reference;
\r
3595 grouping brg-response-information {
\r
3596 container brg-response-information {
\r
3597 uses instance-reference;
\r
3600 grouping connection-attachment-response-information {
\r
3601 container connection-attachment-response-information {
\r
3602 uses instance-reference;
\r
3605 grouping preload-model-information {
\r
3606 list preload-list {
\r
3607 key "preload-id preload-type";
\r
3609 description "vf-module-name or network name";
\r
3615 leaf preload-type {
\r
3616 description "network or vf-module";
\r
3622 uses preload-data;
\r
3625 grouping preload-data {
\r
3626 container preload-data {
\r
3627 uses preload-vf-module-topology-information;
\r
3628 uses preload-network-topology-information;
\r
3629 uses preload-oper-status;
\r
3632 grouping preload-vf-module-topology-information {
\r
3633 container preload-vf-module-topology-information {
\r
3634 uses vnf-topology-identifier-structure;
\r
3635 uses vnf-resource-assignments;
\r
3636 uses vf-module-topology;
\r
3639 grouping preload-network-topology-information {
\r
3640 container preload-network-topology-information {
\r
3641 uses network-topology-identifier-structure;
\r
3643 uses vpn-bindings;
\r
3644 uses network-policy;
\r
3645 uses route-table-reference;
\r
3647 uses provider-network-information;
\r
3650 grouping subnets {
\r
3652 key "start-address";
\r
3653 leaf start-address {
\r
3654 type inet:ip-address;
\r
3656 leaf gateway-address {
\r
3657 type inet:ip-address;
\r
3669 leaf dhcp-enabled {
\r
3670 type enumeration {
\r
3675 leaf dhcp-start-address {
\r
3680 leaf dhcp-end-address {
\r
3685 leaf addr-from-start {
\r
3686 description "Default is N";
\r
3687 type enumeration {
\r
3692 leaf subnet-name {
\r
3697 leaf subnet-role {
\r
3702 leaf subnet-sequence {
\r
3707 grouping vpn-bindings {
\r
3708 list vpn-bindings {
\r
3709 key "vpn-binding-id";
\r
3710 leaf vpn-binding-id {
\r
3720 leaf global-route-target {
\r
3725 leaf route-target-role {
\r
3731 description "AIC Zone the route target associated with";
\r
3738 grouping network-policy {
\r
3739 list network-policy {
\r
3740 key "network-policy-fqdn";
\r
3741 leaf network-policy-fqdn {
\r
3746 leaf network-policy-id {
\r
3753 grouping route-table-reference {
\r
3754 list route-table-reference {
\r
3755 key "route-table-reference-fqdn";
\r
3756 leaf route-table-reference-fqdn {
\r
3762 leaf route-table-reference-id {
\r
3769 grouping provider-network-information {
\r
3770 leaf physical-network-name {
\r
3775 leaf is-provider-network {
\r
3778 leaf is-shared-network {
\r
3781 leaf is-external-network {
\r
3785 grouping host-routes {
\r
3786 list host-routes {
\r
3787 key "route-prefix";
\r
3788 leaf route-prefix {
\r
3794 description "Could be ip-address or hostname or service-instance";
\r
3801 grouping preload-oper-status {
\r
3802 container preload-oper-status {
\r
3803 leaf order-status {
\r
3804 type enumeration {
\r
3806 enum "PendingAssignment";
\r
3807 enum "PendingCreate";
\r
3808 enum "PendingUpdate";
\r
3809 enum "PendingDelete";
\r
3813 leaf last-action {
\r
3814 type enumeration {
\r
3815 enum "PreloadVfModuleRequest";
\r
3816 enum "DeletePreloadVfModuleRequest";
\r
3817 enum "PreloadNetworkRequest";
\r
3818 enum "DeletePreloadNetworkRequest";
\r
3821 leaf last-svc-request-id {
\r
3826 leaf last-order-status {
\r
3827 type enumeration {
\r
3829 enum "PendingAssignment";
\r
3830 enum "PendingCreate";
\r
3831 enum "PendingUpdate";
\r
3832 enum "PendingDelete";
\r
3836 leaf create-timestamp {
\r
3841 leaf modify-timestamp {
\r
3846 leaf maintenance-indicator {
\r
3847 type enumeration {
\r
3854 grouping preload-topology-response-body {
\r
3855 leaf svc-request-id {
\r
3860 leaf response-code {
\r
3865 leaf response-message {
\r
3870 leaf ack-final-indicator {
\r
3876 rpc generic-configuration-notification {
\r
3878 uses sdnc-request-header;
\r
3879 uses request-information;
\r
3880 uses service-information;
\r
3881 uses configuration-information;
\r
3882 uses topology-response-common;
\r
3883 leaf configuration-topology-link {
\r
3884 description "Returns URL to generic-configuration-topology ";
\r
3889 uses vnr-parameters;
\r
3890 uses vnf-vnr-rebuild-data;
\r
3893 container services {
\r
3894 uses service-model-infrastructure;
\r
3896 container contrail-route-allotted-resources {
\r
3897 list contrail-route-allotted-resource {
\r
3898 key "allotted-resource-id";
\r
3899 leaf allotted-resource-id {
\r
3905 container allotted-resource-data {
\r
3906 container allotted-resource-operation-information {
\r
3907 uses contrail-route-operation-information;
\r
3909 uses contrail-route-topology;
\r
3910 uses allotted-resource-oper-status;
\r
3912 uses allotted-resource-status;
\r
3915 container security-zone-allotted-resources {
\r
3916 list security-zone-allotted-resource {
\r
3917 key "allotted-resource-id";
\r
3918 leaf allotted-resource-id {
\r
3924 container allotted-resource-data {
\r
3925 container allotted-resource-operation-information {
\r
3926 uses security-zone-operation-information;
\r
3928 uses security-zone-topology;
\r
3929 container security-zone-parameters {
\r
3932 uses allotted-resource-oper-status;
\r
3934 uses allotted-resource-status;
\r
3937 container tunnelxconn-allotted-resources {
\r
3938 list tunnelxconn-allotted-resource {
\r
3939 key "allotted-resource-id";
\r
3940 leaf allotted-resource-id {
\r
3944 container allotted-resource-data {
\r
3945 container allotted-resource-operation-information {
\r
3946 uses tunnelxconn-operation-information;
\r
3948 uses tunnelxconn-topology;
\r
3949 container tunnelxconn-parameters {
\r
3952 uses allotted-resource-oper-status;
\r
3954 uses allotted-resource-status;
\r
3957 container brg-allotted-resources {
\r
3958 list brg-allotted-resource {
\r
3959 key "allotted-resource-id";
\r
3960 leaf allotted-resource-id {
\r
3964 container allotted-resource-data {
\r
3965 container allotted-resource-operation-information {
\r
3966 uses brg-operation-information;
\r
3968 uses brg-topology;
\r
3969 container brg-parameters {
\r
3972 uses allotted-resource-oper-status;
\r
3974 uses allotted-resource-status;
\r
3977 container connection-attachment-allotted-resources {
\r
3978 list connection-attachment-allotted-resource {
\r
3979 key "allotted-resource-id";
\r
3980 leaf allotted-resource-id {
\r
3984 container allotted-resource-data {
\r
3985 container allotted-resource-operation-information {
\r
3986 uses connection-attachment-operation-information;
\r
3988 uses connection-attachment-topology;
\r
3989 container connection-attachment-parameters {
\r
3992 uses allotted-resource-oper-status;
\r
3994 uses allotted-resource-status;
\r
3997 container port-mirror-configurations {
\r
3998 list port-mirror-configuration {
\r
3999 key "configuration-id";
\r
4000 leaf configuration-id {
\r
4006 container configuration-data {
\r
4007 container configuration-operation-information {
\r
4008 uses port-mirror-topology-operation-information;
\r
4010 uses port-mirror-configuration-topology;
\r
4011 uses configuration-oper-status;
\r
4013 uses configuration-status;
\r
4016 container generic-configurations {
\r
4017 list gc-configuration {
\r
4018 key "configuration-id";
\r
4019 leaf configuration-id {
\r
4025 container configuration-data {
\r
4026 container configuration-operation-information {
\r
4027 uses gc-topology-operation-information;
\r
4029 uses configuration-oper-status;
\r
4031 uses configuration-status;
\r
4034 rpc service-topology-operation {
\r
4036 uses service-operation-information;
\r
4039 uses topology-response-common;
\r
4040 uses service-response-information;
\r
4043 rpc network-topology-operation {
\r
4045 uses network-operation-information;
\r
4048 uses topology-response-common;
\r
4049 uses network-response-information;
\r
4050 uses service-response-information;
\r
4053 rpc vnf-topology-operation {
\r
4055 uses vnf-operation-information;
\r
4058 uses topology-response-common;
\r
4059 uses vnf-response-information;
\r
4060 uses service-response-information;
\r
4063 rpc vf-module-topology-operation {
\r
4065 uses vf-module-operation-information;
\r
4068 uses topology-response-common;
\r
4069 uses vf-module-response-information;
\r
4070 uses vnf-response-information;
\r
4071 uses service-response-information;
\r
4074 rpc pnf-topology-operation {
\r
4076 uses pnf-operation-information;
\r
4079 uses topology-response-common;
\r
4080 uses pnf-response-information;
\r
4081 uses service-response-information;
\r
4084 rpc contrail-route-topology-operation {
\r
4086 uses contrail-route-operation-information;
\r
4089 uses topology-response-common;
\r
4090 uses contrail-route-response-information;
\r
4091 uses service-response-information;
\r
4094 rpc security-zone-topology-operation {
\r
4096 uses security-zone-operation-information;
\r
4099 uses topology-response-common;
\r
4100 uses security-zone-response-information;
\r
4101 uses service-response-information;
\r
4104 rpc tunnelxconn-topology-operation {
\r
4106 uses tunnelxconn-operation-information;
\r
4109 uses topology-response-common;
\r
4110 uses tunnelxconn-response-information;
\r
4111 uses service-response-information;
\r
4114 rpc brg-topology-operation {
\r
4116 uses brg-operation-information;
\r
4119 uses topology-response-common;
\r
4120 uses brg-response-information;
\r
4121 uses service-response-information;
\r
4124 rpc policy-update-notify-operation {
\r
4126 leaf policy-name {
\r
4133 description "Map JSON versionNo to version-id";
\r
4139 leaf update-type {
\r
4159 rpc getpathsegment-topology-operation {
\r
4161 uses forwarding-path-operation-information;
\r
4164 uses topology-response-common;
\r
4165 uses getpathsegment-response-information;
\r
4166 uses service-response-information;
\r
4169 rpc port-mirror-topology-operation {
\r
4171 uses port-mirror-topology-operation-information;
\r
4174 uses topology-response-common;
\r
4175 uses port-mirror-response-information;
\r
4176 uses service-response-information;
\r
4179 rpc generic-configuration-topology-operation {
\r
4181 uses gc-topology-operation-information;
\r
4184 uses topology-response-common;
\r
4185 uses gc-response-information;
\r
4186 uses service-response-information;
\r
4189 rpc vnf-get-resource-request {
\r
4191 uses sdnc-request-header;
\r
4192 uses request-information;
\r
4193 uses service-information;
\r
4194 uses vnf-get-resource-request-input-data;
\r
4197 container vnf-get-resource-response-information {
\r
4198 uses vnf-cloud-param;
\r
4202 container preload-information {
\r
4203 uses preload-model-information;
\r
4205 rpc preload-vf-module-topology-operation {
\r
4207 uses sdnc-request-header;
\r
4208 uses request-information;
\r
4209 uses preload-vf-module-topology-information;
\r
4212 uses preload-topology-response-body;
\r
4215 rpc preload-network-topology-operation {
\r
4217 uses sdnc-request-header;
\r
4218 uses request-information;
\r
4219 uses preload-network-topology-information;
\r
4222 uses preload-topology-response-body;
\r
4226 rpc connection-attachment-topology-operation {
\r
4228 uses connection-attachment-operation-information;
\r
4231 uses topology-response-common;
\r
4232 uses connection-attachment-response-information;
\r
4233 uses service-response-information;
\r
4237 } ////closes the module
\r