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 "2010-09-24"; }
\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
406 leaf network-status {
\r
407 description "assigned, unassigned";
\r
410 container customer-bonding-requests {
\r
411 list customer-bonding-request {
\r
412 key "configuration-id";
\r
413 leaf configuration-id {
\r
414 description "e.g. vlan network receptor configuration id";
\r
423 grouping network-level-oper-status {
\r
424 container network-level-oper-status {
\r
425 uses oper-status-data;
\r
428 grouping vnf-operation-information {
\r
429 uses sdnc-request-header;
\r
430 uses request-information;
\r
431 uses service-information;
\r
432 uses vnf-information;
\r
433 uses vnf-request-input;
\r
434 uses license-information;
\r
436 grouping vnf-information {
\r
437 container vnf-information {
\r
447 uses onap-model-information;
\r
450 grouping vnf-request-input {
\r
451 container vnf-request-input {
\r
452 leaf request-version {
\r
458 uses region-identifier;
\r
459 container vnf-networks {
\r
461 key "network-role";
\r
462 uses vnf-network-data;
\r
465 list vnf-network-instance-group-ids {
\r
466 key "vnf-network-instance-group-id";
\r
467 leaf vnf-network-instance-group-id {
\r
468 description "List of vnf network-instance-group";
\r
472 container vnf-input-parameters {
\r
477 grouping vnf-topology {
\r
478 container vnf-topology {
\r
479 uses vnf-topology-identifier-structure;
\r
480 uses region-identifier;
\r
481 uses onap-model-information;
\r
482 uses vnf-resource-assignments;
\r
483 container vnf-parameters-data {
\r
486 leaf sdnc-generated-cloud-resources {
\r
487 description "Indicate if source is sdnc generated cloud param";
\r
492 grouping vnf-topology-identifier-structure {
\r
493 container vnf-topology-identifier-structure {
\r
498 description "In preload tree, this label is used for the vf-module-type";
\r
511 description "used in vnf naming";
\r
515 description "optionally comes from vnf-request-input container or is assigned by sdn-c";
\r
520 grouping vnf-resource-assignments {
\r
521 container vnf-resource-assignments {
\r
523 description "Orchestration status from AAI - to be set by SDNC";
\r
526 container availability-zones {
\r
527 leaf-list availability-zone {
\r
528 description "Openstack availability zone name or UUID";
\r
533 description "From the TOSCA data. Indicates the largest availability zone count needed by any vf-module in the VNF.";
\r
537 container vnf-networks {
\r
539 key "network-role";
\r
540 uses vnf-network-data;
\r
545 grouping vnf-network-data {
\r
546 leaf network-role {
\r
547 description "A Network Role to which a VNF must connect";
\r
550 leaf network-name {
\r
551 description "Unique Neutron UUID of an instance of the network role ";
\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
562 leaf contrail-network-fqdn {
\r
563 description "contrail network policy object";
\r
566 container subnets-data {
\r
568 key "sdnc-subnet-id";
\r
569 leaf sdnc-subnet-id {
\r
570 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
574 description "Subnet Role for the subnet";
\r
578 description "Populated for preload only";
\r
582 description "Should be ipv4 or ipv6";
\r
586 description "subnet UUID to be passed into the HEAT template";
\r
589 leaf dhcp-enabled {
\r
590 description "Indicator to use this subnet for DHCP ";
\r
596 leaf network-start-address {
\r
597 description "start-address of the subnet";
\r
598 type inet:ip-address;
\r
600 leaf gateway-address {
\r
601 description "subnet gateway address";
\r
602 type inet:ip-address;
\r
605 description "cidr mask";
\r
613 leaf segmentation-id {
\r
616 container related-networks {
\r
617 uses related-network;
\r
620 grouping vnf-level-oper-status {
\r
621 container vnf-level-oper-status {
\r
622 uses oper-status-data;
\r
625 grouping vf-module-operation-information {
\r
626 uses sdnc-request-header;
\r
627 uses request-information;
\r
628 uses service-information;
\r
629 uses vnf-information;
\r
630 uses vf-module-information;
\r
631 uses vf-module-request-input;
\r
633 grouping vf-module-information {
\r
634 container vf-module-information {
\r
635 leaf vf-module-id {
\r
638 leaf vf-module-type {
\r
641 leaf from-preload {
\r
642 description "Indicates if source is preload data";
\r
645 uses onap-model-information;
\r
648 grouping vf-module-request-input {
\r
649 container vf-module-request-input {
\r
650 leaf request-version {
\r
651 description "keep this?";
\r
654 leaf vf-module-name {
\r
657 uses region-identifier;
\r
658 container vf-module-input-parameters {
\r
663 grouping vf-module-topology {
\r
664 container vf-module-topology {
\r
665 uses vf-module-topology-identifier;
\r
666 uses region-identifier;
\r
667 uses onap-model-information;
\r
668 uses vf-module-assignments;
\r
669 container vf-module-parameters {
\r
672 leaf sdnc-generated-cloud-resources {
\r
673 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
678 grouping vf-module-topology-identifier {
\r
679 container vf-module-topology-identifier {
\r
680 leaf vf-module-id {
\r
681 description "vf-module id";
\r
684 leaf vf-module-name {
\r
685 description "vf-module-name";
\r
688 leaf vf-module-type {
\r
693 grouping vf-module-assignments {
\r
694 container vf-module-assignments {
\r
695 leaf vf-module-status {
\r
696 description "Orchestration status from AAI - to be set by SDNC";
\r
702 uses vm-topology-data;
\r
705 uses vlan-vnfc-instance-groups;
\r
708 grouping vm-topology-data {
\r
713 uses onap-model-information;
\r
714 leaf nfc-naming-code {
\r
715 description "used in vm naming(draft 29: changed from nfc-code)";
\r
719 description "from tosca data on vfc";
\r
725 container vm-names {
\r
726 leaf-list vm-name {
\r
735 container vnfc-networks {
\r
736 uses vnfc-network-data;
\r
740 container vm-networks {
\r
742 key "network-role";
\r
743 uses vm-network-data;
\r
747 grouping vnfc-network-data {
\r
748 list vnfc-network-data {
\r
749 key "vnfc-network-role";
\r
750 leaf vnfc-network-role {
\r
757 uses connection-point;
\r
758 container vnfc-ports {
\r
760 key "vnfc-port-id";
\r
761 leaf vnfc-port-id {
\r
762 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
766 leaf common-sub-interface-role {
\r
767 description "If sub-interfaces have common interface role (network role)";
\r
770 container vnic-sub-interfaces {
\r
771 uses sub-interface-network-data;
\r
776 key "vnfc-subnet-role";
\r
777 leaf vnfc-subnet-role {
\r
778 description "Default value if subnet role is not defined.";
\r
782 list vnfc-ip-assignments {
\r
783 key "vnfc-address-family";
\r
784 leaf vnfc-address-family {
\r
785 description "indicates if this is IpV4 or IpV6";
\r
791 leaf vnfc-subnet-dhcp {
\r
792 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
798 leaf vnfc-subnet-ip-count {
\r
799 description "The number of IP addresses to be assigned per vnfc for this subnet role";
\r
802 list vnfc-subnet-ip {
\r
803 key "vnfc-ip-address";
\r
804 leaf vnfc-ip-address {
\r
805 description "Either IpV4 IP or IpV6 IP addresses should be present";
\r
806 type inet:ip-address;
\r
808 leaf vnfc-client-key {
\r
812 description "Capture what type of IP this is, if is virtual IP (AKA, floating IP) or Fixed IP. ";
\r
823 grouping vm-network-data {
\r
824 leaf network-role {
\r
825 description "network (identified by role) that this VM connects to. Should also be included in the vnf-networks for the containing VNF";
\r
829 leaf network-role-tag {
\r
832 container network-information-items {
\r
833 list network-information-item {
\r
836 description "Use ipv4 or ipv6";
\r
840 description "Indicator to use DHCP on this network for this VM";
\r
847 description "The number of ip addresses to be assigned per vm for this network role";
\r
850 container network-ips {
\r
851 leaf-list network-ip {
\r
852 description "List of assigned ip addresses of type ip-version on a network";
\r
859 container mac-addresses {
\r
860 leaf-list mac-address {
\r
861 description "List of network assignments for this vm-type";
\r
866 container floating-ips {
\r
867 leaf-list floating-ip-v4 {
\r
868 description "Floating ipv4 for VMs of a given type on this network";
\r
869 type inet:ip-address;
\r
872 leaf-list floating-ip-v6 {
\r
873 description "Floating ipv6 for VMs of a given type on this network";
\r
874 type inet:ipv6-address;
\r
878 container interface-route-prefixes {
\r
879 leaf-list interface-route-prefix {
\r
880 description "ordered-by: user";
\r
885 container sriov-parameters {
\r
886 container heat-vlan-filters {
\r
887 leaf-list heat-vlan-filter {
\r
892 container application-tags {
\r
910 leaf segmentation-id {
\r
913 container related-networks {
\r
914 uses related-network;
\r
917 grouping vf-module-level-oper-status {
\r
918 container vf-module-level-oper-status {
\r
919 uses oper-status-data;
\r
922 grouping allotted-resource-info {
\r
923 leaf allotted-resource-id {
\r
926 leaf allotted-resource-type {
\r
927 description "Not an enum, but expected values are contrail-route and security-zone.";
\r
930 leaf allotted-resource-pointer {
\r
931 description "Pointer to the allotted-resources topology";
\r
935 grouping forwarding-path-operation-information {
\r
936 uses sdnc-request-header;
\r
937 uses request-information;
\r
938 uses service-information;
\r
939 uses forwarding-path-request-input;
\r
941 grouping forwarding-path-request-input {
\r
942 container forwarding-path-request-input {
\r
943 list forwarding-paths {
\r
944 key "forwarding-path-name";
\r
945 leaf forwarding-path-name {
\r
946 description "Forwarding-path-name from tosca-model. ";
\r
950 uses onap-model-information;
\r
954 grouping forwarding-path-information {
\r
955 leaf forwarding-path-name {
\r
956 description "Fowarding-path name from TOSCA model, or name generated by SDNC";
\r
959 leaf forwarding-path-type {
\r
960 description "Based on MySQL Forwarding_Path tables path_type value from related TOSCA model";
\r
966 uses onap-model-information;
\r
967 container service-paths {
\r
968 list service-path {
\r
969 key "service-path-instance-id";
\r
970 uses service-path-information;
\r
974 grouping service-path-information {
\r
975 leaf service-path-instance-id {
\r
976 description "Service path instance ID generated by SDNC. Identifies a service-path-instance within a forwarding-path definition";
\r
979 leaf service-path-instance-name {
\r
980 description "A unique name generated by SDNC ( forwarding-path-name + service-path-instance-id )";
\r
984 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
988 key "service-instance-id";
\r
989 leaf service-instance-id {
\r
990 description "service-instance-id of each service-instance in the service-path-instance";
\r
993 leaf service-path-sequence-id {
\r
994 description "e.g. S1S2S3S5seq id=1 S1-S2seq id=2 S2S3seq id=3 S3S5Incremental integer value";
\r
999 key "vnf-instance-id";
\r
1000 uses vnf-path-information;
\r
1005 grouping vnf-path-information {
\r
1006 leaf vnf-instance-id {
\r
1007 description "VNF instance ID in the path";
\r
1010 leaf vnf-path-sequence-id {
\r
1011 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
1014 leaf left-network-name {
\r
1015 description "Every VNF instance in the path is connected to one or two VNFs.";
\r
1018 leaf left-network-role {
\r
1021 leaf right-network-name {
\r
1024 leaf right-network-role {
\r
1027 container vf-module-instance {
\r
1028 leaf vf-module-id {
\r
1031 leaf vf-module-name {
\r
1036 grouping forwarding-path-level-oper-status {
\r
1037 container forwarding-path-level-oper-status {
\r
1038 uses oper-status-data;
\r
1041 grouping configuration-info {
\r
1042 leaf configuration-id {
\r
1045 leaf configuration-type {
\r
1046 description "Not an enum, but expected values are port-mirror-configuration, , vlan-network-receptor";
\r
1049 leaf configuration-sub-type {
\r
1050 description "Not an enum, but expected values are vprobe and pprobe";
\r
1053 leaf configuration-topology-link {
\r
1054 description "Pointer to the configurations topology";
\r
1058 grouping vnfc-instance-group {
\r
1059 list vnfc-instance-group {
\r
1060 key "instance-group-role nfc-naming-code configuration-id";
\r
1061 leaf instance-group-role {
\r
1062 description "i.e.TSBC_VNFC_group";
\r
1066 leaf nfc-naming-code {
\r
1067 description "Set to nfc-naming-code from A&AI";
\r
1071 leaf configuration-id {
\r
1076 description " port-mirror-source or port-mirror-dest";
\r
1079 uses vnfc-objects;
\r
1082 grouping vnfc-objects {
\r
1083 container vnfc-objects {
\r
1084 list vnfc-object {
\r
1090 description "Vnfc name as key in A&AI";
\r
1099 leaf vserver-name {
\r
1107 key "vnic-port-name";
\r
1108 leaf vnic-port-name {
\r
1111 leaf vnic-port-id {
\r
1114 container capacity {
\r
1115 leaf vnic-capacity {
\r
1118 leaf used-capacity {
\r
1119 description "Updated for destination port when source port is mapped/unmapped.";
\r
1123 container vnic-ip-addresses {
\r
1124 uses ip-addresses;
\r
1136 description "Vnfc name as key in A&AI";
\r
1139 leaf vserver-name {
\r
1152 key "vnic-port-name";
\r
1153 leaf vnic-port-name {
\r
1156 leaf vnic-port-id {
\r
1159 uses sub-interfaces;
\r
1163 grouping sub-interfaces {
\r
1164 container sub-interfaces {
\r
1165 list sub-interface {
\r
1166 key "sub-interface-port-name";
\r
1167 leaf sub-interface-port-name {
\r
1170 leaf sub-interface-port-id {
\r
1173 container sub-interface-ip-addresses {
\r
1174 uses ip-addresses;
\r
1177 container sub-interface-network {
\r
1178 leaf network-name {
\r
1185 leaf sub-interface-status {
\r
1186 description "NULL, unassigned, assigned";
\r
1192 grouping vlan-tags {
\r
1193 container vlan-tags {
\r
1194 leaf vlan-interface {
\r
1195 description "A&AI Key";
\r
1198 leaf upper-tag-id {
\r
1201 leaf lower-tag-id {
\r
1209 grouping vlan-vnfc-instance-groups {
\r
1210 container vlan-vnfc-instance-groups {
\r
1211 list vlan-vnfc-instance-group {
\r
1212 key "instance-group-id";
\r
1213 leaf instance-group-id {
\r
1214 description "A&AI ID";
\r
1218 leaf instance-group-function {
\r
1236 grouping vnic-groups {
\r
1237 container vnic-groups {
\r
1239 key "vnic-interface-role";
\r
1240 leaf vnic-interface-role {
\r
1241 description "Same as network-role of network where vnic is connected";
\r
1245 leaf network-instance-group-function {
\r
1246 description "network-instance-Group-function for network collection where vnics with vnic-interface-role will connect";
\r
1249 leaf vlan-assignment-policy-name {
\r
1250 description "Policy name in ASDC model & policy definition in Policy Engine";
\r
1253 leaf vlan-tag-index-next {
\r
1254 description "Next tag to be assigned";
\r
1257 container vlan-common-ip-addresses {
\r
1258 uses ip-addresses;
\r
1260 container vlan-vnics {
\r
1262 key "vnic-port-id";
\r
1263 leaf vnic-port-id {
\r
1267 container vnic-sub-interfaces {
\r
1268 uses sub-interface-network-data;
\r
1275 grouping vnf-network-collection {
\r
1276 list vnf-network-collection {
\r
1277 key "network-instance-group-function";
\r
1278 leaf network-instance-group-function {
\r
1279 description "Network Instance-Group function in A&AI";
\r
1283 leaf network-instance-group-id {
\r
1284 description "Network Instance-Group id in A&AI";
\r
1287 leaf network-collection-service-instance-id {
\r
1288 description "Service-instance-id of service that created the network collection";
\r
1291 leaf network-collection-customization-uuid {
\r
1292 description "network-collection-customization-uuid stored in Network IsntanceGroup.customization-uuid in A&AI";
\r
1295 container vnf-floating-ip {
\r
1296 uses ip-addresses;
\r
1300 grouping vnf-sub-interface-group {
\r
1301 list vnf-sub-interface-group {
\r
1302 key "vnfc-instance-group-function network-instance-group-function parent-port-role";
\r
1303 leaf vnfc-instance-group-function {
\r
1307 leaf network-instance-group-function {
\r
1311 leaf parent-port-role {
\r
1316 container customer-bonding-requests {
\r
1317 list customer-bonding-request {
\r
1318 key "configuration-id";
\r
1319 leaf configuration-id {
\r
1320 description "e.g. vlan network receptor configuration id";
\r
1327 grouping sub-interface-network-data {
\r
1328 list sub-interface-network-data {
\r
1331 description "Subinterface network id (UUID in A&AI)";
\r
1335 leaf network-name {
\r
1336 description "Subinterface network name";
\r
1339 leaf vlan-tag-id {
\r
1340 description "Vlan tag assigned to subinterface port";
\r
1343 leaf network-role {
\r
1344 description "e.g. untrusted ";
\r
1347 leaf network-role-tag {
\r
1348 description "Assuming HEAT template network role tag parameter - not used";
\r
1351 container network-information-items {
\r
1352 list network-information-item {
\r
1355 description "Use ipv4 or ipv6";
\r
1359 description "Indicator to use DHCP on this network for this VM - set to N for Vlan tagging";
\r
1360 type enumeration {
\r
1366 description "The number of ip addresses to be assigned per vm for this network role";
\r
1369 container network-ips {
\r
1370 leaf-list network-ip {
\r
1371 description "List of assigned ip addresses of type ip-version on a network.";
\r
1372 type inet:ip-address;
\r
1378 container floating-ips {
\r
1379 leaf-list floating-ip-v4 {
\r
1380 description "Floating ipv4 for VMs of a given type on this network";
\r
1381 type inet:ip-address;
\r
1384 leaf-list floating-ip-v6 {
\r
1385 description "Floating ipv6 for VMs of a given type on this network";
\r
1386 type inet:ipv6-address;
\r
1392 grouping vnf-cloud-param {
\r
1393 leaf service-instance-id {
\r
1396 leaf service-instance-name {
\r
1409 key "vf-module-id";
\r
1410 leaf vf-module-id {
\r
1417 grouping vnf-get-resource-request-input-data {
\r
1424 key "vf-module-id";
\r
1425 leaf vf-module-id {
\r
1431 grouping license-information {
\r
1432 container license-information {
\r
1433 list entitlement-pool-list {
\r
1434 key "entitlement-pool-uuid action";
\r
1435 leaf entitlement-pool-uuid {
\r
1443 leaf entitlement-pool-invariant-uuid {
\r
1446 leaf entitlement-uuid {
\r
1447 description "assigned by ALTS";
\r
1451 list license-key-group-list {
\r
1452 key "license-key-group-uuid action";
\r
1453 leaf license-key-group-uuid {
\r
1461 leaf license-key-group-invariant-uuid {
\r
1464 leaf license-key {
\r
1465 description "assigned by ALTS";
\r
1468 leaf license-uuid {
\r
1469 description "assigned by ALTS";
\r
1475 grouping related-network {
\r
1476 list related-network {
\r
1479 description "Key to l3-network object";
\r
1482 leaf network-role {
\r
1488 grouping connection-point {
\r
1489 container connection-point {
\r
1490 leaf connection-point-id {
\r
1491 description "Key to CP object in A&AI";
\r
1495 description "port-index when multiple CPs connect to same network. Default zero (0)";
\r
1501 description "Key to vlan-tag uuid object in A&AI Generated by vlan mS";
\r
1504 leaf vlan-tag-id {
\r
1507 leaf vlan-tag-description {
\r
1511 description "Inner/Outer roles";
\r
1517 grouping aggregate-routes {
\r
1518 list aggregate-routes {
\r
1521 description "Unique id";
\r
1524 leaf start-address {
\r
1525 type inet:ip-address;
\r
1531 description "Use values 4 or 6.";
\r
1536 grouping pnf-information {
\r
1537 container pnf-information {
\r
1539 description "Key for A&AI query";
\r
1545 uses onap-model-information;
\r
1548 grouping contrail-route-operation-information {
\r
1549 uses sdnc-request-header;
\r
1550 uses request-information;
\r
1551 uses service-information;
\r
1552 uses allotted-resource-information;
\r
1553 uses contrail-route-request-input;
\r
1555 grouping contrail-route-request-input {
\r
1556 container contrail-route-request-input {
\r
1557 container source-network {
\r
1558 uses network-info;
\r
1560 container dest-network {
\r
1561 uses network-info;
\r
1563 container contrail-applied-service-info {
\r
1564 leaf service-instance-id {
\r
1565 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
1568 leaf contrail-fqdn {
\r
1569 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
1573 container contrail-route-input-parameters {
\r
1578 grouping network-info {
\r
1582 leaf network-role {
\r
1586 grouping contrail-route-topology {
\r
1587 container contrail-route-topology {
\r
1588 uses allotted-resource-identifiers;
\r
1589 uses onap-model-information;
\r
1590 uses contrail-route-assignments;
\r
1591 container contrail-route-parameters {
\r
1596 grouping contrail-route-assignments {
\r
1597 container contrail-route-assignments {
\r
1599 description "The Contrail fq-name of the network policy";
\r
1602 leaf contrail-id {
\r
1603 description "The ID assigned by Contrail to the network-policy (one for one with the fq-name)";
\r
1606 container source-network {
\r
1607 uses network-info;
\r
1609 container dest-network {
\r
1610 uses network-info;
\r
1612 container contrail-applied-service {
\r
1613 leaf service-instance-id {
\r
1614 description "The service-instance-id of the vnf from which the contrail applied service is coming";
\r
1618 description "The vnf representing the contrail applied service";
\r
1621 leaf contrail-fqdn {
\r
1622 description "This is the fq-name of the Contrail service instance through which the route is passing.";
\r
1627 description "Contrail-assigned vlan-tag to the vipr vm interface for this route.";
\r
1632 grouping security-zone-operation-information {
\r
1633 uses sdnc-request-header;
\r
1634 uses request-information;
\r
1635 uses service-information;
\r
1636 uses allotted-resource-information;
\r
1637 uses security-zone-request-input;
\r
1639 grouping security-zone-request-input {
\r
1640 container security-zone-request-input {
\r
1644 leaf trusted-network-role {
\r
1645 description "In the case of vIPR, this is the landing networks network-role; used in naming";
\r
1648 leaf untrusted-network-role {
\r
1649 description "In the case of vIPR, this is the tenant oam networks network-role; used in naming";
\r
1652 container security-zone-input-parameters {
\r
1657 grouping security-zone-topology {
\r
1658 container security-zone-topology {
\r
1659 uses allotted-resource-identifiers;
\r
1660 uses onap-model-information;
\r
1661 uses security-zone-assignments;
\r
1662 container security-zone-parameters {
\r
1667 grouping security-zone-assignments {
\r
1668 container security-zone-assignments {
\r
1669 leaf trusted-network-role {
\r
1670 description "In the case of vIPR, this is the landing networks network-role; used in naming";
\r
1673 leaf security-zone-name-trusted {
\r
1676 leaf untrusted-network-role {
\r
1677 description "In the case of vIPR, this is the tenant oam networks network-role; used in naming";
\r
1680 leaf security-zone-name-untrusted {
\r
1683 leaf security-zone-service-instance-id {
\r
1684 description "Will be the same as the parent-service-instance-id";
\r
1687 leaf security-zone-vnf-id {
\r
1688 description "Selected by SDNC from the security-zone-service-instance-id";
\r
1696 grouping port-mirror-topology-operation-information {
\r
1697 uses sdnc-request-header;
\r
1698 uses request-information;
\r
1699 uses service-information;
\r
1700 uses configuration-information;
\r
1701 uses port-mirror-configuration-request-input;
\r
1703 grouping port-mirror-configuration-request-input {
\r
1704 container port-mirror-configuration-request-input {
\r
1705 container source-port {
\r
1707 leaf source-port-id {
\r
1708 description "needed for srv-action=disable/enable";
\r
1712 container dest-port {
\r
1715 uses region-identifier;
\r
1716 container port-mirror-configuration-input-parameters {
\r
1721 grouping port-info {
\r
1722 leaf service-instance-id {
\r
1723 description "May not be need.";
\r
1726 uses pnf-information;
\r
1727 uses vnf-information;
\r
1729 grouping port-mirror-configuration-topology {
\r
1730 container port-mirror-configuration-topology {
\r
1731 uses configuration-identifiers;
\r
1732 uses onap-model-information;
\r
1733 uses port-mirror-configuration-assignments;
\r
1734 container port-mirror-configuration-parameters {
\r
1739 grouping port-mirror-configuration-assignments {
\r
1740 container port-mirror-configuration-assignments {
\r
1741 container contrail-vmi-params {
\r
1744 leaf vnics-group-id {
\r
1747 leaf owning-entity {
\r
1750 leaf tenant-context {
\r
1751 description "From tenant object in A&AI";
\r
1755 description "Tenant name from A&AI for source VNF";
\r
1759 description "tenant-id from A&AI for source VNF";
\r
1762 leaf dest-tenant {
\r
1763 description "Tenant name from A&AI for destination VNF";
\r
1766 leaf dest-tenant-id {
\r
1767 description "tenant-id from A&AI for destination VNF";
\r
1770 leaf cloud-region-id {
\r
1773 leaf cloud-owner {
\r
1776 leaf dest-network-fqdn {
\r
1779 leaf source-network-fqdn {
\r
1782 leaf source-capacity {
\r
1783 description "Source port pps (packets per second) rating from tosca model";
\r
1786 leaf source-vnf-id {
\r
1789 leaf dest-vnf-id {
\r
1790 description "For vProbe";
\r
1793 leaf dest-pnf-name {
\r
1794 description "For pProbe";
\r
1797 leaf dest-p-interface {
\r
1798 description "For pProbe; from policy manager";
\r
1801 leaf dest-pnf-port-policy-name {
\r
1802 description "For pProbe; from tosca model";
\r
1806 description "vprobe or pprobe; derived from configuration-information.configuration-sub-type";
\r
1809 leaf route-allotted-resource-id {
\r
1810 description "For vProbe";
\r
1813 container source-vnfc-instance-group-id {
\r
1814 leaf service-instance-id {
\r
1817 leaf nfc-naming-code {
\r
1820 leaf instance-group-role {
\r
1823 leaf configuration-id {
\r
1827 container dest-vnfc-instance-group-id {
\r
1828 leaf service-instance-id {
\r
1831 leaf nfc-naming-code {
\r
1834 leaf instance-group-role {
\r
1837 leaf configuration-id {
\r
1841 container source-to-dest-maps {
\r
1842 list source-to-dest-map {
\r
1843 key "source-port-id";
\r
1844 leaf source-port-id {
\r
1848 leaf source-port-name {
\r
1851 leaf source-vserver-id {
\r
1854 leaf dest-vserver-id {
\r
1857 leaf dest-port-id {
\r
1860 leaf dest-port-name {
\r
1866 container dest-ip-addresses {
\r
1867 uses ip-addresses;
\r
1873 grouping gc-topology-operation-information {
\r
1874 uses sdnc-request-header;
\r
1875 uses request-information;
\r
1876 uses service-information;
\r
1877 uses configuration-information;
\r
1878 uses gc-request-input;
\r
1880 grouping gc-request-input {
\r
1881 container gc-request-input {
\r
1885 leaf vf-module-id {
\r
1886 description "This is mandatory in case of rebuild";
\r
1889 container input-parameters {
\r
1893 description "Value will indicate what to rebuild";
\r
1896 list configuration-ids {
\r
1897 key "configuration-id";
\r
1898 leaf configuration-id {
\r
1904 grouping vnr-parameters {
\r
1905 container vnr-parameters {
\r
1909 leaf vf-module-id {
\r
1910 description "This is mandatory in case of rebuild";
\r
1913 leaf vnf-service-instance-id {
\r
1916 leaf network-collection-service-instance-id {
\r
1917 description "service instance id that created network-collection";
\r
1920 leaf network-instance-group-id {
\r
1926 leaf vnfc-instance-group-function {
\r
1929 leaf network-instance-group-function {
\r
1932 leaf parent-port-role {
\r
1935 leaf upper-tag-id {
\r
1938 leaf lower-tag-id {
\r
1943 grouping tunnelxconn-operation-information {
\r
1944 uses sdnc-request-header;
\r
1945 uses request-information;
\r
1946 uses service-information;
\r
1947 uses allotted-resource-information;
\r
1948 uses tunnelxconn-request-input;
\r
1950 grouping tunnelxconn-request-input {
\r
1952 container tunnelxconn-request-input {
\r
1953 leaf brg-wan-mac-address {
\r
1958 grouping tunnelxconn-topology {
\r
1959 container tunnelxconn-topology {
\r
1960 uses allotted-resource-identifiers;
\r
1961 uses onap-model-information;
\r
1962 uses tunnelxconn-assignments;
\r
1963 container tunnelxconn-parameters {
\r
1968 grouping tunnelxconn-assignments {
\r
1969 container tunnelxconn-assignments {
\r
1971 description "The Network Controller will assign a VNI value from the associated vGMUX VNI pool";
\r
1974 leaf vgmux-bearer-ip {
\r
1975 description "The Network Controller will look up the vgmux bearer ip from the vgmux vf module";
\r
1976 type inet:ip-address;
\r
1978 leaf vgmux-lan-ip {
\r
1979 description "The Network Controller will look up the vgmux lan ip from the vgmux vg module";
\r
1980 type inet:ip-address;
\r
1983 description "The Network Controller will assign the VG IP address from local inventory";
\r
1984 type inet:ip-address;
\r
1988 grouping brg-operation-information {
\r
1989 uses sdnc-request-header;
\r
1990 uses request-information;
\r
1991 uses service-information;
\r
1992 uses allotted-resource-information;
\r
1993 uses brg-request-input;
\r
1995 grouping brg-request-input {
\r
1996 container brg-request-input {
\r
1997 leaf vgmux-bearer-ip {
\r
1998 type inet:ip-address;
\r
2003 leaf brg-wan-mac-address {
\r
2008 grouping brg-topology {
\r
2009 container brg-topology {
\r
2010 uses allotted-resource-identifiers;
\r
2011 uses onap-model-information;
\r
2012 uses brg-assignments;
\r
2013 container brg-parameters {
\r
2018 grouping brg-assignments {
\r
2019 container brg-assignments {
\r
2020 leaf vbrg-wan-ip {
\r
2021 type inet:ip-address;
\r
2025 grouping connection-attachment-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 connection-attachment-request-input;
\r
2033 grouping connection-attachment-request-input {
\r
2034 container connection-attachment-request-input {
\r
2039 grouping connection-attachment-topology {
\r
2040 container connection-attachment-topology {
\r
2041 uses allotted-resource-identifiers;
\r
2042 uses onap-model-information;
\r
2043 uses connection-attachment-assignments;
\r
2044 container connection-attachment-parameters {
\r
2050 grouping connection-attachment-assignments {
\r
2051 container connection-attachment-assignments {
\r
2055 grouping vnf-vnr-rebuild-data {
\r
2056 container vnf-vnr-rebuild-data {
\r
2060 leaf vnf-service-instance-id {
\r
2064 key "configuration-id";
\r
2065 leaf configuration-id {
\r
2068 leaf network-instance-group-id {
\r
2074 leaf vnfc-instance-group-function {
\r
2077 leaf network-instance-group-function {
\r
2080 leaf parent-port-role {
\r
2083 leaf upper-tag-id {
\r
2086 leaf lower-tag-id {
\r
2092 grouping allotted-resource-information {
\r
2093 container allotted-resource-information {
\r
2094 leaf allotted-resource-id {
\r
2097 leaf allotted-resource-type {
\r
2098 description "Not an enum, but expected values are contrail-route and security-zone.";
\r
2101 leaf parent-service-instance-id {
\r
2102 description "Service-instance-id of the parent service to which this allotted resource belongs.";
\r
2105 uses onap-model-information;
\r
2108 grouping allotted-resource-identifiers {
\r
2109 container allotted-resource-identifiers {
\r
2110 leaf allotted-resource-id {
\r
2113 leaf allotted-resource-name {
\r
2114 description "For a contrail-route, the network policy name.";
\r
2117 leaf allotted-resource-type {
\r
2118 description "(Added in draft 32)Expected to be contrail-route or security-zone.";
\r
2121 leaf consuming-service-instance-id {
\r
2122 description "The service-instance-id of the consuming service of this allotted resource";
\r
2125 leaf parent-service-instance-id {
\r
2126 description "Service-instance-id of the parent service to which this allotted resource belongs.";
\r
2131 grouping allotted-resource-oper-status {
\r
2132 container allotted-resource-oper-status {
\r
2133 uses oper-status-data;
\r
2136 grouping allotted-resource-status {
\r
2137 container allotted-resource-status {
\r
2138 leaf response-code {
\r
2141 leaf response-message {
\r
2144 leaf final-indicator {
\r
2147 leaf request-status {
\r
2148 type enumeration {
\r
2149 enum "synccomplete";
\r
2150 enum "asynccomplete";
\r
2151 enum "notifycomplete";
\r
2155 description "value would one of possible request-actions; match the list in service-data oper-status";
\r
2162 description "this is the svc-action from the incoming request";
\r
2163 type enumeration {
\r
2169 enum "deactivate";
\r
2172 leaf response-timestamp {
\r
2177 grouping configuration-information {
\r
2178 container configuration-information {
\r
2179 leaf configuration-id {
\r
2182 leaf configuration-name {
\r
2185 leaf configuration-type {
\r
2186 description "Not an enum, but expected values are port-mirror-configuration, vlan-network-receptor";
\r
2189 leaf configuration-sub-type {
\r
2190 description "e.g. vprobe and pprobe when configuration-type=port-mirror-configuration";
\r
2193 uses onap-model-information;
\r
2196 grouping configuration-identifiers {
\r
2197 container configuration-identifiers {
\r
2198 leaf configuration-id {
\r
2201 leaf configuration-name {
\r
2204 leaf configuration-type {
\r
2205 description "Not an enum, but expected values are port-mirror-configuration.";
\r
2208 leaf configuration-sub-type {
\r
2209 description " vprobe and pprobe";
\r
2212 leaf parent-service-instance-id {
\r
2213 description "Service-instance-id of the parent service to which this resource belongs.";
\r
2218 grouping configuration-oper-status {
\r
2219 container configuration-oper-status {
\r
2220 uses oper-status-data;
\r
2223 grouping configuration-status {
\r
2224 container configuration-status {
\r
2225 leaf response-code {
\r
2228 leaf response-message {
\r
2231 leaf final-indicator {
\r
2234 leaf request-status {
\r
2235 type enumeration {
\r
2236 enum "synccomplete";
\r
2237 enum "asynccomplete";
\r
2238 enum "notifycomplete";
\r
2242 description "value would one of possible request-actions; match the list in service-data oper-status";
\r
2249 description "this is the svc-action from the incoming request";
\r
2250 type enumeration {
\r
2258 enum "deactivate";
\r
2261 leaf response-timestamp {
\r
2266 grouping topology-response-common {
\r
2267 leaf svc-request-id {
\r
2268 description "the request id from the request message for which this is the responseKeep as M";
\r
2271 leaf response-code {
\r
2272 description "a success code or an defined error codeKeep as M";
\r
2275 leaf response-message {
\r
2276 description "message included for error code";
\r
2279 leaf ack-final-indicator {
\r
2280 description "Expected to be Y or N.";
\r
2284 grouping sdnc-request-header {
\r
2285 container sdnc-request-header {
\r
2286 leaf svc-request-id {
\r
2287 description "Uniquely generated by calling system (e.g. MSO or SDN-GP)";
\r
2291 description "This is the rpcAction";
\r
2292 type enumeration {
\r
2297 enum "changeassign";
\r
2298 enum "changedelete";
\r
2300 enum "deactivate";
\r
2306 enum "reoptimize";
\r
2310 leaf svc-notification-url {
\r
2311 description "Contains URL for asynchronous response";
\r
2316 grouping request-information {
\r
2317 container request-information {
\r
2319 description "Request ID generated upstream of MSO";
\r
2322 leaf request-action {
\r
2323 description "still need to work Disconnect";
\r
2324 type enumeration {
\r
2325 enum "CreateNetworkInstance";
\r
2326 enum "ActivateNetworkInstance";
\r
2327 enum "CreateServiceInstance";
\r
2328 enum "DeleteServiceInstance";
\r
2329 enum "DeleteNetworkInstance";
\r
2330 enum "CreateVnfInstance";
\r
2331 enum "ActivateVnfInstance";
\r
2332 enum "DeleteVnfInstance";
\r
2333 enum "CreateVfModuleInstance";
\r
2334 enum "ActivateVfModuleInstance";
\r
2335 enum "DeleteVfModuleInstance";
\r
2336 enum "CreateContrailRouteInstance";
\r
2337 enum "DeleteContrailRouteInstance";
\r
2338 enum "CreateSecurityZoneInstance";
\r
2339 enum "DeleteSecurityZoneInstance";
\r
2340 enum "ActivateDCINetworkInstance";
\r
2341 enum "DeActivateDCINetworkInstance";
\r
2342 enum "CreateTunnelXConnInstance";
\r
2343 enum "DeleteTunnelXConnInstance";
\r
2344 enum "CreateBRGInstance";
\r
2345 enum "DeleteBRGInstance";
\r
2346 enum "CreateSOTNConnectivityInstance";
\r
2347 enum "ActivateSOTNConnectivityInstance";
\r
2348 enum "DeactivateSOTNConnectivityInstance";
\r
2349 enum "DeleteSOTNConnectivityInstance";
\r
2350 enum "CreateSOTNAttachmentInstance";
\r
2351 enum "ActivateSOTNAttachmentInstance";
\r
2352 enum "DeactivateSOTNAttachmentInstance";
\r
2353 enum "DeleteSOTNAttachmentInstance";
\r
2354 enum "CreateSiteInstance";
\r
2355 enum "ActivateSiteInstance";
\r
2356 enum "DeactivateSiteInstance";
\r
2357 enum "DeleteSiteInstance";
\r
2358 enum "CreatePortMirrorConfigurationInstance";
\r
2359 enum "DeletePortMirrorConfigurationInstance";
\r
2360 enum "ChangePortMirrorConfigurationInstance";
\r
2361 enum "CreateGenericConfigurationInstance";
\r
2362 enum "RebuildGenericConfigurationInstance";
\r
2363 enum "DeleteGenericConfigurationInstance";
\r
2364 enum "PreloadVfModuleRequest";
\r
2365 enum "DeletePreloadVfModuleRequest";
\r
2366 enum "PreloadNetworkRequest";
\r
2367 enum "DeletePreloadNetworkRequest";
\r
2368 enum "CreateForwardingPathInstance";
\r
2369 enum "DeleteForwardingPathInstance";
\r
2370 enum "UpdateForwardingPathInstance";
\r
2371 enum "CreateSDWANConnectivityInstance";
\r
2372 enum "ActivateSDWANConnectivityInstance";
\r
2373 enum "DeactivateSDWANConnectivityInstance";
\r
2374 enum "DeleteSDWANConnectivityInstance";
\r
2375 enum "CreateSDWANDeviceInstance";
\r
2376 enum "ActivateSDWANDeviceInstance";
\r
2377 enum "DeactivateSDWANDeviceInstance";
\r
2378 enum "DeleteSDWANDeviceInstance";
\r
2379 enum "CreateSDWANPortInstance";
\r
2380 enum "ActivateSDWANPortInstance";
\r
2381 enum "DeactivateSDWANPortInstance";
\r
2382 enum "DeleteSDWANPortInstance";
\r
2383 enum "CreateSDWANAttachmentInstance";
\r
2384 enum "ActivateSDWANAttachmentInstance";
\r
2385 enum "DeactivateSDWANAttachmentInstance";
\r
2386 enum "DeleteSDWANAttachmentInstance";
\r
2387 enum "ReoptimizeSOTNInstance";
\r
2393 leaf notification-url {
\r
2396 leaf order-number {
\r
2399 leaf order-version {
\r
2404 grouping service-information {
\r
2405 container service-information {
\r
2407 description "This maps to the product-family-id in A&AI";
\r
2410 leaf subscription-service-type {
\r
2411 description "used to reference a&ai subscription-service-type. For example, we show as vIPR-ATM in example.";
\r
2414 uses onap-model-information;
\r
2415 leaf service-instance-id {
\r
2418 leaf global-customer-id {
\r
2419 description "need for put of data to AnAI (MSO provides)";
\r
2422 leaf subscriber-name {
\r
2423 description "Would not be expected for vIPR-ATM or mobility services.";
\r
2428 grouping onap-model-information {
\r
2429 container onap-model-information {
\r
2430 leaf model-invariant-uuid {
\r
2431 description "identifies the invariant uuid for this service or resource";
\r
2434 leaf model-customization-uuid {
\r
2435 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
2439 description "identifies the uuid for this service or resource, which is version specific";
\r
2442 leaf model-version {
\r
2450 grouping region-identifier {
\r
2454 leaf aic-cloud-region {
\r
2455 description "The AIC cloud region which maps to contrail versions";
\r
2458 leaf cloud-owner {
\r
2459 description "The cloud owner provided by the caller";
\r
2463 description "Not expected to be used";
\r
2476 container resource-resolution-data {
\r
2477 list resource-key {
\r
2487 description "SUCCESS, FAILED, or PENDING - RA returned data as capability";
\r
2490 leaf capability-name {
\r
2491 description "Resource assignment resolution Capability name";
\r
2497 grouping ip-addresses {
\r
2498 container ip-addresses {
\r
2499 leaf ipv4-address {
\r
2500 type inet:ip-address;
\r
2502 leaf ipv6-address {
\r
2503 type inet:ip-address;
\r
2505 leaf vipv4-address {
\r
2506 description "Virtual v4";
\r
2507 type inet:ip-address;
\r
2509 leaf vipv6-address {
\r
2510 description "Virtual v6";
\r
2511 type inet:ip-address;
\r
2515 grouping instance-reference {
\r
2516 leaf instance-id {
\r
2519 leaf object-path {
\r
2520 description "restconf retrieval path to this particular objectE.g. restconf/config/GENERIC-RESOURCE-API:services/service/$service-instance-id/service-data/service-topology/";
\r
2524 grouping oper-status-data {
\r
2525 leaf order-status {
\r
2526 description "TBD - do we need Request failed statuses? RequestFailed | InProgressTimeout";
\r
2527 type enumeration {
\r
2529 enum "PendingAssignment";
\r
2530 enum "PendingCreate";
\r
2531 enum "PendingUpdate";
\r
2532 enum "PendingDelete";
\r
2537 leaf last-rpc-action {
\r
2538 type enumeration {
\r
2543 enum "deactivate";
\r
2545 enum "changeassign";
\r
2546 enum "reoptimize";
\r
2549 leaf last-action {
\r
2550 description "should be list of possible request-actions";
\r
2551 type enumeration {
\r
2552 enum "CreateNetworkInstance";
\r
2553 enum "ActivateNetworkInstance";
\r
2554 enum "CreateServiceInstance";
\r
2555 enum "DeleteServiceInstance";
\r
2556 enum "DeleteNetworkInstance";
\r
2557 enum "CreateVnfInstance";
\r
2558 enum "ActivateVnfInstance";
\r
2559 enum "DeleteVnfInstance";
\r
2560 enum "CreateVfModuleInstance";
\r
2561 enum "ActivateVfModuleInstance";
\r
2562 enum "DeleteVfModuleInstance";
\r
2563 enum "CreateContrailRouteInstance";
\r
2564 enum "DeleteContrailRouteInstance";
\r
2565 enum "CreateSecurityZoneInstance";
\r
2566 enum "DeleteSecurityZoneInstance";
\r
2567 enum "ActivateDCINetworkInstance";
\r
2568 enum "DeActivateDCINetworkInstance";
\r
2569 enum "CreateTunnelXConnInstance";
\r
2570 enum "DeleteTunnelXConnInstance";
\r
2571 enum "CreateBRGInstance";
\r
2572 enum "DeleteBRGInstance";
\r
2573 enum "CreateSOTNConnectivityInstance";
\r
2574 enum "ActivateSOTNConnectivityInstance";
\r
2575 enum "DeactivateSOTNConnectivityInstance";
\r
2576 enum "DeleteSOTNConnectivityInstance";
\r
2577 enum "CreateSOTNAttachmentInstance";
\r
2578 enum "ActivateSOTNAttachmentInstance";
\r
2579 enum "DeactivateSOTNAttachmentInstance";
\r
2580 enum "DeleteSOTNAttachmentInstance";
\r
2581 enum "CreateSiteInstance";
\r
2582 enum "ActivateSiteInstance";
\r
2583 enum "DeactivateSiteInstance";
\r
2584 enum "DeleteSiteInstance";
\r
2585 enum "CreatePortMirrorConfigurationInstance";
\r
2586 enum "DeletePortMirrorConfigurationInstance";
\r
2587 enum "ChangePortMirrorConfigurationInstance";
\r
2588 enum "CreateGenericConfigurationInstance";
\r
2589 enum "DeleteGenericConfigurationInstance";
\r
2590 enum "PreloadVfModuleRequest";
\r
2591 enum "DeletePreloadVfModuleRequest";
\r
2592 enum "PreloadNetworkRequest";
\r
2593 enum "DeletePreloadNetworkRequest";
\r
2594 enum "CreateForwardingPathInstance";
\r
2595 enum "DeleteForwardingPathInstance";
\r
2596 enum "UpdateForwardingPathInstance";
\r
2597 enum "CreateSDWANConnectivityInstance";
\r
2598 enum "ActivateSDWANConnectivityInstance";
\r
2599 enum "DeactivateSDWANConnectivityInstance";
\r
2600 enum "DeleteSDWANConnectivityInstance";
\r
2601 enum "CreateSDWANDeviceInstance";
\r
2602 enum "ActivateSDWANDeviceInstance";
\r
2603 enum "DeactivateSDWANDeviceInstance";
\r
2604 enum "DeleteSDWANDeviceInstance";
\r
2605 enum "CreateSDWANPortInstance";
\r
2606 enum "ActivateSDWANPortInstance";
\r
2607 enum "DeactivateSDWANPortInstance";
\r
2608 enum "DeleteSDWANPortInstance";
\r
2609 enum "CreateSDWANAttachmentInstance";
\r
2610 enum "ActivateSDWANAttachmentInstance";
\r
2611 enum "DeactivateSDWANAttachmentInstance";
\r
2612 enum "DeleteSDWANAttachmentInstance";
\r
2613 enum "ReoptimizeSOTNInstance";
\r
2616 leaf last-svc-request-id {
\r
2617 description "Not currently populated in service data.";
\r
2620 leaf last-order-status {
\r
2621 type enumeration {
\r
2623 enum "PendingAssignment";
\r
2624 enum "PendingCreate";
\r
2625 enum "PendingUpdate";
\r
2626 enum "PendingDelete";
\r
2631 leaf create-timestamp {
\r
2632 description "Not currently populated in service data.";
\r
2635 leaf modify-timestamp {
\r
2639 grouping service-response-information {
\r
2640 container service-response-information {
\r
2641 uses instance-reference;
\r
2644 grouping network-response-information {
\r
2645 container network-response-information {
\r
2646 uses instance-reference;
\r
2649 grouping vnf-response-information {
\r
2650 container vnf-response-information {
\r
2651 uses instance-reference;
\r
2654 grouping vf-module-response-information {
\r
2655 container vf-module-response-information {
\r
2656 uses instance-reference;
\r
2659 grouping contrail-route-response-information {
\r
2660 container contrail-route-response-information {
\r
2661 uses instance-reference;
\r
2664 grouping security-zone-response-information {
\r
2665 container security-zone-response-information {
\r
2666 uses instance-reference;
\r
2669 grouping getpathsegment-response-information {
\r
2670 container getpathsegment-response-information {
\r
2671 uses instance-reference;
\r
2674 grouping port-mirror-response-information {
\r
2675 container port-mirror-response-information {
\r
2676 uses instance-reference;
\r
2679 grouping gc-response-information {
\r
2680 container gc-response-information {
\r
2681 uses instance-reference;
\r
2684 grouping tunnelxconn-response-information {
\r
2685 container tunnelxconn-response-information {
\r
2686 uses instance-reference;
\r
2689 grouping brg-response-information {
\r
2690 container brg-response-information {
\r
2691 uses instance-reference;
\r
2694 grouping connection-attachment-response-information {
\r
2695 container connection-attachment-response-information {
\r
2696 uses instance-reference;
\r
2699 grouping preload-model-information {
\r
2700 list preload-list {
\r
2701 key "preload-id preload-type";
\r
2703 description "vf-module-name or network name";
\r
2707 leaf preload-type {
\r
2708 description "network or vf-module";
\r
2712 uses preload-data;
\r
2715 grouping preload-data {
\r
2716 container preload-data {
\r
2717 uses preload-vf-module-topology-information;
\r
2718 uses preload-network-topology-information;
\r
2719 uses preload-oper-status;
\r
2722 grouping preload-vf-module-topology-information {
\r
2723 container preload-vf-module-topology-information {
\r
2724 uses vnf-topology-identifier-structure;
\r
2725 uses vnf-resource-assignments;
\r
2726 uses vf-module-topology;
\r
2729 grouping preload-network-topology-information {
\r
2730 container preload-network-topology-information {
\r
2731 uses network-topology-identifier-structure;
\r
2733 uses vpn-bindings;
\r
2734 uses network-policy;
\r
2735 uses route-table-reference;
\r
2737 uses provider-network-information;
\r
2740 grouping subnets {
\r
2742 key "start-address";
\r
2743 leaf start-address {
\r
2744 type inet:ip-address;
\r
2746 leaf gateway-address {
\r
2747 type inet:ip-address;
\r
2755 leaf dhcp-enabled {
\r
2756 type enumeration {
\r
2761 leaf dhcp-start-address {
\r
2764 leaf dhcp-end-address {
\r
2767 leaf addr-from-start {
\r
2768 description "Default is N";
\r
2769 type enumeration {
\r
2774 leaf subnet-name {
\r
2777 leaf subnet-role {
\r
2780 leaf subnet-sequence {
\r
2785 grouping vpn-bindings {
\r
2786 list vpn-bindings {
\r
2787 key "vpn-binding-id";
\r
2788 leaf vpn-binding-id {
\r
2794 leaf global-route-target {
\r
2797 leaf route-target-role {
\r
2801 description "AIC Zone the route target associated with";
\r
2806 grouping network-policy {
\r
2807 list network-policy {
\r
2808 key "network-policy-fqdn";
\r
2809 leaf network-policy-fqdn {
\r
2812 leaf network-policy-id {
\r
2817 grouping route-table-reference {
\r
2818 list route-table-reference {
\r
2819 key "route-table-reference-fqdn";
\r
2820 leaf route-table-reference-fqdn {
\r
2824 leaf route-table-reference-id {
\r
2829 grouping provider-network-information {
\r
2830 leaf physical-network-name {
\r
2833 leaf is-provider-network {
\r
2836 leaf is-shared-network {
\r
2839 leaf is-external-network {
\r
2843 grouping host-routes {
\r
2844 list host-routes {
\r
2845 key "route-prefix";
\r
2846 leaf route-prefix {
\r
2850 description "Could be ip-address or hostname or service-instance";
\r
2855 grouping preload-oper-status {
\r
2856 container preload-oper-status {
\r
2857 leaf order-status {
\r
2858 type enumeration {
\r
2860 enum "PendingAssignment";
\r
2861 enum "PendingCreate";
\r
2862 enum "PendingUpdate";
\r
2863 enum "PendingDelete";
\r
2867 leaf last-action {
\r
2868 type enumeration {
\r
2869 enum "PreloadVfModuleRequest";
\r
2870 enum "DeletePreloadVfModuleRequest";
\r
2871 enum "PreloadNetworkRequest";
\r
2872 enum "DeletePreloadNetworkRequest";
\r
2875 leaf last-svc-request-id {
\r
2878 leaf last-order-status {
\r
2879 type enumeration {
\r
2881 enum "PendingAssignment";
\r
2882 enum "PendingCreate";
\r
2883 enum "PendingUpdate";
\r
2884 enum "PendingDelete";
\r
2888 leaf create-timestamp {
\r
2891 leaf modify-timestamp {
\r
2894 leaf maintenance-indicator {
\r
2895 type enumeration {
\r
2902 grouping preload-topology-response-body {
\r
2903 leaf svc-request-id {
\r
2906 leaf response-code {
\r
2909 leaf response-message {
\r
2912 leaf ack-final-indicator {
\r
2916 rpc generic-configuration-notification {
\r
2918 uses sdnc-request-header;
\r
2919 uses request-information;
\r
2920 uses service-information;
\r
2921 uses configuration-information;
\r
2922 uses topology-response-common;
\r
2923 leaf configuration-topology-link {
\r
2924 description "Returns URL to generic-configuration-topology ";
\r
2927 uses vnr-parameters;
\r
2928 uses vnf-vnr-rebuild-data;
\r
2931 container services {
\r
2932 uses service-model-infrastructure;
\r
2934 container contrail-route-allotted-resources {
\r
2935 list contrail-route-allotted-resource {
\r
2936 key "allotted-resource-id";
\r
2937 leaf allotted-resource-id {
\r
2941 container allotted-resource-data {
\r
2942 container allotted-resource-operation-information {
\r
2943 uses contrail-route-operation-information;
\r
2945 uses contrail-route-topology;
\r
2946 uses allotted-resource-oper-status;
\r
2948 uses allotted-resource-status;
\r
2951 container security-zone-allotted-resources {
\r
2952 list security-zone-allotted-resource {
\r
2953 key "allotted-resource-id";
\r
2954 leaf allotted-resource-id {
\r
2958 container allotted-resource-data {
\r
2959 container allotted-resource-operation-information {
\r
2960 uses security-zone-operation-information;
\r
2962 uses security-zone-topology;
\r
2963 container security-zone-parameters {
\r
2966 uses allotted-resource-oper-status;
\r
2968 uses allotted-resource-status;
\r
2971 container tunnelxconn-allotted-resources {
\r
2972 list tunnelxconn-allotted-resource {
\r
2973 key "allotted-resource-id";
\r
2974 leaf allotted-resource-id {
\r
2978 container allotted-resource-data {
\r
2979 container allotted-resource-operation-information {
\r
2980 uses tunnelxconn-operation-information;
\r
2982 uses tunnelxconn-topology;
\r
2983 container tunnelxconn-parameters {
\r
2986 uses allotted-resource-oper-status;
\r
2988 uses allotted-resource-status;
\r
2991 container brg-allotted-resources {
\r
2992 list brg-allotted-resource {
\r
2993 key "allotted-resource-id";
\r
2994 leaf allotted-resource-id {
\r
2998 container allotted-resource-data {
\r
2999 container allotted-resource-operation-information {
\r
3000 uses brg-operation-information;
\r
3002 uses brg-topology;
\r
3003 container brg-parameters {
\r
3006 uses allotted-resource-oper-status;
\r
3008 uses allotted-resource-status;
\r
3011 container connection-attachment-allotted-resources {
\r
3012 list connection-attachment-allotted-resource {
\r
3013 key "allotted-resource-id";
\r
3014 leaf allotted-resource-id {
\r
3018 container allotted-resource-data {
\r
3019 container allotted-resource-operation-information {
\r
3020 uses connection-attachment-operation-information;
\r
3022 uses connection-attachment-topology;
\r
3023 container connection-attachment-parameters {
\r
3026 uses allotted-resource-oper-status;
\r
3028 uses allotted-resource-status;
\r
3031 container port-mirror-configurations {
\r
3032 list port-mirror-configuration {
\r
3033 key "configuration-id";
\r
3034 leaf configuration-id {
\r
3038 container configuration-data {
\r
3039 container configuration-operation-information {
\r
3040 uses port-mirror-topology-operation-information;
\r
3042 uses port-mirror-configuration-topology;
\r
3043 uses configuration-oper-status;
\r
3045 uses configuration-status;
\r
3048 container generic-configurations {
\r
3049 list gc-configuration {
\r
3050 key "configuration-id";
\r
3051 leaf configuration-id {
\r
3055 container configuration-data {
\r
3056 container configuration-operation-information {
\r
3057 uses gc-topology-operation-information;
\r
3059 uses configuration-oper-status;
\r
3061 uses configuration-status;
\r
3064 rpc service-topology-operation {
\r
3066 uses service-operation-information;
\r
3069 uses topology-response-common;
\r
3070 uses service-response-information;
\r
3073 rpc network-topology-operation {
\r
3075 uses network-operation-information;
\r
3078 uses topology-response-common;
\r
3079 uses network-response-information;
\r
3080 uses service-response-information;
\r
3083 rpc vnf-topology-operation {
\r
3085 uses vnf-operation-information;
\r
3088 uses topology-response-common;
\r
3089 uses vnf-response-information;
\r
3090 uses service-response-information;
\r
3093 rpc vf-module-topology-operation {
\r
3095 uses vf-module-operation-information;
\r
3098 uses topology-response-common;
\r
3099 uses vf-module-response-information;
\r
3100 uses vnf-response-information;
\r
3101 uses service-response-information;
\r
3104 rpc contrail-route-topology-operation {
\r
3106 uses contrail-route-operation-information;
\r
3109 uses topology-response-common;
\r
3110 uses contrail-route-response-information;
\r
3111 uses service-response-information;
\r
3114 rpc security-zone-topology-operation {
\r
3116 uses security-zone-operation-information;
\r
3119 uses topology-response-common;
\r
3120 uses security-zone-response-information;
\r
3121 uses service-response-information;
\r
3124 rpc tunnelxconn-topology-operation {
\r
3126 uses tunnelxconn-operation-information;
\r
3129 uses topology-response-common;
\r
3130 uses tunnelxconn-response-information;
\r
3131 uses service-response-information;
\r
3134 rpc brg-topology-operation {
\r
3136 uses brg-operation-information;
\r
3139 uses topology-response-common;
\r
3140 uses brg-response-information;
\r
3141 uses service-response-information;
\r
3144 rpc policy-update-notify-operation {
\r
3146 leaf policy-name {
\r
3151 description "Map JSON versionNo to version-id";
\r
3155 leaf update-type {
\r
3169 rpc getpathsegment-topology-operation {
\r
3171 uses forwarding-path-operation-information;
\r
3174 uses topology-response-common;
\r
3175 uses getpathsegment-response-information;
\r
3176 uses service-response-information;
\r
3179 rpc port-mirror-topology-operation {
\r
3181 uses port-mirror-topology-operation-information;
\r
3184 uses topology-response-common;
\r
3185 uses port-mirror-response-information;
\r
3186 uses service-response-information;
\r
3189 rpc generic-configuration-topology-operation {
\r
3191 uses gc-topology-operation-information;
\r
3194 uses topology-response-common;
\r
3195 uses gc-response-information;
\r
3196 uses service-response-information;
\r
3199 rpc vnf-get-resource-request {
\r
3201 uses sdnc-request-header;
\r
3202 uses request-information;
\r
3203 uses service-information;
\r
3204 uses vnf-get-resource-request-input-data;
\r
3207 container vnf-get-resource-response-information {
\r
3208 uses vnf-cloud-param;
\r
3212 container preload-information {
\r
3213 uses preload-model-information;
\r
3215 rpc preload-vf-module-topology-operation {
\r
3217 uses sdnc-request-header;
\r
3218 uses request-information;
\r
3219 uses preload-vf-module-topology-information;
\r
3222 uses preload-topology-response-body;
\r
3225 rpc preload-network-topology-operation {
\r
3227 uses sdnc-request-header;
\r
3228 uses request-information;
\r
3229 uses preload-network-topology-information;
\r
3232 uses preload-topology-response-body;
\r
3236 rpc connection-attachment-topology-operation {
\r
3238 uses connection-attachment-operation-information;
\r
3241 uses topology-response-common;
\r
3242 uses connection-attachment-response-information;
\r
3243 uses service-response-information;
\r
3247 } ////closes the module
\r
Code Review / sdnc / northbound.git / blob