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 leaf controller-ipv4-address {
\r
37 container networks {
\r
46 container network-data {
\r
47 uses network-operation-information;
\r
48 uses network-topology;
\r
49 container network-provided-allotted-resources {
\r
50 leaf-list network-provided-ar-id {
\r
51 description "List of allotted resources using capacity from this network";
\r
58 uses network-level-oper-status;
\r
69 container pnf-data {
\r
70 uses pnf-operation-information;
\r
72 uses pnf-level-oper-status;
\r
85 container vnf-data {
\r
86 uses vnf-operation-information;
\r
88 container vnf-network-collections {
\r
89 uses vnf-network-collection;
\r
91 container vnf-sub-interface-groups {
\r
92 uses vnf-sub-interface-group;
\r
94 container vnf-provided-allotted-resources {
\r
95 leaf-list vnf-provided-ar-id {
\r
96 description "List of allotted resources using capacity from this vnf";
\r
103 uses vnf-level-oper-status;
\r
104 container vf-modules {
\r
106 key "vf-module-id";
\r
107 leaf vf-module-id {
\r
113 container vf-module-data {
\r
114 uses vf-module-operation-information;
\r
115 uses vf-module-topology;
\r
116 uses vf-module-level-oper-status;
\r
123 container consumed-allotted-resources {
\r
124 list consumed-allotted-resource {
\r
125 key "allotted-resource-id";
\r
126 uses allotted-resource-info;
\r
129 container provided-allotted-resources {
\r
130 list provided-allotted-resource {
\r
131 key "allotted-resource-id";
\r
132 uses allotted-resource-info;
\r
135 container provided-configurations {
\r
136 list provided-configuration {
\r
137 key "configuration-id";
\r
138 uses configuration-info;
\r
141 container vnfc-instance-groups {
\r
142 uses vnfc-instance-group;
\r
144 container network-instance-groups {
\r
145 uses network-instance-group;
\r
147 container forwarding-paths {
\r
148 list forwarding-path {
\r
149 key "forwarding-path-id";
\r
150 leaf forwarding-path-id {
\r
151 description "Generated by SDNC";
\r
157 uses forwarding-path-information;
\r
162 grouping service-status {
\r
163 container service-status {
\r
164 leaf response-code {
\r
169 leaf response-message {
\r
174 leaf final-indicator {
\r
179 leaf request-status {
\r
181 enum "synccomplete";
\r
182 enum "asynccomplete";
\r
183 enum "notifycomplete";
\r
187 description "value would one of possible request-actions; match the list in service-data oper-status";
\r
198 description "this is the svc-action from the incoming request";
\r
209 leaf response-timestamp {
\r
216 grouping service-operation-information {
\r
217 uses sdnc-request-header;
\r
218 uses request-information;
\r
219 uses service-information;
\r
220 uses service-request-input;
\r
222 grouping service-request-input {
\r
223 container service-request-input {
\r
224 leaf service-instance-name {
\r
229 container service-input-parameters {
\r
234 grouping service-topology {
\r
235 container service-topology {
\r
236 uses service-topology-identifier;
\r
237 uses onap-model-information;
\r
238 uses service-assignments;
\r
239 uses service-parameters;
\r
242 grouping service-topology-identifier {
\r
243 container service-topology-identifier {
\r
244 leaf service-instance-id {
\r
245 description "repeated";
\r
250 leaf service-type {
\r
251 description "tag labeled subscription-service-type in the service-information input";
\r
257 description "from MSO input on STO assign";
\r
262 leaf service-instance-name {
\r
263 description "optionally comes from service-request-input container or is assigned by sdn-c";
\r
268 leaf global-customer-id {
\r
275 grouping service-assignments {
\r
276 container service-assignments {
\r
279 grouping service-parameters {
\r
280 container service-parameters {
\r
281 list service-parameter {
\r
282 key "service-parameter-name";
\r
283 leaf service-parameter-name {
\r
288 leaf service-parameter-value {
\r
290 length "0..20000" ;
\r
296 grouping service-level-oper-status {
\r
297 container service-level-oper-status {
\r
298 uses oper-status-data;
\r
301 grouping network-operation-information {
\r
302 uses sdnc-request-header;
\r
303 uses request-information;
\r
304 uses service-information;
\r
305 uses network-information;
\r
306 uses network-request-input;
\r
308 grouping network-information {
\r
309 container network-information {
\r
315 leaf network-type {
\r
320 leaf network-technology {
\r
325 leaf from-preload {
\r
326 description "Indicates if source is preload data";
\r
329 uses onap-model-information;
\r
332 grouping network-request-input {
\r
333 container network-request-input {
\r
334 leaf network-name {
\r
339 uses region-identifier;
\r
340 container network-input-parameters {
\r
343 leaf network-instance-group-id {
\r
344 description "When network has instance-group role in service model";
\r
351 grouping network-topology {
\r
352 container network-topology {
\r
353 uses network-topology-identifier-structure;
\r
354 uses region-identifier;
\r
355 uses onap-model-information;
\r
356 uses network-assignments;
\r
357 uses network-parameters;
\r
360 grouping network-topology-identifier-structure {
\r
361 container network-topology-identifier-structure {
\r
367 leaf network-name {
\r
372 leaf network-role {
\r
377 leaf network-type {
\r
382 leaf network-instance-group-id {
\r
383 description "When network is part of network instance-Group-data & instance Group in A&AI";
\r
388 leaf network-technology {
\r
393 leaf eipam-v4-address-plan {
\r
398 leaf eipam-v6-address-plan {
\r
406 leaf segmentation-id {
\r
411 container related-networks {
\r
412 uses related-network;
\r
416 grouping network-assignments {
\r
417 container network-assignments {
\r
420 grouping network-parameters {
\r
421 container network-parameters {
\r
422 list network-parameter {
\r
423 key "network-parameter-name";
\r
424 leaf network-parameter-name {
\r
429 leaf network-parameter-value {
\r
437 grouping network-instance-group {
\r
438 list network-instance-group {
\r
439 key "network-instance-group-id";
\r
440 leaf network-instance-group-id {
\r
441 description "Also a Key in Network Instance Group in A&AI";
\r
447 leaf network-instance-group-function {
\r
452 leaf service-instance-id {
\r
457 uses onap-model-information;
\r
458 container subnet-assignment-policy {
\r
460 description "Current valid values - unique, shared (default)";
\r
466 container vpn-binding-policy {
\r
482 leaf vpn-platform {
\r
487 leaf global-route-target {
\r
492 leaf route-target-role {
\r
498 container aggregate-route-policy {
\r
499 leaf aggregate-route-policy-name {
\r
504 leaf ipv4-aggregate-route-level {
\r
509 leaf ipv6-aggregate-route-level {
\r
515 uses aggregate-routes;
\r
517 leaf subnet-key-value {
\r
518 description "key-value provided to IPAM when creating shared subnet";
\r
523 container networks {
\r
527 description "Index into network-topology-identifier structure";
\r
533 leaf neutron-network-id {
\r
534 description "Neutron-network-id assigned by PO/RO";
\r
543 leaf network-status {
\r
544 description "assigned, unassigned";
\r
549 container customer-bonding-requests {
\r
550 list customer-bonding-request {
\r
551 key "configuration-id";
\r
552 leaf configuration-id {
\r
553 description "e.g. vlan network receptor configuration id";
\r
564 grouping network-level-oper-status {
\r
565 container network-level-oper-status {
\r
566 uses oper-status-data;
\r
569 grouping pnf-operation-information {
\r
570 uses sdnc-request-header;
\r
571 uses request-information;
\r
572 uses service-information;
\r
574 uses pnf-request-input;
\r
576 grouping pnf-details {
\r
577 container pnf-details {
\r
579 description "pnfId*Identifier of this Pnf information element. CORRELATIONID = PNF-NAME (A&AI)";
\r
584 description "pnfType (template)*Type of Resource. NEW type: PNF (pre-defined in SDC)";
\r
590 uses onap-model-information;
\r
593 grouping pnf-request-input {
\r
594 container pnf-request-input {
\r
595 leaf request-version {
\r
596 description "keep this? e.g. 1702";
\r
602 uses region-identifier;
\r
603 container pnf-input-parameters {
\r
608 grouping pnf-topology {
\r
609 container pnf-topology {
\r
610 uses pnf-topology-identifier-structure;
\r
611 uses region-identifier;
\r
612 uses onap-model-information;
\r
613 container pnf-parameters-data {
\r
616 leaf sdnc-generated-cloud-resources {
\r
617 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
622 grouping pnf-topology-identifier-structure {
\r
623 container pnf-topology-identifier-structure {
\r
628 description "In preload tree, this label is used for the vf-module-type";
\r
632 description "optionally comes from pnf-request-input container or is assigned by sdn-c";
\r
637 grouping pnf-level-oper-status {
\r
638 container pnf-level-oper-status {
\r
639 uses oper-status-data;
\r
642 grouping vnf-operation-information {
\r
643 uses sdnc-request-header;
\r
644 uses request-information;
\r
645 uses service-information;
\r
646 uses vnf-information;
\r
647 uses vnf-request-input;
\r
648 uses license-information;
\r
650 grouping vnf-information {
\r
651 container vnf-information {
\r
667 uses onap-model-information;
\r
670 grouping vnf-request-input {
\r
671 container vnf-request-input {
\r
672 leaf request-version {
\r
673 description "keep this? e.g. 1702";
\r
683 uses region-identifier;
\r
684 container vnf-networks {
\r
686 key "network-role";
\r
687 uses vnf-network-data;
\r
690 list vnf-network-instance-group-ids {
\r
691 key "vnf-network-instance-group-id";
\r
692 leaf vnf-network-instance-group-id {
\r
693 description "List of vnf network-instance-group";
\r
699 container vnf-input-parameters {
\r
704 grouping vnf-topology {
\r
705 container vnf-topology {
\r
706 uses vnf-topology-identifier-structure;
\r
707 uses region-identifier;
\r
708 uses onap-model-information;
\r
709 uses vnf-resource-assignments;
\r
710 container vnf-parameters-data {
\r
713 leaf sdnc-generated-cloud-resources {
\r
714 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
719 grouping vnf-topology-identifier-structure {
\r
720 container vnf-topology-identifier-structure {
\r
727 description "In preload tree, this label is used for the vf-module-type";
\r
746 description "used in vnf naming";
\r
752 description "optionally comes from vnf-request-input container or is assigned by sdn-c";
\r
759 grouping vnf-resource-assignments {
\r
760 container vnf-resource-assignments {
\r
762 description "Orchestration status from AAI - to be set by SDNC";
\r
767 container availability-zones {
\r
768 leaf-list availability-zone {
\r
769 description "Openstack availability zone name or UUID";
\r
776 description "From the TOSCA data. Indicates the largest availability zone count needed by any vf-module in the VNF.";
\r
780 container vnf-networks {
\r
782 key "network-role";
\r
783 uses vnf-network-data;
\r
788 grouping vnf-network-data {
\r
789 leaf network-role {
\r
790 description "A Network Role to which a VNF must connect";
\r
795 leaf network-name {
\r
796 description "Unique Neutron UUID of an instance of the network role ";
\r
802 description "Unique Neutron UUID of an instance of the network role ";
\r
808 description "Unique Neutron UUID of an instance of the network role ";
\r
813 leaf contrail-network-fqdn {
\r
814 description "contrail network policy object";
\r
819 container subnets-data {
\r
821 key "sdnc-subnet-id";
\r
822 leaf sdnc-subnet-id {
\r
823 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
829 description "Subnet Role for the subnet";
\r
835 description "Populated for preload only";
\r
841 description "Should be ipv4 or ipv6";
\r
847 description "subnet UUID to be passed into the HEAT template";
\r
852 leaf dhcp-enabled {
\r
853 description "Indicator to use this subnet for DHCP ";
\r
859 leaf network-start-address {
\r
860 description "start-address of the subnet";
\r
861 type inet:ip-address;
\r
863 leaf gateway-address {
\r
864 description "subnet gateway address";
\r
865 type inet:ip-address;
\r
868 description "cidr mask";
\r
878 leaf segmentation-id {
\r
883 container related-networks {
\r
884 uses related-network;
\r
887 grouping vnf-level-oper-status {
\r
888 container vnf-level-oper-status {
\r
889 uses oper-status-data;
\r
892 grouping vf-module-operation-information {
\r
893 uses sdnc-request-header;
\r
894 uses request-information;
\r
895 uses service-information;
\r
896 uses vnf-information;
\r
897 uses vf-module-information;
\r
898 uses vf-module-request-input;
\r
900 grouping vf-module-information {
\r
901 container vf-module-information {
\r
902 leaf vf-module-id {
\r
907 leaf vf-module-type {
\r
912 leaf from-preload {
\r
913 description "Indicates if source is preload data";
\r
916 uses onap-model-information;
\r
919 grouping vf-module-request-input {
\r
920 container vf-module-request-input {
\r
921 leaf request-version {
\r
922 description "keep this?";
\r
927 leaf vf-module-name {
\r
932 uses region-identifier;
\r
933 container vf-module-input-parameters {
\r
938 grouping vf-module-topology {
\r
939 container vf-module-topology {
\r
940 uses vf-module-topology-identifier;
\r
941 uses region-identifier;
\r
942 uses onap-model-information;
\r
943 uses vf-module-assignments;
\r
944 container vf-module-parameters {
\r
947 leaf sdnc-generated-cloud-resources {
\r
948 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
953 grouping vf-module-topology-identifier {
\r
954 container vf-module-topology-identifier {
\r
955 leaf vf-module-id {
\r
956 description "vf-module id";
\r
961 leaf vf-module-name {
\r
962 description "vf-module-name";
\r
967 leaf vf-module-type {
\r
974 grouping vf-module-assignments {
\r
975 container vf-module-assignments {
\r
976 leaf vf-module-status {
\r
977 description "Orchestration status from AAI";
\r
985 uses vm-topology-data;
\r
988 uses vlan-vnfc-instance-groups;
\r
989 container dhcp-subnet-assignments {
\r
990 list dhcp-subnet-assignment {
\r
991 key "neutron-subnet-id";
\r
992 leaf neutron-subnet-id {
\r
993 description "Same as subnet-id in subnet-data structure";
\r
999 leaf network-role {
\r
1013 grouping vm-topology-data {
\r
1020 uses onap-model-information;
\r
1021 leaf nfc-naming-code {
\r
1022 description "used in vm naming(draft 29: changed from nfc-code)";
\r
1027 leaf vm-type-tag {
\r
1028 description "from tosca data on vfc";
\r
1036 container vm-names {
\r
1037 leaf-list vm-name {
\r
1050 container vnfc-networks {
\r
1051 uses vnfc-network-data;
\r
1055 container vm-networks {
\r
1057 key "network-role";
\r
1058 uses vm-network-data;
\r
1062 grouping vnfc-network-data {
\r
1063 list vnfc-network-data {
\r
1064 key "vnfc-network-role";
\r
1065 leaf vnfc-network-role {
\r
1076 uses connection-point;
\r
1077 container vnfc-ports {
\r
1079 key "vnfc-port-id";
\r
1080 leaf vnfc-port-id {
\r
1081 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
1087 leaf common-sub-interface-role {
\r
1088 description "If sub-interfaces have common interface role (network role)";
\r
1093 container vnic-sub-interfaces {
\r
1094 uses sub-interface-network-data;
\r
1098 list vnfc-subnet {
\r
1099 key "vnfc-subnet-role";
\r
1100 leaf vnfc-subnet-role {
\r
1101 description "Default value if subnet role is not defined.";
\r
1107 list vnfc-ip-assignments {
\r
1108 key "vnfc-address-family";
\r
1109 leaf vnfc-address-family {
\r
1110 description "indicates if this is IpV4 or IpV6";
\r
1111 type enumeration {
\r
1116 leaf vnfc-subnet-dhcp {
\r
1117 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
1118 type enumeration {
\r
1123 leaf vnfc-subnet-ip-count {
\r
1124 description "The number of IP addresses to be assigned per vnfc for this subnet role";
\r
1127 list vnfc-subnet-ip {
\r
1128 key "vnfc-ip-address";
\r
1129 leaf vnfc-ip-address {
\r
1130 description "Either IpV4 IP or IpV6 IP address should be present";
\r
1131 type inet:ip-address;
\r
1133 leaf vnfc-client-key {
\r
1139 description "Capture what type of IP this is, if is virtual IP (AKA, floating IP) or Fixed IP. ";
\r
1140 type enumeration {
\r
1150 grouping vm-network-data {
\r
1151 leaf network-role {
\r
1152 description "network (identified by role) that this VM connects to. Should also be included in the vnf-networks for the containing VNF";
\r
1158 leaf network-role-tag {
\r
1163 container network-information-items {
\r
1164 list network-information-item {
\r
1167 description "Use ipv4 or ipv6";
\r
1173 description "Indicator to use DHCP on this network for this VM";
\r
1174 type enumeration {
\r
1180 description "The number of ip addresses to be assigned per vm for this network role";
\r
1183 container network-ips {
\r
1184 leaf-list network-ip {
\r
1185 description "List of assigned ip addresses of type ip-version on a network";
\r
1194 container mac-addresses {
\r
1195 leaf-list mac-address {
\r
1196 description "List of network assignments for this vm-type";
\r
1203 container floating-ips {
\r
1204 leaf-list floating-ip-v4 {
\r
1205 description "Floating ipv4 for VMs of a given type on this network";
\r
1206 type inet:ip-address;
\r
1209 leaf-list floating-ip-v6 {
\r
1210 description "Floating ipv6 for VMs of a given type on this network";
\r
1211 type inet:ipv6-address;
\r
1215 container interface-route-prefixes {
\r
1216 leaf-list interface-route-prefix {
\r
1217 description "ordered-by: user";
\r
1222 container sriov-parameters {
\r
1223 container heat-vlan-filters {
\r
1224 leaf-list heat-vlan-filter {
\r
1229 container application-tags {
\r
1230 container c-tags {
\r
1238 container s-tags {
\r
1251 leaf segmentation-id {
\r
1256 container related-networks {
\r
1257 uses related-network;
\r
1260 grouping vf-module-level-oper-status {
\r
1261 container vf-module-level-oper-status {
\r
1262 uses oper-status-data;
\r
1265 grouping allotted-resource-info {
\r
1266 leaf allotted-resource-id {
\r
1271 leaf allotted-resource-type {
\r
1272 description "Not an enum, but expected values are contrail-route and security-zone.";
\r
1277 leaf allotted-resource-pointer {
\r
1278 description "Pointer to the allotted-resources topology";
\r
1284 grouping forwarding-path-operation-information {
\r
1285 uses sdnc-request-header;
\r
1286 uses request-information;
\r
1287 uses service-information;
\r
1288 uses forwarding-path-request-input;
\r
1290 grouping forwarding-path-request-input {
\r
1291 container forwarding-path-request-input {
\r
1292 list forwarding-paths {
\r
1293 key "forwarding-path-name";
\r
1294 leaf forwarding-path-name {
\r
1295 description "Forwarding-path-name from tosca-model. ";
\r
1301 uses onap-model-information;
\r
1305 grouping forwarding-path-information {
\r
1306 leaf forwarding-path-name {
\r
1307 description "Fowarding-path name from TOSCA model, or name generated by SDNC";
\r
1312 leaf forwarding-path-type {
\r
1313 description "Based on MySQL Forwarding_Path tables path_type value from related TOSCA model";
\r
1314 type enumeration {
\r
1319 uses onap-model-information;
\r
1320 container service-paths {
\r
1321 list service-path {
\r
1322 key "service-path-instance-id";
\r
1323 uses service-path-information;
\r
1327 grouping service-path-information {
\r
1328 leaf service-path-instance-id {
\r
1329 description "Service path instance ID generated by SDNC. Identifies a service-path-instance within a forwarding-path definition";
\r
1334 leaf service-path-instance-name {
\r
1335 description "A unique name generated by SDNC ( forwarding-path-name + service-path-instance-id )";
\r
1341 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
1347 key "service-instance-id";
\r
1348 leaf service-instance-id {
\r
1349 description "service-instance-id of each service-instance in the service-path-instance";
\r
1354 leaf service-path-sequence-id {
\r
1355 description "e.g. S1S2S3S5seq id=1 S1-S2seq id=2 S2S3seq id=3 S3S5Incremental integer value";
\r
1360 key "vnf-instance-id";
\r
1361 uses vnf-path-information;
\r
1366 grouping vnf-path-information {
\r
1367 leaf vnf-instance-id {
\r
1368 description "VNF instance ID in the path";
\r
1373 leaf vnf-path-sequence-id {
\r
1374 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
1377 leaf left-network-name {
\r
1378 description "Every VNF instance in the path is connected to one or two VNFs.";
\r
1383 leaf left-network-role {
\r
1388 leaf right-network-name {
\r
1393 leaf right-network-role {
\r
1398 container vf-module-instance {
\r
1399 leaf vf-module-id {
\r
1404 leaf vf-module-name {
\r
1411 grouping forwarding-path-level-oper-status {
\r
1412 container forwarding-path-level-oper-status {
\r
1413 uses oper-status-data;
\r
1416 grouping configuration-info {
\r
1417 leaf configuration-id {
\r
1422 leaf configuration-type {
\r
1423 description "Not an enum, but expected values are port-mirror-configuration, , vlan-network-receptor";
\r
1428 leaf configuration-sub-type {
\r
1429 description "Not an enum, but expected values are vprobe and pprobe";
\r
1434 leaf configuration-topology-link {
\r
1435 description "Pointer to the configurations topology";
\r
1441 grouping vnfc-instance-group {
\r
1442 list vnfc-instance-group {
\r
1443 key "instance-group-role nfc-naming-code configuration-id";
\r
1444 leaf instance-group-role {
\r
1445 description "i.e.TSBC_VNFC_group";
\r
1451 leaf nfc-naming-code {
\r
1452 description "Set to nfc-naming-code from A&AI";
\r
1458 leaf configuration-id {
\r
1465 description " port-mirror-source or port-mirror-dest";
\r
1470 uses vnfc-objects;
\r
1473 grouping vnfc-objects {
\r
1474 container vnfc-objects {
\r
1475 list vnfc-object {
\r
1483 description "Vnfc name as key in A&AI";
\r
1498 leaf vserver-name {
\r
1510 key "vnic-port-name";
\r
1511 leaf vnic-port-name {
\r
1516 leaf vnic-port-id {
\r
1521 container capacity {
\r
1522 leaf vnic-capacity {
\r
1525 leaf used-capacity {
\r
1526 description "Updated for destination port when source port is mapped/unmapped.";
\r
1530 container vnic-ip-addresses {
\r
1531 uses ip-addresses;
\r
1543 description "Vnfc name as key in A&AI";
\r
1548 leaf vserver-name {
\r
1565 key "vnic-port-name";
\r
1566 leaf vnic-port-name {
\r
1571 leaf vnic-port-id {
\r
1576 uses sub-interfaces;
\r
1580 grouping sub-interfaces {
\r
1581 container sub-interfaces {
\r
1582 list sub-interface {
\r
1583 key "sub-interface-port-name";
\r
1584 leaf sub-interface-port-name {
\r
1589 leaf sub-interface-port-id {
\r
1594 container sub-interface-ip-addresses {
\r
1595 uses ip-addresses;
\r
1598 container sub-interface-network {
\r
1599 leaf network-name {
\r
1610 leaf sub-interface-status {
\r
1611 description "NULL, unassigned, assigned";
\r
1619 grouping vlan-tags {
\r
1620 container vlan-tags {
\r
1621 leaf vlan-interface {
\r
1622 description "A&AI Key";
\r
1627 leaf upper-tag-id {
\r
1628 description "aka outer tag";
\r
1631 leaf lower-tag-id {
\r
1632 description "aka inner tag";
\r
1640 grouping vlan-vnfc-instance-groups {
\r
1641 container vlan-vnfc-instance-groups {
\r
1642 list vlan-vnfc-instance-group {
\r
1643 key "instance-group-id";
\r
1644 leaf instance-group-id {
\r
1645 description "A&AI ID";
\r
1651 leaf instance-group-function {
\r
1675 grouping vnic-groups {
\r
1676 container vnic-groups {
\r
1678 key "vnic-interface-role";
\r
1679 leaf vnic-interface-role {
\r
1680 description "Same as network-role of network where vnic is connected";
\r
1686 leaf network-instance-group-function {
\r
1687 description "network-instance-Group-function for network collection where vnics with vnic-interface-role will connect";
\r
1692 leaf vlan-assignment-policy-name {
\r
1693 description "Policy name in ASDC model & policy definition in Policy Engine";
\r
1698 leaf vlan-tag-index-next {
\r
1699 description "Next tag to be assigned";
\r
1702 container vlan-common-ip-addresses {
\r
1703 uses ip-addresses;
\r
1705 container vlan-vnics {
\r
1707 key "vnic-port-id";
\r
1708 leaf vnic-port-id {
\r
1714 container vnic-sub-interfaces {
\r
1715 uses sub-interface-network-data;
\r
1722 grouping vnf-cloud-param {
\r
1723 leaf service-instance-id {
\r
1728 leaf service-instance-name {
\r
1747 key "vf-module-id";
\r
1748 leaf vf-module-id {
\r
1757 grouping vnf-network-collection {
\r
1758 list vnf-network-collection {
\r
1759 key "network-instance-group-function";
\r
1760 leaf network-instance-group-function {
\r
1761 description "Network Instance-Group function in A&AI";
\r
1767 leaf network-instance-group-id {
\r
1768 description "Network Instance-Group id in A&AI";
\r
1773 leaf network-collection-service-instance-id {
\r
1774 description "Service-instance-id of service that created the network collection";
\r
1779 leaf network-collection-customization-uuid {
\r
1780 description "network-collection-customization-uuid stored in Network IsntanceGroup.customization-uuid in A&AI";
\r
1785 container networks {
\r
1789 description "Index into network-topology-identifier structure";
\r
1795 leaf neutron-network-id {
\r
1796 description "Neutron-network-id assigned by PO/RO";
\r
1803 container vnf-floating-ip {
\r
1804 uses ip-addresses;
\r
1808 grouping vnf-sub-interface-group {
\r
1809 list vnf-sub-interface-group {
\r
1810 key "vnfc-instance-group-function network-instance-group-function parent-port-role";
\r
1811 leaf vnfc-instance-group-function {
\r
1817 leaf network-instance-group-function {
\r
1823 leaf parent-port-role {
\r
1830 container customer-bonding-requests {
\r
1831 list customer-bonding-request {
\r
1832 key "configuration-id";
\r
1833 leaf configuration-id {
\r
1834 description "e.g. vlan network receptor configuration id";
\r
1843 grouping sub-interface-network-data {
\r
1844 list sub-interface-network-data {
\r
1847 description "Subinterface network id (UUID in A&AI)";
\r
1853 leaf neutron-network-id {
\r
1854 description "Neutron network id assigned by PO/RP";
\r
1859 leaf network-name {
\r
1860 description "Subinterface network name";
\r
1863 leaf vlan-tag-id {
\r
1864 description "Vlan tag assigned to subinterface port";
\r
1867 leaf network-role {
\r
1868 description "e.g. untrusted ";
\r
1873 leaf network-role-tag {
\r
1874 description "Assuming HEAT template network role tag parameter - not used";
\r
1879 container network-information-items {
\r
1880 list network-information-item {
\r
1883 description "Use ipv4 or ipv6";
\r
1889 description "Indicator to use DHCP on this network for this VM - set to N for Vlan tagging";
\r
1890 type enumeration {
\r
1896 description "The number of ip addresses to be assigned per vm for this network role";
\r
1899 container network-ips {
\r
1900 leaf-list network-ip {
\r
1901 description "List of assigned ip addresses of type ip-version on a network.";
\r
1902 type inet:ip-address;
\r
1908 container floating-ips {
\r
1909 leaf-list floating-ip-v4 {
\r
1910 description "Floating ipv4 for VMs of a given type on this network";
\r
1911 type inet:ip-address;
\r
1914 leaf-list floating-ip-v6 {
\r
1915 description "Floating ipv6 for VMs of a given type on this network";
\r
1916 type inet:ipv6-address;
\r
1922 grouping vnf-get-resource-request-input-data {
\r
1931 key "vf-module-id";
\r
1932 leaf vf-module-id {
\r
1940 grouping license-information {
\r
1941 container license-information {
\r
1942 list entitlement-pool-list {
\r
1943 key "entitlement-pool-uuid action";
\r
1944 leaf entitlement-pool-uuid {
\r
1956 leaf entitlement-pool-invariant-uuid {
\r
1961 leaf entitlement-uuid {
\r
1962 description "assigned by ALTS";
\r
1968 list license-key-group-list {
\r
1969 key "license-key-group-uuid action";
\r
1970 leaf license-key-group-uuid {
\r
1982 leaf license-key-group-invariant-uuid {
\r
1987 leaf license-key {
\r
1988 description "assigned by ALTS";
\r
1993 leaf license-uuid {
\r
1994 description "assigned by ALTS";
\r
2002 grouping related-network {
\r
2003 list related-network {
\r
2006 description "Key to l3-network object";
\r
2011 leaf network-role {
\r
2019 grouping connection-point {
\r
2020 container connection-point {
\r
2021 leaf connection-point-id {
\r
2022 description "Key to CP object in A&AI";
\r
2028 description "port-index when multiple CPs connect to same network. Default zero (0)";
\r
2036 description "Key to vlan-tag uuid object in A&AI Generated by vlan mS";
\r
2041 leaf vlan-tag-id {
\r
2046 leaf vlan-tag-description {
\r
2052 description "Inner/Outer roles";
\r
2060 grouping aggregate-routes {
\r
2061 list aggregate-routes {
\r
2064 description "Unique id";
\r
2069 leaf start-address {
\r
2070 type inet:ip-address;
\r
2078 description "Use values 4 or 6.";
\r
2085 grouping pnf-information {
\r
2086 container pnf-information {
\r
2088 description "Key for A&AI query";
\r
2098 uses onap-model-information;
\r
2101 grouping contrail-route-operation-information {
\r
2102 uses sdnc-request-header;
\r
2103 uses request-information;
\r
2104 uses service-information;
\r
2105 uses allotted-resource-information;
\r
2106 uses contrail-route-request-input;
\r
2108 grouping contrail-route-request-input {
\r
2109 container contrail-route-request-input {
\r
2110 container source-network {
\r
2111 uses network-info;
\r
2113 container dest-network {
\r
2114 uses network-info;
\r
2116 container contrail-applied-service-info {
\r
2117 leaf service-instance-id {
\r
2118 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
2123 leaf contrail-fqdn {
\r
2124 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
2130 container contrail-route-input-parameters {
\r
2135 grouping network-info {
\r
2141 leaf network-role {
\r
2147 grouping contrail-route-topology {
\r
2148 container contrail-route-topology {
\r
2149 uses allotted-resource-identifiers;
\r
2150 uses onap-model-information;
\r
2151 uses contrail-route-assignments;
\r
2152 container contrail-route-parameters {
\r
2157 grouping contrail-route-assignments {
\r
2158 container contrail-route-assignments {
\r
2160 description "The Contrail fq-name of the network policy";
\r
2165 leaf contrail-id {
\r
2166 description "The ID assigned by Contrail to the network-policy (one for one with the fq-name)";
\r
2171 container source-network {
\r
2172 uses network-info;
\r
2174 container dest-network {
\r
2175 uses network-info;
\r
2177 container contrail-applied-service {
\r
2178 leaf service-instance-id {
\r
2179 description "The service-instance-id of the vnf from which the contrail applied service is coming";
\r
2185 description "The vnf representing the contrail applied service";
\r
2190 leaf contrail-fqdn {
\r
2191 description "This is the fq-name of the Contrail service instance through which the route is passing.";
\r
2198 description "Contrail-assigned vlan-tag to the vipr vm interface for this route.";
\r
2205 grouping security-zone-operation-information {
\r
2206 uses sdnc-request-header;
\r
2207 uses request-information;
\r
2208 uses service-information;
\r
2209 uses allotted-resource-information;
\r
2210 uses security-zone-request-input;
\r
2212 grouping security-zone-request-input {
\r
2213 container security-zone-request-input {
\r
2219 leaf trusted-network-role {
\r
2220 description "In the case of vIPR, this is the landing networks network-role; used in naming";
\r
2225 leaf untrusted-network-role {
\r
2226 description "In the case of vIPR, this is the tenant oam networks network-role; used in naming";
\r
2231 container security-zone-input-parameters {
\r
2236 grouping security-zone-topology {
\r
2237 container security-zone-topology {
\r
2238 uses allotted-resource-identifiers;
\r
2239 uses onap-model-information;
\r
2240 uses security-zone-assignments;
\r
2241 container security-zone-parameters {
\r
2246 grouping security-zone-assignments {
\r
2247 container security-zone-assignments {
\r
2248 leaf trusted-network-role {
\r
2249 description "In the case of vIPR, this is the landing networks network-role; used in naming";
\r
2254 leaf security-zone-name-trusted {
\r
2259 leaf untrusted-network-role {
\r
2260 description "In the case of vIPR, this is the tenant oam networks network-role; used in naming";
\r
2265 leaf security-zone-name-untrusted {
\r
2270 leaf security-zone-service-instance-id {
\r
2271 description "Will be the same as the parent-service-instance-id";
\r
2276 leaf security-zone-vnf-id {
\r
2277 description "Selected by SDNC from the security-zone-service-instance-id";
\r
2289 grouping port-mirror-topology-operation-information {
\r
2290 uses sdnc-request-header;
\r
2291 uses request-information;
\r
2292 uses service-information;
\r
2293 uses configuration-information;
\r
2294 uses port-mirror-configuration-request-input;
\r
2296 grouping port-mirror-configuration-request-input {
\r
2297 container port-mirror-configuration-request-input {
\r
2298 container source-port {
\r
2300 leaf source-port-id {
\r
2301 description "needed for srv-action=disable/enable";
\r
2307 container dest-port {
\r
2310 uses region-identifier;
\r
2311 container port-mirror-configuration-input-parameters {
\r
2316 grouping port-info {
\r
2317 leaf service-instance-id {
\r
2318 description "May not be need.";
\r
2323 uses pnf-information;
\r
2324 uses vnf-information;
\r
2326 grouping port-mirror-configuration-topology {
\r
2327 container port-mirror-configuration-topology {
\r
2328 uses configuration-identifiers;
\r
2329 uses onap-model-information;
\r
2330 uses port-mirror-configuration-assignments;
\r
2331 container port-mirror-configuration-parameters {
\r
2336 grouping port-mirror-configuration-assignments {
\r
2337 container port-mirror-configuration-assignments {
\r
2338 container contrail-vmi-params {
\r
2341 leaf vnics-group-id {
\r
2346 leaf owning-entity {
\r
2351 leaf tenant-context {
\r
2352 description "From tenant object in A&AI";
\r
2358 description "Tenant name from A&AI for source VNF";
\r
2364 description "tenant-id from A&AI for source VNF";
\r
2369 leaf dest-tenant {
\r
2370 description "Tenant name from A&AI for destination VNF";
\r
2375 leaf dest-tenant-id {
\r
2376 description "tenant-id from A&AI for destination VNF";
\r
2381 leaf cloud-region-id {
\r
2386 leaf cloud-owner {
\r
2391 leaf dest-network-fqdn {
\r
2396 leaf source-network-fqdn {
\r
2401 leaf source-capacity {
\r
2402 description "Source port pps (packets per second) rating from tosca model";
\r
2405 leaf source-vnf-id {
\r
2410 leaf dest-vnf-id {
\r
2411 description "For vProbe";
\r
2416 leaf dest-pnf-name {
\r
2417 description "For pProbe";
\r
2422 leaf dest-p-interface {
\r
2423 description "For pProbe; from policy manager";
\r
2428 leaf dest-pnf-port-policy-name {
\r
2429 description "For pProbe; from tosca model";
\r
2435 description "vprobe or pprobe; derived from configuration-information.configuration-sub-type";
\r
2440 leaf route-allotted-resource-id {
\r
2441 description "For vProbe";
\r
2446 container source-vnfc-instance-group-id {
\r
2447 leaf service-instance-id {
\r
2452 leaf nfc-naming-code {
\r
2453 description "Set to nfc-naming-code";
\r
2458 leaf instance-group-role {
\r
2463 leaf configuration-id {
\r
2469 container dest-vnfc-instance-group-id {
\r
2470 leaf service-instance-id {
\r
2475 leaf nfc-naming-code {
\r
2476 description "Set to nfc-naming-code";
\r
2481 leaf instance-group-role {
\r
2486 leaf configuration-id {
\r
2492 container source-to-dest-maps {
\r
2493 list source-to-dest-map {
\r
2494 key "source-port-id";
\r
2495 leaf source-port-id {
\r
2501 leaf source-port-name {
\r
2506 leaf source-vserver-id {
\r
2511 leaf dest-vserver-id {
\r
2516 leaf dest-port-id {
\r
2521 leaf dest-port-name {
\r
2531 container dest-ip-addresses {
\r
2532 uses ip-addresses;
\r
2538 grouping gc-topology-operation-information {
\r
2539 uses sdnc-request-header;
\r
2540 uses request-information;
\r
2541 uses service-information;
\r
2542 uses configuration-information;
\r
2543 uses gc-request-input;
\r
2545 grouping gc-request-input {
\r
2546 container gc-request-input {
\r
2552 leaf vf-module-id {
\r
2553 description "This is mandatory in case of rebuild";
\r
2558 container input-parameters {
\r
2562 description "Value will indicate what to rebuild";
\r
2567 list configuration-ids {
\r
2568 key "configuration-id";
\r
2569 leaf configuration-id {
\r
2577 grouping vnr-parameters {
\r
2578 container vnr-parameters {
\r
2584 leaf vf-module-id {
\r
2585 description "This is mandatory in case of rebuild";
\r
2590 leaf vnf-service-instance-id {
\r
2595 leaf network-collection-service-instance-id {
\r
2596 description "service instance id that created network-collection";
\r
2601 leaf network-instance-group-id {
\r
2611 leaf vnfc-instance-group-function {
\r
2616 leaf network-instance-group-function {
\r
2621 leaf parent-port-role {
\r
2626 leaf upper-tag-id {
\r
2629 leaf lower-tag-id {
\r
2634 grouping tunnelxconn-operation-information {
\r
2635 uses sdnc-request-header;
\r
2636 uses request-information;
\r
2637 uses service-information;
\r
2638 uses allotted-resource-information;
\r
2639 uses tunnelxconn-request-input;
\r
2641 grouping tunnelxconn-request-input {
\r
2643 container tunnelxconn-request-input {
\r
2644 leaf brg-wan-mac-address {
\r
2649 grouping tunnelxconn-topology {
\r
2650 container tunnelxconn-topology {
\r
2651 uses allotted-resource-identifiers;
\r
2652 uses onap-model-information;
\r
2653 uses tunnelxconn-assignments;
\r
2654 container tunnelxconn-parameters {
\r
2659 grouping tunnelxconn-assignments {
\r
2660 container tunnelxconn-assignments {
\r
2662 description "The Network Controller will assign a VNI value from the associated vGMUX VNI pool";
\r
2665 leaf vgmux-bearer-ip {
\r
2666 description "The Network Controller will look up the vgmux bearer ip from the vgmux vf module";
\r
2667 type inet:ip-address;
\r
2669 leaf vgmux-lan-ip {
\r
2670 description "The Network Controller will look up the vgmux lan ip from the vgmux vg module";
\r
2671 type inet:ip-address;
\r
2674 description "The Network Controller will assign the VG IP address from local inventory";
\r
2675 type inet:ip-address;
\r
2679 grouping brg-operation-information {
\r
2680 uses sdnc-request-header;
\r
2681 uses request-information;
\r
2682 uses service-information;
\r
2683 uses allotted-resource-information;
\r
2684 uses brg-request-input;
\r
2686 grouping brg-request-input {
\r
2687 container brg-request-input {
\r
2688 leaf vgmux-bearer-ip {
\r
2689 type inet:ip-address;
\r
2694 leaf brg-wan-mac-address {
\r
2699 grouping brg-topology {
\r
2700 container brg-topology {
\r
2701 uses allotted-resource-identifiers;
\r
2702 uses onap-model-information;
\r
2703 uses brg-assignments;
\r
2704 container brg-parameters {
\r
2709 grouping brg-assignments {
\r
2710 container brg-assignments {
\r
2711 leaf vbrg-wan-ip {
\r
2712 type inet:ip-address;
\r
2716 grouping connection-attachment-operation-information {
\r
2717 uses sdnc-request-header;
\r
2718 uses request-information;
\r
2719 uses service-information;
\r
2720 uses allotted-resource-information;
\r
2721 uses connection-attachment-request-input;
\r
2724 grouping connection-attachment-request-input {
\r
2725 container connection-attachment-request-input {
\r
2730 grouping connection-attachment-topology {
\r
2731 container connection-attachment-topology {
\r
2732 uses allotted-resource-identifiers;
\r
2733 uses onap-model-information;
\r
2734 uses connection-attachment-assignments;
\r
2735 container connection-attachment-parameters {
\r
2741 grouping connection-attachment-assignments {
\r
2742 container connection-attachment-assignments {
\r
2746 grouping vnf-vnr-rebuild-data {
\r
2747 container vnf-vnr-rebuild-data {
\r
2753 leaf vnf-service-instance-id {
\r
2759 key "configuration-id";
\r
2760 leaf configuration-id {
\r
2765 leaf network-instance-group-id {
\r
2775 leaf vnfc-instance-group-function {
\r
2780 leaf network-instance-group-function {
\r
2785 leaf parent-port-role {
\r
2790 leaf upper-tag-id {
\r
2793 leaf lower-tag-id {
\r
2799 grouping allotted-resource-information {
\r
2800 container allotted-resource-information {
\r
2801 leaf allotted-resource-id {
\r
2806 leaf allotted-resource-type {
\r
2807 description "Not an enum, but expected values are contrail-route and security-zone.";
\r
2812 leaf parent-service-instance-id {
\r
2813 description "Service-instance-id of the parent service to which this allotted resource belongs.";
\r
2818 uses onap-model-information;
\r
2821 grouping allotted-resource-identifiers {
\r
2822 container allotted-resource-identifiers {
\r
2823 leaf allotted-resource-id {
\r
2828 leaf allotted-resource-name {
\r
2829 description "For a contrail-route, the network policy name.";
\r
2834 leaf allotted-resource-type {
\r
2835 description "(Added in draft 32)Expected to be contrail-route or security-zone.";
\r
2840 leaf consuming-service-instance-id {
\r
2841 description "The service-instance-id of the consuming service of this allotted resource";
\r
2846 leaf parent-service-instance-id {
\r
2847 description "Service-instance-id of the parent service to which this allotted resource belongs.";
\r
2854 grouping allotted-resource-oper-status {
\r
2855 container allotted-resource-oper-status {
\r
2856 uses oper-status-data;
\r
2859 grouping allotted-resource-status {
\r
2860 container allotted-resource-status {
\r
2861 leaf response-code {
\r
2866 leaf response-message {
\r
2871 leaf final-indicator {
\r
2876 leaf request-status {
\r
2877 type enumeration {
\r
2878 enum "synccomplete";
\r
2879 enum "asynccomplete";
\r
2880 enum "notifycomplete";
\r
2884 description "value would one of possible request-actions; match the list in service-data oper-status";
\r
2895 description "this is the svc-action from the incoming request";
\r
2896 type enumeration {
\r
2902 enum "deactivate";
\r
2905 leaf response-timestamp {
\r
2912 grouping configuration-information {
\r
2913 container configuration-information {
\r
2914 leaf configuration-id {
\r
2919 leaf configuration-name {
\r
2924 leaf configuration-type {
\r
2925 description "Not an enum, but expected values are port-mirror-configuration, vlan-network-receptor";
\r
2930 leaf configuration-sub-type {
\r
2931 description "e.g. vprobe and pprobe when configuration-type=port-mirror-configuration";
\r
2936 uses onap-model-information;
\r
2939 grouping configuration-identifiers {
\r
2940 container configuration-identifiers {
\r
2941 leaf configuration-id {
\r
2946 leaf configuration-name {
\r
2951 leaf configuration-type {
\r
2952 description "Not an enum, but expected values are port-mirror-configuration.";
\r
2957 leaf configuration-sub-type {
\r
2958 description " vprobe and pprobe";
\r
2963 leaf parent-service-instance-id {
\r
2964 description "Service-instance-id of the parent service to which this resource belongs.";
\r
2971 grouping configuration-oper-status {
\r
2972 container configuration-oper-status {
\r
2973 uses oper-status-data;
\r
2976 grouping configuration-status {
\r
2977 container configuration-status {
\r
2978 leaf response-code {
\r
2983 leaf response-message {
\r
2988 leaf final-indicator {
\r
2993 leaf request-status {
\r
2994 type enumeration {
\r
2995 enum "synccomplete";
\r
2996 enum "asynccomplete";
\r
2997 enum "notifycomplete";
\r
3001 description "value would one of possible request-actions; match the list in service-data oper-status";
\r
3012 description "this is the svc-action from the incoming request";
\r
3013 type enumeration {
\r
3021 enum "deactivate";
\r
3024 leaf response-timestamp {
\r
3031 grouping topology-response-common {
\r
3032 leaf svc-request-id {
\r
3033 description "the request id from the request message for which this is the responseKeep as M";
\r
3038 leaf response-code {
\r
3039 description "a success code or an defined error codeKeep as M";
\r
3044 leaf response-message {
\r
3045 description "message included for error code";
\r
3050 leaf ack-final-indicator {
\r
3051 description "Expected to be Y or N.";
\r
3057 grouping sdnc-request-header {
\r
3058 container sdnc-request-header {
\r
3059 leaf svc-request-id {
\r
3060 description "Uniquely generated by calling system (e.g. MSO or SDN-GP)";
\r
3066 description "This is the rpcAction";
\r
3067 type enumeration {
\r
3072 enum "changeassign";
\r
3073 enum "changedelete";
\r
3075 enum "deactivate";
\r
3081 enum "reoptimize";
\r
3085 leaf svc-notification-url {
\r
3086 description "Contains URL for asynchronous response";
\r
3093 grouping request-information {
\r
3094 container request-information {
\r
3096 description "Request ID generated upstream of MSO";
\r
3101 leaf request-action {
\r
3102 description "still need to work Disconnect";
\r
3103 type enumeration {
\r
3104 enum "CreateNetworkInstance";
\r
3105 enum "ActivateNetworkInstance";
\r
3106 enum "DeActivateNetworkInstance";
\r
3107 enum "CreateServiceInstance";
\r
3108 enum "DeleteServiceInstance";
\r
3109 enum "DeleteNetworkInstance";
\r
3110 enum "CreateVnfInstance";
\r
3111 enum "ActivateVnfInstance";
\r
3112 enum "DeleteVnfInstance";
\r
3113 enum "CreatePnfInstance";
\r
3114 enum "ActivatePnfInstance";
\r
3115 enum "DeletePnfInstance";
\r
3116 enum "CreateVfModuleInstance";
\r
3117 enum "ActivateVfModuleInstance";
\r
3118 enum "DeleteVfModuleInstance";
\r
3119 enum "CreateContrailRouteInstance";
\r
3120 enum "DeleteContrailRouteInstance";
\r
3121 enum "CreateSecurityZoneInstance";
\r
3122 enum "DeleteSecurityZoneInstance";
\r
3123 enum "ActivateDCINetworkInstance";
\r
3124 enum "DeActivateDCINetworkInstance";
\r
3125 enum "CreateTunnelXConnInstance";
\r
3126 enum "DeleteTunnelXConnInstance";
\r
3127 enum "CreateBRGInstance";
\r
3128 enum "DeleteBRGInstance";
\r
3129 enum "CreateSOTNConnectivityInstance";
\r
3130 enum "ActivateSOTNConnectivityInstance";
\r
3131 enum "DeactivateSOTNConnectivityInstance";
\r
3132 enum "DeleteSOTNConnectivityInstance";
\r
3133 enum "CreateSOTNAttachmentInstance";
\r
3134 enum "ActivateSOTNAttachmentInstance";
\r
3135 enum "DeactivateSOTNAttachmentInstance";
\r
3136 enum "DeleteSOTNAttachmentInstance";
\r
3137 enum "CreateSiteInstance";
\r
3138 enum "ActivateSiteInstance";
\r
3139 enum "DeactivateSiteInstance";
\r
3140 enum "DeleteSiteInstance";
\r
3141 enum "CreatePortMirrorConfigurationInstance";
\r
3142 enum "DeletePortMirrorConfigurationInstance";
\r
3143 enum "ChangePortMirrorConfigurationInstance";
\r
3144 enum "CreateGenericConfigurationInstance";
\r
3145 enum "RebuildGenericConfigurationInstance";
\r
3146 enum "DeleteGenericConfigurationInstance";
\r
3147 enum "PreloadVfModuleRequest";
\r
3148 enum "DeletePreloadVfModuleRequest";
\r
3149 enum "PreloadNetworkRequest";
\r
3150 enum "DeletePreloadNetworkRequest";
\r
3151 enum "CreateForwardingPathInstance";
\r
3152 enum "DeleteForwardingPathInstance";
\r
3153 enum "UpdateForwardingPathInstance";
\r
3154 enum "CreateSDWANDeviceInstance";
\r
3155 enum "ActivateSDWANDeviceInstance";
\r
3156 enum "DeactivateSDWANDeviceInstance";
\r
3157 enum "DeleteSDWANDeviceInstance";
\r
3158 enum "CreateSDWANPortInstance";
\r
3159 enum "ActivateSDWANPortInstance";
\r
3160 enum "DeactivateSDWANPortInstance";
\r
3161 enum "DeleteSDWANPortInstance";
\r
3162 enum "ReoptimizeSOTNInstance";
\r
3163 enum "CreateSDWANLanPortInstance";
\r
3164 enum "ActivateSDWANLanPortInstance";
\r
3165 enum "DeactivateSDWANLanPortInstance";
\r
3166 enum "DeleteSDWANLanPortInstance";
\r
3167 enum "CreateSDWANVpnInstance";
\r
3168 enum "ActivateSDWANVpnInstance";
\r
3169 enum "DeactivateSDWANVpnInstance";
\r
3170 enum "DeleteSDWANVpnInstance";
\r
3171 enum "CreateSDWANSiteInstance";
\r
3172 enum "ActivateSDWANSiteInstance";
\r
3173 enum "DeactivateSDWANSiteInstance";
\r
3174 enum "DeleteSDWANSiteInstance";
\r
3175 enum "SdwanBandwidthChange";
\r
3176 enum "CreateAccessConnectivityInstance";
\r
3177 enum "DeleteAccessConnectivityInstance";
\r
3178 enum "CreateInternetProfileInstance";
\r
3179 enum "ChangeInternetProfileInstance";
\r
3180 enum "DeleteInternetProfileInstance";
\r
3181 enum "CreateSOTNUnderlayInstance";
\r
3182 enum "ActivateSOTNUnderlayInstance";
\r
3183 enum "DeactivateSOTNUnderlayInstance";
\r
3184 enum "DeleteSOTNUnderlayInstance";
\r
3185 enum "CreateSOTNUniInstance";
\r
3186 enum "ActivateSOTNUniInstance";
\r
3187 enum "DeactivateSOTNUniInstance";
\r
3188 enum "DeleteSOTNUniInstance";
\r
3189 enum "CreateSOTNL2VpnInstance";
\r
3190 enum "ActivateSOTNL2VpnInstance";
\r
3191 enum "DeactivateSOTNL2VpnInstance";
\r
3192 enum "DeleteSOTNL2VpnInstance";
\r
3193 enum "AllocateTransportSliceInstance";
\r
3194 enum "ActivateTransportSliceInstance";
\r
3195 enum "DeactivateTransportSliceInstance";
\r
3196 enum "DeleteTransportSliceInstance";
\r
3197 enum "ModifyTransportSliceInstance";
\r
3198 enum "CreateCloudLeasedLineInstance";
\r
3199 enum "ModifyCloudLeasedLineInstance";
\r
3200 enum "DeleteCloudLeasedLineInstance";
\r
3208 leaf notification-url {
\r
3213 leaf order-number {
\r
3218 leaf order-version {
\r
3225 grouping service-information {
\r
3226 container service-information {
\r
3228 description "This maps to the product-family-id in A&AI";
\r
3233 leaf subscription-service-type {
\r
3234 description "used to reference a&ai subscription-service-type. For example, we show as vIPR-ATM in example.";
\r
3239 uses onap-model-information;
\r
3240 leaf service-instance-id {
\r
3245 leaf global-customer-id {
\r
3246 description "need for put of data to AnAI (MSO provides)";
\r
3251 leaf subscriber-name {
\r
3252 description "Would not be expected for vIPR-ATM or mobility services.";
\r
3259 grouping onap-model-information {
\r
3260 container onap-model-information {
\r
3261 leaf model-invariant-uuid {
\r
3262 description "identifies the invariant uuid for this service or resource";
\r
3267 leaf model-customization-uuid {
\r
3268 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
3274 description "identifies the uuid for this service or resource, which is version specific";
\r
3279 leaf model-version {
\r
3291 grouping region-identifier {
\r
3297 leaf aic-cloud-region {
\r
3298 description "The AIC cloud region which maps to contrail versions";
\r
3301 leaf cloud-owner {
\r
3307 description "Not expected to be used";
\r
3323 length "0..20000";
\r
3326 container resource-resolution-data {
\r
3327 list resource-key {
\r
3336 length "0..20000";
\r
3341 description "SUCCESS, FAILED, or PENDING - RA returned data as capability";
\r
3346 leaf capability-name {
\r
3347 description "Resource assignment resolution Capability name";
\r
3358 grouping ip-addresses {
\r
3359 container ip-addresses {
\r
3360 leaf ipv4-address {
\r
3361 type inet:ip-address;
\r
3363 leaf ipv6-address {
\r
3364 type inet:ip-address;
\r
3366 leaf vipv4-address {
\r
3367 description "Virtual v4";
\r
3368 type inet:ip-address;
\r
3370 leaf vipv6-address {
\r
3371 description "Virtual v6";
\r
3372 type inet:ip-address;
\r
3376 grouping instance-reference {
\r
3377 leaf instance-id {
\r
3382 leaf object-path {
\r
3383 description "restconf retrieval path to this particular objectE.g. restconf/config/GENERIC-RESOURCE-API:services/service/$service-instance-id/service-data/service-topology/";
\r
3389 grouping oper-status-data {
\r
3390 leaf order-status {
\r
3391 description "TBD - do we need Request failed statuses? RequestFailed | InProgressTimeout";
\r
3392 type enumeration {
\r
3394 enum "PendingAssignment";
\r
3395 enum "PendingCreate";
\r
3396 enum "PendingUpdate";
\r
3397 enum "PendingDelete";
\r
3402 leaf last-rpc-action {
\r
3403 type enumeration {
\r
3408 enum "deactivate";
\r
3410 enum "changeassign";
\r
3411 enum "reoptimize";
\r
3414 leaf last-action {
\r
3415 description "should be list of possible request-actions";
\r
3416 type enumeration {
\r
3417 enum "CreateNetworkInstance";
\r
3418 enum "ActivateNetworkInstance";
\r
3419 enum "DeActivateNetworkInstance";
\r
3420 enum "DeleteNetworkInstance";
\r
3421 enum "CreateServiceInstance";
\r
3422 enum "DeleteServiceInstance";
\r
3423 enum "CreateVnfInstance";
\r
3424 enum "ActivateVnfInstance";
\r
3425 enum "DeleteVnfInstance";
\r
3426 enum "CreatePnfInstance";
\r
3427 enum "ActivatePnfInstance";
\r
3428 enum "DeletePnfInstance";
\r
3429 enum "CreateVfModuleInstance";
\r
3430 enum "ActivateVfModuleInstance";
\r
3431 enum "DeleteVfModuleInstance";
\r
3432 enum "CreateContrailRouteInstance";
\r
3433 enum "DeleteContrailRouteInstance";
\r
3434 enum "CreateSecurityZoneInstance";
\r
3435 enum "DeleteSecurityZoneInstance";
\r
3436 enum "ActivateDCINetworkInstance";
\r
3437 enum "DeActivateDCINetworkInstance";
\r
3438 enum "CreateTunnelXConnInstance";
\r
3439 enum "DeleteTunnelXConnInstance";
\r
3440 enum "CreateBRGInstance";
\r
3441 enum "DeleteBRGInstance";
\r
3442 enum "CreateSOTNConnectivityInstance";
\r
3443 enum "ActivateSOTNConnectivityInstance";
\r
3444 enum "DeactivateSOTNConnectivityInstance";
\r
3445 enum "DeleteSOTNConnectivityInstance";
\r
3446 enum "CreateSOTNAttachmentInstance";
\r
3447 enum "ActivateSOTNAttachmentInstance";
\r
3448 enum "DeactivateSOTNAttachmentInstance";
\r
3449 enum "DeleteSOTNAttachmentInstance";
\r
3450 enum "CreateSiteInstance";
\r
3451 enum "ActivateSiteInstance";
\r
3452 enum "DeactivateSiteInstance";
\r
3453 enum "DeleteSiteInstance";
\r
3454 enum "CreatePortMirrorConfigurationInstance";
\r
3455 enum "DeletePortMirrorConfigurationInstance";
\r
3456 enum "ChangePortMirrorConfigurationInstance";
\r
3457 enum "CreateGenericConfigurationInstance";
\r
3458 enum "DeleteGenericConfigurationInstance";
\r
3459 enum "PreloadVfModuleRequest";
\r
3460 enum "DeletePreloadVfModuleRequest";
\r
3461 enum "PreloadNetworkRequest";
\r
3462 enum "DeletePreloadNetworkRequest";
\r
3463 enum "CreateForwardingPathInstance";
\r
3464 enum "DeleteForwardingPathInstance";
\r
3465 enum "UpdateForwardingPathInstance";
\r
3466 enum "CreateSDWANDeviceInstance";
\r
3467 enum "ActivateSDWANDeviceInstance";
\r
3468 enum "DeactivateSDWANDeviceInstance";
\r
3469 enum "DeleteSDWANDeviceInstance";
\r
3470 enum "CreateSDWANPortInstance";
\r
3471 enum "ActivateSDWANPortInstance";
\r
3472 enum "DeactivateSDWANPortInstance";
\r
3473 enum "DeleteSDWANPortInstance";
\r
3474 enum "ReoptimizeSOTNInstance";
\r
3475 enum "CreateSDWANLanPortInstance";
\r
3476 enum "ActivateSDWANLanPortInstance";
\r
3477 enum "DeactivateSDWANLanPortInstance";
\r
3478 enum "DeleteSDWANLanPortInstance";
\r
3479 enum "CreateSDWANVpnInstance";
\r
3480 enum "ActivateSDWANVpnInstance";
\r
3481 enum "DeactivateSDWANVpnInstance";
\r
3482 enum "DeleteSDWANVpnInstance";
\r
3483 enum "CreateSDWANSiteInstance";
\r
3484 enum "ActivateSDWANSiteInstance";
\r
3485 enum "DeactivateSDWANSiteInstance";
\r
3486 enum "DeleteSDWANSiteInstance";
\r
3487 enum "SdwanBandwidthChange";
\r
3488 enum "CreateAccessConnectivityInstance";
\r
3489 enum "DeleteAccessConnectivityInstance";
\r
3490 enum "CreateInternetProfileInstance";
\r
3491 enum "ChangeInternetProfileInstance";
\r
3492 enum "DeleteInternetProfileInstance";
\r
3493 enum "CreateSOTNUnderlayInstance";
\r
3494 enum "ActivateSOTNUnderlayInstance";
\r
3495 enum "DeactivateSOTNUnderlayInstance";
\r
3496 enum "DeleteSOTNUnderlayInstance";
\r
3497 enum "CreateSOTNUniInstance";
\r
3498 enum "ActivateSOTNUniInstance";
\r
3499 enum "DeactivateSOTNUniInstance";
\r
3500 enum "DeleteSOTNUniInstance";
\r
3501 enum "CreateSOTNL2VpnInstance";
\r
3502 enum "ActivateSOTNL2VpnInstance";
\r
3503 enum "DeactivateSOTNL2VpnInstance";
\r
3504 enum "DeleteSOTNL2VpnInstance";
\r
3505 enum "AllocateTransportSliceInstance";
\r
3506 enum "ActivateTransportSliceInstance";
\r
3507 enum "DeactivateTransportSliceInstance";
\r
3508 enum "DeleteTransportSliceInstance";
\r
3509 enum "ModifyTransportSliceInstance";
\r
3510 enum "CreateCloudLeasedLineInstance";
\r
3511 enum "ModifyCloudLeasedLineInstance";
\r
3512 enum "DeleteCloudLeasedLineInstance";
\r
3515 leaf last-svc-request-id {
\r
3516 description "Not currently populated in service data.";
\r
3521 leaf last-order-status {
\r
3522 type enumeration {
\r
3524 enum "PendingAssignment";
\r
3525 enum "PendingCreate";
\r
3526 enum "PendingUpdate";
\r
3527 enum "PendingDelete";
\r
3532 leaf create-timestamp {
\r
3533 description "Not currently populated in service data.";
\r
3538 leaf modify-timestamp {
\r
3544 grouping service-response-information {
\r
3545 container service-response-information {
\r
3546 uses instance-reference;
\r
3549 grouping network-response-information {
\r
3550 container network-response-information {
\r
3551 uses instance-reference;
\r
3554 grouping vnf-response-information {
\r
3555 container vnf-response-information {
\r
3556 uses instance-reference;
\r
3559 grouping vf-module-response-information {
\r
3560 container vf-module-response-information {
\r
3561 uses instance-reference;
\r
3564 grouping pnf-response-information {
\r
3565 container pnf-response-information {
\r
3566 uses instance-reference;
\r
3569 grouping contrail-route-response-information {
\r
3570 container contrail-route-response-information {
\r
3571 uses instance-reference;
\r
3574 grouping security-zone-response-information {
\r
3575 container security-zone-response-information {
\r
3576 uses instance-reference;
\r
3579 grouping getpathsegment-response-information {
\r
3580 container getpathsegment-response-information {
\r
3581 uses instance-reference;
\r
3584 grouping port-mirror-response-information {
\r
3585 container port-mirror-response-information {
\r
3586 uses instance-reference;
\r
3589 grouping gc-response-information {
\r
3590 container gc-response-information {
\r
3591 uses instance-reference;
\r
3594 grouping tunnelxconn-response-information {
\r
3595 container tunnelxconn-response-information {
\r
3596 uses instance-reference;
\r
3599 grouping brg-response-information {
\r
3600 container brg-response-information {
\r
3601 uses instance-reference;
\r
3604 grouping connection-attachment-response-information {
\r
3605 container connection-attachment-response-information {
\r
3606 uses instance-reference;
\r
3609 grouping preload-model-information {
\r
3610 list preload-list {
\r
3611 key "preload-id preload-type";
\r
3613 description "vf-module-name or network name";
\r
3619 leaf preload-type {
\r
3620 description "network or vf-module";
\r
3626 uses preload-data;
\r
3629 grouping preload-data {
\r
3630 container preload-data {
\r
3631 uses preload-vf-module-topology-information;
\r
3632 uses preload-network-topology-information;
\r
3633 uses preload-oper-status;
\r
3636 grouping preload-vf-module-topology-information {
\r
3637 container preload-vf-module-topology-information {
\r
3638 uses vnf-topology-identifier-structure;
\r
3639 uses vnf-resource-assignments;
\r
3640 uses vf-module-topology;
\r
3643 grouping preload-network-topology-information {
\r
3644 container preload-network-topology-information {
\r
3645 uses network-topology-identifier-structure;
\r
3647 uses vpn-bindings;
\r
3648 uses network-policy;
\r
3649 uses route-table-reference;
\r
3651 uses provider-network-information;
\r
3654 grouping subnets {
\r
3656 key "start-address";
\r
3657 leaf start-address {
\r
3658 type inet:ip-address;
\r
3660 leaf gateway-address {
\r
3661 type inet:ip-address;
\r
3673 leaf dhcp-enabled {
\r
3674 type enumeration {
\r
3679 leaf dhcp-start-address {
\r
3684 leaf dhcp-end-address {
\r
3689 leaf addr-from-start {
\r
3690 description "Default is N";
\r
3691 type enumeration {
\r
3696 leaf subnet-name {
\r
3701 leaf subnet-role {
\r
3706 leaf subnet-sequence {
\r
3711 grouping vpn-bindings {
\r
3712 list vpn-bindings {
\r
3713 key "vpn-binding-id";
\r
3714 leaf vpn-binding-id {
\r
3724 leaf global-route-target {
\r
3729 leaf route-target-role {
\r
3735 description "AIC Zone the route target associated with";
\r
3742 grouping network-policy {
\r
3743 list network-policy {
\r
3744 key "network-policy-fqdn";
\r
3745 leaf network-policy-fqdn {
\r
3750 leaf network-policy-id {
\r
3757 grouping route-table-reference {
\r
3758 list route-table-reference {
\r
3759 key "route-table-reference-fqdn";
\r
3760 leaf route-table-reference-fqdn {
\r
3766 leaf route-table-reference-id {
\r
3773 grouping provider-network-information {
\r
3774 leaf physical-network-name {
\r
3779 leaf is-provider-network {
\r
3782 leaf is-shared-network {
\r
3785 leaf is-external-network {
\r
3789 grouping host-routes {
\r
3790 list host-routes {
\r
3791 key "route-prefix";
\r
3792 leaf route-prefix {
\r
3798 description "Could be ip-address or hostname or service-instance";
\r
3805 grouping preload-oper-status {
\r
3806 container preload-oper-status {
\r
3807 leaf order-status {
\r
3808 type enumeration {
\r
3810 enum "PendingAssignment";
\r
3811 enum "PendingCreate";
\r
3812 enum "PendingUpdate";
\r
3813 enum "PendingDelete";
\r
3817 leaf last-action {
\r
3818 type enumeration {
\r
3819 enum "PreloadVfModuleRequest";
\r
3820 enum "DeletePreloadVfModuleRequest";
\r
3821 enum "PreloadNetworkRequest";
\r
3822 enum "DeletePreloadNetworkRequest";
\r
3825 leaf last-svc-request-id {
\r
3830 leaf last-order-status {
\r
3831 type enumeration {
\r
3833 enum "PendingAssignment";
\r
3834 enum "PendingCreate";
\r
3835 enum "PendingUpdate";
\r
3836 enum "PendingDelete";
\r
3840 leaf create-timestamp {
\r
3845 leaf modify-timestamp {
\r
3850 leaf maintenance-indicator {
\r
3851 type enumeration {
\r
3858 grouping preload-topology-response-body {
\r
3859 leaf svc-request-id {
\r
3864 leaf response-code {
\r
3869 leaf response-message {
\r
3874 leaf ack-final-indicator {
\r
3880 rpc generic-configuration-notification {
\r
3882 uses sdnc-request-header;
\r
3883 uses request-information;
\r
3884 uses service-information;
\r
3885 uses configuration-information;
\r
3886 uses topology-response-common;
\r
3887 leaf configuration-topology-link {
\r
3888 description "Returns URL to generic-configuration-topology ";
\r
3893 uses vnr-parameters;
\r
3894 uses vnf-vnr-rebuild-data;
\r
3897 container services {
\r
3898 uses service-model-infrastructure;
\r
3900 container contrail-route-allotted-resources {
\r
3901 list contrail-route-allotted-resource {
\r
3902 key "allotted-resource-id";
\r
3903 leaf allotted-resource-id {
\r
3909 container allotted-resource-data {
\r
3910 container allotted-resource-operation-information {
\r
3911 uses contrail-route-operation-information;
\r
3913 uses contrail-route-topology;
\r
3914 uses allotted-resource-oper-status;
\r
3916 uses allotted-resource-status;
\r
3919 container security-zone-allotted-resources {
\r
3920 list security-zone-allotted-resource {
\r
3921 key "allotted-resource-id";
\r
3922 leaf allotted-resource-id {
\r
3928 container allotted-resource-data {
\r
3929 container allotted-resource-operation-information {
\r
3930 uses security-zone-operation-information;
\r
3932 uses security-zone-topology;
\r
3933 container security-zone-parameters {
\r
3936 uses allotted-resource-oper-status;
\r
3938 uses allotted-resource-status;
\r
3941 container tunnelxconn-allotted-resources {
\r
3942 list tunnelxconn-allotted-resource {
\r
3943 key "allotted-resource-id";
\r
3944 leaf allotted-resource-id {
\r
3948 container allotted-resource-data {
\r
3949 container allotted-resource-operation-information {
\r
3950 uses tunnelxconn-operation-information;
\r
3952 uses tunnelxconn-topology;
\r
3953 container tunnelxconn-parameters {
\r
3956 uses allotted-resource-oper-status;
\r
3958 uses allotted-resource-status;
\r
3961 container brg-allotted-resources {
\r
3962 list brg-allotted-resource {
\r
3963 key "allotted-resource-id";
\r
3964 leaf allotted-resource-id {
\r
3968 container allotted-resource-data {
\r
3969 container allotted-resource-operation-information {
\r
3970 uses brg-operation-information;
\r
3972 uses brg-topology;
\r
3973 container brg-parameters {
\r
3976 uses allotted-resource-oper-status;
\r
3978 uses allotted-resource-status;
\r
3981 container connection-attachment-allotted-resources {
\r
3982 list connection-attachment-allotted-resource {
\r
3983 key "allotted-resource-id";
\r
3984 leaf allotted-resource-id {
\r
3988 container allotted-resource-data {
\r
3989 container allotted-resource-operation-information {
\r
3990 uses connection-attachment-operation-information;
\r
3992 uses connection-attachment-topology;
\r
3993 container connection-attachment-parameters {
\r
3996 uses allotted-resource-oper-status;
\r
3998 uses allotted-resource-status;
\r
4001 container port-mirror-configurations {
\r
4002 list port-mirror-configuration {
\r
4003 key "configuration-id";
\r
4004 leaf configuration-id {
\r
4010 container configuration-data {
\r
4011 container configuration-operation-information {
\r
4012 uses port-mirror-topology-operation-information;
\r
4014 uses port-mirror-configuration-topology;
\r
4015 uses configuration-oper-status;
\r
4017 uses configuration-status;
\r
4020 container generic-configurations {
\r
4021 list gc-configuration {
\r
4022 key "configuration-id";
\r
4023 leaf configuration-id {
\r
4029 container configuration-data {
\r
4030 container configuration-operation-information {
\r
4031 uses gc-topology-operation-information;
\r
4033 uses configuration-oper-status;
\r
4035 uses configuration-status;
\r
4038 rpc service-topology-operation {
\r
4040 uses service-operation-information;
\r
4043 uses topology-response-common;
\r
4044 uses service-response-information;
\r
4047 rpc network-topology-operation {
\r
4049 uses network-operation-information;
\r
4052 uses topology-response-common;
\r
4053 uses network-response-information;
\r
4054 uses service-response-information;
\r
4057 rpc vnf-topology-operation {
\r
4059 uses vnf-operation-information;
\r
4062 uses topology-response-common;
\r
4063 uses vnf-response-information;
\r
4064 uses service-response-information;
\r
4067 rpc vf-module-topology-operation {
\r
4069 uses vf-module-operation-information;
\r
4072 uses topology-response-common;
\r
4073 uses vf-module-response-information;
\r
4074 uses vnf-response-information;
\r
4075 uses service-response-information;
\r
4078 rpc pnf-topology-operation {
\r
4080 uses pnf-operation-information;
\r
4083 uses topology-response-common;
\r
4084 uses pnf-response-information;
\r
4085 uses service-response-information;
\r
4088 rpc contrail-route-topology-operation {
\r
4090 uses contrail-route-operation-information;
\r
4093 uses topology-response-common;
\r
4094 uses contrail-route-response-information;
\r
4095 uses service-response-information;
\r
4098 rpc security-zone-topology-operation {
\r
4100 uses security-zone-operation-information;
\r
4103 uses topology-response-common;
\r
4104 uses security-zone-response-information;
\r
4105 uses service-response-information;
\r
4108 rpc tunnelxconn-topology-operation {
\r
4110 uses tunnelxconn-operation-information;
\r
4113 uses topology-response-common;
\r
4114 uses tunnelxconn-response-information;
\r
4115 uses service-response-information;
\r
4118 rpc brg-topology-operation {
\r
4120 uses brg-operation-information;
\r
4123 uses topology-response-common;
\r
4124 uses brg-response-information;
\r
4125 uses service-response-information;
\r
4128 rpc policy-update-notify-operation {
\r
4130 leaf policy-name {
\r
4137 description "Map JSON versionNo to version-id";
\r
4143 leaf update-type {
\r
4163 rpc getpathsegment-topology-operation {
\r
4165 uses forwarding-path-operation-information;
\r
4168 uses topology-response-common;
\r
4169 uses getpathsegment-response-information;
\r
4170 uses service-response-information;
\r
4173 rpc port-mirror-topology-operation {
\r
4175 uses port-mirror-topology-operation-information;
\r
4178 uses topology-response-common;
\r
4179 uses port-mirror-response-information;
\r
4180 uses service-response-information;
\r
4183 rpc generic-configuration-topology-operation {
\r
4185 uses gc-topology-operation-information;
\r
4188 uses topology-response-common;
\r
4189 uses gc-response-information;
\r
4190 uses service-response-information;
\r
4193 rpc vnf-get-resource-request {
\r
4195 uses sdnc-request-header;
\r
4196 uses request-information;
\r
4197 uses service-information;
\r
4198 uses vnf-get-resource-request-input-data;
\r
4201 container vnf-get-resource-response-information {
\r
4202 uses vnf-cloud-param;
\r
4206 container preload-information {
\r
4207 uses preload-model-information;
\r
4209 rpc preload-vf-module-topology-operation {
\r
4211 uses sdnc-request-header;
\r
4212 uses request-information;
\r
4213 uses preload-vf-module-topology-information;
\r
4216 uses preload-topology-response-body;
\r
4219 rpc preload-network-topology-operation {
\r
4221 uses sdnc-request-header;
\r
4222 uses request-information;
\r
4223 uses preload-network-topology-information;
\r
4226 uses preload-topology-response-body;
\r
4230 rpc connection-attachment-topology-operation {
\r
4232 uses connection-attachment-operation-information;
\r
4235 uses topology-response-common;
\r
4236 uses connection-attachment-response-information;
\r
4237 uses service-response-information;
\r
4241 rpc collectPerformanceData {
\r
4243 uses sdnc-request-header;
\r
4244 uses request-information;
\r
4245 uses service-information;
\r
4246 leaf controller-ipv4-address {
\r
4252 uses topology-response-common;
\r
4256 } ////closes the module
\r