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
712 grouping vm-topology-data {
\r
717 uses onap-model-information;
\r
718 leaf nfc-naming-code {
\r
719 description "used in vm naming(draft 29: changed from nfc-code)";
\r
723 description "from tosca data on vfc";
\r
729 container vm-names {
\r
730 leaf-list vm-name {
\r
739 container vnfc-networks {
\r
740 uses vnfc-network-data;
\r
744 container vm-networks {
\r
746 key "network-role";
\r
747 uses vm-network-data;
\r
751 grouping vnfc-network-data {
\r
752 list vnfc-network-data {
\r
753 key "vnfc-network-role";
\r
754 leaf vnfc-network-role {
\r
761 uses connection-point;
\r
762 container vnfc-ports {
\r
764 key "vnfc-port-id";
\r
765 leaf vnfc-port-id {
\r
766 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
770 leaf common-sub-interface-role {
\r
771 description "If sub-interfaces have common interface role (network role)";
\r
774 container vnic-sub-interfaces {
\r
775 uses sub-interface-network-data;
\r
780 key "vnfc-subnet-role";
\r
781 leaf vnfc-subnet-role {
\r
782 description "Default value if subnet role is not defined.";
\r
786 list vnfc-ip-assignments {
\r
787 key "vnfc-address-family";
\r
788 leaf vnfc-address-family {
\r
789 description "indicates if this is IpV4 or IpV6";
\r
795 leaf vnfc-subnet-dhcp {
\r
796 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
802 leaf vnfc-subnet-ip-count {
\r
803 description "The number of IP addresses to be assigned per vnfc for this subnet role";
\r
806 list vnfc-subnet-ip {
\r
807 key "vnfc-ip-address";
\r
808 leaf vnfc-ip-address {
\r
809 description "Either IpV4 IP or IpV6 IP addresses should be present";
\r
810 type inet:ip-address;
\r
812 leaf vnfc-client-key {
\r
816 description "Capture what type of IP this is, if is virtual IP (AKA, floating IP) or Fixed IP. ";
\r
827 grouping vm-network-data {
\r
828 leaf network-role {
\r
829 description "network (identified by role) that this VM connects to. Should also be included in the vnf-networks for the containing VNF";
\r
833 leaf network-role-tag {
\r
836 container network-information-items {
\r
837 list network-information-item {
\r
840 description "Use ipv4 or ipv6";
\r
844 description "Indicator to use DHCP on this network for this VM";
\r
851 description "The number of ip addresses to be assigned per vm for this network role";
\r
854 container network-ips {
\r
855 leaf-list network-ip {
\r
856 description "List of assigned ip addresses of type ip-version on a network";
\r
863 container mac-addresses {
\r
864 leaf-list mac-address {
\r
865 description "List of network assignments for this vm-type";
\r
870 container floating-ips {
\r
871 leaf-list floating-ip-v4 {
\r
872 description "Floating ipv4 for VMs of a given type on this network";
\r
873 type inet:ip-address;
\r
876 leaf-list floating-ip-v6 {
\r
877 description "Floating ipv6 for VMs of a given type on this network";
\r
878 type inet:ipv6-address;
\r
882 container interface-route-prefixes {
\r
883 leaf-list interface-route-prefix {
\r
884 description "ordered-by: user";
\r
889 container sriov-parameters {
\r
890 container heat-vlan-filters {
\r
891 leaf-list heat-vlan-filter {
\r
896 container application-tags {
\r
914 leaf segmentation-id {
\r
917 container related-networks {
\r
918 uses related-network;
\r
921 grouping vf-module-level-oper-status {
\r
922 container vf-module-level-oper-status {
\r
923 uses oper-status-data;
\r
926 grouping allotted-resource-info {
\r
927 leaf allotted-resource-id {
\r
930 leaf allotted-resource-type {
\r
931 description "Not an enum, but expected values are contrail-route and security-zone.";
\r
934 leaf allotted-resource-pointer {
\r
935 description "Pointer to the allotted-resources topology";
\r
939 grouping forwarding-path-operation-information {
\r
940 uses sdnc-request-header;
\r
941 uses request-information;
\r
942 uses service-information;
\r
943 uses forwarding-path-request-input;
\r
945 grouping forwarding-path-request-input {
\r
946 container forwarding-path-request-input {
\r
947 list forwarding-paths {
\r
948 key "forwarding-path-name";
\r
949 leaf forwarding-path-name {
\r
950 description "Forwarding-path-name from tosca-model. ";
\r
954 uses onap-model-information;
\r
958 grouping forwarding-path-information {
\r
959 leaf forwarding-path-name {
\r
960 description "Fowarding-path name from TOSCA model, or name generated by SDNC";
\r
963 leaf forwarding-path-type {
\r
964 description "Based on MySQL Forwarding_Path tables path_type value from related TOSCA model";
\r
970 uses onap-model-information;
\r
971 container service-paths {
\r
972 list service-path {
\r
973 key "service-path-instance-id";
\r
974 uses service-path-information;
\r
978 grouping service-path-information {
\r
979 leaf service-path-instance-id {
\r
980 description "Service path instance ID generated by SDNC. Identifies a service-path-instance within a forwarding-path definition";
\r
983 leaf service-path-instance-name {
\r
984 description "A unique name generated by SDNC ( forwarding-path-name + service-path-instance-id )";
\r
988 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
992 key "service-instance-id";
\r
993 leaf service-instance-id {
\r
994 description "service-instance-id of each service-instance in the service-path-instance";
\r
997 leaf service-path-sequence-id {
\r
998 description "e.g. S1S2S3S5seq id=1 S1-S2seq id=2 S2S3seq id=3 S3S5Incremental integer value";
\r
1003 key "vnf-instance-id";
\r
1004 uses vnf-path-information;
\r
1009 grouping vnf-path-information {
\r
1010 leaf vnf-instance-id {
\r
1011 description "VNF instance ID in the path";
\r
1014 leaf vnf-path-sequence-id {
\r
1015 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
1018 leaf left-network-name {
\r
1019 description "Every VNF instance in the path is connected to one or two VNFs.";
\r
1022 leaf left-network-role {
\r
1025 leaf right-network-name {
\r
1028 leaf right-network-role {
\r
1031 container vf-module-instance {
\r
1032 leaf vf-module-id {
\r
1035 leaf vf-module-name {
\r
1040 grouping forwarding-path-level-oper-status {
\r
1041 container forwarding-path-level-oper-status {
\r
1042 uses oper-status-data;
\r
1045 grouping configuration-info {
\r
1046 leaf configuration-id {
\r
1049 leaf configuration-type {
\r
1050 description "Not an enum, but expected values are port-mirror-configuration, , vlan-network-receptor";
\r
1053 leaf configuration-sub-type {
\r
1054 description "Not an enum, but expected values are vprobe and pprobe";
\r
1057 leaf configuration-topology-link {
\r
1058 description "Pointer to the configurations topology";
\r
1062 grouping vnfc-instance-group {
\r
1063 list vnfc-instance-group {
\r
1064 key "instance-group-role nfc-naming-code configuration-id";
\r
1065 leaf instance-group-role {
\r
1066 description "i.e.TSBC_VNFC_group";
\r
1070 leaf nfc-naming-code {
\r
1071 description "Set to nfc-naming-code from A&AI";
\r
1075 leaf configuration-id {
\r
1080 description " port-mirror-source or port-mirror-dest";
\r
1083 uses vnfc-objects;
\r
1086 grouping vnfc-objects {
\r
1087 container vnfc-objects {
\r
1088 list vnfc-object {
\r
1094 description "Vnfc name as key in A&AI";
\r
1103 leaf vserver-name {
\r
1111 key "vnic-port-name";
\r
1112 leaf vnic-port-name {
\r
1115 leaf vnic-port-id {
\r
1118 container capacity {
\r
1119 leaf vnic-capacity {
\r
1122 leaf used-capacity {
\r
1123 description "Updated for destination port when source port is mapped/unmapped.";
\r
1127 container vnic-ip-addresses {
\r
1128 uses ip-addresses;
\r
1140 description "Vnfc name as key in A&AI";
\r
1143 leaf vserver-name {
\r
1156 key "vnic-port-name";
\r
1157 leaf vnic-port-name {
\r
1160 leaf vnic-port-id {
\r
1163 uses sub-interfaces;
\r
1167 grouping sub-interfaces {
\r
1168 container sub-interfaces {
\r
1169 list sub-interface {
\r
1170 key "sub-interface-port-name";
\r
1171 leaf sub-interface-port-name {
\r
1174 leaf sub-interface-port-id {
\r
1177 container sub-interface-ip-addresses {
\r
1178 uses ip-addresses;
\r
1181 container sub-interface-network {
\r
1182 leaf network-name {
\r
1189 leaf sub-interface-status {
\r
1190 description "NULL, unassigned, assigned";
\r
1196 grouping vlan-tags {
\r
1197 container vlan-tags {
\r
1198 leaf vlan-interface {
\r
1199 description "A&AI Key";
\r
1202 leaf upper-tag-id {
\r
1205 leaf lower-tag-id {
\r
1213 grouping vlan-vnfc-instance-groups {
\r
1214 container vlan-vnfc-instance-groups {
\r
1215 list vlan-vnfc-instance-group {
\r
1216 key "instance-group-id";
\r
1217 leaf instance-group-id {
\r
1218 description "A&AI ID";
\r
1222 leaf instance-group-function {
\r
1240 grouping vnic-groups {
\r
1241 container vnic-groups {
\r
1243 key "vnic-interface-role";
\r
1244 leaf vnic-interface-role {
\r
1245 description "Same as network-role of network where vnic is connected";
\r
1249 leaf network-instance-group-function {
\r
1250 description "network-instance-Group-function for network collection where vnics with vnic-interface-role will connect";
\r
1253 leaf vlan-assignment-policy-name {
\r
1254 description "Policy name in ASDC model & policy definition in Policy Engine";
\r
1257 leaf vlan-tag-index-next {
\r
1258 description "Next tag to be assigned";
\r
1261 container vlan-common-ip-addresses {
\r
1262 uses ip-addresses;
\r
1264 container vlan-vnics {
\r
1266 key "vnic-port-id";
\r
1267 leaf vnic-port-id {
\r
1271 container vnic-sub-interfaces {
\r
1272 uses sub-interface-network-data;
\r
1279 grouping vnf-network-collection {
\r
1280 list vnf-network-collection {
\r
1281 key "network-instance-group-function";
\r
1282 leaf network-instance-group-function {
\r
1283 description "Network Instance-Group function in A&AI";
\r
1287 leaf network-instance-group-id {
\r
1288 description "Network Instance-Group id in A&AI";
\r
1291 leaf network-collection-service-instance-id {
\r
1292 description "Service-instance-id of service that created the network collection";
\r
1295 leaf network-collection-customization-uuid {
\r
1296 description "network-collection-customization-uuid stored in Network IsntanceGroup.customization-uuid in A&AI";
\r
1299 container networks {
\r
1303 description "Index into network-topology-identifier structure";
\r
1307 leaf neutron-network-id {
\r
1308 description "Neutron-network-id assigned by PO/RO";
\r
1313 container vnf-floating-ip {
\r
1314 uses ip-addresses;
\r
1318 grouping vnf-sub-interface-group {
\r
1319 list vnf-sub-interface-group {
\r
1320 key "vnfc-instance-group-function network-instance-group-function parent-port-role";
\r
1321 leaf vnfc-instance-group-function {
\r
1325 leaf network-instance-group-function {
\r
1329 leaf parent-port-role {
\r
1334 container customer-bonding-requests {
\r
1335 list customer-bonding-request {
\r
1336 key "configuration-id";
\r
1337 leaf configuration-id {
\r
1338 description "e.g. vlan network receptor configuration id";
\r
1345 grouping sub-interface-network-data {
\r
1346 list sub-interface-network-data {
\r
1349 description "Subinterface network id (UUID in A&AI)";
\r
1353 leaf neutron-network-id {
\r
1354 description "Neutron network id assigned by PO/RP";
\r
1357 leaf network-name {
\r
1358 description "Subinterface network name";
\r
1361 leaf vlan-tag-id {
\r
1362 description "Vlan tag assigned to subinterface port";
\r
1365 leaf network-role {
\r
1366 description "e.g. untrusted ";
\r
1369 leaf network-role-tag {
\r
1370 description "Assuming HEAT template network role tag parameter - not used";
\r
1373 container network-information-items {
\r
1374 list network-information-item {
\r
1377 description "Use ipv4 or ipv6";
\r
1381 description "Indicator to use DHCP on this network for this VM - set to N for Vlan tagging";
\r
1382 type enumeration {
\r
1388 description "The number of ip addresses to be assigned per vm for this network role";
\r
1391 container network-ips {
\r
1392 leaf-list network-ip {
\r
1393 description "List of assigned ip addresses of type ip-version on a network.";
\r
1394 type inet:ip-address;
\r
1400 container floating-ips {
\r
1401 leaf-list floating-ip-v4 {
\r
1402 description "Floating ipv4 for VMs of a given type on this network";
\r
1403 type inet:ip-address;
\r
1406 leaf-list floating-ip-v6 {
\r
1407 description "Floating ipv6 for VMs of a given type on this network";
\r
1408 type inet:ipv6-address;
\r
1414 grouping vnf-cloud-param {
\r
1415 leaf service-instance-id {
\r
1418 leaf service-instance-name {
\r
1431 key "vf-module-id";
\r
1432 leaf vf-module-id {
\r
1439 grouping vnf-get-resource-request-input-data {
\r
1446 key "vf-module-id";
\r
1447 leaf vf-module-id {
\r
1453 grouping license-information {
\r
1454 container license-information {
\r
1455 list entitlement-pool-list {
\r
1456 key "entitlement-pool-uuid action";
\r
1457 leaf entitlement-pool-uuid {
\r
1465 leaf entitlement-pool-invariant-uuid {
\r
1468 leaf entitlement-uuid {
\r
1469 description "assigned by ALTS";
\r
1473 list license-key-group-list {
\r
1474 key "license-key-group-uuid action";
\r
1475 leaf license-key-group-uuid {
\r
1483 leaf license-key-group-invariant-uuid {
\r
1486 leaf license-key {
\r
1487 description "assigned by ALTS";
\r
1490 leaf license-uuid {
\r
1491 description "assigned by ALTS";
\r
1497 grouping related-network {
\r
1498 list related-network {
\r
1501 description "Key to l3-network object";
\r
1504 leaf network-role {
\r
1510 grouping connection-point {
\r
1511 container connection-point {
\r
1512 leaf connection-point-id {
\r
1513 description "Key to CP object in A&AI";
\r
1517 description "port-index when multiple CPs connect to same network. Default zero (0)";
\r
1523 description "Key to vlan-tag uuid object in A&AI Generated by vlan mS";
\r
1526 leaf vlan-tag-id {
\r
1529 leaf vlan-tag-description {
\r
1533 description "Inner/Outer roles";
\r
1539 grouping aggregate-routes {
\r
1540 list aggregate-routes {
\r
1543 description "Unique id";
\r
1546 leaf start-address {
\r
1547 type inet:ip-address;
\r
1553 description "Use values 4 or 6.";
\r
1558 grouping pnf-information {
\r
1559 container pnf-information {
\r
1561 description "Key for A&AI query";
\r
1567 uses onap-model-information;
\r
1570 grouping contrail-route-operation-information {
\r
1571 uses sdnc-request-header;
\r
1572 uses request-information;
\r
1573 uses service-information;
\r
1574 uses allotted-resource-information;
\r
1575 uses contrail-route-request-input;
\r
1577 grouping contrail-route-request-input {
\r
1578 container contrail-route-request-input {
\r
1579 container source-network {
\r
1580 uses network-info;
\r
1582 container dest-network {
\r
1583 uses network-info;
\r
1585 container contrail-applied-service-info {
\r
1586 leaf service-instance-id {
\r
1587 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
1590 leaf contrail-fqdn {
\r
1591 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
1595 container contrail-route-input-parameters {
\r
1600 grouping network-info {
\r
1604 leaf network-role {
\r
1608 grouping contrail-route-topology {
\r
1609 container contrail-route-topology {
\r
1610 uses allotted-resource-identifiers;
\r
1611 uses onap-model-information;
\r
1612 uses contrail-route-assignments;
\r
1613 container contrail-route-parameters {
\r
1618 grouping contrail-route-assignments {
\r
1619 container contrail-route-assignments {
\r
1621 description "The Contrail fq-name of the network policy";
\r
1624 leaf contrail-id {
\r
1625 description "The ID assigned by Contrail to the network-policy (one for one with the fq-name)";
\r
1628 container source-network {
\r
1629 uses network-info;
\r
1631 container dest-network {
\r
1632 uses network-info;
\r
1634 container contrail-applied-service {
\r
1635 leaf service-instance-id {
\r
1636 description "The service-instance-id of the vnf from which the contrail applied service is coming";
\r
1640 description "The vnf representing the contrail applied service";
\r
1643 leaf contrail-fqdn {
\r
1644 description "This is the fq-name of the Contrail service instance through which the route is passing.";
\r
1649 description "Contrail-assigned vlan-tag to the vipr vm interface for this route.";
\r
1654 grouping security-zone-operation-information {
\r
1655 uses sdnc-request-header;
\r
1656 uses request-information;
\r
1657 uses service-information;
\r
1658 uses allotted-resource-information;
\r
1659 uses security-zone-request-input;
\r
1661 grouping security-zone-request-input {
\r
1662 container security-zone-request-input {
\r
1666 leaf trusted-network-role {
\r
1667 description "In the case of vIPR, this is the landing networks network-role; used in naming";
\r
1670 leaf untrusted-network-role {
\r
1671 description "In the case of vIPR, this is the tenant oam networks network-role; used in naming";
\r
1674 container security-zone-input-parameters {
\r
1679 grouping security-zone-topology {
\r
1680 container security-zone-topology {
\r
1681 uses allotted-resource-identifiers;
\r
1682 uses onap-model-information;
\r
1683 uses security-zone-assignments;
\r
1684 container security-zone-parameters {
\r
1689 grouping security-zone-assignments {
\r
1690 container security-zone-assignments {
\r
1691 leaf trusted-network-role {
\r
1692 description "In the case of vIPR, this is the landing networks network-role; used in naming";
\r
1695 leaf security-zone-name-trusted {
\r
1698 leaf untrusted-network-role {
\r
1699 description "In the case of vIPR, this is the tenant oam networks network-role; used in naming";
\r
1702 leaf security-zone-name-untrusted {
\r
1705 leaf security-zone-service-instance-id {
\r
1706 description "Will be the same as the parent-service-instance-id";
\r
1709 leaf security-zone-vnf-id {
\r
1710 description "Selected by SDNC from the security-zone-service-instance-id";
\r
1718 grouping port-mirror-topology-operation-information {
\r
1719 uses sdnc-request-header;
\r
1720 uses request-information;
\r
1721 uses service-information;
\r
1722 uses configuration-information;
\r
1723 uses port-mirror-configuration-request-input;
\r
1725 grouping port-mirror-configuration-request-input {
\r
1726 container port-mirror-configuration-request-input {
\r
1727 container source-port {
\r
1729 leaf source-port-id {
\r
1730 description "needed for srv-action=disable/enable";
\r
1734 container dest-port {
\r
1737 uses region-identifier;
\r
1738 container port-mirror-configuration-input-parameters {
\r
1743 grouping port-info {
\r
1744 leaf service-instance-id {
\r
1745 description "May not be need.";
\r
1748 uses pnf-information;
\r
1749 uses vnf-information;
\r
1751 grouping port-mirror-configuration-topology {
\r
1752 container port-mirror-configuration-topology {
\r
1753 uses configuration-identifiers;
\r
1754 uses onap-model-information;
\r
1755 uses port-mirror-configuration-assignments;
\r
1756 container port-mirror-configuration-parameters {
\r
1761 grouping port-mirror-configuration-assignments {
\r
1762 container port-mirror-configuration-assignments {
\r
1763 container contrail-vmi-params {
\r
1766 leaf vnics-group-id {
\r
1769 leaf owning-entity {
\r
1772 leaf tenant-context {
\r
1773 description "From tenant object in A&AI";
\r
1777 description "Tenant name from A&AI for source VNF";
\r
1781 description "tenant-id from A&AI for source VNF";
\r
1784 leaf dest-tenant {
\r
1785 description "Tenant name from A&AI for destination VNF";
\r
1788 leaf dest-tenant-id {
\r
1789 description "tenant-id from A&AI for destination VNF";
\r
1792 leaf cloud-region-id {
\r
1795 leaf cloud-owner {
\r
1798 leaf dest-network-fqdn {
\r
1801 leaf source-network-fqdn {
\r
1804 leaf source-capacity {
\r
1805 description "Source port pps (packets per second) rating from tosca model";
\r
1808 leaf source-vnf-id {
\r
1811 leaf dest-vnf-id {
\r
1812 description "For vProbe";
\r
1815 leaf dest-pnf-name {
\r
1816 description "For pProbe";
\r
1819 leaf dest-p-interface {
\r
1820 description "For pProbe; from policy manager";
\r
1823 leaf dest-pnf-port-policy-name {
\r
1824 description "For pProbe; from tosca model";
\r
1828 description "vprobe or pprobe; derived from configuration-information.configuration-sub-type";
\r
1831 leaf route-allotted-resource-id {
\r
1832 description "For vProbe";
\r
1835 container source-vnfc-instance-group-id {
\r
1836 leaf service-instance-id {
\r
1839 leaf nfc-naming-code {
\r
1842 leaf instance-group-role {
\r
1845 leaf configuration-id {
\r
1849 container dest-vnfc-instance-group-id {
\r
1850 leaf service-instance-id {
\r
1853 leaf nfc-naming-code {
\r
1856 leaf instance-group-role {
\r
1859 leaf configuration-id {
\r
1863 container source-to-dest-maps {
\r
1864 list source-to-dest-map {
\r
1865 key "source-port-id";
\r
1866 leaf source-port-id {
\r
1870 leaf source-port-name {
\r
1873 leaf source-vserver-id {
\r
1876 leaf dest-vserver-id {
\r
1879 leaf dest-port-id {
\r
1882 leaf dest-port-name {
\r
1888 container dest-ip-addresses {
\r
1889 uses ip-addresses;
\r
1895 grouping gc-topology-operation-information {
\r
1896 uses sdnc-request-header;
\r
1897 uses request-information;
\r
1898 uses service-information;
\r
1899 uses configuration-information;
\r
1900 uses gc-request-input;
\r
1902 grouping gc-request-input {
\r
1903 container gc-request-input {
\r
1907 leaf vf-module-id {
\r
1908 description "This is mandatory in case of rebuild";
\r
1911 container input-parameters {
\r
1915 description "Value will indicate what to rebuild";
\r
1918 list configuration-ids {
\r
1919 key "configuration-id";
\r
1920 leaf configuration-id {
\r
1926 grouping vnr-parameters {
\r
1927 container vnr-parameters {
\r
1931 leaf vf-module-id {
\r
1932 description "This is mandatory in case of rebuild";
\r
1935 leaf vnf-service-instance-id {
\r
1938 leaf network-collection-service-instance-id {
\r
1939 description "service instance id that created network-collection";
\r
1942 leaf network-instance-group-id {
\r
1948 leaf vnfc-instance-group-function {
\r
1951 leaf network-instance-group-function {
\r
1954 leaf parent-port-role {
\r
1957 leaf upper-tag-id {
\r
1960 leaf lower-tag-id {
\r
1965 grouping tunnelxconn-operation-information {
\r
1966 uses sdnc-request-header;
\r
1967 uses request-information;
\r
1968 uses service-information;
\r
1969 uses allotted-resource-information;
\r
1970 uses tunnelxconn-request-input;
\r
1972 grouping tunnelxconn-request-input {
\r
1974 container tunnelxconn-request-input {
\r
1975 leaf brg-wan-mac-address {
\r
1980 grouping tunnelxconn-topology {
\r
1981 container tunnelxconn-topology {
\r
1982 uses allotted-resource-identifiers;
\r
1983 uses onap-model-information;
\r
1984 uses tunnelxconn-assignments;
\r
1985 container tunnelxconn-parameters {
\r
1990 grouping tunnelxconn-assignments {
\r
1991 container tunnelxconn-assignments {
\r
1993 description "The Network Controller will assign a VNI value from the associated vGMUX VNI pool";
\r
1996 leaf vgmux-bearer-ip {
\r
1997 description "The Network Controller will look up the vgmux bearer ip from the vgmux vf module";
\r
1998 type inet:ip-address;
\r
2000 leaf vgmux-lan-ip {
\r
2001 description "The Network Controller will look up the vgmux lan ip from the vgmux vg module";
\r
2002 type inet:ip-address;
\r
2005 description "The Network Controller will assign the VG IP address from local inventory";
\r
2006 type inet:ip-address;
\r
2010 grouping brg-operation-information {
\r
2011 uses sdnc-request-header;
\r
2012 uses request-information;
\r
2013 uses service-information;
\r
2014 uses allotted-resource-information;
\r
2015 uses brg-request-input;
\r
2017 grouping brg-request-input {
\r
2018 container brg-request-input {
\r
2019 leaf vgmux-bearer-ip {
\r
2020 type inet:ip-address;
\r
2025 leaf brg-wan-mac-address {
\r
2030 grouping brg-topology {
\r
2031 container brg-topology {
\r
2032 uses allotted-resource-identifiers;
\r
2033 uses onap-model-information;
\r
2034 uses brg-assignments;
\r
2035 container brg-parameters {
\r
2040 grouping brg-assignments {
\r
2041 container brg-assignments {
\r
2042 leaf vbrg-wan-ip {
\r
2043 type inet:ip-address;
\r
2047 grouping connection-attachment-operation-information {
\r
2048 uses sdnc-request-header;
\r
2049 uses request-information;
\r
2050 uses service-information;
\r
2051 uses allotted-resource-information;
\r
2052 uses connection-attachment-request-input;
\r
2055 grouping connection-attachment-request-input {
\r
2056 container connection-attachment-request-input {
\r
2061 grouping connection-attachment-topology {
\r
2062 container connection-attachment-topology {
\r
2063 uses allotted-resource-identifiers;
\r
2064 uses onap-model-information;
\r
2065 uses connection-attachment-assignments;
\r
2066 container connection-attachment-parameters {
\r
2072 grouping connection-attachment-assignments {
\r
2073 container connection-attachment-assignments {
\r
2077 grouping vnf-vnr-rebuild-data {
\r
2078 container vnf-vnr-rebuild-data {
\r
2082 leaf vnf-service-instance-id {
\r
2086 key "configuration-id";
\r
2087 leaf configuration-id {
\r
2090 leaf network-instance-group-id {
\r
2096 leaf vnfc-instance-group-function {
\r
2099 leaf network-instance-group-function {
\r
2102 leaf parent-port-role {
\r
2105 leaf upper-tag-id {
\r
2108 leaf lower-tag-id {
\r
2114 grouping allotted-resource-information {
\r
2115 container allotted-resource-information {
\r
2116 leaf allotted-resource-id {
\r
2119 leaf allotted-resource-type {
\r
2120 description "Not an enum, but expected values are contrail-route and security-zone.";
\r
2123 leaf parent-service-instance-id {
\r
2124 description "Service-instance-id of the parent service to which this allotted resource belongs.";
\r
2127 uses onap-model-information;
\r
2130 grouping allotted-resource-identifiers {
\r
2131 container allotted-resource-identifiers {
\r
2132 leaf allotted-resource-id {
\r
2135 leaf allotted-resource-name {
\r
2136 description "For a contrail-route, the network policy name.";
\r
2139 leaf allotted-resource-type {
\r
2140 description "(Added in draft 32)Expected to be contrail-route or security-zone.";
\r
2143 leaf consuming-service-instance-id {
\r
2144 description "The service-instance-id of the consuming service of this allotted resource";
\r
2147 leaf parent-service-instance-id {
\r
2148 description "Service-instance-id of the parent service to which this allotted resource belongs.";
\r
2153 grouping allotted-resource-oper-status {
\r
2154 container allotted-resource-oper-status {
\r
2155 uses oper-status-data;
\r
2158 grouping allotted-resource-status {
\r
2159 container allotted-resource-status {
\r
2160 leaf response-code {
\r
2163 leaf response-message {
\r
2166 leaf final-indicator {
\r
2169 leaf request-status {
\r
2170 type enumeration {
\r
2171 enum "synccomplete";
\r
2172 enum "asynccomplete";
\r
2173 enum "notifycomplete";
\r
2177 description "value would one of possible request-actions; match the list in service-data oper-status";
\r
2184 description "this is the svc-action from the incoming request";
\r
2185 type enumeration {
\r
2191 enum "deactivate";
\r
2194 leaf response-timestamp {
\r
2199 grouping configuration-information {
\r
2200 container configuration-information {
\r
2201 leaf configuration-id {
\r
2204 leaf configuration-name {
\r
2207 leaf configuration-type {
\r
2208 description "Not an enum, but expected values are port-mirror-configuration, vlan-network-receptor";
\r
2211 leaf configuration-sub-type {
\r
2212 description "e.g. vprobe and pprobe when configuration-type=port-mirror-configuration";
\r
2215 uses onap-model-information;
\r
2218 grouping configuration-identifiers {
\r
2219 container configuration-identifiers {
\r
2220 leaf configuration-id {
\r
2223 leaf configuration-name {
\r
2226 leaf configuration-type {
\r
2227 description "Not an enum, but expected values are port-mirror-configuration.";
\r
2230 leaf configuration-sub-type {
\r
2231 description " vprobe and pprobe";
\r
2234 leaf parent-service-instance-id {
\r
2235 description "Service-instance-id of the parent service to which this resource belongs.";
\r
2240 grouping configuration-oper-status {
\r
2241 container configuration-oper-status {
\r
2242 uses oper-status-data;
\r
2245 grouping configuration-status {
\r
2246 container configuration-status {
\r
2247 leaf response-code {
\r
2250 leaf response-message {
\r
2253 leaf final-indicator {
\r
2256 leaf request-status {
\r
2257 type enumeration {
\r
2258 enum "synccomplete";
\r
2259 enum "asynccomplete";
\r
2260 enum "notifycomplete";
\r
2264 description "value would one of possible request-actions; match the list in service-data oper-status";
\r
2271 description "this is the svc-action from the incoming request";
\r
2272 type enumeration {
\r
2280 enum "deactivate";
\r
2283 leaf response-timestamp {
\r
2288 grouping topology-response-common {
\r
2289 leaf svc-request-id {
\r
2290 description "the request id from the request message for which this is the responseKeep as M";
\r
2293 leaf response-code {
\r
2294 description "a success code or an defined error codeKeep as M";
\r
2297 leaf response-message {
\r
2298 description "message included for error code";
\r
2301 leaf ack-final-indicator {
\r
2302 description "Expected to be Y or N.";
\r
2306 grouping sdnc-request-header {
\r
2307 container sdnc-request-header {
\r
2308 leaf svc-request-id {
\r
2309 description "Uniquely generated by calling system (e.g. MSO or SDN-GP)";
\r
2313 description "This is the rpcAction";
\r
2314 type enumeration {
\r
2319 enum "changeassign";
\r
2320 enum "changedelete";
\r
2322 enum "deactivate";
\r
2328 enum "reoptimize";
\r
2332 leaf svc-notification-url {
\r
2333 description "Contains URL for asynchronous response";
\r
2338 grouping request-information {
\r
2339 container request-information {
\r
2341 description "Request ID generated upstream of MSO";
\r
2344 leaf request-action {
\r
2345 description "still need to work Disconnect";
\r
2346 type enumeration {
\r
2347 enum "CreateNetworkInstance";
\r
2348 enum "ActivateNetworkInstance";
\r
2349 enum "DeActivateNetworkInstance";
\r
2350 enum "CreateServiceInstance";
\r
2351 enum "DeleteServiceInstance";
\r
2352 enum "DeleteNetworkInstance";
\r
2353 enum "CreateVnfInstance";
\r
2354 enum "ActivateVnfInstance";
\r
2355 enum "DeleteVnfInstance";
\r
2356 enum "CreateVfModuleInstance";
\r
2357 enum "ActivateVfModuleInstance";
\r
2358 enum "DeleteVfModuleInstance";
\r
2359 enum "CreateContrailRouteInstance";
\r
2360 enum "DeleteContrailRouteInstance";
\r
2361 enum "CreateSecurityZoneInstance";
\r
2362 enum "DeleteSecurityZoneInstance";
\r
2363 enum "ActivateDCINetworkInstance";
\r
2364 enum "DeActivateDCINetworkInstance";
\r
2365 enum "CreateTunnelXConnInstance";
\r
2366 enum "DeleteTunnelXConnInstance";
\r
2367 enum "CreateBRGInstance";
\r
2368 enum "DeleteBRGInstance";
\r
2369 enum "CreateSOTNConnectivityInstance";
\r
2370 enum "ActivateSOTNConnectivityInstance";
\r
2371 enum "DeactivateSOTNConnectivityInstance";
\r
2372 enum "DeleteSOTNConnectivityInstance";
\r
2373 enum "CreateSOTNAttachmentInstance";
\r
2374 enum "ActivateSOTNAttachmentInstance";
\r
2375 enum "DeactivateSOTNAttachmentInstance";
\r
2376 enum "DeleteSOTNAttachmentInstance";
\r
2377 enum "CreateSiteInstance";
\r
2378 enum "ActivateSiteInstance";
\r
2379 enum "DeactivateSiteInstance";
\r
2380 enum "DeleteSiteInstance";
\r
2381 enum "CreatePortMirrorConfigurationInstance";
\r
2382 enum "DeletePortMirrorConfigurationInstance";
\r
2383 enum "ChangePortMirrorConfigurationInstance";
\r
2384 enum "CreateGenericConfigurationInstance";
\r
2385 enum "RebuildGenericConfigurationInstance";
\r
2386 enum "DeleteGenericConfigurationInstance";
\r
2387 enum "PreloadVfModuleRequest";
\r
2388 enum "DeletePreloadVfModuleRequest";
\r
2389 enum "PreloadNetworkRequest";
\r
2390 enum "DeletePreloadNetworkRequest";
\r
2391 enum "CreateForwardingPathInstance";
\r
2392 enum "DeleteForwardingPathInstance";
\r
2393 enum "UpdateForwardingPathInstance";
\r
2394 enum "CreateSDWANConnectivityInstance";
\r
2395 enum "ActivateSDWANConnectivityInstance";
\r
2396 enum "DeactivateSDWANConnectivityInstance";
\r
2397 enum "DeleteSDWANConnectivityInstance";
\r
2398 enum "CreateSDWANDeviceInstance";
\r
2399 enum "ActivateSDWANDeviceInstance";
\r
2400 enum "DeactivateSDWANDeviceInstance";
\r
2401 enum "DeleteSDWANDeviceInstance";
\r
2402 enum "CreateSDWANPortInstance";
\r
2403 enum "ActivateSDWANPortInstance";
\r
2404 enum "DeactivateSDWANPortInstance";
\r
2405 enum "DeleteSDWANPortInstance";
\r
2406 enum "CreateSDWANAttachmentInstance";
\r
2407 enum "ActivateSDWANAttachmentInstance";
\r
2408 enum "DeactivateSDWANAttachmentInstance";
\r
2409 enum "DeleteSDWANAttachmentInstance";
\r
2410 enum "ReoptimizeSOTNInstance";
\r
2416 leaf notification-url {
\r
2419 leaf order-number {
\r
2422 leaf order-version {
\r
2427 grouping service-information {
\r
2428 container service-information {
\r
2430 description "This maps to the product-family-id in A&AI";
\r
2433 leaf subscription-service-type {
\r
2434 description "used to reference a&ai subscription-service-type. For example, we show as vIPR-ATM in example.";
\r
2437 uses onap-model-information;
\r
2438 leaf service-instance-id {
\r
2441 leaf global-customer-id {
\r
2442 description "need for put of data to AnAI (MSO provides)";
\r
2445 leaf subscriber-name {
\r
2446 description "Would not be expected for vIPR-ATM or mobility services.";
\r
2451 grouping onap-model-information {
\r
2452 container onap-model-information {
\r
2453 leaf model-invariant-uuid {
\r
2454 description "identifies the invariant uuid for this service or resource";
\r
2457 leaf model-customization-uuid {
\r
2458 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
2462 description "identifies the uuid for this service or resource, which is version specific";
\r
2465 leaf model-version {
\r
2473 grouping region-identifier {
\r
2477 leaf aic-cloud-region {
\r
2478 description "The AIC cloud region which maps to contrail versions";
\r
2481 leaf cloud-owner {
\r
2482 description "The cloud owner provided by the caller";
\r
2486 description "Not expected to be used";
\r
2499 container resource-resolution-data {
\r
2500 list resource-key {
\r
2510 description "SUCCESS, FAILED, or PENDING - RA returned data as capability";
\r
2513 leaf capability-name {
\r
2514 description "Resource assignment resolution Capability name";
\r
2520 grouping ip-addresses {
\r
2521 container ip-addresses {
\r
2522 leaf ipv4-address {
\r
2523 type inet:ip-address;
\r
2525 leaf ipv6-address {
\r
2526 type inet:ip-address;
\r
2528 leaf vipv4-address {
\r
2529 description "Virtual v4";
\r
2530 type inet:ip-address;
\r
2532 leaf vipv6-address {
\r
2533 description "Virtual v6";
\r
2534 type inet:ip-address;
\r
2538 grouping instance-reference {
\r
2539 leaf instance-id {
\r
2542 leaf object-path {
\r
2543 description "restconf retrieval path to this particular objectE.g. restconf/config/GENERIC-RESOURCE-API:services/service/$service-instance-id/service-data/service-topology/";
\r
2547 grouping oper-status-data {
\r
2548 leaf order-status {
\r
2549 description "TBD - do we need Request failed statuses? RequestFailed | InProgressTimeout";
\r
2550 type enumeration {
\r
2552 enum "PendingAssignment";
\r
2553 enum "PendingCreate";
\r
2554 enum "PendingUpdate";
\r
2555 enum "PendingDelete";
\r
2560 leaf last-rpc-action {
\r
2561 type enumeration {
\r
2566 enum "deactivate";
\r
2568 enum "changeassign";
\r
2569 enum "reoptimize";
\r
2572 leaf last-action {
\r
2573 description "should be list of possible request-actions";
\r
2574 type enumeration {
\r
2575 enum "CreateNetworkInstance";
\r
2576 enum "ActivateNetworkInstance";
\r
2577 enum "DeActivateNetworkInstance";
\r
2578 enum "CreateServiceInstance";
\r
2579 enum "DeleteServiceInstance";
\r
2580 enum "DeleteNetworkInstance";
\r
2581 enum "CreateVnfInstance";
\r
2582 enum "ActivateVnfInstance";
\r
2583 enum "DeleteVnfInstance";
\r
2584 enum "CreateVfModuleInstance";
\r
2585 enum "ActivateVfModuleInstance";
\r
2586 enum "DeleteVfModuleInstance";
\r
2587 enum "CreateContrailRouteInstance";
\r
2588 enum "DeleteContrailRouteInstance";
\r
2589 enum "CreateSecurityZoneInstance";
\r
2590 enum "DeleteSecurityZoneInstance";
\r
2591 enum "ActivateDCINetworkInstance";
\r
2592 enum "DeActivateDCINetworkInstance";
\r
2593 enum "CreateTunnelXConnInstance";
\r
2594 enum "DeleteTunnelXConnInstance";
\r
2595 enum "CreateBRGInstance";
\r
2596 enum "DeleteBRGInstance";
\r
2597 enum "CreateSOTNConnectivityInstance";
\r
2598 enum "ActivateSOTNConnectivityInstance";
\r
2599 enum "DeactivateSOTNConnectivityInstance";
\r
2600 enum "DeleteSOTNConnectivityInstance";
\r
2601 enum "CreateSOTNAttachmentInstance";
\r
2602 enum "ActivateSOTNAttachmentInstance";
\r
2603 enum "DeactivateSOTNAttachmentInstance";
\r
2604 enum "DeleteSOTNAttachmentInstance";
\r
2605 enum "CreateSiteInstance";
\r
2606 enum "ActivateSiteInstance";
\r
2607 enum "DeactivateSiteInstance";
\r
2608 enum "DeleteSiteInstance";
\r
2609 enum "CreatePortMirrorConfigurationInstance";
\r
2610 enum "DeletePortMirrorConfigurationInstance";
\r
2611 enum "ChangePortMirrorConfigurationInstance";
\r
2612 enum "CreateGenericConfigurationInstance";
\r
2613 enum "DeleteGenericConfigurationInstance";
\r
2614 enum "PreloadVfModuleRequest";
\r
2615 enum "DeletePreloadVfModuleRequest";
\r
2616 enum "PreloadNetworkRequest";
\r
2617 enum "DeletePreloadNetworkRequest";
\r
2618 enum "CreateForwardingPathInstance";
\r
2619 enum "DeleteForwardingPathInstance";
\r
2620 enum "UpdateForwardingPathInstance";
\r
2621 enum "CreateSDWANConnectivityInstance";
\r
2622 enum "ActivateSDWANConnectivityInstance";
\r
2623 enum "DeactivateSDWANConnectivityInstance";
\r
2624 enum "DeleteSDWANConnectivityInstance";
\r
2625 enum "CreateSDWANDeviceInstance";
\r
2626 enum "ActivateSDWANDeviceInstance";
\r
2627 enum "DeactivateSDWANDeviceInstance";
\r
2628 enum "DeleteSDWANDeviceInstance";
\r
2629 enum "CreateSDWANPortInstance";
\r
2630 enum "ActivateSDWANPortInstance";
\r
2631 enum "DeactivateSDWANPortInstance";
\r
2632 enum "DeleteSDWANPortInstance";
\r
2633 enum "CreateSDWANAttachmentInstance";
\r
2634 enum "ActivateSDWANAttachmentInstance";
\r
2635 enum "DeactivateSDWANAttachmentInstance";
\r
2636 enum "DeleteSDWANAttachmentInstance";
\r
2637 enum "ReoptimizeSOTNInstance";
\r
2640 leaf last-svc-request-id {
\r
2641 description "Not currently populated in service data.";
\r
2644 leaf last-order-status {
\r
2645 type enumeration {
\r
2647 enum "PendingAssignment";
\r
2648 enum "PendingCreate";
\r
2649 enum "PendingUpdate";
\r
2650 enum "PendingDelete";
\r
2655 leaf create-timestamp {
\r
2656 description "Not currently populated in service data.";
\r
2659 leaf modify-timestamp {
\r
2663 grouping service-response-information {
\r
2664 container service-response-information {
\r
2665 uses instance-reference;
\r
2668 grouping network-response-information {
\r
2669 container network-response-information {
\r
2670 uses instance-reference;
\r
2673 grouping vnf-response-information {
\r
2674 container vnf-response-information {
\r
2675 uses instance-reference;
\r
2678 grouping vf-module-response-information {
\r
2679 container vf-module-response-information {
\r
2680 uses instance-reference;
\r
2683 grouping contrail-route-response-information {
\r
2684 container contrail-route-response-information {
\r
2685 uses instance-reference;
\r
2688 grouping security-zone-response-information {
\r
2689 container security-zone-response-information {
\r
2690 uses instance-reference;
\r
2693 grouping getpathsegment-response-information {
\r
2694 container getpathsegment-response-information {
\r
2695 uses instance-reference;
\r
2698 grouping port-mirror-response-information {
\r
2699 container port-mirror-response-information {
\r
2700 uses instance-reference;
\r
2703 grouping gc-response-information {
\r
2704 container gc-response-information {
\r
2705 uses instance-reference;
\r
2708 grouping tunnelxconn-response-information {
\r
2709 container tunnelxconn-response-information {
\r
2710 uses instance-reference;
\r
2713 grouping brg-response-information {
\r
2714 container brg-response-information {
\r
2715 uses instance-reference;
\r
2718 grouping connection-attachment-response-information {
\r
2719 container connection-attachment-response-information {
\r
2720 uses instance-reference;
\r
2723 grouping preload-model-information {
\r
2724 list preload-list {
\r
2725 key "preload-id preload-type";
\r
2727 description "vf-module-name or network name";
\r
2731 leaf preload-type {
\r
2732 description "network or vf-module";
\r
2736 uses preload-data;
\r
2739 grouping preload-data {
\r
2740 container preload-data {
\r
2741 uses preload-vf-module-topology-information;
\r
2742 uses preload-network-topology-information;
\r
2743 uses preload-oper-status;
\r
2746 grouping preload-vf-module-topology-information {
\r
2747 container preload-vf-module-topology-information {
\r
2748 uses vnf-topology-identifier-structure;
\r
2749 uses vnf-resource-assignments;
\r
2750 uses vf-module-topology;
\r
2753 grouping preload-network-topology-information {
\r
2754 container preload-network-topology-information {
\r
2755 uses network-topology-identifier-structure;
\r
2757 uses vpn-bindings;
\r
2758 uses network-policy;
\r
2759 uses route-table-reference;
\r
2761 uses provider-network-information;
\r
2764 grouping subnets {
\r
2766 key "start-address";
\r
2767 leaf start-address {
\r
2768 type inet:ip-address;
\r
2770 leaf gateway-address {
\r
2771 type inet:ip-address;
\r
2779 leaf dhcp-enabled {
\r
2780 type enumeration {
\r
2785 leaf dhcp-start-address {
\r
2788 leaf dhcp-end-address {
\r
2791 leaf addr-from-start {
\r
2792 description "Default is N";
\r
2793 type enumeration {
\r
2798 leaf subnet-name {
\r
2801 leaf subnet-role {
\r
2804 leaf subnet-sequence {
\r
2809 grouping vpn-bindings {
\r
2810 list vpn-bindings {
\r
2811 key "vpn-binding-id";
\r
2812 leaf vpn-binding-id {
\r
2818 leaf global-route-target {
\r
2821 leaf route-target-role {
\r
2825 description "AIC Zone the route target associated with";
\r
2830 grouping network-policy {
\r
2831 list network-policy {
\r
2832 key "network-policy-fqdn";
\r
2833 leaf network-policy-fqdn {
\r
2836 leaf network-policy-id {
\r
2841 grouping route-table-reference {
\r
2842 list route-table-reference {
\r
2843 key "route-table-reference-fqdn";
\r
2844 leaf route-table-reference-fqdn {
\r
2848 leaf route-table-reference-id {
\r
2853 grouping provider-network-information {
\r
2854 leaf physical-network-name {
\r
2857 leaf is-provider-network {
\r
2860 leaf is-shared-network {
\r
2863 leaf is-external-network {
\r
2867 grouping host-routes {
\r
2868 list host-routes {
\r
2869 key "route-prefix";
\r
2870 leaf route-prefix {
\r
2874 description "Could be ip-address or hostname or service-instance";
\r
2879 grouping preload-oper-status {
\r
2880 container preload-oper-status {
\r
2881 leaf order-status {
\r
2882 type enumeration {
\r
2884 enum "PendingAssignment";
\r
2885 enum "PendingCreate";
\r
2886 enum "PendingUpdate";
\r
2887 enum "PendingDelete";
\r
2891 leaf last-action {
\r
2892 type enumeration {
\r
2893 enum "PreloadVfModuleRequest";
\r
2894 enum "DeletePreloadVfModuleRequest";
\r
2895 enum "PreloadNetworkRequest";
\r
2896 enum "DeletePreloadNetworkRequest";
\r
2899 leaf last-svc-request-id {
\r
2902 leaf last-order-status {
\r
2903 type enumeration {
\r
2905 enum "PendingAssignment";
\r
2906 enum "PendingCreate";
\r
2907 enum "PendingUpdate";
\r
2908 enum "PendingDelete";
\r
2912 leaf create-timestamp {
\r
2915 leaf modify-timestamp {
\r
2918 leaf maintenance-indicator {
\r
2919 type enumeration {
\r
2926 grouping preload-topology-response-body {
\r
2927 leaf svc-request-id {
\r
2930 leaf response-code {
\r
2933 leaf response-message {
\r
2936 leaf ack-final-indicator {
\r
2940 rpc generic-configuration-notification {
\r
2942 uses sdnc-request-header;
\r
2943 uses request-information;
\r
2944 uses service-information;
\r
2945 uses configuration-information;
\r
2946 uses topology-response-common;
\r
2947 leaf configuration-topology-link {
\r
2948 description "Returns URL to generic-configuration-topology ";
\r
2951 uses vnr-parameters;
\r
2952 uses vnf-vnr-rebuild-data;
\r
2955 container services {
\r
2956 uses service-model-infrastructure;
\r
2958 container contrail-route-allotted-resources {
\r
2959 list contrail-route-allotted-resource {
\r
2960 key "allotted-resource-id";
\r
2961 leaf allotted-resource-id {
\r
2965 container allotted-resource-data {
\r
2966 container allotted-resource-operation-information {
\r
2967 uses contrail-route-operation-information;
\r
2969 uses contrail-route-topology;
\r
2970 uses allotted-resource-oper-status;
\r
2972 uses allotted-resource-status;
\r
2975 container security-zone-allotted-resources {
\r
2976 list security-zone-allotted-resource {
\r
2977 key "allotted-resource-id";
\r
2978 leaf allotted-resource-id {
\r
2982 container allotted-resource-data {
\r
2983 container allotted-resource-operation-information {
\r
2984 uses security-zone-operation-information;
\r
2986 uses security-zone-topology;
\r
2987 container security-zone-parameters {
\r
2990 uses allotted-resource-oper-status;
\r
2992 uses allotted-resource-status;
\r
2995 container tunnelxconn-allotted-resources {
\r
2996 list tunnelxconn-allotted-resource {
\r
2997 key "allotted-resource-id";
\r
2998 leaf allotted-resource-id {
\r
3002 container allotted-resource-data {
\r
3003 container allotted-resource-operation-information {
\r
3004 uses tunnelxconn-operation-information;
\r
3006 uses tunnelxconn-topology;
\r
3007 container tunnelxconn-parameters {
\r
3010 uses allotted-resource-oper-status;
\r
3012 uses allotted-resource-status;
\r
3015 container brg-allotted-resources {
\r
3016 list brg-allotted-resource {
\r
3017 key "allotted-resource-id";
\r
3018 leaf allotted-resource-id {
\r
3022 container allotted-resource-data {
\r
3023 container allotted-resource-operation-information {
\r
3024 uses brg-operation-information;
\r
3026 uses brg-topology;
\r
3027 container brg-parameters {
\r
3030 uses allotted-resource-oper-status;
\r
3032 uses allotted-resource-status;
\r
3035 container connection-attachment-allotted-resources {
\r
3036 list connection-attachment-allotted-resource {
\r
3037 key "allotted-resource-id";
\r
3038 leaf allotted-resource-id {
\r
3042 container allotted-resource-data {
\r
3043 container allotted-resource-operation-information {
\r
3044 uses connection-attachment-operation-information;
\r
3046 uses connection-attachment-topology;
\r
3047 container connection-attachment-parameters {
\r
3050 uses allotted-resource-oper-status;
\r
3052 uses allotted-resource-status;
\r
3055 container port-mirror-configurations {
\r
3056 list port-mirror-configuration {
\r
3057 key "configuration-id";
\r
3058 leaf configuration-id {
\r
3062 container configuration-data {
\r
3063 container configuration-operation-information {
\r
3064 uses port-mirror-topology-operation-information;
\r
3066 uses port-mirror-configuration-topology;
\r
3067 uses configuration-oper-status;
\r
3069 uses configuration-status;
\r
3072 container generic-configurations {
\r
3073 list gc-configuration {
\r
3074 key "configuration-id";
\r
3075 leaf configuration-id {
\r
3079 container configuration-data {
\r
3080 container configuration-operation-information {
\r
3081 uses gc-topology-operation-information;
\r
3083 uses configuration-oper-status;
\r
3085 uses configuration-status;
\r
3088 rpc service-topology-operation {
\r
3090 uses service-operation-information;
\r
3093 uses topology-response-common;
\r
3094 uses service-response-information;
\r
3097 rpc network-topology-operation {
\r
3099 uses network-operation-information;
\r
3102 uses topology-response-common;
\r
3103 uses network-response-information;
\r
3104 uses service-response-information;
\r
3107 rpc vnf-topology-operation {
\r
3109 uses vnf-operation-information;
\r
3112 uses topology-response-common;
\r
3113 uses vnf-response-information;
\r
3114 uses service-response-information;
\r
3117 rpc vf-module-topology-operation {
\r
3119 uses vf-module-operation-information;
\r
3122 uses topology-response-common;
\r
3123 uses vf-module-response-information;
\r
3124 uses vnf-response-information;
\r
3125 uses service-response-information;
\r
3128 rpc contrail-route-topology-operation {
\r
3130 uses contrail-route-operation-information;
\r
3133 uses topology-response-common;
\r
3134 uses contrail-route-response-information;
\r
3135 uses service-response-information;
\r
3138 rpc security-zone-topology-operation {
\r
3140 uses security-zone-operation-information;
\r
3143 uses topology-response-common;
\r
3144 uses security-zone-response-information;
\r
3145 uses service-response-information;
\r
3148 rpc tunnelxconn-topology-operation {
\r
3150 uses tunnelxconn-operation-information;
\r
3153 uses topology-response-common;
\r
3154 uses tunnelxconn-response-information;
\r
3155 uses service-response-information;
\r
3158 rpc brg-topology-operation {
\r
3160 uses brg-operation-information;
\r
3163 uses topology-response-common;
\r
3164 uses brg-response-information;
\r
3165 uses service-response-information;
\r
3168 rpc policy-update-notify-operation {
\r
3170 leaf policy-name {
\r
3175 description "Map JSON versionNo to version-id";
\r
3179 leaf update-type {
\r
3193 rpc getpathsegment-topology-operation {
\r
3195 uses forwarding-path-operation-information;
\r
3198 uses topology-response-common;
\r
3199 uses getpathsegment-response-information;
\r
3200 uses service-response-information;
\r
3203 rpc port-mirror-topology-operation {
\r
3205 uses port-mirror-topology-operation-information;
\r
3208 uses topology-response-common;
\r
3209 uses port-mirror-response-information;
\r
3210 uses service-response-information;
\r
3213 rpc generic-configuration-topology-operation {
\r
3215 uses gc-topology-operation-information;
\r
3218 uses topology-response-common;
\r
3219 uses gc-response-information;
\r
3220 uses service-response-information;
\r
3223 rpc vnf-get-resource-request {
\r
3225 uses sdnc-request-header;
\r
3226 uses request-information;
\r
3227 uses service-information;
\r
3228 uses vnf-get-resource-request-input-data;
\r
3231 container vnf-get-resource-response-information {
\r
3232 uses vnf-cloud-param;
\r
3236 container preload-information {
\r
3237 uses preload-model-information;
\r
3239 rpc preload-vf-module-topology-operation {
\r
3241 uses sdnc-request-header;
\r
3242 uses request-information;
\r
3243 uses preload-vf-module-topology-information;
\r
3246 uses preload-topology-response-body;
\r
3249 rpc preload-network-topology-operation {
\r
3251 uses sdnc-request-header;
\r
3252 uses request-information;
\r
3253 uses preload-network-topology-information;
\r
3256 uses preload-topology-response-body;
\r
3260 rpc connection-attachment-topology-operation {
\r
3262 uses connection-attachment-operation-information;
\r
3265 uses topology-response-common;
\r
3266 uses connection-attachment-response-information;
\r
3267 uses service-response-information;
\r
3271 } ////closes the module
\r
Code Review / sdnc / northbound.git / blob