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
40 container network-data {
\r
41 uses network-operation-information;
\r
42 uses network-topology;
\r
43 container network-provided-allotted-resources {
\r
44 leaf-list network-provided-ar-id {
\r
45 description "List of allotted resources using capacity from this network";
\r
50 uses network-level-oper-status;
\r
61 container pnf-data {
\r
62 uses pnf-operation-information;
\r
64 uses pnf-level-oper-status;
\r
75 container vnf-data {
\r
76 uses vnf-operation-information;
\r
78 container vnf-network-collections {
\r
79 uses vnf-network-collection;
\r
81 container vnf-sub-interface-groups {
\r
82 uses vnf-sub-interface-group;
\r
84 container vnf-provided-allotted-resources {
\r
85 leaf-list vnf-provided-ar-id {
\r
86 description "List of allotted resources using capacity from this vnf";
\r
91 uses vnf-level-oper-status;
\r
92 container vf-modules {
\r
99 container vf-module-data {
\r
100 uses vf-module-operation-information;
\r
101 uses vf-module-topology;
\r
102 uses vf-module-level-oper-status;
\r
109 container consumed-allotted-resources {
\r
110 list consumed-allotted-resource {
\r
111 key "allotted-resource-id";
\r
112 uses allotted-resource-info;
\r
115 container provided-allotted-resources {
\r
116 list provided-allotted-resource {
\r
117 key "allotted-resource-id";
\r
118 uses allotted-resource-info;
\r
121 container provided-configurations {
\r
122 list provided-configuration {
\r
123 key "configuration-id";
\r
124 uses configuration-info;
\r
127 container vnfc-instance-groups {
\r
128 uses vnfc-instance-group;
\r
130 container network-instance-groups {
\r
131 uses network-instance-group;
\r
133 container forwarding-paths {
\r
134 list forwarding-path {
\r
135 key "forwarding-path-id";
\r
136 leaf forwarding-path-id {
\r
137 description "Generated by SDNC";
\r
141 uses forwarding-path-information;
\r
146 grouping service-status {
\r
147 container service-status {
\r
148 leaf response-code {
\r
151 leaf response-message {
\r
154 leaf final-indicator {
\r
157 leaf request-status {
\r
159 enum "synccomplete";
\r
160 enum "asynccomplete";
\r
161 enum "notifycomplete";
\r
165 description "value would one of possible request-actions; match the list in service-data oper-status";
\r
172 description "this is the svc-action from the incoming request";
\r
183 leaf response-timestamp {
\r
188 grouping service-operation-information {
\r
189 uses sdnc-request-header;
\r
190 uses request-information;
\r
191 uses service-information;
\r
192 uses service-request-input;
\r
194 grouping service-request-input {
\r
195 container service-request-input {
\r
196 leaf service-instance-name {
\r
199 container service-input-parameters {
\r
204 grouping service-topology {
\r
205 container service-topology {
\r
206 uses service-topology-identifier;
\r
207 uses onap-model-information;
\r
208 uses service-assignments;
\r
209 uses service-parameters;
\r
212 grouping service-topology-identifier {
\r
213 container service-topology-identifier {
\r
214 leaf service-instance-id {
\r
215 description "repeated";
\r
218 leaf service-type {
\r
219 description "tag labeled subscription-service-type in the service-information input";
\r
223 description "from MSO input on STO assign";
\r
226 leaf service-instance-name {
\r
227 description "optionally comes from service-request-input container or is assigned by sdn-c";
\r
230 leaf global-customer-id {
\r
235 grouping service-assignments {
\r
236 container service-assignments {
\r
239 grouping service-parameters {
\r
240 container service-parameters {
\r
241 list service-parameter {
\r
242 key "service-parameter-name";
\r
243 leaf service-parameter-name {
\r
246 leaf service-parameter-value {
\r
252 grouping service-level-oper-status {
\r
253 container service-level-oper-status {
\r
254 uses oper-status-data;
\r
257 grouping network-operation-information {
\r
258 uses sdnc-request-header;
\r
259 uses request-information;
\r
260 uses service-information;
\r
261 uses network-information;
\r
262 uses network-request-input;
\r
264 grouping network-information {
\r
265 container network-information {
\r
269 leaf network-type {
\r
272 leaf network-technology {
\r
275 leaf from-preload {
\r
276 description "Indicates if source is preload data";
\r
279 uses onap-model-information;
\r
282 grouping network-request-input {
\r
283 container network-request-input {
\r
284 leaf network-name {
\r
287 uses region-identifier;
\r
288 container network-input-parameters {
\r
291 leaf network-instance-group-id {
\r
292 description "When network has instance-group role in service model";
\r
297 grouping network-topology {
\r
298 container network-topology {
\r
299 uses network-topology-identifier-structure;
\r
300 uses region-identifier;
\r
301 uses onap-model-information;
\r
302 uses network-assignments;
\r
303 uses network-parameters;
\r
306 grouping network-topology-identifier-structure {
\r
307 container network-topology-identifier-structure {
\r
311 leaf network-name {
\r
314 leaf network-role {
\r
317 leaf network-type {
\r
320 leaf network-instance-group-id {
\r
321 description "When network is part of network instance-Group-data & instance Group in A&AI";
\r
324 leaf network-technology {
\r
327 leaf eipam-v4-address-plan {
\r
330 leaf eipam-v6-address-plan {
\r
336 leaf segmentation-id {
\r
339 container related-networks {
\r
340 uses related-network;
\r
344 grouping network-assignments {
\r
345 container network-assignments {
\r
348 grouping network-parameters {
\r
349 container network-parameters {
\r
350 list network-parameter {
\r
351 key "network-parameter-name";
\r
352 leaf network-parameter-name {
\r
355 leaf network-parameter-value {
\r
361 grouping network-instance-group {
\r
362 list network-instance-group {
\r
363 key "network-instance-group-id";
\r
364 leaf network-instance-group-id {
\r
365 description "Also a Key in Network Instance Group in A&AI";
\r
369 leaf network-instance-group-function {
\r
372 leaf service-instance-id {
\r
375 uses onap-model-information;
\r
376 container subnet-assignment-policy {
\r
378 description "Current valid values - unique, shared (default)";
\r
382 container vpn-binding-policy {
\r
392 leaf vpn-platform {
\r
395 leaf global-route-target {
\r
398 leaf route-target-role {
\r
402 container aggregate-route-policy {
\r
403 leaf aggregate-route-policy-name {
\r
406 leaf ipv4-aggregate-route-level {
\r
409 leaf ipv6-aggregate-route-level {
\r
413 uses aggregate-routes;
\r
415 leaf subnet-key-value {
\r
416 description "key-value provided to EIPAM when creating shared subnet";
\r
419 container networks {
\r
423 description "Index into network-topology-identifier structure";
\r
427 leaf neutron-network-id {
\r
428 description "Neutron-network-id assigned by PO/RO";
\r
435 leaf network-status {
\r
436 description "assigned, unassigned";
\r
439 container customer-bonding-requests {
\r
440 list customer-bonding-request {
\r
441 key "configuration-id";
\r
442 leaf configuration-id {
\r
443 description "e.g. vlan network receptor configuration id";
\r
452 grouping network-level-oper-status {
\r
453 container network-level-oper-status {
\r
454 uses oper-status-data;
\r
457 grouping pnf-operation-information {
\r
458 uses sdnc-request-header;
\r
459 uses request-information;
\r
460 uses service-information;
\r
462 uses pnf-request-input;
\r
464 grouping pnf-details {
\r
465 container pnf-details {
\r
467 description "pnfId*Identifier of this Pnf information element. CORRELATIONID = PNF-NAME (A&AI)";
\r
472 description "pnfType (template)*Type of Resource. NEW type: PNF (pre-defined in SDC)";
\r
478 uses onap-model-information;
\r
481 grouping pnf-request-input {
\r
482 container pnf-request-input {
\r
483 leaf request-version {
\r
484 description "keep this? e.g. 1702";
\r
490 uses region-identifier;
\r
491 container pnf-input-parameters {
\r
496 grouping pnf-topology {
\r
497 container pnf-topology {
\r
498 uses pnf-topology-identifier-structure;
\r
499 uses region-identifier;
\r
500 uses onap-model-information;
\r
501 container pnf-parameters-data {
\r
504 leaf sdnc-generated-cloud-resources {
\r
505 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
510 grouping pnf-topology-identifier-structure {
\r
511 container pnf-topology-identifier-structure {
\r
516 description "In preload tree, this label is used for the vf-module-type";
\r
520 description "optionally comes from pnf-request-input container or is assigned by sdn-c";
\r
525 grouping pnf-level-oper-status {
\r
526 container pnf-level-oper-status {
\r
527 uses oper-status-data;
\r
530 grouping vnf-operation-information {
\r
531 uses sdnc-request-header;
\r
532 uses request-information;
\r
533 uses service-information;
\r
534 uses vnf-information;
\r
535 uses vnf-request-input;
\r
536 uses license-information;
\r
538 grouping vnf-information {
\r
539 container vnf-information {
\r
549 uses onap-model-information;
\r
552 grouping vnf-request-input {
\r
553 container vnf-request-input {
\r
554 leaf request-version {
\r
560 uses region-identifier;
\r
561 container vnf-networks {
\r
563 key "network-role";
\r
564 uses vnf-network-data;
\r
567 list vnf-network-instance-group-ids {
\r
568 key "vnf-network-instance-group-id";
\r
569 leaf vnf-network-instance-group-id {
\r
570 description "List of vnf network-instance-group";
\r
574 container vnf-input-parameters {
\r
579 grouping vnf-topology {
\r
580 container vnf-topology {
\r
581 uses vnf-topology-identifier-structure;
\r
582 uses region-identifier;
\r
583 uses onap-model-information;
\r
584 uses vnf-resource-assignments;
\r
585 container vnf-parameters-data {
\r
588 leaf sdnc-generated-cloud-resources {
\r
589 description "Indicate if source is sdnc generated cloud param";
\r
594 grouping vnf-topology-identifier-structure {
\r
595 container vnf-topology-identifier-structure {
\r
600 description "In preload tree, this label is used for the vf-module-type";
\r
613 description "used in vnf naming";
\r
617 description "optionally comes from vnf-request-input container or is assigned by sdn-c";
\r
622 grouping vnf-resource-assignments {
\r
623 container vnf-resource-assignments {
\r
625 description "Orchestration status from AAI - to be set by SDNC";
\r
628 container availability-zones {
\r
629 leaf-list availability-zone {
\r
630 description "Openstack availability zone name or UUID";
\r
635 description "From the TOSCA data. Indicates the largest availability zone count needed by any vf-module in the VNF.";
\r
639 container vnf-networks {
\r
641 key "network-role";
\r
642 uses vnf-network-data;
\r
647 grouping vnf-network-data {
\r
648 leaf network-role {
\r
649 description "A Network Role to which a VNF must connect";
\r
652 leaf network-name {
\r
653 description "Unique Neutron UUID of an instance of the network role ";
\r
657 description "Unique Neutron UUID of an instance of the network role ";
\r
661 description "Unique Neutron UUID of an instance of the network role ";
\r
664 leaf contrail-network-fqdn {
\r
665 description "contrail network policy object";
\r
668 container subnets-data {
\r
670 key "sdnc-subnet-id";
\r
671 leaf sdnc-subnet-id {
\r
672 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
676 description "Subnet Role for the subnet";
\r
680 description "Populated for preload only";
\r
684 description "Should be ipv4 or ipv6";
\r
688 description "subnet UUID to be passed into the HEAT template";
\r
691 leaf dhcp-enabled {
\r
692 description "Indicator to use this subnet for DHCP ";
\r
698 leaf network-start-address {
\r
699 description "start-address of the subnet";
\r
700 type inet:ip-address;
\r
702 leaf gateway-address {
\r
703 description "subnet gateway address";
\r
704 type inet:ip-address;
\r
707 description "cidr mask";
\r
715 leaf segmentation-id {
\r
718 container related-networks {
\r
719 uses related-network;
\r
722 grouping vnf-level-oper-status {
\r
723 container vnf-level-oper-status {
\r
724 uses oper-status-data;
\r
727 grouping vf-module-operation-information {
\r
728 uses sdnc-request-header;
\r
729 uses request-information;
\r
730 uses service-information;
\r
731 uses vnf-information;
\r
732 uses vf-module-information;
\r
733 uses vf-module-request-input;
\r
735 grouping vf-module-information {
\r
736 container vf-module-information {
\r
737 leaf vf-module-id {
\r
740 leaf vf-module-type {
\r
743 leaf from-preload {
\r
744 description "Indicates if source is preload data";
\r
747 uses onap-model-information;
\r
750 grouping vf-module-request-input {
\r
751 container vf-module-request-input {
\r
752 leaf request-version {
\r
753 description "keep this?";
\r
756 leaf vf-module-name {
\r
759 uses region-identifier;
\r
760 container vf-module-input-parameters {
\r
765 grouping vf-module-topology {
\r
766 container vf-module-topology {
\r
767 uses vf-module-topology-identifier;
\r
768 uses region-identifier;
\r
769 uses onap-model-information;
\r
770 uses vf-module-assignments;
\r
771 container vf-module-parameters {
\r
774 leaf sdnc-generated-cloud-resources {
\r
775 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
780 grouping vf-module-topology-identifier {
\r
781 container vf-module-topology-identifier {
\r
782 leaf vf-module-id {
\r
783 description "vf-module id";
\r
786 leaf vf-module-name {
\r
787 description "vf-module-name";
\r
790 leaf vf-module-type {
\r
795 grouping vf-module-assignments {
\r
796 container vf-module-assignments {
\r
797 leaf vf-module-status {
\r
798 description "Orchestration status from AAI - to be set by SDNC";
\r
804 uses vm-topology-data;
\r
807 uses vlan-vnfc-instance-groups;
\r
808 container dhcp-subnet-assignments {
\r
809 list dhcp-subnet-assignment {
\r
810 key "neutron-subnet-id";
\r
811 leaf neutron-subnet-id {
\r
812 description "Same as subnet-id in subnet-data structure";
\r
815 leaf network-role {
\r
825 grouping vm-topology-data {
\r
830 uses onap-model-information;
\r
831 leaf nfc-naming-code {
\r
832 description "used in vm naming(draft 29: changed from nfc-code)";
\r
836 description "from tosca data on vfc";
\r
842 container vm-names {
\r
843 leaf-list vm-name {
\r
852 container vnfc-networks {
\r
853 uses vnfc-network-data;
\r
857 container vm-networks {
\r
859 key "network-role";
\r
860 uses vm-network-data;
\r
864 grouping vnfc-network-data {
\r
865 list vnfc-network-data {
\r
866 key "vnfc-network-role";
\r
867 leaf vnfc-network-role {
\r
874 uses connection-point;
\r
875 container vnfc-ports {
\r
877 key "vnfc-port-id";
\r
878 leaf vnfc-port-id {
\r
879 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
883 leaf common-sub-interface-role {
\r
884 description "If sub-interfaces have common interface role (network role)";
\r
887 container vnic-sub-interfaces {
\r
888 uses sub-interface-network-data;
\r
893 key "vnfc-subnet-role";
\r
894 leaf vnfc-subnet-role {
\r
895 description "Default value if subnet role is not defined.";
\r
899 list vnfc-ip-assignments {
\r
900 key "vnfc-address-family";
\r
901 leaf vnfc-address-family {
\r
902 description "indicates if this is IpV4 or IpV6";
\r
908 leaf vnfc-subnet-dhcp {
\r
909 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
915 leaf vnfc-subnet-ip-count {
\r
916 description "The number of IP addresses to be assigned per vnfc for this subnet role";
\r
919 list vnfc-subnet-ip {
\r
920 key "vnfc-ip-address";
\r
921 leaf vnfc-ip-address {
\r
922 description "Either IpV4 IP or IpV6 IP addresses should be present";
\r
923 type inet:ip-address;
\r
925 leaf vnfc-client-key {
\r
929 description "Capture what type of IP this is, if is virtual IP (AKA, floating IP) or Fixed IP. ";
\r
940 grouping vm-network-data {
\r
941 leaf network-role {
\r
942 description "network (identified by role) that this VM connects to. Should also be included in the vnf-networks for the containing VNF";
\r
946 leaf network-role-tag {
\r
949 container network-information-items {
\r
950 list network-information-item {
\r
953 description "Use ipv4 or ipv6";
\r
957 description "Indicator to use DHCP on this network for this VM";
\r
964 description "The number of ip addresses to be assigned per vm for this network role";
\r
967 container network-ips {
\r
968 leaf-list network-ip {
\r
969 description "List of assigned ip addresses of type ip-version on a network";
\r
976 container mac-addresses {
\r
977 leaf-list mac-address {
\r
978 description "List of network assignments for this vm-type";
\r
983 container floating-ips {
\r
984 leaf-list floating-ip-v4 {
\r
985 description "Floating ipv4 for VMs of a given type on this network";
\r
986 type inet:ip-address;
\r
989 leaf-list floating-ip-v6 {
\r
990 description "Floating ipv6 for VMs of a given type on this network";
\r
991 type inet:ipv6-address;
\r
995 container interface-route-prefixes {
\r
996 leaf-list interface-route-prefix {
\r
997 description "ordered-by: user";
\r
1002 container sriov-parameters {
\r
1003 container heat-vlan-filters {
\r
1004 leaf-list heat-vlan-filter {
\r
1009 container application-tags {
\r
1010 container c-tags {
\r
1016 container s-tags {
\r
1027 leaf segmentation-id {
\r
1030 container related-networks {
\r
1031 uses related-network;
\r
1034 grouping vf-module-level-oper-status {
\r
1035 container vf-module-level-oper-status {
\r
1036 uses oper-status-data;
\r
1039 grouping allotted-resource-info {
\r
1040 leaf allotted-resource-id {
\r
1043 leaf allotted-resource-type {
\r
1044 description "Not an enum, but expected values are contrail-route and security-zone.";
\r
1047 leaf allotted-resource-pointer {
\r
1048 description "Pointer to the allotted-resources topology";
\r
1052 grouping forwarding-path-operation-information {
\r
1053 uses sdnc-request-header;
\r
1054 uses request-information;
\r
1055 uses service-information;
\r
1056 uses forwarding-path-request-input;
\r
1058 grouping forwarding-path-request-input {
\r
1059 container forwarding-path-request-input {
\r
1060 list forwarding-paths {
\r
1061 key "forwarding-path-name";
\r
1062 leaf forwarding-path-name {
\r
1063 description "Forwarding-path-name from tosca-model. ";
\r
1067 uses onap-model-information;
\r
1071 grouping forwarding-path-information {
\r
1072 leaf forwarding-path-name {
\r
1073 description "Fowarding-path name from TOSCA model, or name generated by SDNC";
\r
1076 leaf forwarding-path-type {
\r
1077 description "Based on MySQL Forwarding_Path tables path_type value from related TOSCA model";
\r
1078 type enumeration {
\r
1083 uses onap-model-information;
\r
1084 container service-paths {
\r
1085 list service-path {
\r
1086 key "service-path-instance-id";
\r
1087 uses service-path-information;
\r
1091 grouping service-path-information {
\r
1092 leaf service-path-instance-id {
\r
1093 description "Service path instance ID generated by SDNC. Identifies a service-path-instance within a forwarding-path definition";
\r
1096 leaf service-path-instance-name {
\r
1097 description "A unique name generated by SDNC ( forwarding-path-name + service-path-instance-id )";
\r
1101 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
1105 key "service-instance-id";
\r
1106 leaf service-instance-id {
\r
1107 description "service-instance-id of each service-instance in the service-path-instance";
\r
1110 leaf service-path-sequence-id {
\r
1111 description "e.g. S1S2S3S5seq id=1 S1-S2seq id=2 S2S3seq id=3 S3S5Incremental integer value";
\r
1116 key "vnf-instance-id";
\r
1117 uses vnf-path-information;
\r
1122 grouping vnf-path-information {
\r
1123 leaf vnf-instance-id {
\r
1124 description "VNF instance ID in the path";
\r
1127 leaf vnf-path-sequence-id {
\r
1128 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
1131 leaf left-network-name {
\r
1132 description "Every VNF instance in the path is connected to one or two VNFs.";
\r
1135 leaf left-network-role {
\r
1138 leaf right-network-name {
\r
1141 leaf right-network-role {
\r
1144 container vf-module-instance {
\r
1145 leaf vf-module-id {
\r
1148 leaf vf-module-name {
\r
1153 grouping forwarding-path-level-oper-status {
\r
1154 container forwarding-path-level-oper-status {
\r
1155 uses oper-status-data;
\r
1158 grouping configuration-info {
\r
1159 leaf configuration-id {
\r
1162 leaf configuration-type {
\r
1163 description "Not an enum, but expected values are port-mirror-configuration, , vlan-network-receptor";
\r
1166 leaf configuration-sub-type {
\r
1167 description "Not an enum, but expected values are vprobe and pprobe";
\r
1170 leaf configuration-topology-link {
\r
1171 description "Pointer to the configurations topology";
\r
1175 grouping vnfc-instance-group {
\r
1176 list vnfc-instance-group {
\r
1177 key "instance-group-role nfc-naming-code configuration-id";
\r
1178 leaf instance-group-role {
\r
1179 description "i.e.TSBC_VNFC_group";
\r
1183 leaf nfc-naming-code {
\r
1184 description "Set to nfc-naming-code from A&AI";
\r
1188 leaf configuration-id {
\r
1193 description " port-mirror-source or port-mirror-dest";
\r
1196 uses vnfc-objects;
\r
1199 grouping vnfc-objects {
\r
1200 container vnfc-objects {
\r
1201 list vnfc-object {
\r
1207 description "Vnfc name as key in A&AI";
\r
1216 leaf vserver-name {
\r
1224 key "vnic-port-name";
\r
1225 leaf vnic-port-name {
\r
1228 leaf vnic-port-id {
\r
1231 container capacity {
\r
1232 leaf vnic-capacity {
\r
1235 leaf used-capacity {
\r
1236 description "Updated for destination port when source port is mapped/unmapped.";
\r
1240 container vnic-ip-addresses {
\r
1241 uses ip-addresses;
\r
1253 description "Vnfc name as key in A&AI";
\r
1256 leaf vserver-name {
\r
1269 key "vnic-port-name";
\r
1270 leaf vnic-port-name {
\r
1273 leaf vnic-port-id {
\r
1276 uses sub-interfaces;
\r
1280 grouping sub-interfaces {
\r
1281 container sub-interfaces {
\r
1282 list sub-interface {
\r
1283 key "sub-interface-port-name";
\r
1284 leaf sub-interface-port-name {
\r
1287 leaf sub-interface-port-id {
\r
1290 container sub-interface-ip-addresses {
\r
1291 uses ip-addresses;
\r
1294 container sub-interface-network {
\r
1295 leaf network-name {
\r
1302 leaf sub-interface-status {
\r
1303 description "NULL, unassigned, assigned";
\r
1309 grouping vlan-tags {
\r
1310 container vlan-tags {
\r
1311 leaf vlan-interface {
\r
1312 description "A&AI Key";
\r
1315 leaf upper-tag-id {
\r
1318 leaf lower-tag-id {
\r
1326 grouping vlan-vnfc-instance-groups {
\r
1327 container vlan-vnfc-instance-groups {
\r
1328 list vlan-vnfc-instance-group {
\r
1329 key "instance-group-id";
\r
1330 leaf instance-group-id {
\r
1331 description "A&AI ID";
\r
1335 leaf instance-group-function {
\r
1353 grouping vnic-groups {
\r
1354 container vnic-groups {
\r
1356 key "vnic-interface-role";
\r
1357 leaf vnic-interface-role {
\r
1358 description "Same as network-role of network where vnic is connected";
\r
1362 leaf network-instance-group-function {
\r
1363 description "network-instance-Group-function for network collection where vnics with vnic-interface-role will connect";
\r
1366 leaf vlan-assignment-policy-name {
\r
1367 description "Policy name in ASDC model & policy definition in Policy Engine";
\r
1370 leaf vlan-tag-index-next {
\r
1371 description "Next tag to be assigned";
\r
1374 container vlan-common-ip-addresses {
\r
1375 uses ip-addresses;
\r
1377 container vlan-vnics {
\r
1379 key "vnic-port-id";
\r
1380 leaf vnic-port-id {
\r
1384 container vnic-sub-interfaces {
\r
1385 uses sub-interface-network-data;
\r
1392 grouping vnf-network-collection {
\r
1393 list vnf-network-collection {
\r
1394 key "network-instance-group-function";
\r
1395 leaf network-instance-group-function {
\r
1396 description "Network Instance-Group function in A&AI";
\r
1400 leaf network-instance-group-id {
\r
1401 description "Network Instance-Group id in A&AI";
\r
1404 leaf network-collection-service-instance-id {
\r
1405 description "Service-instance-id of service that created the network collection";
\r
1408 leaf network-collection-customization-uuid {
\r
1409 description "network-collection-customization-uuid stored in Network IsntanceGroup.customization-uuid in A&AI";
\r
1412 container networks {
\r
1416 description "Index into network-topology-identifier structure";
\r
1420 leaf neutron-network-id {
\r
1421 description "Neutron-network-id assigned by PO/RO";
\r
1426 container vnf-floating-ip {
\r
1427 uses ip-addresses;
\r
1431 grouping vnf-sub-interface-group {
\r
1432 list vnf-sub-interface-group {
\r
1433 key "vnfc-instance-group-function network-instance-group-function parent-port-role";
\r
1434 leaf vnfc-instance-group-function {
\r
1438 leaf network-instance-group-function {
\r
1442 leaf parent-port-role {
\r
1447 container customer-bonding-requests {
\r
1448 list customer-bonding-request {
\r
1449 key "configuration-id";
\r
1450 leaf configuration-id {
\r
1451 description "e.g. vlan network receptor configuration id";
\r
1458 grouping sub-interface-network-data {
\r
1459 list sub-interface-network-data {
\r
1462 description "Subinterface network id (UUID in A&AI)";
\r
1466 leaf neutron-network-id {
\r
1467 description "Neutron network id assigned by PO/RP";
\r
1470 leaf network-name {
\r
1471 description "Subinterface network name";
\r
1474 leaf vlan-tag-id {
\r
1475 description "Vlan tag assigned to subinterface port";
\r
1478 leaf network-role {
\r
1479 description "e.g. untrusted ";
\r
1482 leaf network-role-tag {
\r
1483 description "Assuming HEAT template network role tag parameter - not used";
\r
1486 container network-information-items {
\r
1487 list network-information-item {
\r
1490 description "Use ipv4 or ipv6";
\r
1494 description "Indicator to use DHCP on this network for this VM - set to N for Vlan tagging";
\r
1495 type enumeration {
\r
1501 description "The number of ip addresses to be assigned per vm for this network role";
\r
1504 container network-ips {
\r
1505 leaf-list network-ip {
\r
1506 description "List of assigned ip addresses of type ip-version on a network.";
\r
1507 type inet:ip-address;
\r
1513 container floating-ips {
\r
1514 leaf-list floating-ip-v4 {
\r
1515 description "Floating ipv4 for VMs of a given type on this network";
\r
1516 type inet:ip-address;
\r
1519 leaf-list floating-ip-v6 {
\r
1520 description "Floating ipv6 for VMs of a given type on this network";
\r
1521 type inet:ipv6-address;
\r
1527 grouping vnf-cloud-param {
\r
1528 leaf service-instance-id {
\r
1531 leaf service-instance-name {
\r
1544 key "vf-module-id";
\r
1545 leaf vf-module-id {
\r
1552 grouping vnf-get-resource-request-input-data {
\r
1559 key "vf-module-id";
\r
1560 leaf vf-module-id {
\r
1566 grouping license-information {
\r
1567 container license-information {
\r
1568 list entitlement-pool-list {
\r
1569 key "entitlement-pool-uuid action";
\r
1570 leaf entitlement-pool-uuid {
\r
1578 leaf entitlement-pool-invariant-uuid {
\r
1581 leaf entitlement-uuid {
\r
1582 description "assigned by ALTS";
\r
1586 list license-key-group-list {
\r
1587 key "license-key-group-uuid action";
\r
1588 leaf license-key-group-uuid {
\r
1596 leaf license-key-group-invariant-uuid {
\r
1599 leaf license-key {
\r
1600 description "assigned by ALTS";
\r
1603 leaf license-uuid {
\r
1604 description "assigned by ALTS";
\r
1610 grouping related-network {
\r
1611 list related-network {
\r
1614 description "Key to l3-network object";
\r
1617 leaf network-role {
\r
1623 grouping connection-point {
\r
1624 container connection-point {
\r
1625 leaf connection-point-id {
\r
1626 description "Key to CP object in A&AI";
\r
1630 description "port-index when multiple CPs connect to same network. Default zero (0)";
\r
1636 description "Key to vlan-tag uuid object in A&AI Generated by vlan mS";
\r
1639 leaf vlan-tag-id {
\r
1642 leaf vlan-tag-description {
\r
1646 description "Inner/Outer roles";
\r
1652 grouping aggregate-routes {
\r
1653 list aggregate-routes {
\r
1656 description "Unique id";
\r
1659 leaf start-address {
\r
1660 type inet:ip-address;
\r
1666 description "Use values 4 or 6.";
\r
1671 grouping pnf-information {
\r
1672 container pnf-information {
\r
1674 description "Key for A&AI query";
\r
1680 uses onap-model-information;
\r
1683 grouping contrail-route-operation-information {
\r
1684 uses sdnc-request-header;
\r
1685 uses request-information;
\r
1686 uses service-information;
\r
1687 uses allotted-resource-information;
\r
1688 uses contrail-route-request-input;
\r
1690 grouping contrail-route-request-input {
\r
1691 container contrail-route-request-input {
\r
1692 container source-network {
\r
1693 uses network-info;
\r
1695 container dest-network {
\r
1696 uses network-info;
\r
1698 container contrail-applied-service-info {
\r
1699 leaf service-instance-id {
\r
1700 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
1703 leaf contrail-fqdn {
\r
1704 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
1708 container contrail-route-input-parameters {
\r
1713 grouping network-info {
\r
1717 leaf network-role {
\r
1721 grouping contrail-route-topology {
\r
1722 container contrail-route-topology {
\r
1723 uses allotted-resource-identifiers;
\r
1724 uses onap-model-information;
\r
1725 uses contrail-route-assignments;
\r
1726 container contrail-route-parameters {
\r
1731 grouping contrail-route-assignments {
\r
1732 container contrail-route-assignments {
\r
1734 description "The Contrail fq-name of the network policy";
\r
1737 leaf contrail-id {
\r
1738 description "The ID assigned by Contrail to the network-policy (one for one with the fq-name)";
\r
1741 container source-network {
\r
1742 uses network-info;
\r
1744 container dest-network {
\r
1745 uses network-info;
\r
1747 container contrail-applied-service {
\r
1748 leaf service-instance-id {
\r
1749 description "The service-instance-id of the vnf from which the contrail applied service is coming";
\r
1753 description "The vnf representing the contrail applied service";
\r
1756 leaf contrail-fqdn {
\r
1757 description "This is the fq-name of the Contrail service instance through which the route is passing.";
\r
1762 description "Contrail-assigned vlan-tag to the vipr vm interface for this route.";
\r
1767 grouping security-zone-operation-information {
\r
1768 uses sdnc-request-header;
\r
1769 uses request-information;
\r
1770 uses service-information;
\r
1771 uses allotted-resource-information;
\r
1772 uses security-zone-request-input;
\r
1774 grouping security-zone-request-input {
\r
1775 container security-zone-request-input {
\r
1779 leaf trusted-network-role {
\r
1780 description "In the case of vIPR, this is the landing networks network-role; used in naming";
\r
1783 leaf untrusted-network-role {
\r
1784 description "In the case of vIPR, this is the tenant oam networks network-role; used in naming";
\r
1787 container security-zone-input-parameters {
\r
1792 grouping security-zone-topology {
\r
1793 container security-zone-topology {
\r
1794 uses allotted-resource-identifiers;
\r
1795 uses onap-model-information;
\r
1796 uses security-zone-assignments;
\r
1797 container security-zone-parameters {
\r
1802 grouping security-zone-assignments {
\r
1803 container security-zone-assignments {
\r
1804 leaf trusted-network-role {
\r
1805 description "In the case of vIPR, this is the landing networks network-role; used in naming";
\r
1808 leaf security-zone-name-trusted {
\r
1811 leaf untrusted-network-role {
\r
1812 description "In the case of vIPR, this is the tenant oam networks network-role; used in naming";
\r
1815 leaf security-zone-name-untrusted {
\r
1818 leaf security-zone-service-instance-id {
\r
1819 description "Will be the same as the parent-service-instance-id";
\r
1822 leaf security-zone-vnf-id {
\r
1823 description "Selected by SDNC from the security-zone-service-instance-id";
\r
1831 grouping port-mirror-topology-operation-information {
\r
1832 uses sdnc-request-header;
\r
1833 uses request-information;
\r
1834 uses service-information;
\r
1835 uses configuration-information;
\r
1836 uses port-mirror-configuration-request-input;
\r
1838 grouping port-mirror-configuration-request-input {
\r
1839 container port-mirror-configuration-request-input {
\r
1840 container source-port {
\r
1842 leaf source-port-id {
\r
1843 description "needed for srv-action=disable/enable";
\r
1847 container dest-port {
\r
1850 uses region-identifier;
\r
1851 container port-mirror-configuration-input-parameters {
\r
1856 grouping port-info {
\r
1857 leaf service-instance-id {
\r
1858 description "May not be need.";
\r
1861 uses pnf-information;
\r
1862 uses vnf-information;
\r
1864 grouping port-mirror-configuration-topology {
\r
1865 container port-mirror-configuration-topology {
\r
1866 uses configuration-identifiers;
\r
1867 uses onap-model-information;
\r
1868 uses port-mirror-configuration-assignments;
\r
1869 container port-mirror-configuration-parameters {
\r
1874 grouping port-mirror-configuration-assignments {
\r
1875 container port-mirror-configuration-assignments {
\r
1876 container contrail-vmi-params {
\r
1879 leaf vnics-group-id {
\r
1882 leaf owning-entity {
\r
1885 leaf tenant-context {
\r
1886 description "From tenant object in A&AI";
\r
1890 description "Tenant name from A&AI for source VNF";
\r
1894 description "tenant-id from A&AI for source VNF";
\r
1897 leaf dest-tenant {
\r
1898 description "Tenant name from A&AI for destination VNF";
\r
1901 leaf dest-tenant-id {
\r
1902 description "tenant-id from A&AI for destination VNF";
\r
1905 leaf cloud-region-id {
\r
1908 leaf cloud-owner {
\r
1911 leaf dest-network-fqdn {
\r
1914 leaf source-network-fqdn {
\r
1917 leaf source-capacity {
\r
1918 description "Source port pps (packets per second) rating from tosca model";
\r
1921 leaf source-vnf-id {
\r
1924 leaf dest-vnf-id {
\r
1925 description "For vProbe";
\r
1928 leaf dest-pnf-name {
\r
1929 description "For pProbe";
\r
1932 leaf dest-p-interface {
\r
1933 description "For pProbe; from policy manager";
\r
1936 leaf dest-pnf-port-policy-name {
\r
1937 description "For pProbe; from tosca model";
\r
1941 description "vprobe or pprobe; derived from configuration-information.configuration-sub-type";
\r
1944 leaf route-allotted-resource-id {
\r
1945 description "For vProbe";
\r
1948 container source-vnfc-instance-group-id {
\r
1949 leaf service-instance-id {
\r
1952 leaf nfc-naming-code {
\r
1955 leaf instance-group-role {
\r
1958 leaf configuration-id {
\r
1962 container dest-vnfc-instance-group-id {
\r
1963 leaf service-instance-id {
\r
1966 leaf nfc-naming-code {
\r
1969 leaf instance-group-role {
\r
1972 leaf configuration-id {
\r
1976 container source-to-dest-maps {
\r
1977 list source-to-dest-map {
\r
1978 key "source-port-id";
\r
1979 leaf source-port-id {
\r
1983 leaf source-port-name {
\r
1986 leaf source-vserver-id {
\r
1989 leaf dest-vserver-id {
\r
1992 leaf dest-port-id {
\r
1995 leaf dest-port-name {
\r
2001 container dest-ip-addresses {
\r
2002 uses ip-addresses;
\r
2008 grouping gc-topology-operation-information {
\r
2009 uses sdnc-request-header;
\r
2010 uses request-information;
\r
2011 uses service-information;
\r
2012 uses configuration-information;
\r
2013 uses gc-request-input;
\r
2015 grouping gc-request-input {
\r
2016 container gc-request-input {
\r
2020 leaf vf-module-id {
\r
2021 description "This is mandatory in case of rebuild";
\r
2024 container input-parameters {
\r
2028 description "Value will indicate what to rebuild";
\r
2031 list configuration-ids {
\r
2032 key "configuration-id";
\r
2033 leaf configuration-id {
\r
2039 grouping vnr-parameters {
\r
2040 container vnr-parameters {
\r
2044 leaf vf-module-id {
\r
2045 description "This is mandatory in case of rebuild";
\r
2048 leaf vnf-service-instance-id {
\r
2051 leaf network-collection-service-instance-id {
\r
2052 description "service instance id that created network-collection";
\r
2055 leaf network-instance-group-id {
\r
2061 leaf vnfc-instance-group-function {
\r
2064 leaf network-instance-group-function {
\r
2067 leaf parent-port-role {
\r
2070 leaf upper-tag-id {
\r
2073 leaf lower-tag-id {
\r
2078 grouping tunnelxconn-operation-information {
\r
2079 uses sdnc-request-header;
\r
2080 uses request-information;
\r
2081 uses service-information;
\r
2082 uses allotted-resource-information;
\r
2083 uses tunnelxconn-request-input;
\r
2085 grouping tunnelxconn-request-input {
\r
2087 container tunnelxconn-request-input {
\r
2088 leaf brg-wan-mac-address {
\r
2093 grouping tunnelxconn-topology {
\r
2094 container tunnelxconn-topology {
\r
2095 uses allotted-resource-identifiers;
\r
2096 uses onap-model-information;
\r
2097 uses tunnelxconn-assignments;
\r
2098 container tunnelxconn-parameters {
\r
2103 grouping tunnelxconn-assignments {
\r
2104 container tunnelxconn-assignments {
\r
2106 description "The Network Controller will assign a VNI value from the associated vGMUX VNI pool";
\r
2109 leaf vgmux-bearer-ip {
\r
2110 description "The Network Controller will look up the vgmux bearer ip from the vgmux vf module";
\r
2111 type inet:ip-address;
\r
2113 leaf vgmux-lan-ip {
\r
2114 description "The Network Controller will look up the vgmux lan ip from the vgmux vg module";
\r
2115 type inet:ip-address;
\r
2118 description "The Network Controller will assign the VG IP address from local inventory";
\r
2119 type inet:ip-address;
\r
2123 grouping brg-operation-information {
\r
2124 uses sdnc-request-header;
\r
2125 uses request-information;
\r
2126 uses service-information;
\r
2127 uses allotted-resource-information;
\r
2128 uses brg-request-input;
\r
2130 grouping brg-request-input {
\r
2131 container brg-request-input {
\r
2132 leaf vgmux-bearer-ip {
\r
2133 type inet:ip-address;
\r
2138 leaf brg-wan-mac-address {
\r
2143 grouping brg-topology {
\r
2144 container brg-topology {
\r
2145 uses allotted-resource-identifiers;
\r
2146 uses onap-model-information;
\r
2147 uses brg-assignments;
\r
2148 container brg-parameters {
\r
2153 grouping brg-assignments {
\r
2154 container brg-assignments {
\r
2155 leaf vbrg-wan-ip {
\r
2156 type inet:ip-address;
\r
2160 grouping connection-attachment-operation-information {
\r
2161 uses sdnc-request-header;
\r
2162 uses request-information;
\r
2163 uses service-information;
\r
2164 uses allotted-resource-information;
\r
2165 uses connection-attachment-request-input;
\r
2168 grouping connection-attachment-request-input {
\r
2169 container connection-attachment-request-input {
\r
2174 grouping connection-attachment-topology {
\r
2175 container connection-attachment-topology {
\r
2176 uses allotted-resource-identifiers;
\r
2177 uses onap-model-information;
\r
2178 uses connection-attachment-assignments;
\r
2179 container connection-attachment-parameters {
\r
2185 grouping connection-attachment-assignments {
\r
2186 container connection-attachment-assignments {
\r
2190 grouping vnf-vnr-rebuild-data {
\r
2191 container vnf-vnr-rebuild-data {
\r
2195 leaf vnf-service-instance-id {
\r
2199 key "configuration-id";
\r
2200 leaf configuration-id {
\r
2203 leaf network-instance-group-id {
\r
2209 leaf vnfc-instance-group-function {
\r
2212 leaf network-instance-group-function {
\r
2215 leaf parent-port-role {
\r
2218 leaf upper-tag-id {
\r
2221 leaf lower-tag-id {
\r
2227 grouping allotted-resource-information {
\r
2228 container allotted-resource-information {
\r
2229 leaf allotted-resource-id {
\r
2232 leaf allotted-resource-type {
\r
2233 description "Not an enum, but expected values are contrail-route and security-zone.";
\r
2236 leaf parent-service-instance-id {
\r
2237 description "Service-instance-id of the parent service to which this allotted resource belongs.";
\r
2240 uses onap-model-information;
\r
2243 grouping allotted-resource-identifiers {
\r
2244 container allotted-resource-identifiers {
\r
2245 leaf allotted-resource-id {
\r
2248 leaf allotted-resource-name {
\r
2249 description "For a contrail-route, the network policy name.";
\r
2252 leaf allotted-resource-type {
\r
2253 description "(Added in draft 32)Expected to be contrail-route or security-zone.";
\r
2256 leaf consuming-service-instance-id {
\r
2257 description "The service-instance-id of the consuming service of this allotted resource";
\r
2260 leaf parent-service-instance-id {
\r
2261 description "Service-instance-id of the parent service to which this allotted resource belongs.";
\r
2266 grouping allotted-resource-oper-status {
\r
2267 container allotted-resource-oper-status {
\r
2268 uses oper-status-data;
\r
2271 grouping allotted-resource-status {
\r
2272 container allotted-resource-status {
\r
2273 leaf response-code {
\r
2276 leaf response-message {
\r
2279 leaf final-indicator {
\r
2282 leaf request-status {
\r
2283 type enumeration {
\r
2284 enum "synccomplete";
\r
2285 enum "asynccomplete";
\r
2286 enum "notifycomplete";
\r
2290 description "value would one of possible request-actions; match the list in service-data oper-status";
\r
2297 description "this is the svc-action from the incoming request";
\r
2298 type enumeration {
\r
2304 enum "deactivate";
\r
2307 leaf response-timestamp {
\r
2312 grouping configuration-information {
\r
2313 container configuration-information {
\r
2314 leaf configuration-id {
\r
2317 leaf configuration-name {
\r
2320 leaf configuration-type {
\r
2321 description "Not an enum, but expected values are port-mirror-configuration, vlan-network-receptor";
\r
2324 leaf configuration-sub-type {
\r
2325 description "e.g. vprobe and pprobe when configuration-type=port-mirror-configuration";
\r
2328 uses onap-model-information;
\r
2331 grouping configuration-identifiers {
\r
2332 container configuration-identifiers {
\r
2333 leaf configuration-id {
\r
2336 leaf configuration-name {
\r
2339 leaf configuration-type {
\r
2340 description "Not an enum, but expected values are port-mirror-configuration.";
\r
2343 leaf configuration-sub-type {
\r
2344 description " vprobe and pprobe";
\r
2347 leaf parent-service-instance-id {
\r
2348 description "Service-instance-id of the parent service to which this resource belongs.";
\r
2353 grouping configuration-oper-status {
\r
2354 container configuration-oper-status {
\r
2355 uses oper-status-data;
\r
2358 grouping configuration-status {
\r
2359 container configuration-status {
\r
2360 leaf response-code {
\r
2363 leaf response-message {
\r
2366 leaf final-indicator {
\r
2369 leaf request-status {
\r
2370 type enumeration {
\r
2371 enum "synccomplete";
\r
2372 enum "asynccomplete";
\r
2373 enum "notifycomplete";
\r
2377 description "value would one of possible request-actions; match the list in service-data oper-status";
\r
2384 description "this is the svc-action from the incoming request";
\r
2385 type enumeration {
\r
2393 enum "deactivate";
\r
2396 leaf response-timestamp {
\r
2401 grouping topology-response-common {
\r
2402 leaf svc-request-id {
\r
2403 description "the request id from the request message for which this is the responseKeep as M";
\r
2406 leaf response-code {
\r
2407 description "a success code or an defined error codeKeep as M";
\r
2410 leaf response-message {
\r
2411 description "message included for error code";
\r
2414 leaf ack-final-indicator {
\r
2415 description "Expected to be Y or N.";
\r
2419 grouping sdnc-request-header {
\r
2420 container sdnc-request-header {
\r
2421 leaf svc-request-id {
\r
2422 description "Uniquely generated by calling system (e.g. MSO or SDN-GP)";
\r
2426 description "This is the rpcAction";
\r
2427 type enumeration {
\r
2432 enum "changeassign";
\r
2433 enum "changedelete";
\r
2435 enum "deactivate";
\r
2441 enum "reoptimize";
\r
2445 leaf svc-notification-url {
\r
2446 description "Contains URL for asynchronous response";
\r
2451 grouping request-information {
\r
2452 container request-information {
\r
2454 description "Request ID generated upstream of MSO";
\r
2457 leaf request-action {
\r
2458 description "still need to work Disconnect";
\r
2459 type enumeration {
\r
2460 enum "CreateNetworkInstance";
\r
2461 enum "ActivateNetworkInstance";
\r
2462 enum "DeActivateNetworkInstance";
\r
2463 enum "CreateServiceInstance";
\r
2464 enum "DeleteServiceInstance";
\r
2465 enum "DeleteNetworkInstance";
\r
2466 enum "CreateVnfInstance";
\r
2467 enum "ActivateVnfInstance";
\r
2468 enum "DeleteVnfInstance";
\r
2469 enum "CreatePnfInstance";
\r
2470 enum "ActivatePnfInstance";
\r
2471 enum "DeletePnfInstance";
\r
2472 enum "CreateVfModuleInstance";
\r
2473 enum "ActivateVfModuleInstance";
\r
2474 enum "DeleteVfModuleInstance";
\r
2475 enum "CreateContrailRouteInstance";
\r
2476 enum "DeleteContrailRouteInstance";
\r
2477 enum "CreateSecurityZoneInstance";
\r
2478 enum "DeleteSecurityZoneInstance";
\r
2479 enum "ActivateDCINetworkInstance";
\r
2480 enum "DeActivateDCINetworkInstance";
\r
2481 enum "CreateTunnelXConnInstance";
\r
2482 enum "DeleteTunnelXConnInstance";
\r
2483 enum "CreateBRGInstance";
\r
2484 enum "DeleteBRGInstance";
\r
2485 enum "CreateSOTNConnectivityInstance";
\r
2486 enum "ActivateSOTNConnectivityInstance";
\r
2487 enum "DeactivateSOTNConnectivityInstance";
\r
2488 enum "DeleteSOTNConnectivityInstance";
\r
2489 enum "CreateSOTNAttachmentInstance";
\r
2490 enum "ActivateSOTNAttachmentInstance";
\r
2491 enum "DeactivateSOTNAttachmentInstance";
\r
2492 enum "DeleteSOTNAttachmentInstance";
\r
2493 enum "CreateSiteInstance";
\r
2494 enum "ActivateSiteInstance";
\r
2495 enum "DeactivateSiteInstance";
\r
2496 enum "DeleteSiteInstance";
\r
2497 enum "CreatePortMirrorConfigurationInstance";
\r
2498 enum "DeletePortMirrorConfigurationInstance";
\r
2499 enum "ChangePortMirrorConfigurationInstance";
\r
2500 enum "CreateGenericConfigurationInstance";
\r
2501 enum "RebuildGenericConfigurationInstance";
\r
2502 enum "DeleteGenericConfigurationInstance";
\r
2503 enum "PreloadVfModuleRequest";
\r
2504 enum "DeletePreloadVfModuleRequest";
\r
2505 enum "PreloadNetworkRequest";
\r
2506 enum "DeletePreloadNetworkRequest";
\r
2507 enum "CreateForwardingPathInstance";
\r
2508 enum "DeleteForwardingPathInstance";
\r
2509 enum "UpdateForwardingPathInstance";
\r
2510 enum "CreateSDWANDeviceInstance";
\r
2511 enum "ActivateSDWANDeviceInstance";
\r
2512 enum "DeactivateSDWANDeviceInstance";
\r
2513 enum "DeleteSDWANDeviceInstance";
\r
2514 enum "CreateSDWANPortInstance";
\r
2515 enum "ActivateSDWANPortInstance";
\r
2516 enum "DeactivateSDWANPortInstance";
\r
2517 enum "DeleteSDWANPortInstance";
\r
2518 enum "ReoptimizeSOTNInstance";
\r
2519 enum "CreateSDWANLanPortInstance";
\r
2520 enum "ActivateSDWANLanPortInstance";
\r
2521 enum "DeactivateSDWANLanPortInstance";
\r
2522 enum "DeleteSDWANLanPortInstance";
\r
2523 enum "CreateSDWANVpnInstance";
\r
2524 enum "ActivateSDWANVpnInstance";
\r
2525 enum "DeactivateSDWANVpnInstance";
\r
2526 enum "DeleteSDWANVpnInstance";
\r
2527 enum "CreateSDWANSiteInstance";
\r
2528 enum "ActivateSDWANSiteInstance";
\r
2529 enum "DeactivateSDWANSiteInstance";
\r
2530 enum "DeleteSDWANSiteInstance";
\r
2531 enum "SdwanBandwidthChange";
\r
2532 enum "CreateAccessConnectivityInstance";
\r
2533 enum "DeleteAccessConnectivityInstance";
\r
2534 enum "CreateInternetProfileInstance";
\r
2535 enum "ChangeInternetProfileInstance";
\r
2536 enum "DeleteInternetProfileInstance";
\r
2537 enum "CreateSOTNUnderlayInstance";
\r
2538 enum "ActivateSOTNUnderlayInstance";
\r
2539 enum "DeactivateSOTNUnderlayInstance";
\r
2540 enum "DeleteSOTNUnderlayInstance";
\r
2541 enum "CreateSOTNUniInstance";
\r
2542 enum "ActivateSOTNUniInstance";
\r
2543 enum "DeactivateSOTNUniInstance";
\r
2544 enum "DeleteSOTNUniInstance";
\r
2545 enum "CreateSOTNL2VpnInstance";
\r
2546 enum "ActivateSOTNL2VpnInstance";
\r
2547 enum "DeactivateSOTNL2VpnInstance";
\r
2548 enum "DeleteSOTNL2VpnInstance";
\r
2554 leaf notification-url {
\r
2557 leaf order-number {
\r
2560 leaf order-version {
\r
2565 grouping service-information {
\r
2566 container service-information {
\r
2568 description "This maps to the product-family-id in A&AI";
\r
2571 leaf subscription-service-type {
\r
2572 description "used to reference a&ai subscription-service-type. For example, we show as vIPR-ATM in example.";
\r
2575 uses onap-model-information;
\r
2576 leaf service-instance-id {
\r
2579 leaf global-customer-id {
\r
2580 description "need for put of data to AnAI (MSO provides)";
\r
2583 leaf subscriber-name {
\r
2584 description "Would not be expected for vIPR-ATM or mobility services.";
\r
2589 grouping onap-model-information {
\r
2590 container onap-model-information {
\r
2591 leaf model-invariant-uuid {
\r
2592 description "identifies the invariant uuid for this service or resource";
\r
2595 leaf model-customization-uuid {
\r
2596 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
2600 description "identifies the uuid for this service or resource, which is version specific";
\r
2603 leaf model-version {
\r
2611 grouping region-identifier {
\r
2615 leaf aic-cloud-region {
\r
2616 description "The AIC cloud region which maps to contrail versions";
\r
2619 leaf cloud-owner {
\r
2620 description "The cloud owner provided by the caller";
\r
2624 description "Not expected to be used";
\r
2637 container resource-resolution-data {
\r
2638 list resource-key {
\r
2648 description "SUCCESS, FAILED, or PENDING - RA returned data as capability";
\r
2651 leaf capability-name {
\r
2652 description "Resource assignment resolution Capability name";
\r
2661 grouping ip-addresses {
\r
2662 container ip-addresses {
\r
2663 leaf ipv4-address {
\r
2664 type inet:ip-address;
\r
2666 leaf ipv6-address {
\r
2667 type inet:ip-address;
\r
2669 leaf vipv4-address {
\r
2670 description "Virtual v4";
\r
2671 type inet:ip-address;
\r
2673 leaf vipv6-address {
\r
2674 description "Virtual v6";
\r
2675 type inet:ip-address;
\r
2679 grouping instance-reference {
\r
2680 leaf instance-id {
\r
2683 leaf object-path {
\r
2684 description "restconf retrieval path to this particular objectE.g. restconf/config/GENERIC-RESOURCE-API:services/service/$service-instance-id/service-data/service-topology/";
\r
2688 grouping oper-status-data {
\r
2689 leaf order-status {
\r
2690 description "TBD - do we need Request failed statuses? RequestFailed | InProgressTimeout";
\r
2691 type enumeration {
\r
2693 enum "PendingAssignment";
\r
2694 enum "PendingCreate";
\r
2695 enum "PendingUpdate";
\r
2696 enum "PendingDelete";
\r
2701 leaf last-rpc-action {
\r
2702 type enumeration {
\r
2707 enum "deactivate";
\r
2709 enum "changeassign";
\r
2710 enum "reoptimize";
\r
2713 leaf last-action {
\r
2714 description "should be list of possible request-actions";
\r
2715 type enumeration {
\r
2716 enum "CreateNetworkInstance";
\r
2717 enum "ActivateNetworkInstance";
\r
2718 enum "DeActivateNetworkInstance";
\r
2719 enum "DeleteNetworkInstance";
\r
2720 enum "CreateServiceInstance";
\r
2721 enum "DeleteServiceInstance";
\r
2722 enum "CreateVnfInstance";
\r
2723 enum "ActivateVnfInstance";
\r
2724 enum "DeleteVnfInstance";
\r
2725 enum "CreatePnfInstance";
\r
2726 enum "ActivatePnfInstance";
\r
2727 enum "DeletePnfInstance";
\r
2728 enum "CreateVfModuleInstance";
\r
2729 enum "ActivateVfModuleInstance";
\r
2730 enum "DeleteVfModuleInstance";
\r
2731 enum "CreateContrailRouteInstance";
\r
2732 enum "DeleteContrailRouteInstance";
\r
2733 enum "CreateSecurityZoneInstance";
\r
2734 enum "DeleteSecurityZoneInstance";
\r
2735 enum "ActivateDCINetworkInstance";
\r
2736 enum "DeActivateDCINetworkInstance";
\r
2737 enum "CreateTunnelXConnInstance";
\r
2738 enum "DeleteTunnelXConnInstance";
\r
2739 enum "CreateBRGInstance";
\r
2740 enum "DeleteBRGInstance";
\r
2741 enum "CreateSOTNConnectivityInstance";
\r
2742 enum "ActivateSOTNConnectivityInstance";
\r
2743 enum "DeactivateSOTNConnectivityInstance";
\r
2744 enum "DeleteSOTNConnectivityInstance";
\r
2745 enum "CreateSOTNAttachmentInstance";
\r
2746 enum "ActivateSOTNAttachmentInstance";
\r
2747 enum "DeactivateSOTNAttachmentInstance";
\r
2748 enum "DeleteSOTNAttachmentInstance";
\r
2749 enum "CreateSiteInstance";
\r
2750 enum "ActivateSiteInstance";
\r
2751 enum "DeactivateSiteInstance";
\r
2752 enum "DeleteSiteInstance";
\r
2753 enum "CreatePortMirrorConfigurationInstance";
\r
2754 enum "DeletePortMirrorConfigurationInstance";
\r
2755 enum "ChangePortMirrorConfigurationInstance";
\r
2756 enum "CreateGenericConfigurationInstance";
\r
2757 enum "DeleteGenericConfigurationInstance";
\r
2758 enum "PreloadVfModuleRequest";
\r
2759 enum "DeletePreloadVfModuleRequest";
\r
2760 enum "PreloadNetworkRequest";
\r
2761 enum "DeletePreloadNetworkRequest";
\r
2762 enum "CreateForwardingPathInstance";
\r
2763 enum "DeleteForwardingPathInstance";
\r
2764 enum "UpdateForwardingPathInstance";
\r
2765 enum "CreateSDWANDeviceInstance";
\r
2766 enum "ActivateSDWANDeviceInstance";
\r
2767 enum "DeactivateSDWANDeviceInstance";
\r
2768 enum "DeleteSDWANDeviceInstance";
\r
2769 enum "CreateSDWANPortInstance";
\r
2770 enum "ActivateSDWANPortInstance";
\r
2771 enum "DeactivateSDWANPortInstance";
\r
2772 enum "DeleteSDWANPortInstance";
\r
2773 enum "ReoptimizeSOTNInstance";
\r
2774 enum "CreateSDWANLanPortInstance";
\r
2775 enum "ActivateSDWANLanPortInstance";
\r
2776 enum "DeactivateSDWANLanPortInstance";
\r
2777 enum "DeleteSDWANLanPortInstance";
\r
2778 enum "CreateSDWANVpnInstance";
\r
2779 enum "ActivateSDWANVpnInstance";
\r
2780 enum "DeactivateSDWANVpnInstance";
\r
2781 enum "DeleteSDWANVpnInstance";
\r
2782 enum "CreateSDWANSiteInstance";
\r
2783 enum "ActivateSDWANSiteInstance";
\r
2784 enum "DeactivateSDWANSiteInstance";
\r
2785 enum "DeleteSDWANSiteInstance";
\r
2786 enum "SdwanBandwidthChange";
\r
2787 enum "CreateAccessConnectivityInstance";
\r
2788 enum "DeleteAccessConnectivityInstance";
\r
2789 enum "CreateInternetProfileInstance";
\r
2790 enum "ChangeInternetProfileInstance";
\r
2791 enum "DeleteInternetProfileInstance";
\r
2792 enum "CreateSOTNUnderlayInstance";
\r
2793 enum "ActivateSOTNUnderlayInstance";
\r
2794 enum "DeactivateSOTNUnderlayInstance";
\r
2795 enum "DeleteSOTNUnderlayInstance";
\r
2796 enum "CreateSOTNUniInstance";
\r
2797 enum "ActivateSOTNUniInstance";
\r
2798 enum "DeactivateSOTNUniInstance";
\r
2799 enum "DeleteSOTNUniInstance";
\r
2800 enum "CreateSOTNL2VpnInstance";
\r
2801 enum "ActivateSOTNL2VpnInstance";
\r
2802 enum "DeactivateSOTNL2VpnInstance";
\r
2803 enum "DeleteSOTNL2VpnInstance";
\r
2806 leaf last-svc-request-id {
\r
2807 description "Not currently populated in service data.";
\r
2810 leaf last-order-status {
\r
2811 type enumeration {
\r
2813 enum "PendingAssignment";
\r
2814 enum "PendingCreate";
\r
2815 enum "PendingUpdate";
\r
2816 enum "PendingDelete";
\r
2821 leaf create-timestamp {
\r
2822 description "Not currently populated in service data.";
\r
2825 leaf modify-timestamp {
\r
2829 grouping service-response-information {
\r
2830 container service-response-information {
\r
2831 uses instance-reference;
\r
2834 grouping network-response-information {
\r
2835 container network-response-information {
\r
2836 uses instance-reference;
\r
2839 grouping vnf-response-information {
\r
2840 container vnf-response-information {
\r
2841 uses instance-reference;
\r
2844 grouping vf-module-response-information {
\r
2845 container vf-module-response-information {
\r
2846 uses instance-reference;
\r
2849 grouping pnf-response-information {
\r
2850 container pnf-response-information {
\r
2851 uses instance-reference;
\r
2854 grouping contrail-route-response-information {
\r
2855 container contrail-route-response-information {
\r
2856 uses instance-reference;
\r
2859 grouping security-zone-response-information {
\r
2860 container security-zone-response-information {
\r
2861 uses instance-reference;
\r
2864 grouping getpathsegment-response-information {
\r
2865 container getpathsegment-response-information {
\r
2866 uses instance-reference;
\r
2869 grouping port-mirror-response-information {
\r
2870 container port-mirror-response-information {
\r
2871 uses instance-reference;
\r
2874 grouping gc-response-information {
\r
2875 container gc-response-information {
\r
2876 uses instance-reference;
\r
2879 grouping tunnelxconn-response-information {
\r
2880 container tunnelxconn-response-information {
\r
2881 uses instance-reference;
\r
2884 grouping brg-response-information {
\r
2885 container brg-response-information {
\r
2886 uses instance-reference;
\r
2889 grouping connection-attachment-response-information {
\r
2890 container connection-attachment-response-information {
\r
2891 uses instance-reference;
\r
2894 grouping preload-model-information {
\r
2895 list preload-list {
\r
2896 key "preload-id preload-type";
\r
2898 description "vf-module-name or network name";
\r
2902 leaf preload-type {
\r
2903 description "network or vf-module";
\r
2907 uses preload-data;
\r
2910 grouping preload-data {
\r
2911 container preload-data {
\r
2912 uses preload-vf-module-topology-information;
\r
2913 uses preload-network-topology-information;
\r
2914 uses preload-oper-status;
\r
2917 grouping preload-vf-module-topology-information {
\r
2918 container preload-vf-module-topology-information {
\r
2919 uses vnf-topology-identifier-structure;
\r
2920 uses vnf-resource-assignments;
\r
2921 uses vf-module-topology;
\r
2924 grouping preload-network-topology-information {
\r
2925 container preload-network-topology-information {
\r
2926 uses network-topology-identifier-structure;
\r
2928 uses vpn-bindings;
\r
2929 uses network-policy;
\r
2930 uses route-table-reference;
\r
2932 uses provider-network-information;
\r
2935 grouping subnets {
\r
2937 key "start-address";
\r
2938 leaf start-address {
\r
2939 type inet:ip-address;
\r
2941 leaf gateway-address {
\r
2942 type inet:ip-address;
\r
2950 leaf dhcp-enabled {
\r
2951 type enumeration {
\r
2956 leaf dhcp-start-address {
\r
2959 leaf dhcp-end-address {
\r
2962 leaf addr-from-start {
\r
2963 description "Default is N";
\r
2964 type enumeration {
\r
2969 leaf subnet-name {
\r
2972 leaf subnet-role {
\r
2975 leaf subnet-sequence {
\r
2980 grouping vpn-bindings {
\r
2981 list vpn-bindings {
\r
2982 key "vpn-binding-id";
\r
2983 leaf vpn-binding-id {
\r
2989 leaf global-route-target {
\r
2992 leaf route-target-role {
\r
2996 description "AIC Zone the route target associated with";
\r
3001 grouping network-policy {
\r
3002 list network-policy {
\r
3003 key "network-policy-fqdn";
\r
3004 leaf network-policy-fqdn {
\r
3007 leaf network-policy-id {
\r
3012 grouping route-table-reference {
\r
3013 list route-table-reference {
\r
3014 key "route-table-reference-fqdn";
\r
3015 leaf route-table-reference-fqdn {
\r
3019 leaf route-table-reference-id {
\r
3024 grouping provider-network-information {
\r
3025 leaf physical-network-name {
\r
3028 leaf is-provider-network {
\r
3031 leaf is-shared-network {
\r
3034 leaf is-external-network {
\r
3038 grouping host-routes {
\r
3039 list host-routes {
\r
3040 key "route-prefix";
\r
3041 leaf route-prefix {
\r
3045 description "Could be ip-address or hostname or service-instance";
\r
3050 grouping preload-oper-status {
\r
3051 container preload-oper-status {
\r
3052 leaf order-status {
\r
3053 type enumeration {
\r
3055 enum "PendingAssignment";
\r
3056 enum "PendingCreate";
\r
3057 enum "PendingUpdate";
\r
3058 enum "PendingDelete";
\r
3062 leaf last-action {
\r
3063 type enumeration {
\r
3064 enum "PreloadVfModuleRequest";
\r
3065 enum "DeletePreloadVfModuleRequest";
\r
3066 enum "PreloadNetworkRequest";
\r
3067 enum "DeletePreloadNetworkRequest";
\r
3070 leaf last-svc-request-id {
\r
3073 leaf last-order-status {
\r
3074 type enumeration {
\r
3076 enum "PendingAssignment";
\r
3077 enum "PendingCreate";
\r
3078 enum "PendingUpdate";
\r
3079 enum "PendingDelete";
\r
3083 leaf create-timestamp {
\r
3086 leaf modify-timestamp {
\r
3089 leaf maintenance-indicator {
\r
3090 type enumeration {
\r
3097 grouping preload-topology-response-body {
\r
3098 leaf svc-request-id {
\r
3101 leaf response-code {
\r
3104 leaf response-message {
\r
3107 leaf ack-final-indicator {
\r
3111 rpc generic-configuration-notification {
\r
3113 uses sdnc-request-header;
\r
3114 uses request-information;
\r
3115 uses service-information;
\r
3116 uses configuration-information;
\r
3117 uses topology-response-common;
\r
3118 leaf configuration-topology-link {
\r
3119 description "Returns URL to generic-configuration-topology ";
\r
3122 uses vnr-parameters;
\r
3123 uses vnf-vnr-rebuild-data;
\r
3126 container services {
\r
3127 uses service-model-infrastructure;
\r
3129 container contrail-route-allotted-resources {
\r
3130 list contrail-route-allotted-resource {
\r
3131 key "allotted-resource-id";
\r
3132 leaf allotted-resource-id {
\r
3136 container allotted-resource-data {
\r
3137 container allotted-resource-operation-information {
\r
3138 uses contrail-route-operation-information;
\r
3140 uses contrail-route-topology;
\r
3141 uses allotted-resource-oper-status;
\r
3143 uses allotted-resource-status;
\r
3146 container security-zone-allotted-resources {
\r
3147 list security-zone-allotted-resource {
\r
3148 key "allotted-resource-id";
\r
3149 leaf allotted-resource-id {
\r
3153 container allotted-resource-data {
\r
3154 container allotted-resource-operation-information {
\r
3155 uses security-zone-operation-information;
\r
3157 uses security-zone-topology;
\r
3158 container security-zone-parameters {
\r
3161 uses allotted-resource-oper-status;
\r
3163 uses allotted-resource-status;
\r
3166 container tunnelxconn-allotted-resources {
\r
3167 list tunnelxconn-allotted-resource {
\r
3168 key "allotted-resource-id";
\r
3169 leaf allotted-resource-id {
\r
3173 container allotted-resource-data {
\r
3174 container allotted-resource-operation-information {
\r
3175 uses tunnelxconn-operation-information;
\r
3177 uses tunnelxconn-topology;
\r
3178 container tunnelxconn-parameters {
\r
3181 uses allotted-resource-oper-status;
\r
3183 uses allotted-resource-status;
\r
3186 container brg-allotted-resources {
\r
3187 list brg-allotted-resource {
\r
3188 key "allotted-resource-id";
\r
3189 leaf allotted-resource-id {
\r
3193 container allotted-resource-data {
\r
3194 container allotted-resource-operation-information {
\r
3195 uses brg-operation-information;
\r
3197 uses brg-topology;
\r
3198 container brg-parameters {
\r
3201 uses allotted-resource-oper-status;
\r
3203 uses allotted-resource-status;
\r
3206 container connection-attachment-allotted-resources {
\r
3207 list connection-attachment-allotted-resource {
\r
3208 key "allotted-resource-id";
\r
3209 leaf allotted-resource-id {
\r
3213 container allotted-resource-data {
\r
3214 container allotted-resource-operation-information {
\r
3215 uses connection-attachment-operation-information;
\r
3217 uses connection-attachment-topology;
\r
3218 container connection-attachment-parameters {
\r
3221 uses allotted-resource-oper-status;
\r
3223 uses allotted-resource-status;
\r
3226 container port-mirror-configurations {
\r
3227 list port-mirror-configuration {
\r
3228 key "configuration-id";
\r
3229 leaf configuration-id {
\r
3233 container configuration-data {
\r
3234 container configuration-operation-information {
\r
3235 uses port-mirror-topology-operation-information;
\r
3237 uses port-mirror-configuration-topology;
\r
3238 uses configuration-oper-status;
\r
3240 uses configuration-status;
\r
3243 container generic-configurations {
\r
3244 list gc-configuration {
\r
3245 key "configuration-id";
\r
3246 leaf configuration-id {
\r
3250 container configuration-data {
\r
3251 container configuration-operation-information {
\r
3252 uses gc-topology-operation-information;
\r
3254 uses configuration-oper-status;
\r
3256 uses configuration-status;
\r
3259 rpc service-topology-operation {
\r
3261 uses service-operation-information;
\r
3264 uses topology-response-common;
\r
3265 uses service-response-information;
\r
3268 rpc network-topology-operation {
\r
3270 uses network-operation-information;
\r
3273 uses topology-response-common;
\r
3274 uses network-response-information;
\r
3275 uses service-response-information;
\r
3278 rpc vnf-topology-operation {
\r
3280 uses vnf-operation-information;
\r
3283 uses topology-response-common;
\r
3284 uses vnf-response-information;
\r
3285 uses service-response-information;
\r
3288 rpc vf-module-topology-operation {
\r
3290 uses vf-module-operation-information;
\r
3293 uses topology-response-common;
\r
3294 uses vf-module-response-information;
\r
3295 uses vnf-response-information;
\r
3296 uses service-response-information;
\r
3299 rpc pnf-topology-operation {
\r
3301 uses pnf-operation-information;
\r
3304 uses topology-response-common;
\r
3305 uses pnf-response-information;
\r
3306 uses service-response-information;
\r
3309 rpc contrail-route-topology-operation {
\r
3311 uses contrail-route-operation-information;
\r
3314 uses topology-response-common;
\r
3315 uses contrail-route-response-information;
\r
3316 uses service-response-information;
\r
3319 rpc security-zone-topology-operation {
\r
3321 uses security-zone-operation-information;
\r
3324 uses topology-response-common;
\r
3325 uses security-zone-response-information;
\r
3326 uses service-response-information;
\r
3329 rpc tunnelxconn-topology-operation {
\r
3331 uses tunnelxconn-operation-information;
\r
3334 uses topology-response-common;
\r
3335 uses tunnelxconn-response-information;
\r
3336 uses service-response-information;
\r
3339 rpc brg-topology-operation {
\r
3341 uses brg-operation-information;
\r
3344 uses topology-response-common;
\r
3345 uses brg-response-information;
\r
3346 uses service-response-information;
\r
3349 rpc policy-update-notify-operation {
\r
3351 leaf policy-name {
\r
3356 description "Map JSON versionNo to version-id";
\r
3360 leaf update-type {
\r
3374 rpc getpathsegment-topology-operation {
\r
3376 uses forwarding-path-operation-information;
\r
3379 uses topology-response-common;
\r
3380 uses getpathsegment-response-information;
\r
3381 uses service-response-information;
\r
3384 rpc port-mirror-topology-operation {
\r
3386 uses port-mirror-topology-operation-information;
\r
3389 uses topology-response-common;
\r
3390 uses port-mirror-response-information;
\r
3391 uses service-response-information;
\r
3394 rpc generic-configuration-topology-operation {
\r
3396 uses gc-topology-operation-information;
\r
3399 uses topology-response-common;
\r
3400 uses gc-response-information;
\r
3401 uses service-response-information;
\r
3404 rpc vnf-get-resource-request {
\r
3406 uses sdnc-request-header;
\r
3407 uses request-information;
\r
3408 uses service-information;
\r
3409 uses vnf-get-resource-request-input-data;
\r
3412 container vnf-get-resource-response-information {
\r
3413 uses vnf-cloud-param;
\r
3417 container preload-information {
\r
3418 uses preload-model-information;
\r
3420 rpc preload-vf-module-topology-operation {
\r
3422 uses sdnc-request-header;
\r
3423 uses request-information;
\r
3424 uses preload-vf-module-topology-information;
\r
3427 uses preload-topology-response-body;
\r
3430 rpc preload-network-topology-operation {
\r
3432 uses sdnc-request-header;
\r
3433 uses request-information;
\r
3434 uses preload-network-topology-information;
\r
3437 uses preload-topology-response-body;
\r
3441 rpc connection-attachment-topology-operation {
\r
3443 uses connection-attachment-operation-information;
\r
3446 uses topology-response-common;
\r
3447 uses connection-attachment-response-information;
\r
3448 uses service-response-information;
\r
3452 } ////closes the module
\r