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 vnf-data {
\r
62 uses vnf-operation-information;
\r
64 container vnf-network-collections {
\r
65 uses vnf-network-collection;
\r
67 container vnf-sub-interface-groups {
\r
68 uses vnf-sub-interface-group;
\r
70 container vnf-provided-allotted-resources {
\r
71 leaf-list vnf-provided-ar-id {
\r
72 description "List of allotted resources using capacity from this vnf";
\r
77 uses vnf-level-oper-status;
\r
78 container vf-modules {
\r
85 container vf-module-data {
\r
86 uses vf-module-operation-information;
\r
87 uses vf-module-topology;
\r
88 uses vf-module-level-oper-status;
\r
95 container consumed-allotted-resources {
\r
96 list consumed-allotted-resource {
\r
97 key "allotted-resource-id";
\r
98 uses allotted-resource-info;
\r
101 container provided-allotted-resources {
\r
102 list provided-allotted-resource {
\r
103 key "allotted-resource-id";
\r
104 uses allotted-resource-info;
\r
107 container provided-configurations {
\r
108 list provided-configuration {
\r
109 key "configuration-id";
\r
110 uses configuration-info;
\r
113 container vnfc-instance-groups {
\r
114 uses vnfc-instance-group;
\r
116 container network-instance-groups {
\r
117 uses network-instance-group;
\r
119 container forwarding-paths {
\r
120 list forwarding-path {
\r
121 key "forwarding-path-id";
\r
122 leaf forwarding-path-id {
\r
123 description "Generated by SDNC";
\r
127 uses forwarding-path-information;
\r
132 grouping service-status {
\r
133 container service-status {
\r
134 leaf response-code {
\r
137 leaf response-message {
\r
140 leaf final-indicator {
\r
143 leaf request-status {
\r
145 enum "synccomplete";
\r
146 enum "asynccomplete";
\r
147 enum "notifycomplete";
\r
151 description "value would one of possible request-actions; match the list in service-data oper-status";
\r
158 description "this is the svc-action from the incoming request";
\r
169 leaf response-timestamp {
\r
174 grouping service-operation-information {
\r
175 uses sdnc-request-header;
\r
176 uses request-information;
\r
177 uses service-information;
\r
178 uses service-request-input;
\r
180 grouping service-request-input {
\r
181 container service-request-input {
\r
182 leaf service-instance-name {
\r
185 container service-input-parameters {
\r
190 grouping service-topology {
\r
191 container service-topology {
\r
192 uses service-topology-identifier;
\r
193 uses onap-model-information;
\r
194 uses service-assignments;
\r
195 uses service-parameters;
\r
198 grouping service-topology-identifier {
\r
199 container service-topology-identifier {
\r
200 leaf service-instance-id {
\r
201 description "repeated";
\r
204 leaf service-type {
\r
205 description "tag labeled subscription-service-type in the service-information input";
\r
209 description "from MSO input on STO assign";
\r
212 leaf service-instance-name {
\r
213 description "optionally comes from service-request-input container or is assigned by sdn-c";
\r
216 leaf global-customer-id {
\r
221 grouping service-assignments {
\r
222 container service-assignments {
\r
225 grouping service-parameters {
\r
226 container service-parameters {
\r
227 list service-parameter {
\r
228 key "service-parameter-name";
\r
229 leaf service-parameter-name {
\r
232 leaf service-parameter-value {
\r
238 grouping service-level-oper-status {
\r
239 container service-level-oper-status {
\r
240 uses oper-status-data;
\r
243 grouping network-operation-information {
\r
244 uses sdnc-request-header;
\r
245 uses request-information;
\r
246 uses service-information;
\r
247 uses network-information;
\r
248 uses network-request-input;
\r
250 grouping network-information {
\r
251 container network-information {
\r
255 leaf network-type {
\r
258 leaf network-technology {
\r
261 leaf from-preload {
\r
262 description "Indicates if source is preload data";
\r
265 uses onap-model-information;
\r
268 grouping network-request-input {
\r
269 container network-request-input {
\r
270 leaf network-name {
\r
273 uses region-identifier;
\r
274 container network-input-parameters {
\r
277 leaf network-instance-group-id {
\r
278 description "When network has instance-group role in service model";
\r
283 grouping network-topology {
\r
284 container network-topology {
\r
285 uses network-topology-identifier-structure;
\r
286 uses region-identifier;
\r
287 uses onap-model-information;
\r
288 uses network-assignments;
\r
289 uses network-parameters;
\r
292 grouping network-topology-identifier-structure {
\r
293 container network-topology-identifier-structure {
\r
297 leaf network-name {
\r
300 leaf network-role {
\r
303 leaf network-type {
\r
306 leaf network-instance-group-id {
\r
307 description "When network is part of network instance-Group-data & instance Group in A&AI";
\r
310 leaf network-technology {
\r
313 leaf eipam-v4-address-plan {
\r
316 leaf eipam-v6-address-plan {
\r
322 leaf segmentation-id {
\r
325 container related-networks {
\r
326 uses related-network;
\r
330 grouping network-assignments {
\r
331 container network-assignments {
\r
334 grouping network-parameters {
\r
335 container network-parameters {
\r
336 list network-parameter {
\r
337 key "network-parameter-name";
\r
338 leaf network-parameter-name {
\r
341 leaf network-parameter-value {
\r
347 grouping network-instance-group {
\r
348 list network-instance-group {
\r
349 key "network-instance-group-id";
\r
350 leaf network-instance-group-id {
\r
351 description "Also a Key in Network Instance Group in A&AI";
\r
355 leaf network-instance-group-function {
\r
358 leaf service-instance-id {
\r
361 uses onap-model-information;
\r
362 container subnet-assignment-policy {
\r
364 description "Current valid values - unique, shared (default)";
\r
368 container vpn-binding-policy {
\r
378 leaf vpn-platform {
\r
381 leaf global-route-target {
\r
384 leaf route-target-role {
\r
388 uses aggregate-routes;
\r
390 leaf subnet-key-value {
\r
391 description "key-value provided to EIPAM when creating shared subnet";
\r
394 container networks {
\r
398 description "Index into network-topology-identifier structure";
\r
402 leaf neutron-network-id {
\r
403 description "Neutron-network-id assigned by PO/RO";
\r
410 leaf network-status {
\r
411 description "assigned, unassigned";
\r
414 container customer-bonding-requests {
\r
415 list customer-bonding-request {
\r
416 key "configuration-id";
\r
417 leaf configuration-id {
\r
418 description "e.g. vlan network receptor configuration id";
\r
427 grouping network-level-oper-status {
\r
428 container network-level-oper-status {
\r
429 uses oper-status-data;
\r
432 grouping vnf-operation-information {
\r
433 uses sdnc-request-header;
\r
434 uses request-information;
\r
435 uses service-information;
\r
436 uses vnf-information;
\r
437 uses vnf-request-input;
\r
438 uses license-information;
\r
440 grouping vnf-information {
\r
441 container vnf-information {
\r
451 uses onap-model-information;
\r
454 grouping vnf-request-input {
\r
455 container vnf-request-input {
\r
456 leaf request-version {
\r
462 uses region-identifier;
\r
463 container vnf-networks {
\r
465 key "network-role";
\r
466 uses vnf-network-data;
\r
469 list vnf-network-instance-group-ids {
\r
470 key "vnf-network-instance-group-id";
\r
471 leaf vnf-network-instance-group-id {
\r
472 description "List of vnf network-instance-group";
\r
476 container vnf-input-parameters {
\r
481 grouping vnf-topology {
\r
482 container vnf-topology {
\r
483 uses vnf-topology-identifier-structure;
\r
484 uses region-identifier;
\r
485 uses onap-model-information;
\r
486 uses vnf-resource-assignments;
\r
487 container vnf-parameters-data {
\r
490 leaf sdnc-generated-cloud-resources {
\r
491 description "Indicate if source is sdnc generated cloud param";
\r
496 grouping vnf-topology-identifier-structure {
\r
497 container vnf-topology-identifier-structure {
\r
502 description "In preload tree, this label is used for the vf-module-type";
\r
515 description "used in vnf naming";
\r
519 description "optionally comes from vnf-request-input container or is assigned by sdn-c";
\r
524 grouping vnf-resource-assignments {
\r
525 container vnf-resource-assignments {
\r
527 description "Orchestration status from AAI - to be set by SDNC";
\r
530 container availability-zones {
\r
531 leaf-list availability-zone {
\r
532 description "Openstack availability zone name or UUID";
\r
537 description "From the TOSCA data. Indicates the largest availability zone count needed by any vf-module in the VNF.";
\r
541 container vnf-networks {
\r
543 key "network-role";
\r
544 uses vnf-network-data;
\r
549 grouping vnf-network-data {
\r
550 leaf network-role {
\r
551 description "A Network Role to which a VNF must connect";
\r
554 leaf network-name {
\r
555 description "Unique Neutron UUID of an instance of the network role ";
\r
559 description "Unique Neutron UUID of an instance of the network role ";
\r
563 description "Unique Neutron UUID of an instance of the network role ";
\r
566 leaf contrail-network-fqdn {
\r
567 description "contrail network policy object";
\r
570 container subnets-data {
\r
572 key "sdnc-subnet-id";
\r
573 leaf sdnc-subnet-id {
\r
574 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
578 description "Subnet Role for the subnet";
\r
582 description "Populated for preload only";
\r
586 description "Should be ipv4 or ipv6";
\r
590 description "subnet UUID to be passed into the HEAT template";
\r
593 leaf dhcp-enabled {
\r
594 description "Indicator to use this subnet for DHCP ";
\r
600 leaf network-start-address {
\r
601 description "start-address of the subnet";
\r
602 type inet:ip-address;
\r
604 leaf gateway-address {
\r
605 description "subnet gateway address";
\r
606 type inet:ip-address;
\r
609 description "cidr mask";
\r
617 leaf segmentation-id {
\r
620 container related-networks {
\r
621 uses related-network;
\r
624 grouping vnf-level-oper-status {
\r
625 container vnf-level-oper-status {
\r
626 uses oper-status-data;
\r
629 grouping vf-module-operation-information {
\r
630 uses sdnc-request-header;
\r
631 uses request-information;
\r
632 uses service-information;
\r
633 uses vnf-information;
\r
634 uses vf-module-information;
\r
635 uses vf-module-request-input;
\r
637 grouping vf-module-information {
\r
638 container vf-module-information {
\r
639 leaf vf-module-id {
\r
642 leaf vf-module-type {
\r
645 leaf from-preload {
\r
646 description "Indicates if source is preload data";
\r
649 uses onap-model-information;
\r
652 grouping vf-module-request-input {
\r
653 container vf-module-request-input {
\r
654 leaf request-version {
\r
655 description "keep this?";
\r
658 leaf vf-module-name {
\r
661 uses region-identifier;
\r
662 container vf-module-input-parameters {
\r
667 grouping vf-module-topology {
\r
668 container vf-module-topology {
\r
669 uses vf-module-topology-identifier;
\r
670 uses region-identifier;
\r
671 uses onap-model-information;
\r
672 uses vf-module-assignments;
\r
673 container vf-module-parameters {
\r
676 leaf sdnc-generated-cloud-resources {
\r
677 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
682 grouping vf-module-topology-identifier {
\r
683 container vf-module-topology-identifier {
\r
684 leaf vf-module-id {
\r
685 description "vf-module id";
\r
688 leaf vf-module-name {
\r
689 description "vf-module-name";
\r
692 leaf vf-module-type {
\r
697 grouping vf-module-assignments {
\r
698 container vf-module-assignments {
\r
699 leaf vf-module-status {
\r
700 description "Orchestration status from AAI - to be set by SDNC";
\r
706 uses vm-topology-data;
\r
709 uses vlan-vnfc-instance-groups;
\r
710 container dhcp-subnet-assignments {
\r
711 list dhcp-subnet-assignment {
\r
712 key "neutron-subnet-id";
\r
713 leaf neutron-subnet-id {
\r
714 description "Same as subnet-id in subnet-data structure";
\r
717 leaf network-role {
\r
727 grouping vm-topology-data {
\r
732 uses onap-model-information;
\r
733 leaf nfc-naming-code {
\r
734 description "used in vm naming(draft 29: changed from nfc-code)";
\r
738 description "from tosca data on vfc";
\r
744 container vm-names {
\r
745 leaf-list vm-name {
\r
754 container vnfc-networks {
\r
755 uses vnfc-network-data;
\r
759 container vm-networks {
\r
761 key "network-role";
\r
762 uses vm-network-data;
\r
766 grouping vnfc-network-data {
\r
767 list vnfc-network-data {
\r
768 key "vnfc-network-role";
\r
769 leaf vnfc-network-role {
\r
776 uses connection-point;
\r
777 container vnfc-ports {
\r
779 key "vnfc-port-id";
\r
780 leaf vnfc-port-id {
\r
781 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
785 leaf common-sub-interface-role {
\r
786 description "If sub-interfaces have common interface role (network role)";
\r
789 container vnic-sub-interfaces {
\r
790 uses sub-interface-network-data;
\r
795 key "vnfc-subnet-role";
\r
796 leaf vnfc-subnet-role {
\r
797 description "Default value if subnet role is not defined.";
\r
801 list vnfc-ip-assignments {
\r
802 key "vnfc-address-family";
\r
803 leaf vnfc-address-family {
\r
804 description "indicates if this is IpV4 or IpV6";
\r
810 leaf vnfc-subnet-dhcp {
\r
811 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
817 leaf vnfc-subnet-ip-count {
\r
818 description "The number of IP addresses to be assigned per vnfc for this subnet role";
\r
821 list vnfc-subnet-ip {
\r
822 key "vnfc-ip-address";
\r
823 leaf vnfc-ip-address {
\r
824 description "Either IpV4 IP or IpV6 IP addresses should be present";
\r
825 type inet:ip-address;
\r
827 leaf vnfc-client-key {
\r
831 description "Capture what type of IP this is, if is virtual IP (AKA, floating IP) or Fixed IP. ";
\r
842 grouping vm-network-data {
\r
843 leaf network-role {
\r
844 description "network (identified by role) that this VM connects to. Should also be included in the vnf-networks for the containing VNF";
\r
848 leaf network-role-tag {
\r
851 container network-information-items {
\r
852 list network-information-item {
\r
855 description "Use ipv4 or ipv6";
\r
859 description "Indicator to use DHCP on this network for this VM";
\r
866 description "The number of ip addresses to be assigned per vm for this network role";
\r
869 container network-ips {
\r
870 leaf-list network-ip {
\r
871 description "List of assigned ip addresses of type ip-version on a network";
\r
878 container mac-addresses {
\r
879 leaf-list mac-address {
\r
880 description "List of network assignments for this vm-type";
\r
885 container floating-ips {
\r
886 leaf-list floating-ip-v4 {
\r
887 description "Floating ipv4 for VMs of a given type on this network";
\r
888 type inet:ip-address;
\r
891 leaf-list floating-ip-v6 {
\r
892 description "Floating ipv6 for VMs of a given type on this network";
\r
893 type inet:ipv6-address;
\r
897 container interface-route-prefixes {
\r
898 leaf-list interface-route-prefix {
\r
899 description "ordered-by: user";
\r
904 container sriov-parameters {
\r
905 container heat-vlan-filters {
\r
906 leaf-list heat-vlan-filter {
\r
911 container application-tags {
\r
929 leaf segmentation-id {
\r
932 container related-networks {
\r
933 uses related-network;
\r
936 grouping vf-module-level-oper-status {
\r
937 container vf-module-level-oper-status {
\r
938 uses oper-status-data;
\r
941 grouping allotted-resource-info {
\r
942 leaf allotted-resource-id {
\r
945 leaf allotted-resource-type {
\r
946 description "Not an enum, but expected values are contrail-route and security-zone.";
\r
949 leaf allotted-resource-pointer {
\r
950 description "Pointer to the allotted-resources topology";
\r
954 grouping forwarding-path-operation-information {
\r
955 uses sdnc-request-header;
\r
956 uses request-information;
\r
957 uses service-information;
\r
958 uses forwarding-path-request-input;
\r
960 grouping forwarding-path-request-input {
\r
961 container forwarding-path-request-input {
\r
962 list forwarding-paths {
\r
963 key "forwarding-path-name";
\r
964 leaf forwarding-path-name {
\r
965 description "Forwarding-path-name from tosca-model. ";
\r
969 uses onap-model-information;
\r
973 grouping forwarding-path-information {
\r
974 leaf forwarding-path-name {
\r
975 description "Fowarding-path name from TOSCA model, or name generated by SDNC";
\r
978 leaf forwarding-path-type {
\r
979 description "Based on MySQL Forwarding_Path tables path_type value from related TOSCA model";
\r
985 uses onap-model-information;
\r
986 container service-paths {
\r
987 list service-path {
\r
988 key "service-path-instance-id";
\r
989 uses service-path-information;
\r
993 grouping service-path-information {
\r
994 leaf service-path-instance-id {
\r
995 description "Service path instance ID generated by SDNC. Identifies a service-path-instance within a forwarding-path definition";
\r
998 leaf service-path-instance-name {
\r
999 description "A unique name generated by SDNC ( forwarding-path-name + service-path-instance-id )";
\r
1003 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
1007 key "service-instance-id";
\r
1008 leaf service-instance-id {
\r
1009 description "service-instance-id of each service-instance in the service-path-instance";
\r
1012 leaf service-path-sequence-id {
\r
1013 description "e.g. S1S2S3S5seq id=1 S1-S2seq id=2 S2S3seq id=3 S3S5Incremental integer value";
\r
1018 key "vnf-instance-id";
\r
1019 uses vnf-path-information;
\r
1024 grouping vnf-path-information {
\r
1025 leaf vnf-instance-id {
\r
1026 description "VNF instance ID in the path";
\r
1029 leaf vnf-path-sequence-id {
\r
1030 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
1033 leaf left-network-name {
\r
1034 description "Every VNF instance in the path is connected to one or two VNFs.";
\r
1037 leaf left-network-role {
\r
1040 leaf right-network-name {
\r
1043 leaf right-network-role {
\r
1046 container vf-module-instance {
\r
1047 leaf vf-module-id {
\r
1050 leaf vf-module-name {
\r
1055 grouping forwarding-path-level-oper-status {
\r
1056 container forwarding-path-level-oper-status {
\r
1057 uses oper-status-data;
\r
1060 grouping configuration-info {
\r
1061 leaf configuration-id {
\r
1064 leaf configuration-type {
\r
1065 description "Not an enum, but expected values are port-mirror-configuration, , vlan-network-receptor";
\r
1068 leaf configuration-sub-type {
\r
1069 description "Not an enum, but expected values are vprobe and pprobe";
\r
1072 leaf configuration-topology-link {
\r
1073 description "Pointer to the configurations topology";
\r
1077 grouping vnfc-instance-group {
\r
1078 list vnfc-instance-group {
\r
1079 key "instance-group-role nfc-naming-code configuration-id";
\r
1080 leaf instance-group-role {
\r
1081 description "i.e.TSBC_VNFC_group";
\r
1085 leaf nfc-naming-code {
\r
1086 description "Set to nfc-naming-code from A&AI";
\r
1090 leaf configuration-id {
\r
1095 description " port-mirror-source or port-mirror-dest";
\r
1098 uses vnfc-objects;
\r
1101 grouping vnfc-objects {
\r
1102 container vnfc-objects {
\r
1103 list vnfc-object {
\r
1109 description "Vnfc name as key in A&AI";
\r
1118 leaf vserver-name {
\r
1126 key "vnic-port-name";
\r
1127 leaf vnic-port-name {
\r
1130 leaf vnic-port-id {
\r
1133 container capacity {
\r
1134 leaf vnic-capacity {
\r
1137 leaf used-capacity {
\r
1138 description "Updated for destination port when source port is mapped/unmapped.";
\r
1142 container vnic-ip-addresses {
\r
1143 uses ip-addresses;
\r
1155 description "Vnfc name as key in A&AI";
\r
1158 leaf vserver-name {
\r
1171 key "vnic-port-name";
\r
1172 leaf vnic-port-name {
\r
1175 leaf vnic-port-id {
\r
1178 uses sub-interfaces;
\r
1182 grouping sub-interfaces {
\r
1183 container sub-interfaces {
\r
1184 list sub-interface {
\r
1185 key "sub-interface-port-name";
\r
1186 leaf sub-interface-port-name {
\r
1189 leaf sub-interface-port-id {
\r
1192 container sub-interface-ip-addresses {
\r
1193 uses ip-addresses;
\r
1196 container sub-interface-network {
\r
1197 leaf network-name {
\r
1204 leaf sub-interface-status {
\r
1205 description "NULL, unassigned, assigned";
\r
1211 grouping vlan-tags {
\r
1212 container vlan-tags {
\r
1213 leaf vlan-interface {
\r
1214 description "A&AI Key";
\r
1217 leaf upper-tag-id {
\r
1220 leaf lower-tag-id {
\r
1228 grouping vlan-vnfc-instance-groups {
\r
1229 container vlan-vnfc-instance-groups {
\r
1230 list vlan-vnfc-instance-group {
\r
1231 key "instance-group-id";
\r
1232 leaf instance-group-id {
\r
1233 description "A&AI ID";
\r
1237 leaf instance-group-function {
\r
1255 grouping vnic-groups {
\r
1256 container vnic-groups {
\r
1258 key "vnic-interface-role";
\r
1259 leaf vnic-interface-role {
\r
1260 description "Same as network-role of network where vnic is connected";
\r
1264 leaf network-instance-group-function {
\r
1265 description "network-instance-Group-function for network collection where vnics with vnic-interface-role will connect";
\r
1268 leaf vlan-assignment-policy-name {
\r
1269 description "Policy name in ASDC model & policy definition in Policy Engine";
\r
1272 leaf vlan-tag-index-next {
\r
1273 description "Next tag to be assigned";
\r
1276 container vlan-common-ip-addresses {
\r
1277 uses ip-addresses;
\r
1279 container vlan-vnics {
\r
1281 key "vnic-port-id";
\r
1282 leaf vnic-port-id {
\r
1286 container vnic-sub-interfaces {
\r
1287 uses sub-interface-network-data;
\r
1294 grouping vnf-network-collection {
\r
1295 list vnf-network-collection {
\r
1296 key "network-instance-group-function";
\r
1297 leaf network-instance-group-function {
\r
1298 description "Network Instance-Group function in A&AI";
\r
1302 leaf network-instance-group-id {
\r
1303 description "Network Instance-Group id in A&AI";
\r
1306 leaf network-collection-service-instance-id {
\r
1307 description "Service-instance-id of service that created the network collection";
\r
1310 leaf network-collection-customization-uuid {
\r
1311 description "network-collection-customization-uuid stored in Network IsntanceGroup.customization-uuid in A&AI";
\r
1314 container networks {
\r
1318 description "Index into network-topology-identifier structure";
\r
1322 leaf neutron-network-id {
\r
1323 description "Neutron-network-id assigned by PO/RO";
\r
1328 container vnf-floating-ip {
\r
1329 uses ip-addresses;
\r
1333 grouping vnf-sub-interface-group {
\r
1334 list vnf-sub-interface-group {
\r
1335 key "vnfc-instance-group-function network-instance-group-function parent-port-role";
\r
1336 leaf vnfc-instance-group-function {
\r
1340 leaf network-instance-group-function {
\r
1344 leaf parent-port-role {
\r
1349 container customer-bonding-requests {
\r
1350 list customer-bonding-request {
\r
1351 key "configuration-id";
\r
1352 leaf configuration-id {
\r
1353 description "e.g. vlan network receptor configuration id";
\r
1360 grouping sub-interface-network-data {
\r
1361 list sub-interface-network-data {
\r
1364 description "Subinterface network id (UUID in A&AI)";
\r
1368 leaf neutron-network-id {
\r
1369 description "Neutron network id assigned by PO/RP";
\r
1372 leaf network-name {
\r
1373 description "Subinterface network name";
\r
1376 leaf vlan-tag-id {
\r
1377 description "Vlan tag assigned to subinterface port";
\r
1380 leaf network-role {
\r
1381 description "e.g. untrusted ";
\r
1384 leaf network-role-tag {
\r
1385 description "Assuming HEAT template network role tag parameter - not used";
\r
1388 container network-information-items {
\r
1389 list network-information-item {
\r
1392 description "Use ipv4 or ipv6";
\r
1396 description "Indicator to use DHCP on this network for this VM - set to N for Vlan tagging";
\r
1397 type enumeration {
\r
1403 description "The number of ip addresses to be assigned per vm for this network role";
\r
1406 container network-ips {
\r
1407 leaf-list network-ip {
\r
1408 description "List of assigned ip addresses of type ip-version on a network.";
\r
1409 type inet:ip-address;
\r
1415 container floating-ips {
\r
1416 leaf-list floating-ip-v4 {
\r
1417 description "Floating ipv4 for VMs of a given type on this network";
\r
1418 type inet:ip-address;
\r
1421 leaf-list floating-ip-v6 {
\r
1422 description "Floating ipv6 for VMs of a given type on this network";
\r
1423 type inet:ipv6-address;
\r
1429 grouping vnf-cloud-param {
\r
1430 leaf service-instance-id {
\r
1433 leaf service-instance-name {
\r
1446 key "vf-module-id";
\r
1447 leaf vf-module-id {
\r
1454 grouping vnf-get-resource-request-input-data {
\r
1461 key "vf-module-id";
\r
1462 leaf vf-module-id {
\r
1468 grouping license-information {
\r
1469 container license-information {
\r
1470 list entitlement-pool-list {
\r
1471 key "entitlement-pool-uuid action";
\r
1472 leaf entitlement-pool-uuid {
\r
1480 leaf entitlement-pool-invariant-uuid {
\r
1483 leaf entitlement-uuid {
\r
1484 description "assigned by ALTS";
\r
1488 list license-key-group-list {
\r
1489 key "license-key-group-uuid action";
\r
1490 leaf license-key-group-uuid {
\r
1498 leaf license-key-group-invariant-uuid {
\r
1501 leaf license-key {
\r
1502 description "assigned by ALTS";
\r
1505 leaf license-uuid {
\r
1506 description "assigned by ALTS";
\r
1512 grouping related-network {
\r
1513 list related-network {
\r
1516 description "Key to l3-network object";
\r
1519 leaf network-role {
\r
1525 grouping connection-point {
\r
1526 container connection-point {
\r
1527 leaf connection-point-id {
\r
1528 description "Key to CP object in A&AI";
\r
1532 description "port-index when multiple CPs connect to same network. Default zero (0)";
\r
1538 description "Key to vlan-tag uuid object in A&AI Generated by vlan mS";
\r
1541 leaf vlan-tag-id {
\r
1544 leaf vlan-tag-description {
\r
1548 description "Inner/Outer roles";
\r
1554 grouping aggregate-routes {
\r
1555 list aggregate-routes {
\r
1558 description "Unique id";
\r
1561 leaf start-address {
\r
1562 type inet:ip-address;
\r
1568 description "Use values 4 or 6.";
\r
1573 grouping pnf-information {
\r
1574 container pnf-information {
\r
1576 description "Key for A&AI query";
\r
1582 uses onap-model-information;
\r
1585 grouping contrail-route-operation-information {
\r
1586 uses sdnc-request-header;
\r
1587 uses request-information;
\r
1588 uses service-information;
\r
1589 uses allotted-resource-information;
\r
1590 uses contrail-route-request-input;
\r
1592 grouping contrail-route-request-input {
\r
1593 container contrail-route-request-input {
\r
1594 container source-network {
\r
1595 uses network-info;
\r
1597 container dest-network {
\r
1598 uses network-info;
\r
1600 container contrail-applied-service-info {
\r
1601 leaf service-instance-id {
\r
1602 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
1605 leaf contrail-fqdn {
\r
1606 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
1610 container contrail-route-input-parameters {
\r
1615 grouping network-info {
\r
1619 leaf network-role {
\r
1623 grouping contrail-route-topology {
\r
1624 container contrail-route-topology {
\r
1625 uses allotted-resource-identifiers;
\r
1626 uses onap-model-information;
\r
1627 uses contrail-route-assignments;
\r
1628 container contrail-route-parameters {
\r
1633 grouping contrail-route-assignments {
\r
1634 container contrail-route-assignments {
\r
1636 description "The Contrail fq-name of the network policy";
\r
1639 leaf contrail-id {
\r
1640 description "The ID assigned by Contrail to the network-policy (one for one with the fq-name)";
\r
1643 container source-network {
\r
1644 uses network-info;
\r
1646 container dest-network {
\r
1647 uses network-info;
\r
1649 container contrail-applied-service {
\r
1650 leaf service-instance-id {
\r
1651 description "The service-instance-id of the vnf from which the contrail applied service is coming";
\r
1655 description "The vnf representing the contrail applied service";
\r
1658 leaf contrail-fqdn {
\r
1659 description "This is the fq-name of the Contrail service instance through which the route is passing.";
\r
1664 description "Contrail-assigned vlan-tag to the vipr vm interface for this route.";
\r
1669 grouping security-zone-operation-information {
\r
1670 uses sdnc-request-header;
\r
1671 uses request-information;
\r
1672 uses service-information;
\r
1673 uses allotted-resource-information;
\r
1674 uses security-zone-request-input;
\r
1676 grouping security-zone-request-input {
\r
1677 container security-zone-request-input {
\r
1681 leaf trusted-network-role {
\r
1682 description "In the case of vIPR, this is the landing networks network-role; used in naming";
\r
1685 leaf untrusted-network-role {
\r
1686 description "In the case of vIPR, this is the tenant oam networks network-role; used in naming";
\r
1689 container security-zone-input-parameters {
\r
1694 grouping security-zone-topology {
\r
1695 container security-zone-topology {
\r
1696 uses allotted-resource-identifiers;
\r
1697 uses onap-model-information;
\r
1698 uses security-zone-assignments;
\r
1699 container security-zone-parameters {
\r
1704 grouping security-zone-assignments {
\r
1705 container security-zone-assignments {
\r
1706 leaf trusted-network-role {
\r
1707 description "In the case of vIPR, this is the landing networks network-role; used in naming";
\r
1710 leaf security-zone-name-trusted {
\r
1713 leaf untrusted-network-role {
\r
1714 description "In the case of vIPR, this is the tenant oam networks network-role; used in naming";
\r
1717 leaf security-zone-name-untrusted {
\r
1720 leaf security-zone-service-instance-id {
\r
1721 description "Will be the same as the parent-service-instance-id";
\r
1724 leaf security-zone-vnf-id {
\r
1725 description "Selected by SDNC from the security-zone-service-instance-id";
\r
1733 grouping port-mirror-topology-operation-information {
\r
1734 uses sdnc-request-header;
\r
1735 uses request-information;
\r
1736 uses service-information;
\r
1737 uses configuration-information;
\r
1738 uses port-mirror-configuration-request-input;
\r
1740 grouping port-mirror-configuration-request-input {
\r
1741 container port-mirror-configuration-request-input {
\r
1742 container source-port {
\r
1744 leaf source-port-id {
\r
1745 description "needed for srv-action=disable/enable";
\r
1749 container dest-port {
\r
1752 uses region-identifier;
\r
1753 container port-mirror-configuration-input-parameters {
\r
1758 grouping port-info {
\r
1759 leaf service-instance-id {
\r
1760 description "May not be need.";
\r
1763 uses pnf-information;
\r
1764 uses vnf-information;
\r
1766 grouping port-mirror-configuration-topology {
\r
1767 container port-mirror-configuration-topology {
\r
1768 uses configuration-identifiers;
\r
1769 uses onap-model-information;
\r
1770 uses port-mirror-configuration-assignments;
\r
1771 container port-mirror-configuration-parameters {
\r
1776 grouping port-mirror-configuration-assignments {
\r
1777 container port-mirror-configuration-assignments {
\r
1778 container contrail-vmi-params {
\r
1781 leaf vnics-group-id {
\r
1784 leaf owning-entity {
\r
1787 leaf tenant-context {
\r
1788 description "From tenant object in A&AI";
\r
1792 description "Tenant name from A&AI for source VNF";
\r
1796 description "tenant-id from A&AI for source VNF";
\r
1799 leaf dest-tenant {
\r
1800 description "Tenant name from A&AI for destination VNF";
\r
1803 leaf dest-tenant-id {
\r
1804 description "tenant-id from A&AI for destination VNF";
\r
1807 leaf cloud-region-id {
\r
1810 leaf cloud-owner {
\r
1813 leaf dest-network-fqdn {
\r
1816 leaf source-network-fqdn {
\r
1819 leaf source-capacity {
\r
1820 description "Source port pps (packets per second) rating from tosca model";
\r
1823 leaf source-vnf-id {
\r
1826 leaf dest-vnf-id {
\r
1827 description "For vProbe";
\r
1830 leaf dest-pnf-name {
\r
1831 description "For pProbe";
\r
1834 leaf dest-p-interface {
\r
1835 description "For pProbe; from policy manager";
\r
1838 leaf dest-pnf-port-policy-name {
\r
1839 description "For pProbe; from tosca model";
\r
1843 description "vprobe or pprobe; derived from configuration-information.configuration-sub-type";
\r
1846 leaf route-allotted-resource-id {
\r
1847 description "For vProbe";
\r
1850 container source-vnfc-instance-group-id {
\r
1851 leaf service-instance-id {
\r
1854 leaf nfc-naming-code {
\r
1857 leaf instance-group-role {
\r
1860 leaf configuration-id {
\r
1864 container dest-vnfc-instance-group-id {
\r
1865 leaf service-instance-id {
\r
1868 leaf nfc-naming-code {
\r
1871 leaf instance-group-role {
\r
1874 leaf configuration-id {
\r
1878 container source-to-dest-maps {
\r
1879 list source-to-dest-map {
\r
1880 key "source-port-id";
\r
1881 leaf source-port-id {
\r
1885 leaf source-port-name {
\r
1888 leaf source-vserver-id {
\r
1891 leaf dest-vserver-id {
\r
1894 leaf dest-port-id {
\r
1897 leaf dest-port-name {
\r
1903 container dest-ip-addresses {
\r
1904 uses ip-addresses;
\r
1910 grouping gc-topology-operation-information {
\r
1911 uses sdnc-request-header;
\r
1912 uses request-information;
\r
1913 uses service-information;
\r
1914 uses configuration-information;
\r
1915 uses gc-request-input;
\r
1917 grouping gc-request-input {
\r
1918 container gc-request-input {
\r
1922 leaf vf-module-id {
\r
1923 description "This is mandatory in case of rebuild";
\r
1926 container input-parameters {
\r
1930 description "Value will indicate what to rebuild";
\r
1933 list configuration-ids {
\r
1934 key "configuration-id";
\r
1935 leaf configuration-id {
\r
1941 grouping vnr-parameters {
\r
1942 container vnr-parameters {
\r
1946 leaf vf-module-id {
\r
1947 description "This is mandatory in case of rebuild";
\r
1950 leaf vnf-service-instance-id {
\r
1953 leaf network-collection-service-instance-id {
\r
1954 description "service instance id that created network-collection";
\r
1957 leaf network-instance-group-id {
\r
1963 leaf vnfc-instance-group-function {
\r
1966 leaf network-instance-group-function {
\r
1969 leaf parent-port-role {
\r
1972 leaf upper-tag-id {
\r
1975 leaf lower-tag-id {
\r
1980 grouping tunnelxconn-operation-information {
\r
1981 uses sdnc-request-header;
\r
1982 uses request-information;
\r
1983 uses service-information;
\r
1984 uses allotted-resource-information;
\r
1985 uses tunnelxconn-request-input;
\r
1987 grouping tunnelxconn-request-input {
\r
1989 container tunnelxconn-request-input {
\r
1990 leaf brg-wan-mac-address {
\r
1995 grouping tunnelxconn-topology {
\r
1996 container tunnelxconn-topology {
\r
1997 uses allotted-resource-identifiers;
\r
1998 uses onap-model-information;
\r
1999 uses tunnelxconn-assignments;
\r
2000 container tunnelxconn-parameters {
\r
2005 grouping tunnelxconn-assignments {
\r
2006 container tunnelxconn-assignments {
\r
2008 description "The Network Controller will assign a VNI value from the associated vGMUX VNI pool";
\r
2011 leaf vgmux-bearer-ip {
\r
2012 description "The Network Controller will look up the vgmux bearer ip from the vgmux vf module";
\r
2013 type inet:ip-address;
\r
2015 leaf vgmux-lan-ip {
\r
2016 description "The Network Controller will look up the vgmux lan ip from the vgmux vg module";
\r
2017 type inet:ip-address;
\r
2020 description "The Network Controller will assign the VG IP address from local inventory";
\r
2021 type inet:ip-address;
\r
2025 grouping brg-operation-information {
\r
2026 uses sdnc-request-header;
\r
2027 uses request-information;
\r
2028 uses service-information;
\r
2029 uses allotted-resource-information;
\r
2030 uses brg-request-input;
\r
2032 grouping brg-request-input {
\r
2033 container brg-request-input {
\r
2034 leaf vgmux-bearer-ip {
\r
2035 type inet:ip-address;
\r
2040 leaf brg-wan-mac-address {
\r
2045 grouping brg-topology {
\r
2046 container brg-topology {
\r
2047 uses allotted-resource-identifiers;
\r
2048 uses onap-model-information;
\r
2049 uses brg-assignments;
\r
2050 container brg-parameters {
\r
2055 grouping brg-assignments {
\r
2056 container brg-assignments {
\r
2057 leaf vbrg-wan-ip {
\r
2058 type inet:ip-address;
\r
2062 grouping connection-attachment-operation-information {
\r
2063 uses sdnc-request-header;
\r
2064 uses request-information;
\r
2065 uses service-information;
\r
2066 uses allotted-resource-information;
\r
2067 uses connection-attachment-request-input;
\r
2070 grouping connection-attachment-request-input {
\r
2071 container connection-attachment-request-input {
\r
2076 grouping connection-attachment-topology {
\r
2077 container connection-attachment-topology {
\r
2078 uses allotted-resource-identifiers;
\r
2079 uses onap-model-information;
\r
2080 uses connection-attachment-assignments;
\r
2081 container connection-attachment-parameters {
\r
2087 grouping connection-attachment-assignments {
\r
2088 container connection-attachment-assignments {
\r
2092 grouping vnf-vnr-rebuild-data {
\r
2093 container vnf-vnr-rebuild-data {
\r
2097 leaf vnf-service-instance-id {
\r
2101 key "configuration-id";
\r
2102 leaf configuration-id {
\r
2105 leaf network-instance-group-id {
\r
2111 leaf vnfc-instance-group-function {
\r
2114 leaf network-instance-group-function {
\r
2117 leaf parent-port-role {
\r
2120 leaf upper-tag-id {
\r
2123 leaf lower-tag-id {
\r
2129 grouping allotted-resource-information {
\r
2130 container allotted-resource-information {
\r
2131 leaf allotted-resource-id {
\r
2134 leaf allotted-resource-type {
\r
2135 description "Not an enum, but expected values are contrail-route and security-zone.";
\r
2138 leaf parent-service-instance-id {
\r
2139 description "Service-instance-id of the parent service to which this allotted resource belongs.";
\r
2142 uses onap-model-information;
\r
2145 grouping allotted-resource-identifiers {
\r
2146 container allotted-resource-identifiers {
\r
2147 leaf allotted-resource-id {
\r
2150 leaf allotted-resource-name {
\r
2151 description "For a contrail-route, the network policy name.";
\r
2154 leaf allotted-resource-type {
\r
2155 description "(Added in draft 32)Expected to be contrail-route or security-zone.";
\r
2158 leaf consuming-service-instance-id {
\r
2159 description "The service-instance-id of the consuming service of this allotted resource";
\r
2162 leaf parent-service-instance-id {
\r
2163 description "Service-instance-id of the parent service to which this allotted resource belongs.";
\r
2168 grouping allotted-resource-oper-status {
\r
2169 container allotted-resource-oper-status {
\r
2170 uses oper-status-data;
\r
2173 grouping allotted-resource-status {
\r
2174 container allotted-resource-status {
\r
2175 leaf response-code {
\r
2178 leaf response-message {
\r
2181 leaf final-indicator {
\r
2184 leaf request-status {
\r
2185 type enumeration {
\r
2186 enum "synccomplete";
\r
2187 enum "asynccomplete";
\r
2188 enum "notifycomplete";
\r
2192 description "value would one of possible request-actions; match the list in service-data oper-status";
\r
2199 description "this is the svc-action from the incoming request";
\r
2200 type enumeration {
\r
2206 enum "deactivate";
\r
2209 leaf response-timestamp {
\r
2214 grouping configuration-information {
\r
2215 container configuration-information {
\r
2216 leaf configuration-id {
\r
2219 leaf configuration-name {
\r
2222 leaf configuration-type {
\r
2223 description "Not an enum, but expected values are port-mirror-configuration, vlan-network-receptor";
\r
2226 leaf configuration-sub-type {
\r
2227 description "e.g. vprobe and pprobe when configuration-type=port-mirror-configuration";
\r
2230 uses onap-model-information;
\r
2233 grouping configuration-identifiers {
\r
2234 container configuration-identifiers {
\r
2235 leaf configuration-id {
\r
2238 leaf configuration-name {
\r
2241 leaf configuration-type {
\r
2242 description "Not an enum, but expected values are port-mirror-configuration.";
\r
2245 leaf configuration-sub-type {
\r
2246 description " vprobe and pprobe";
\r
2249 leaf parent-service-instance-id {
\r
2250 description "Service-instance-id of the parent service to which this resource belongs.";
\r
2255 grouping configuration-oper-status {
\r
2256 container configuration-oper-status {
\r
2257 uses oper-status-data;
\r
2260 grouping configuration-status {
\r
2261 container configuration-status {
\r
2262 leaf response-code {
\r
2265 leaf response-message {
\r
2268 leaf final-indicator {
\r
2271 leaf request-status {
\r
2272 type enumeration {
\r
2273 enum "synccomplete";
\r
2274 enum "asynccomplete";
\r
2275 enum "notifycomplete";
\r
2279 description "value would one of possible request-actions; match the list in service-data oper-status";
\r
2286 description "this is the svc-action from the incoming request";
\r
2287 type enumeration {
\r
2295 enum "deactivate";
\r
2298 leaf response-timestamp {
\r
2303 grouping topology-response-common {
\r
2304 leaf svc-request-id {
\r
2305 description "the request id from the request message for which this is the responseKeep as M";
\r
2308 leaf response-code {
\r
2309 description "a success code or an defined error codeKeep as M";
\r
2312 leaf response-message {
\r
2313 description "message included for error code";
\r
2316 leaf ack-final-indicator {
\r
2317 description "Expected to be Y or N.";
\r
2321 grouping sdnc-request-header {
\r
2322 container sdnc-request-header {
\r
2323 leaf svc-request-id {
\r
2324 description "Uniquely generated by calling system (e.g. MSO or SDN-GP)";
\r
2328 description "This is the rpcAction";
\r
2329 type enumeration {
\r
2334 enum "changeassign";
\r
2335 enum "changedelete";
\r
2337 enum "deactivate";
\r
2343 enum "reoptimize";
\r
2347 leaf svc-notification-url {
\r
2348 description "Contains URL for asynchronous response";
\r
2353 grouping request-information {
\r
2354 container request-information {
\r
2356 description "Request ID generated upstream of MSO";
\r
2359 leaf request-action {
\r
2360 description "still need to work Disconnect";
\r
2361 type enumeration {
\r
2362 enum "CreateNetworkInstance";
\r
2363 enum "ActivateNetworkInstance";
\r
2364 enum "DeActivateNetworkInstance";
\r
2365 enum "CreateServiceInstance";
\r
2366 enum "DeleteServiceInstance";
\r
2367 enum "DeleteNetworkInstance";
\r
2368 enum "CreateVnfInstance";
\r
2369 enum "ActivateVnfInstance";
\r
2370 enum "DeleteVnfInstance";
\r
2371 enum "CreateVfModuleInstance";
\r
2372 enum "ActivateVfModuleInstance";
\r
2373 enum "DeleteVfModuleInstance";
\r
2374 enum "CreateContrailRouteInstance";
\r
2375 enum "DeleteContrailRouteInstance";
\r
2376 enum "CreateSecurityZoneInstance";
\r
2377 enum "DeleteSecurityZoneInstance";
\r
2378 enum "ActivateDCINetworkInstance";
\r
2379 enum "DeActivateDCINetworkInstance";
\r
2380 enum "CreateTunnelXConnInstance";
\r
2381 enum "DeleteTunnelXConnInstance";
\r
2382 enum "CreateBRGInstance";
\r
2383 enum "DeleteBRGInstance";
\r
2384 enum "CreateSOTNConnectivityInstance";
\r
2385 enum "ActivateSOTNConnectivityInstance";
\r
2386 enum "DeactivateSOTNConnectivityInstance";
\r
2387 enum "DeleteSOTNConnectivityInstance";
\r
2388 enum "CreateSOTNAttachmentInstance";
\r
2389 enum "ActivateSOTNAttachmentInstance";
\r
2390 enum "DeactivateSOTNAttachmentInstance";
\r
2391 enum "DeleteSOTNAttachmentInstance";
\r
2392 enum "CreateSiteInstance";
\r
2393 enum "ActivateSiteInstance";
\r
2394 enum "DeactivateSiteInstance";
\r
2395 enum "DeleteSiteInstance";
\r
2396 enum "CreatePortMirrorConfigurationInstance";
\r
2397 enum "DeletePortMirrorConfigurationInstance";
\r
2398 enum "ChangePortMirrorConfigurationInstance";
\r
2399 enum "CreateGenericConfigurationInstance";
\r
2400 enum "RebuildGenericConfigurationInstance";
\r
2401 enum "DeleteGenericConfigurationInstance";
\r
2402 enum "PreloadVfModuleRequest";
\r
2403 enum "DeletePreloadVfModuleRequest";
\r
2404 enum "PreloadNetworkRequest";
\r
2405 enum "DeletePreloadNetworkRequest";
\r
2406 enum "CreateForwardingPathInstance";
\r
2407 enum "DeleteForwardingPathInstance";
\r
2408 enum "UpdateForwardingPathInstance";
\r
2409 enum "CreateSDWANDeviceInstance";
\r
2410 enum "ActivateSDWANDeviceInstance";
\r
2411 enum "DeactivateSDWANDeviceInstance";
\r
2412 enum "DeleteSDWANDeviceInstance";
\r
2413 enum "CreateSDWANPortInstance";
\r
2414 enum "ActivateSDWANPortInstance";
\r
2415 enum "DeactivateSDWANPortInstance";
\r
2416 enum "DeleteSDWANPortInstance";
\r
2417 enum "ReoptimizeSOTNInstance";
\r
2418 enum "CreateSDWANLanPortInstance";
\r
2419 enum "ActivateSDWANLanPortInstance";
\r
2420 enum "DeactivateSDWANLanPortInstance";
\r
2421 enum "DeleteSDWANLanPortInstance";
\r
2422 enum "CreateSDWANVpnInstance";
\r
2423 enum "ActivateSDWANVpnInstance";
\r
2424 enum "DeactivateSDWANVpnInstance";
\r
2425 enum "DeleteSDWANVpnInstance";
\r
2426 enum "CreateSDWANSiteInstance";
\r
2427 enum "ActivateSDWANSiteInstance";
\r
2428 enum "DeactivateSDWANSiteInstance";
\r
2429 enum "DeleteSDWANSiteInstance";
\r
2430 enum "SdwanBandwidthChange";
\r
2436 leaf notification-url {
\r
2439 leaf order-number {
\r
2442 leaf order-version {
\r
2447 grouping service-information {
\r
2448 container service-information {
\r
2450 description "This maps to the product-family-id in A&AI";
\r
2453 leaf subscription-service-type {
\r
2454 description "used to reference a&ai subscription-service-type. For example, we show as vIPR-ATM in example.";
\r
2457 uses onap-model-information;
\r
2458 leaf service-instance-id {
\r
2461 leaf global-customer-id {
\r
2462 description "need for put of data to AnAI (MSO provides)";
\r
2465 leaf subscriber-name {
\r
2466 description "Would not be expected for vIPR-ATM or mobility services.";
\r
2471 grouping onap-model-information {
\r
2472 container onap-model-information {
\r
2473 leaf model-invariant-uuid {
\r
2474 description "identifies the invariant uuid for this service or resource";
\r
2477 leaf model-customization-uuid {
\r
2478 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
2482 description "identifies the uuid for this service or resource, which is version specific";
\r
2485 leaf model-version {
\r
2493 grouping region-identifier {
\r
2497 leaf aic-cloud-region {
\r
2498 description "The AIC cloud region which maps to contrail versions";
\r
2501 leaf cloud-owner {
\r
2502 description "The cloud owner provided by the caller";
\r
2506 description "Not expected to be used";
\r
2519 container resource-resolution-data {
\r
2520 list resource-key {
\r
2530 description "SUCCESS, FAILED, or PENDING - RA returned data as capability";
\r
2533 leaf capability-name {
\r
2534 description "Resource assignment resolution Capability name";
\r
2540 grouping ip-addresses {
\r
2541 container ip-addresses {
\r
2542 leaf ipv4-address {
\r
2543 type inet:ip-address;
\r
2545 leaf ipv6-address {
\r
2546 type inet:ip-address;
\r
2548 leaf vipv4-address {
\r
2549 description "Virtual v4";
\r
2550 type inet:ip-address;
\r
2552 leaf vipv6-address {
\r
2553 description "Virtual v6";
\r
2554 type inet:ip-address;
\r
2558 grouping instance-reference {
\r
2559 leaf instance-id {
\r
2562 leaf object-path {
\r
2563 description "restconf retrieval path to this particular objectE.g. restconf/config/GENERIC-RESOURCE-API:services/service/$service-instance-id/service-data/service-topology/";
\r
2567 grouping oper-status-data {
\r
2568 leaf order-status {
\r
2569 description "TBD - do we need Request failed statuses? RequestFailed | InProgressTimeout";
\r
2570 type enumeration {
\r
2572 enum "PendingAssignment";
\r
2573 enum "PendingCreate";
\r
2574 enum "PendingUpdate";
\r
2575 enum "PendingDelete";
\r
2580 leaf last-rpc-action {
\r
2581 type enumeration {
\r
2586 enum "deactivate";
\r
2588 enum "changeassign";
\r
2589 enum "reoptimize";
\r
2592 leaf last-action {
\r
2593 description "should be list of possible request-actions";
\r
2594 type enumeration {
\r
2595 enum "CreateNetworkInstance";
\r
2596 enum "ActivateNetworkInstance";
\r
2597 enum "DeActivateNetworkInstance";
\r
2598 enum "CreateServiceInstance";
\r
2599 enum "DeleteServiceInstance";
\r
2600 enum "DeleteNetworkInstance";
\r
2601 enum "CreateVnfInstance";
\r
2602 enum "ActivateVnfInstance";
\r
2603 enum "DeleteVnfInstance";
\r
2604 enum "CreateVfModuleInstance";
\r
2605 enum "ActivateVfModuleInstance";
\r
2606 enum "DeleteVfModuleInstance";
\r
2607 enum "CreateContrailRouteInstance";
\r
2608 enum "DeleteContrailRouteInstance";
\r
2609 enum "CreateSecurityZoneInstance";
\r
2610 enum "DeleteSecurityZoneInstance";
\r
2611 enum "ActivateDCINetworkInstance";
\r
2612 enum "DeActivateDCINetworkInstance";
\r
2613 enum "CreateTunnelXConnInstance";
\r
2614 enum "DeleteTunnelXConnInstance";
\r
2615 enum "CreateBRGInstance";
\r
2616 enum "DeleteBRGInstance";
\r
2617 enum "CreateSOTNConnectivityInstance";
\r
2618 enum "ActivateSOTNConnectivityInstance";
\r
2619 enum "DeactivateSOTNConnectivityInstance";
\r
2620 enum "DeleteSOTNConnectivityInstance";
\r
2621 enum "CreateSOTNAttachmentInstance";
\r
2622 enum "ActivateSOTNAttachmentInstance";
\r
2623 enum "DeactivateSOTNAttachmentInstance";
\r
2624 enum "DeleteSOTNAttachmentInstance";
\r
2625 enum "CreateSiteInstance";
\r
2626 enum "ActivateSiteInstance";
\r
2627 enum "DeactivateSiteInstance";
\r
2628 enum "DeleteSiteInstance";
\r
2629 enum "CreatePortMirrorConfigurationInstance";
\r
2630 enum "DeletePortMirrorConfigurationInstance";
\r
2631 enum "ChangePortMirrorConfigurationInstance";
\r
2632 enum "CreateGenericConfigurationInstance";
\r
2633 enum "DeleteGenericConfigurationInstance";
\r
2634 enum "PreloadVfModuleRequest";
\r
2635 enum "DeletePreloadVfModuleRequest";
\r
2636 enum "PreloadNetworkRequest";
\r
2637 enum "DeletePreloadNetworkRequest";
\r
2638 enum "CreateForwardingPathInstance";
\r
2639 enum "DeleteForwardingPathInstance";
\r
2640 enum "UpdateForwardingPathInstance";
\r
2641 enum "CreateSDWANDeviceInstance";
\r
2642 enum "ActivateSDWANDeviceInstance";
\r
2643 enum "DeactivateSDWANDeviceInstance";
\r
2644 enum "DeleteSDWANDeviceInstance";
\r
2645 enum "CreateSDWANPortInstance";
\r
2646 enum "ActivateSDWANPortInstance";
\r
2647 enum "DeactivateSDWANPortInstance";
\r
2648 enum "DeleteSDWANPortInstance";
\r
2649 enum "ReoptimizeSOTNInstance";
\r
2650 enum "CreateSDWANLanPortInstance";
\r
2651 enum "ActivateSDWANLanPortInstance";
\r
2652 enum "DeactivateSDWANLanPortInstance";
\r
2653 enum "DeleteSDWANLanPortInstance";
\r
2654 enum "CreateSDWANVpnInstance";
\r
2655 enum "ActivateSDWANVpnInstance";
\r
2656 enum "DeactivateSDWANVpnInstance";
\r
2657 enum "DeleteSDWANVpnInstance";
\r
2658 enum "CreateSDWANSiteInstance";
\r
2659 enum "ActivateSDWANSiteInstance";
\r
2660 enum "DeactivateSDWANSiteInstance";
\r
2661 enum "DeleteSDWANSiteInstance";
\r
2662 enum "SdwanBandwidthChange";
\r
2665 leaf last-svc-request-id {
\r
2666 description "Not currently populated in service data.";
\r
2669 leaf last-order-status {
\r
2670 type enumeration {
\r
2672 enum "PendingAssignment";
\r
2673 enum "PendingCreate";
\r
2674 enum "PendingUpdate";
\r
2675 enum "PendingDelete";
\r
2680 leaf create-timestamp {
\r
2681 description "Not currently populated in service data.";
\r
2684 leaf modify-timestamp {
\r
2688 grouping service-response-information {
\r
2689 container service-response-information {
\r
2690 uses instance-reference;
\r
2693 grouping network-response-information {
\r
2694 container network-response-information {
\r
2695 uses instance-reference;
\r
2698 grouping vnf-response-information {
\r
2699 container vnf-response-information {
\r
2700 uses instance-reference;
\r
2703 grouping vf-module-response-information {
\r
2704 container vf-module-response-information {
\r
2705 uses instance-reference;
\r
2708 grouping contrail-route-response-information {
\r
2709 container contrail-route-response-information {
\r
2710 uses instance-reference;
\r
2713 grouping security-zone-response-information {
\r
2714 container security-zone-response-information {
\r
2715 uses instance-reference;
\r
2718 grouping getpathsegment-response-information {
\r
2719 container getpathsegment-response-information {
\r
2720 uses instance-reference;
\r
2723 grouping port-mirror-response-information {
\r
2724 container port-mirror-response-information {
\r
2725 uses instance-reference;
\r
2728 grouping gc-response-information {
\r
2729 container gc-response-information {
\r
2730 uses instance-reference;
\r
2733 grouping tunnelxconn-response-information {
\r
2734 container tunnelxconn-response-information {
\r
2735 uses instance-reference;
\r
2738 grouping brg-response-information {
\r
2739 container brg-response-information {
\r
2740 uses instance-reference;
\r
2743 grouping connection-attachment-response-information {
\r
2744 container connection-attachment-response-information {
\r
2745 uses instance-reference;
\r
2748 grouping preload-model-information {
\r
2749 list preload-list {
\r
2750 key "preload-id preload-type";
\r
2752 description "vf-module-name or network name";
\r
2756 leaf preload-type {
\r
2757 description "network or vf-module";
\r
2761 uses preload-data;
\r
2764 grouping preload-data {
\r
2765 container preload-data {
\r
2766 uses preload-vf-module-topology-information;
\r
2767 uses preload-network-topology-information;
\r
2768 uses preload-oper-status;
\r
2771 grouping preload-vf-module-topology-information {
\r
2772 container preload-vf-module-topology-information {
\r
2773 uses vnf-topology-identifier-structure;
\r
2774 uses vnf-resource-assignments;
\r
2775 uses vf-module-topology;
\r
2778 grouping preload-network-topology-information {
\r
2779 container preload-network-topology-information {
\r
2780 uses network-topology-identifier-structure;
\r
2782 uses vpn-bindings;
\r
2783 uses network-policy;
\r
2784 uses route-table-reference;
\r
2786 uses provider-network-information;
\r
2789 grouping subnets {
\r
2791 key "start-address";
\r
2792 leaf start-address {
\r
2793 type inet:ip-address;
\r
2795 leaf gateway-address {
\r
2796 type inet:ip-address;
\r
2804 leaf dhcp-enabled {
\r
2805 type enumeration {
\r
2810 leaf dhcp-start-address {
\r
2813 leaf dhcp-end-address {
\r
2816 leaf addr-from-start {
\r
2817 description "Default is N";
\r
2818 type enumeration {
\r
2823 leaf subnet-name {
\r
2826 leaf subnet-role {
\r
2829 leaf subnet-sequence {
\r
2834 grouping vpn-bindings {
\r
2835 list vpn-bindings {
\r
2836 key "vpn-binding-id";
\r
2837 leaf vpn-binding-id {
\r
2843 leaf global-route-target {
\r
2846 leaf route-target-role {
\r
2850 description "AIC Zone the route target associated with";
\r
2855 grouping network-policy {
\r
2856 list network-policy {
\r
2857 key "network-policy-fqdn";
\r
2858 leaf network-policy-fqdn {
\r
2861 leaf network-policy-id {
\r
2866 grouping route-table-reference {
\r
2867 list route-table-reference {
\r
2868 key "route-table-reference-fqdn";
\r
2869 leaf route-table-reference-fqdn {
\r
2873 leaf route-table-reference-id {
\r
2878 grouping provider-network-information {
\r
2879 leaf physical-network-name {
\r
2882 leaf is-provider-network {
\r
2885 leaf is-shared-network {
\r
2888 leaf is-external-network {
\r
2892 grouping host-routes {
\r
2893 list host-routes {
\r
2894 key "route-prefix";
\r
2895 leaf route-prefix {
\r
2899 description "Could be ip-address or hostname or service-instance";
\r
2904 grouping preload-oper-status {
\r
2905 container preload-oper-status {
\r
2906 leaf order-status {
\r
2907 type enumeration {
\r
2909 enum "PendingAssignment";
\r
2910 enum "PendingCreate";
\r
2911 enum "PendingUpdate";
\r
2912 enum "PendingDelete";
\r
2916 leaf last-action {
\r
2917 type enumeration {
\r
2918 enum "PreloadVfModuleRequest";
\r
2919 enum "DeletePreloadVfModuleRequest";
\r
2920 enum "PreloadNetworkRequest";
\r
2921 enum "DeletePreloadNetworkRequest";
\r
2924 leaf last-svc-request-id {
\r
2927 leaf last-order-status {
\r
2928 type enumeration {
\r
2930 enum "PendingAssignment";
\r
2931 enum "PendingCreate";
\r
2932 enum "PendingUpdate";
\r
2933 enum "PendingDelete";
\r
2937 leaf create-timestamp {
\r
2940 leaf modify-timestamp {
\r
2943 leaf maintenance-indicator {
\r
2944 type enumeration {
\r
2951 grouping preload-topology-response-body {
\r
2952 leaf svc-request-id {
\r
2955 leaf response-code {
\r
2958 leaf response-message {
\r
2961 leaf ack-final-indicator {
\r
2965 rpc generic-configuration-notification {
\r
2967 uses sdnc-request-header;
\r
2968 uses request-information;
\r
2969 uses service-information;
\r
2970 uses configuration-information;
\r
2971 uses topology-response-common;
\r
2972 leaf configuration-topology-link {
\r
2973 description "Returns URL to generic-configuration-topology ";
\r
2976 uses vnr-parameters;
\r
2977 uses vnf-vnr-rebuild-data;
\r
2980 container services {
\r
2981 uses service-model-infrastructure;
\r
2983 container contrail-route-allotted-resources {
\r
2984 list contrail-route-allotted-resource {
\r
2985 key "allotted-resource-id";
\r
2986 leaf allotted-resource-id {
\r
2990 container allotted-resource-data {
\r
2991 container allotted-resource-operation-information {
\r
2992 uses contrail-route-operation-information;
\r
2994 uses contrail-route-topology;
\r
2995 uses allotted-resource-oper-status;
\r
2997 uses allotted-resource-status;
\r
3000 container security-zone-allotted-resources {
\r
3001 list security-zone-allotted-resource {
\r
3002 key "allotted-resource-id";
\r
3003 leaf allotted-resource-id {
\r
3007 container allotted-resource-data {
\r
3008 container allotted-resource-operation-information {
\r
3009 uses security-zone-operation-information;
\r
3011 uses security-zone-topology;
\r
3012 container security-zone-parameters {
\r
3015 uses allotted-resource-oper-status;
\r
3017 uses allotted-resource-status;
\r
3020 container tunnelxconn-allotted-resources {
\r
3021 list tunnelxconn-allotted-resource {
\r
3022 key "allotted-resource-id";
\r
3023 leaf allotted-resource-id {
\r
3027 container allotted-resource-data {
\r
3028 container allotted-resource-operation-information {
\r
3029 uses tunnelxconn-operation-information;
\r
3031 uses tunnelxconn-topology;
\r
3032 container tunnelxconn-parameters {
\r
3035 uses allotted-resource-oper-status;
\r
3037 uses allotted-resource-status;
\r
3040 container brg-allotted-resources {
\r
3041 list brg-allotted-resource {
\r
3042 key "allotted-resource-id";
\r
3043 leaf allotted-resource-id {
\r
3047 container allotted-resource-data {
\r
3048 container allotted-resource-operation-information {
\r
3049 uses brg-operation-information;
\r
3051 uses brg-topology;
\r
3052 container brg-parameters {
\r
3055 uses allotted-resource-oper-status;
\r
3057 uses allotted-resource-status;
\r
3060 container connection-attachment-allotted-resources {
\r
3061 list connection-attachment-allotted-resource {
\r
3062 key "allotted-resource-id";
\r
3063 leaf allotted-resource-id {
\r
3067 container allotted-resource-data {
\r
3068 container allotted-resource-operation-information {
\r
3069 uses connection-attachment-operation-information;
\r
3071 uses connection-attachment-topology;
\r
3072 container connection-attachment-parameters {
\r
3075 uses allotted-resource-oper-status;
\r
3077 uses allotted-resource-status;
\r
3080 container port-mirror-configurations {
\r
3081 list port-mirror-configuration {
\r
3082 key "configuration-id";
\r
3083 leaf configuration-id {
\r
3087 container configuration-data {
\r
3088 container configuration-operation-information {
\r
3089 uses port-mirror-topology-operation-information;
\r
3091 uses port-mirror-configuration-topology;
\r
3092 uses configuration-oper-status;
\r
3094 uses configuration-status;
\r
3097 container generic-configurations {
\r
3098 list gc-configuration {
\r
3099 key "configuration-id";
\r
3100 leaf configuration-id {
\r
3104 container configuration-data {
\r
3105 container configuration-operation-information {
\r
3106 uses gc-topology-operation-information;
\r
3108 uses configuration-oper-status;
\r
3110 uses configuration-status;
\r
3113 rpc service-topology-operation {
\r
3115 uses service-operation-information;
\r
3118 uses topology-response-common;
\r
3119 uses service-response-information;
\r
3122 rpc network-topology-operation {
\r
3124 uses network-operation-information;
\r
3127 uses topology-response-common;
\r
3128 uses network-response-information;
\r
3129 uses service-response-information;
\r
3132 rpc vnf-topology-operation {
\r
3134 uses vnf-operation-information;
\r
3137 uses topology-response-common;
\r
3138 uses vnf-response-information;
\r
3139 uses service-response-information;
\r
3142 rpc vf-module-topology-operation {
\r
3144 uses vf-module-operation-information;
\r
3147 uses topology-response-common;
\r
3148 uses vf-module-response-information;
\r
3149 uses vnf-response-information;
\r
3150 uses service-response-information;
\r
3153 rpc contrail-route-topology-operation {
\r
3155 uses contrail-route-operation-information;
\r
3158 uses topology-response-common;
\r
3159 uses contrail-route-response-information;
\r
3160 uses service-response-information;
\r
3163 rpc security-zone-topology-operation {
\r
3165 uses security-zone-operation-information;
\r
3168 uses topology-response-common;
\r
3169 uses security-zone-response-information;
\r
3170 uses service-response-information;
\r
3173 rpc tunnelxconn-topology-operation {
\r
3175 uses tunnelxconn-operation-information;
\r
3178 uses topology-response-common;
\r
3179 uses tunnelxconn-response-information;
\r
3180 uses service-response-information;
\r
3183 rpc brg-topology-operation {
\r
3185 uses brg-operation-information;
\r
3188 uses topology-response-common;
\r
3189 uses brg-response-information;
\r
3190 uses service-response-information;
\r
3193 rpc policy-update-notify-operation {
\r
3195 leaf policy-name {
\r
3200 description "Map JSON versionNo to version-id";
\r
3204 leaf update-type {
\r
3218 rpc getpathsegment-topology-operation {
\r
3220 uses forwarding-path-operation-information;
\r
3223 uses topology-response-common;
\r
3224 uses getpathsegment-response-information;
\r
3225 uses service-response-information;
\r
3228 rpc port-mirror-topology-operation {
\r
3230 uses port-mirror-topology-operation-information;
\r
3233 uses topology-response-common;
\r
3234 uses port-mirror-response-information;
\r
3235 uses service-response-information;
\r
3238 rpc generic-configuration-topology-operation {
\r
3240 uses gc-topology-operation-information;
\r
3243 uses topology-response-common;
\r
3244 uses gc-response-information;
\r
3245 uses service-response-information;
\r
3248 rpc vnf-get-resource-request {
\r
3250 uses sdnc-request-header;
\r
3251 uses request-information;
\r
3252 uses service-information;
\r
3253 uses vnf-get-resource-request-input-data;
\r
3256 container vnf-get-resource-response-information {
\r
3257 uses vnf-cloud-param;
\r
3261 container preload-information {
\r
3262 uses preload-model-information;
\r
3264 rpc preload-vf-module-topology-operation {
\r
3266 uses sdnc-request-header;
\r
3267 uses request-information;
\r
3268 uses preload-vf-module-topology-information;
\r
3271 uses preload-topology-response-body;
\r
3274 rpc preload-network-topology-operation {
\r
3276 uses sdnc-request-header;
\r
3277 uses request-information;
\r
3278 uses preload-network-topology-information;
\r
3281 uses preload-topology-response-body;
\r
3285 rpc connection-attachment-topology-operation {
\r
3287 uses connection-attachment-operation-information;
\r
3290 uses topology-response-common;
\r
3291 uses connection-attachment-response-information;
\r
3292 uses service-response-information;
\r
3296 } ////closes the module
\r
Code Review / sdnc / northbound.git / blob