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
389 leaf subnet-key-value {
\r
390 description "key-value provided to EIPAM when creating shared subnet";
\r
393 container networks {
\r
397 description "Index into network-topology-identifier structure";
\r
405 leaf network-status {
\r
406 description "assigned, unassigned";
\r
409 container customer-bonding-requests {
\r
410 list customer-bonding-request {
\r
411 key "configuration-id";
\r
412 leaf configuration-id {
\r
413 description "e.g. vlan network receptor configuration id";
\r
422 grouping network-level-oper-status {
\r
423 container network-level-oper-status {
\r
424 uses oper-status-data;
\r
427 grouping vnf-operation-information {
\r
428 uses sdnc-request-header;
\r
429 uses request-information;
\r
430 uses service-information;
\r
431 uses vnf-information;
\r
432 uses vnf-request-input;
\r
433 uses license-information;
\r
435 grouping vnf-information {
\r
436 container vnf-information {
\r
446 uses onap-model-information;
\r
449 grouping vnf-request-input {
\r
450 container vnf-request-input {
\r
451 leaf request-version {
\r
457 uses region-identifier;
\r
458 container vnf-networks {
\r
460 key "network-role";
\r
461 uses vnf-network-data;
\r
464 list vnf-network-instance-group-ids {
\r
465 key "vnf-network-instance-group-id";
\r
466 leaf vnf-network-instance-group-id {
\r
467 description "List of vnf network-instance-group";
\r
471 container vnf-input-parameters {
\r
476 grouping vnf-topology {
\r
477 container vnf-topology {
\r
478 uses vnf-topology-identifier-structure;
\r
479 uses region-identifier;
\r
480 uses onap-model-information;
\r
481 uses vnf-resource-assignments;
\r
482 container vnf-parameters-data {
\r
485 leaf sdnc-generated-cloud-resources {
\r
486 description "Indicate if source is sdnc generated cloud param";
\r
491 grouping vnf-topology-identifier-structure {
\r
492 container vnf-topology-identifier-structure {
\r
497 description "In preload tree, this label is used for the vf-module-type";
\r
510 description "used in vnf naming";
\r
514 description "optionally comes from vnf-request-input container or is assigned by sdn-c";
\r
519 grouping vnf-resource-assignments {
\r
520 container vnf-resource-assignments {
\r
522 description "Orchestration status from AAI - to be set by SDNC";
\r
525 container availability-zones {
\r
526 leaf-list availability-zone {
\r
527 description "Openstack availability zone name or UUID";
\r
532 description "From the TOSCA data. Indicates the largest availability zone count needed by any vf-module in the VNF.";
\r
536 container vnf-networks {
\r
538 key "network-role";
\r
539 uses vnf-network-data;
\r
544 grouping vnf-network-data {
\r
545 leaf network-role {
\r
546 description "A Network Role to which a VNF must connect";
\r
549 leaf network-name {
\r
550 description "Unique Neutron UUID of an instance of the network role ";
\r
554 description "Unique Neutron UUID of an instance of the network role ";
\r
558 description "Unique Neutron UUID of an instance of the network role ";
\r
561 leaf contrail-network-fqdn {
\r
562 description "contrail network policy object";
\r
565 container subnets-data {
\r
567 key "sdnc-subnet-id";
\r
568 leaf sdnc-subnet-id {
\r
569 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
573 description "Subnet Role for the subnet";
\r
577 description "Populated for preload only";
\r
581 description "Should be ipv4 or ipv6";
\r
585 description "subnet UUID to be passed into the HEAT template";
\r
588 leaf dhcp-enabled {
\r
589 description "Indicator to use this subnet for DHCP ";
\r
595 leaf network-start-address {
\r
596 description "start-address of the subnet";
\r
597 type inet:ip-address;
\r
599 leaf gateway-address {
\r
600 description "subnet gateway address";
\r
601 type inet:ip-address;
\r
604 description "cidr mask";
\r
612 leaf segmentation-id {
\r
615 container related-networks {
\r
616 uses related-network;
\r
619 grouping vnf-level-oper-status {
\r
620 container vnf-level-oper-status {
\r
621 uses oper-status-data;
\r
624 grouping vf-module-operation-information {
\r
625 uses sdnc-request-header;
\r
626 uses request-information;
\r
627 uses service-information;
\r
628 uses vnf-information;
\r
629 uses vf-module-information;
\r
630 uses vf-module-request-input;
\r
632 grouping vf-module-information {
\r
633 container vf-module-information {
\r
634 leaf vf-module-id {
\r
637 leaf vf-module-type {
\r
640 leaf from-preload {
\r
641 description "Indicates if source is preload data";
\r
644 uses onap-model-information;
\r
647 grouping vf-module-request-input {
\r
648 container vf-module-request-input {
\r
649 leaf request-version {
\r
650 description "keep this?";
\r
653 leaf vf-module-name {
\r
656 uses region-identifier;
\r
657 container vf-module-input-parameters {
\r
662 grouping vf-module-topology {
\r
663 container vf-module-topology {
\r
664 uses vf-module-topology-identifier;
\r
665 uses region-identifier;
\r
666 uses onap-model-information;
\r
667 uses vf-module-assignments;
\r
668 container vf-module-parameters {
\r
671 leaf sdnc-generated-cloud-resources {
\r
672 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
677 grouping vf-module-topology-identifier {
\r
678 container vf-module-topology-identifier {
\r
679 leaf vf-module-id {
\r
680 description "vf-module id";
\r
683 leaf vf-module-name {
\r
684 description "vf-module-name";
\r
687 leaf vf-module-type {
\r
692 grouping vf-module-assignments {
\r
693 container vf-module-assignments {
\r
694 leaf vf-module-status {
\r
695 description "Orchestration status from AAI - to be set by SDNC";
\r
701 uses vm-topology-data;
\r
704 uses vlan-vnfc-instance-groups;
\r
707 grouping vm-topology-data {
\r
712 uses onap-model-information;
\r
713 leaf nfc-naming-code {
\r
714 description "used in vm naming(draft 29: changed from nfc-code)";
\r
718 description "from tosca data on vfc";
\r
724 container vm-names {
\r
725 leaf-list vm-name {
\r
734 container vnfc-networks {
\r
735 uses vnfc-network-data;
\r
739 container vm-networks {
\r
741 key "network-role";
\r
742 uses vm-network-data;
\r
746 grouping vnfc-network-data {
\r
747 list vnfc-network-data {
\r
748 key "vnfc-network-role";
\r
749 leaf vnfc-network-role {
\r
756 uses connection-point;
\r
757 container vnfc-ports {
\r
759 key "vnfc-port-id";
\r
760 leaf vnfc-port-id {
\r
761 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
765 leaf common-sub-interface-role {
\r
766 description "If sub-interfaces have common interface role (network role)";
\r
769 container vnic-sub-interfaces {
\r
770 uses sub-interface-network-data;
\r
775 key "vnfc-subnet-role";
\r
776 leaf vnfc-subnet-role {
\r
777 description "Default value if subnet role is not defined.";
\r
781 list vnfc-ip-assignments {
\r
782 key "vnfc-address-family";
\r
783 leaf vnfc-address-family {
\r
784 description "indicates if this is IpV4 or IpV6";
\r
790 leaf vnfc-subnet-dhcp {
\r
791 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
797 leaf vnfc-subnet-ip-count {
\r
798 description "The number of IP addresses to be assigned per vnfc for this subnet role";
\r
801 list vnfc-subnet-ip {
\r
802 key "vnfc-ip-address";
\r
803 leaf vnfc-ip-address {
\r
804 description "Either IpV4 IP or IpV6 IP addresses should be present";
\r
805 type inet:ip-address;
\r
807 leaf vnfc-client-key {
\r
811 description "Capture what type of IP this is, if is virtual IP (AKA, floating IP) or Fixed IP. ";
\r
822 grouping vm-network-data {
\r
823 leaf network-role {
\r
824 description "network (identified by role) that this VM connects to. Should also be included in the vnf-networks for the containing VNF";
\r
828 leaf network-role-tag {
\r
831 container network-information-items {
\r
832 list network-information-item {
\r
835 description "Use ipv4 or ipv6";
\r
839 description "Indicator to use DHCP on this network for this VM";
\r
846 description "The number of ip addresses to be assigned per vm for this network role";
\r
849 container network-ips {
\r
850 leaf-list network-ip {
\r
851 description "List of assigned ip addresses of type ip-version on a network";
\r
858 container mac-addresses {
\r
859 leaf-list mac-address {
\r
860 description "List of network assignments for this vm-type";
\r
865 container floating-ips {
\r
866 leaf-list floating-ip-v4 {
\r
867 description "Floating ipv4 for VMs of a given type on this network";
\r
868 type inet:ip-address;
\r
871 leaf-list floating-ip-v6 {
\r
872 description "Floating ipv6 for VMs of a given type on this network";
\r
873 type inet:ipv6-address;
\r
877 container interface-route-prefixes {
\r
878 leaf-list interface-route-prefix {
\r
879 description "ordered-by: user";
\r
887 leaf segmentation-id {
\r
890 container related-networks {
\r
891 uses related-network;
\r
894 grouping vf-module-level-oper-status {
\r
895 container vf-module-level-oper-status {
\r
896 uses oper-status-data;
\r
899 grouping allotted-resource-info {
\r
900 leaf allotted-resource-id {
\r
903 leaf allotted-resource-type {
\r
904 description "Not an enum, but expected values are contrail-route and security-zone.";
\r
907 leaf allotted-resource-pointer {
\r
908 description "Pointer to the allotted-resources topology";
\r
912 grouping forwarding-path-operation-information {
\r
913 uses sdnc-request-header;
\r
914 uses request-information;
\r
915 uses service-information;
\r
916 uses forwarding-path-request-input;
\r
918 grouping forwarding-path-request-input {
\r
919 container forwarding-path-request-input {
\r
920 list forwarding-paths {
\r
921 key "forwarding-path-name";
\r
922 leaf forwarding-path-name {
\r
923 description "Forwarding-path-name from tosca-model. ";
\r
927 uses onap-model-information;
\r
931 grouping forwarding-path-information {
\r
932 leaf forwarding-path-name {
\r
933 description "Fowarding-path name from TOSCA model, or name generated by SDNC";
\r
936 leaf forwarding-path-type {
\r
937 description "Based on MySQL Forwarding_Path tables path_type value from related TOSCA model";
\r
943 uses onap-model-information;
\r
944 container service-paths {
\r
945 list service-path {
\r
946 key "service-path-instance-id";
\r
947 uses service-path-information;
\r
951 grouping service-path-information {
\r
952 leaf service-path-instance-id {
\r
953 description "Service path instance ID generated by SDNC. Identifies a service-path-instance within a forwarding-path definition";
\r
956 leaf service-path-instance-name {
\r
957 description "A unique name generated by SDNC ( forwarding-path-name + service-path-instance-id )";
\r
961 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
965 key "service-instance-id";
\r
966 leaf service-instance-id {
\r
967 description "service-instance-id of each service-instance in the service-path-instance";
\r
970 leaf service-path-sequence-id {
\r
971 description "e.g. S1S2S3S5seq id=1 S1-S2seq id=2 S2S3seq id=3 S3S5Incremental integer value";
\r
976 key "vnf-instance-id";
\r
977 uses vnf-path-information;
\r
982 grouping vnf-path-information {
\r
983 leaf vnf-instance-id {
\r
984 description "VNF instance ID in the path";
\r
987 leaf vnf-path-sequence-id {
\r
988 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
991 leaf left-network-name {
\r
992 description "Every VNF instance in the path is connected to one or two VNFs.";
\r
995 leaf left-network-role {
\r
998 leaf right-network-name {
\r
1001 leaf right-network-role {
\r
1004 container vf-module-instance {
\r
1005 leaf vf-module-id {
\r
1008 leaf vf-module-name {
\r
1013 grouping forwarding-path-level-oper-status {
\r
1014 container forwarding-path-level-oper-status {
\r
1015 uses oper-status-data;
\r
1018 grouping configuration-info {
\r
1019 leaf configuration-id {
\r
1022 leaf configuration-type {
\r
1023 description "Not an enum, but expected values are port-mirror-configuration, , vlan-network-receptor";
\r
1026 leaf configuration-sub-type {
\r
1027 description "Not an enum, but expected values are vprobe and pprobe";
\r
1030 leaf configuration-topology-link {
\r
1031 description "Pointer to the configurations topology";
\r
1035 grouping vnfc-instance-group {
\r
1036 list vnfc-instance-group {
\r
1037 key "instance-group-role nfc-naming-code configuration-id";
\r
1038 leaf instance-group-role {
\r
1039 description "i.e.TSBC_VNFC_group";
\r
1043 leaf nfc-naming-code {
\r
1044 description "Set to nfc-naming-code from A&AI";
\r
1048 leaf configuration-id {
\r
1053 description " port-mirror-source or port-mirror-dest";
\r
1056 uses vnfc-objects;
\r
1059 grouping vnfc-objects {
\r
1060 container vnfc-objects {
\r
1061 list vnfc-object {
\r
1067 description "Vnfc name as key in A&AI";
\r
1076 leaf vserver-name {
\r
1084 key "vnic-port-name";
\r
1085 leaf vnic-port-name {
\r
1088 leaf vnic-port-id {
\r
1091 container capacity {
\r
1092 leaf vnic-capacity {
\r
1095 leaf used-capacity {
\r
1096 description "Updated for destination port when source port is mapped/unmapped.";
\r
1100 container vnic-ip-addresses {
\r
1101 uses ip-addresses;
\r
1113 description "Vnfc name as key in A&AI";
\r
1116 leaf vserver-name {
\r
1129 key "vnic-port-name";
\r
1130 leaf vnic-port-name {
\r
1133 leaf vnic-port-id {
\r
1136 uses sub-interfaces;
\r
1140 grouping sub-interfaces {
\r
1141 container sub-interfaces {
\r
1142 list sub-interface {
\r
1143 key "sub-interface-port-name";
\r
1144 leaf sub-interface-port-name {
\r
1147 leaf sub-interface-port-id {
\r
1150 container sub-interface-ip-addresses {
\r
1151 uses ip-addresses;
\r
1154 container sub-interface-network {
\r
1155 leaf network-name {
\r
1162 leaf sub-interface-status {
\r
1163 description "NULL, unassigned, assigned";
\r
1169 grouping vlan-tags {
\r
1170 container vlan-tags {
\r
1171 leaf vlan-interface {
\r
1172 description "A&AI Key";
\r
1175 leaf upper-tag-id {
\r
1178 leaf lower-tag-id {
\r
1186 grouping vlan-vnfc-instance-groups {
\r
1187 container vlan-vnfc-instance-groups {
\r
1188 list vlan-vnfc-instance-group {
\r
1189 key "instance-group-id";
\r
1190 leaf instance-group-id {
\r
1191 description "A&AI ID";
\r
1195 leaf instance-group-function {
\r
1213 grouping vnic-groups {
\r
1214 container vnic-groups {
\r
1216 key "vnic-interface-role";
\r
1217 leaf vnic-interface-role {
\r
1218 description "Same as network-role of network where vnic is connected";
\r
1222 leaf network-instance-group-function {
\r
1223 description "network-instance-Group-function for network collection where vnics with vnic-interface-role will connect";
\r
1226 leaf vlan-assignment-policy-name {
\r
1227 description "Policy name in ASDC model & policy definition in Policy Engine";
\r
1230 leaf vlan-tag-index-next {
\r
1231 description "Next tag to be assigned";
\r
1234 container vlan-common-ip-addresses {
\r
1235 uses ip-addresses;
\r
1237 container vlan-vnics {
\r
1239 key "vnic-port-id";
\r
1240 leaf vnic-port-id {
\r
1244 container vnic-sub-interfaces {
\r
1245 uses sub-interface-network-data;
\r
1252 grouping vnf-network-collection {
\r
1253 list vnf-network-collection {
\r
1254 key "network-instance-group-function";
\r
1255 leaf network-instance-group-function {
\r
1256 description "Network Instance-Group function in A&AI";
\r
1260 leaf network-instance-group-id {
\r
1261 description "Network Instance-Group id in A&AI";
\r
1264 leaf network-collection-service-instance-id {
\r
1265 description "Service-instance-id of service that created the network collection";
\r
1268 leaf network-collection-customization-uuid {
\r
1269 description "network-collection-customization-uuid stored in Network IsntanceGroup.customization-uuid in A&AI";
\r
1272 container vnf-floating-ip {
\r
1273 uses ip-addresses;
\r
1277 grouping vnf-sub-interface-group {
\r
1278 list vnf-sub-interface-group {
\r
1279 key "vnfc-instance-group-function network-instance-group-function parent-port-role";
\r
1280 leaf vnfc-instance-group-function {
\r
1284 leaf network-instance-group-function {
\r
1288 leaf parent-port-role {
\r
1293 container customer-bonding-requests {
\r
1294 list customer-bonding-request {
\r
1295 key "configuration-id";
\r
1296 leaf configuration-id {
\r
1297 description "e.g. vlan network receptor configuration id";
\r
1304 grouping sub-interface-network-data {
\r
1305 list sub-interface-network-data {
\r
1308 description "Subinterface network id (UUID in A&AI)";
\r
1312 leaf network-name {
\r
1313 description "Subinterface network name";
\r
1316 leaf vlan-tag-id {
\r
1317 description "Vlan tag assigned to subinterface port";
\r
1320 leaf network-role {
\r
1321 description "e.g. untrusted ";
\r
1324 leaf network-role-tag {
\r
1325 description "Assuming HEAT template network role tag parameter - not used";
\r
1328 container network-information-items {
\r
1329 list network-information-item {
\r
1332 description "Use ipv4 or ipv6";
\r
1336 description "Indicator to use DHCP on this network for this VM - set to N for Vlan tagging";
\r
1337 type enumeration {
\r
1343 description "The number of ip addresses to be assigned per vm for this network role";
\r
1346 container network-ips {
\r
1347 leaf-list network-ip {
\r
1348 description "List of assigned ip addresses of type ip-version on a network.";
\r
1349 type inet:ip-address;
\r
1355 container floating-ips {
\r
1356 leaf-list floating-ip-v4 {
\r
1357 description "Floating ipv4 for VMs of a given type on this network";
\r
1358 type inet:ip-address;
\r
1361 leaf-list floating-ip-v6 {
\r
1362 description "Floating ipv6 for VMs of a given type on this network";
\r
1363 type inet:ipv6-address;
\r
1369 grouping vnf-cloud-param {
\r
1370 leaf service-instance-id {
\r
1373 leaf service-instance-name {
\r
1386 key "vf-module-id";
\r
1387 leaf vf-module-id {
\r
1394 grouping vnf-get-resource-request-input-data {
\r
1401 key "vf-module-id";
\r
1402 leaf vf-module-id {
\r
1408 grouping license-information {
\r
1409 container license-information {
\r
1410 list entitlement-pool-list {
\r
1411 key "entitlement-pool-uuid action";
\r
1412 leaf entitlement-pool-uuid {
\r
1420 leaf entitlement-pool-invariant-uuid {
\r
1423 leaf entitlement-uuid {
\r
1424 description "assigned by ALTS";
\r
1428 list license-key-group-list {
\r
1429 key "license-key-group-uuid action";
\r
1430 leaf license-key-group-uuid {
\r
1438 leaf license-key-group-invariant-uuid {
\r
1441 leaf license-key {
\r
1442 description "assigned by ALTS";
\r
1445 leaf license-uuid {
\r
1446 description "assigned by ALTS";
\r
1452 grouping related-network {
\r
1453 list related-network {
\r
1456 description "Key to l3-network object";
\r
1459 leaf network-role {
\r
1465 grouping connection-point {
\r
1466 container connection-point {
\r
1467 leaf connection-point-id {
\r
1468 description "Key to CP object in A&AI";
\r
1472 description "port-index when multiple CPs connect to same network. Default zero (0)";
\r
1478 description "Key to vlan-tag uuid object in A&AI Generated by vlan mS";
\r
1481 leaf vlan-tag-id {
\r
1484 leaf vlan-tag-description {
\r
1488 description "Inner/Outer roles";
\r
1494 grouping pnf-information {
\r
1495 container pnf-information {
\r
1497 description "Key for A&AI query";
\r
1503 uses onap-model-information;
\r
1506 grouping contrail-route-operation-information {
\r
1507 uses sdnc-request-header;
\r
1508 uses request-information;
\r
1509 uses service-information;
\r
1510 uses allotted-resource-information;
\r
1511 uses contrail-route-request-input;
\r
1513 grouping contrail-route-request-input {
\r
1514 container contrail-route-request-input {
\r
1515 container source-network {
\r
1516 uses network-info;
\r
1518 container dest-network {
\r
1519 uses network-info;
\r
1521 container contrail-applied-service-info {
\r
1522 leaf service-instance-id {
\r
1523 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
1526 leaf contrail-fqdn {
\r
1527 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
1531 container contrail-route-input-parameters {
\r
1536 grouping network-info {
\r
1540 leaf network-role {
\r
1544 grouping contrail-route-topology {
\r
1545 container contrail-route-topology {
\r
1546 uses allotted-resource-identifiers;
\r
1547 uses onap-model-information;
\r
1548 uses contrail-route-assignments;
\r
1549 container contrail-route-parameters {
\r
1554 grouping contrail-route-assignments {
\r
1555 container contrail-route-assignments {
\r
1557 description "The Contrail fq-name of the network policy";
\r
1560 leaf contrail-id {
\r
1561 description "The ID assigned by Contrail to the network-policy (one for one with the fq-name)";
\r
1564 container source-network {
\r
1565 uses network-info;
\r
1567 container dest-network {
\r
1568 uses network-info;
\r
1570 container contrail-applied-service {
\r
1571 leaf service-instance-id {
\r
1572 description "The service-instance-id of the vnf from which the contrail applied service is coming";
\r
1576 description "The vnf representing the contrail applied service";
\r
1579 leaf contrail-fqdn {
\r
1580 description "This is the fq-name of the Contrail service instance through which the route is passing.";
\r
1585 description "Contrail-assigned vlan-tag to the vipr vm interface for this route.";
\r
1590 grouping security-zone-operation-information {
\r
1591 uses sdnc-request-header;
\r
1592 uses request-information;
\r
1593 uses service-information;
\r
1594 uses allotted-resource-information;
\r
1595 uses security-zone-request-input;
\r
1597 grouping security-zone-request-input {
\r
1598 container security-zone-request-input {
\r
1602 leaf trusted-network-role {
\r
1603 description "In the case of vIPR, this is the landing networks network-role; used in naming";
\r
1606 leaf untrusted-network-role {
\r
1607 description "In the case of vIPR, this is the tenant oam networks network-role; used in naming";
\r
1610 container security-zone-input-parameters {
\r
1615 grouping security-zone-topology {
\r
1616 container security-zone-topology {
\r
1617 uses allotted-resource-identifiers;
\r
1618 uses onap-model-information;
\r
1619 uses security-zone-assignments;
\r
1620 container security-zone-parameters {
\r
1625 grouping security-zone-assignments {
\r
1626 container security-zone-assignments {
\r
1627 leaf trusted-network-role {
\r
1628 description "In the case of vIPR, this is the landing networks network-role; used in naming";
\r
1631 leaf security-zone-name-trusted {
\r
1634 leaf untrusted-network-role {
\r
1635 description "In the case of vIPR, this is the tenant oam networks network-role; used in naming";
\r
1638 leaf security-zone-name-untrusted {
\r
1641 leaf security-zone-service-instance-id {
\r
1642 description "Will be the same as the parent-service-instance-id";
\r
1645 leaf security-zone-vnf-id {
\r
1646 description "Selected by SDNC from the security-zone-service-instance-id";
\r
1654 grouping port-mirror-topology-operation-information {
\r
1655 uses sdnc-request-header;
\r
1656 uses request-information;
\r
1657 uses service-information;
\r
1658 uses configuration-information;
\r
1659 uses port-mirror-configuration-request-input;
\r
1661 grouping port-mirror-configuration-request-input {
\r
1662 container port-mirror-configuration-request-input {
\r
1663 container source-port {
\r
1665 leaf source-port-id {
\r
1666 description "needed for srv-action=disable/enable";
\r
1670 container dest-port {
\r
1673 uses region-identifier;
\r
1674 container port-mirror-configuration-input-parameters {
\r
1679 grouping port-info {
\r
1680 leaf service-instance-id {
\r
1681 description "May not be need.";
\r
1684 uses pnf-information;
\r
1685 uses vnf-information;
\r
1687 grouping port-mirror-configuration-topology {
\r
1688 container port-mirror-configuration-topology {
\r
1689 uses configuration-identifiers;
\r
1690 uses onap-model-information;
\r
1691 uses port-mirror-configuration-assignments;
\r
1692 container port-mirror-configuration-parameters {
\r
1697 grouping port-mirror-configuration-assignments {
\r
1698 container port-mirror-configuration-assignments {
\r
1699 container contrail-vmi-params {
\r
1702 leaf vnics-group-id {
\r
1705 leaf owning-entity {
\r
1708 leaf tenant-context {
\r
1709 description "From tenant object in A&AI";
\r
1713 description "Tenant name from A&AI for source VNF";
\r
1717 description "tenant-id from A&AI for source VNF";
\r
1720 leaf dest-tenant {
\r
1721 description "Tenant name from A&AI for destination VNF";
\r
1724 leaf dest-tenant-id {
\r
1725 description "tenant-id from A&AI for destination VNF";
\r
1728 leaf cloud-region-id {
\r
1731 leaf cloud-owner {
\r
1734 leaf dest-network-fqdn {
\r
1737 leaf source-network-fqdn {
\r
1740 leaf source-capacity {
\r
1741 description "Source port pps (packets per second) rating from tosca model";
\r
1744 leaf source-vnf-id {
\r
1747 leaf dest-vnf-id {
\r
1748 description "For vProbe";
\r
1751 leaf dest-pnf-name {
\r
1752 description "For pProbe";
\r
1755 leaf dest-p-interface {
\r
1756 description "For pProbe; from policy manager";
\r
1759 leaf dest-pnf-port-policy-name {
\r
1760 description "For pProbe; from tosca model";
\r
1764 description "vprobe or pprobe; derived from configuration-information.configuration-sub-type";
\r
1767 leaf route-allotted-resource-id {
\r
1768 description "For vProbe";
\r
1771 container source-vnfc-instance-group-id {
\r
1772 leaf service-instance-id {
\r
1775 leaf nfc-naming-code {
\r
1778 leaf instance-group-role {
\r
1781 leaf configuration-id {
\r
1785 container dest-vnfc-instance-group-id {
\r
1786 leaf service-instance-id {
\r
1789 leaf nfc-naming-code {
\r
1792 leaf instance-group-role {
\r
1795 leaf configuration-id {
\r
1799 container source-to-dest-maps {
\r
1800 list source-to-dest-map {
\r
1801 key "source-port-id";
\r
1802 leaf source-port-id {
\r
1806 leaf source-port-name {
\r
1809 leaf source-vserver-id {
\r
1812 leaf dest-vserver-id {
\r
1815 leaf dest-port-id {
\r
1818 leaf dest-port-name {
\r
1824 container dest-ip-addresses {
\r
1825 uses ip-addresses;
\r
1831 grouping gc-topology-operation-information {
\r
1832 uses sdnc-request-header;
\r
1833 uses request-information;
\r
1834 uses service-information;
\r
1835 uses configuration-information;
\r
1836 uses gc-request-input;
\r
1838 grouping gc-request-input {
\r
1839 container gc-request-input {
\r
1843 container input-parameters {
\r
1848 grouping vnr-parameters {
\r
1849 container vnr-parameters {
\r
1853 leaf vnf-service-instance-id {
\r
1856 leaf network-collection-service-instance-id {
\r
1857 description "service instance id that created network-collection";
\r
1860 leaf network-instance-group-id {
\r
1866 leaf vnfc-instance-group-function {
\r
1869 leaf network-instance-group-function {
\r
1872 leaf parent-port-role {
\r
1875 leaf upper-tag-id {
\r
1878 leaf lower-tag-id {
\r
1883 grouping tunnelxconn-operation-information {
\r
1884 uses sdnc-request-header;
\r
1885 uses request-information;
\r
1886 uses service-information;
\r
1887 uses allotted-resource-information;
\r
1888 uses tunnelxconn-request-input;
\r
1890 grouping tunnelxconn-request-input {
\r
1892 container tunnelxconn-request-input {
\r
1893 leaf brg-wan-mac-address {
\r
1898 grouping tunnelxconn-topology {
\r
1899 container tunnelxconn-topology {
\r
1900 uses allotted-resource-identifiers;
\r
1901 uses onap-model-information;
\r
1902 uses tunnelxconn-assignments;
\r
1903 container tunnelxconn-parameters {
\r
1908 grouping tunnelxconn-assignments {
\r
1909 container tunnelxconn-assignments {
\r
1911 description "The Network Controller will assign a VNI value from the associated vGMUX VNI pool";
\r
1914 leaf vgmux-bearer-ip {
\r
1915 description "The Network Controller will look up the vgmux bearer ip from the vgmux vf module";
\r
1916 type inet:ip-address;
\r
1918 leaf vgmux-lan-ip {
\r
1919 description "The Network Controller will look up the vgmux lan ip from the vgmux vg module";
\r
1920 type inet:ip-address;
\r
1923 description "The Network Controller will assign the VG IP address from local inventory";
\r
1924 type inet:ip-address;
\r
1928 grouping brg-operation-information {
\r
1929 uses sdnc-request-header;
\r
1930 uses request-information;
\r
1931 uses service-information;
\r
1932 uses allotted-resource-information;
\r
1933 uses brg-request-input;
\r
1935 grouping brg-request-input {
\r
1936 container brg-request-input {
\r
1937 leaf vgmux-bearer-ip {
\r
1938 type inet:ip-address;
\r
1943 leaf brg-wan-mac-address {
\r
1948 grouping brg-topology {
\r
1949 container brg-topology {
\r
1950 uses allotted-resource-identifiers;
\r
1951 uses onap-model-information;
\r
1952 uses brg-assignments;
\r
1953 container brg-parameters {
\r
1958 grouping brg-assignments {
\r
1959 container brg-assignments {
\r
1960 leaf vbrg-wan-ip {
\r
1961 type inet:ip-address;
\r
1965 grouping connection-attachment-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 connection-attachment-request-input;
\r
1973 grouping connection-attachment-request-input {
\r
1974 container connection-attachment-request-input {
\r
1979 grouping connection-attachment-topology {
\r
1980 container brg-topology {
\r
1981 uses allotted-resource-identifiers;
\r
1982 uses onap-model-information;
\r
1983 uses connection-attachment-assignments;
\r
1984 container connection-attachment-parameters {
\r
1990 grouping connection-attachment-assignments {
\r
1991 container connection-attachment-assignments {
\r
1995 grouping allotted-resource-information {
\r
1996 container allotted-resource-information {
\r
1997 leaf allotted-resource-id {
\r
2000 leaf allotted-resource-type {
\r
2001 description "Not an enum, but expected values are contrail-route and security-zone.";
\r
2004 leaf parent-service-instance-id {
\r
2005 description "Service-instance-id of the parent service to which this allotted resource belongs.";
\r
2008 uses onap-model-information;
\r
2011 grouping allotted-resource-identifiers {
\r
2012 container allotted-resource-identifiers {
\r
2013 leaf allotted-resource-id {
\r
2016 leaf allotted-resource-name {
\r
2017 description "For a contrail-route, the network policy name.";
\r
2020 leaf allotted-resource-type {
\r
2021 description "(Added in draft 32)Expected to be contrail-route or security-zone.";
\r
2024 leaf consuming-service-instance-id {
\r
2025 description "The service-instance-id of the consuming service of this allotted resource";
\r
2028 leaf parent-service-instance-id {
\r
2029 description "Service-instance-id of the parent service to which this allotted resource belongs.";
\r
2034 grouping allotted-resource-oper-status {
\r
2035 container allotted-resource-oper-status {
\r
2036 uses oper-status-data;
\r
2039 grouping allotted-resource-status {
\r
2040 container allotted-resource-status {
\r
2041 leaf response-code {
\r
2044 leaf response-message {
\r
2047 leaf final-indicator {
\r
2050 leaf request-status {
\r
2051 type enumeration {
\r
2052 enum "synccomplete";
\r
2053 enum "asynccomplete";
\r
2054 enum "notifycomplete";
\r
2058 description "value would one of possible request-actions; match the list in service-data oper-status";
\r
2065 description "this is the svc-action from the incoming request";
\r
2066 type enumeration {
\r
2072 enum "deactivate";
\r
2075 leaf response-timestamp {
\r
2080 grouping configuration-information {
\r
2081 container configuration-information {
\r
2082 leaf configuration-id {
\r
2085 leaf configuration-name {
\r
2088 leaf configuration-type {
\r
2089 description "Not an enum, but expected values are port-mirror-configuration, vlan-network-receptor";
\r
2092 leaf configuration-sub-type {
\r
2093 description "e.g. vprobe and pprobe when configuration-type=port-mirror-configuration";
\r
2096 uses onap-model-information;
\r
2099 grouping configuration-identifiers {
\r
2100 container configuration-identifiers {
\r
2101 leaf configuration-id {
\r
2104 leaf configuration-name {
\r
2107 leaf configuration-type {
\r
2108 description "Not an enum, but expected values are port-mirror-configuration.";
\r
2111 leaf configuration-sub-type {
\r
2112 description " vprobe and pprobe";
\r
2115 leaf parent-service-instance-id {
\r
2116 description "Service-instance-id of the parent service to which this resource belongs.";
\r
2121 grouping configuration-oper-status {
\r
2122 container configuration-oper-status {
\r
2123 uses oper-status-data;
\r
2126 grouping configuration-status {
\r
2127 container configuration-status {
\r
2128 leaf response-code {
\r
2131 leaf response-message {
\r
2134 leaf final-indicator {
\r
2137 leaf request-status {
\r
2138 type enumeration {
\r
2139 enum "synccomplete";
\r
2140 enum "asynccomplete";
\r
2141 enum "notifycomplete";
\r
2145 description "value would one of possible request-actions; match the list in service-data oper-status";
\r
2152 description "this is the svc-action from the incoming request";
\r
2153 type enumeration {
\r
2161 enum "deactivate";
\r
2164 leaf response-timestamp {
\r
2169 grouping topology-response-common {
\r
2170 leaf svc-request-id {
\r
2171 description "the request id from the request message for which this is the responseKeep as M";
\r
2174 leaf response-code {
\r
2175 description "a success code or an defined error codeKeep as M";
\r
2178 leaf response-message {
\r
2179 description "message included for error code";
\r
2182 leaf ack-final-indicator {
\r
2183 description "Expected to be Y or N.";
\r
2187 grouping sdnc-request-header {
\r
2188 container sdnc-request-header {
\r
2189 leaf svc-request-id {
\r
2190 description "Uniquely generated by calling system (e.g. MSO or SDN-GP)";
\r
2194 description "This is the rpcAction";
\r
2195 type enumeration {
\r
2200 enum "changeassign";
\r
2201 enum "changedelete";
\r
2203 enum "deactivate";
\r
2211 leaf svc-notification-url {
\r
2212 description "Contains URL for asynchronous response";
\r
2217 grouping request-information {
\r
2218 container request-information {
\r
2220 description "Request ID generated upstream of MSO";
\r
2223 leaf request-action {
\r
2224 description "still need to work Disconnect";
\r
2225 type enumeration {
\r
2226 enum "CreateNetworkInstance";
\r
2227 enum "ActivateNetworkInstance";
\r
2228 enum "CreateServiceInstance";
\r
2229 enum "DeleteServiceInstance";
\r
2230 enum "DeleteNetworkInstance";
\r
2231 enum "CreateVnfInstance";
\r
2232 enum "ActivateVnfInstance";
\r
2233 enum "DeleteVnfInstance";
\r
2234 enum "CreateVfModuleInstance";
\r
2235 enum "ActivateVfModuleInstance";
\r
2236 enum "DeleteVfModuleInstance";
\r
2237 enum "CreateContrailRouteInstance";
\r
2238 enum "DeleteContrailRouteInstance";
\r
2239 enum "CreateSecurityZoneInstance";
\r
2240 enum "DeleteSecurityZoneInstance";
\r
2241 enum "ActivateDCINetworkInstance";
\r
2242 enum "DeActivateDCINetworkInstance";
\r
2243 enum "CreateTunnelXConnInstance";
\r
2244 enum "DeleteTunnelXConnInstance";
\r
2245 enum "CreateBRGInstance";
\r
2246 enum "DeleteBRGInstance";
\r
2247 enum "CreateSOTNConnectivityInstance";
\r
2248 enum "ActivateSOTNConnectivityInstance";
\r
2249 enum "DeactivateSOTNConnectivityInstance";
\r
2250 enum "DeleteSOTNConnectivityInstance";
\r
2251 enum "CreateSOTNAttachmentInstance";
\r
2252 enum "ActivateSOTNAttachmentInstance";
\r
2253 enum "DeactivateSOTNAttachmentInstance";
\r
2254 enum "DeleteSOTNAttachmentInstance";
\r
2255 enum "CreateSiteInstance";
\r
2256 enum "ActivateSiteInstance";
\r
2257 enum "DeactivateSiteInstance";
\r
2258 enum "DeleteSiteInstance";
\r
2259 enum "CreatePortMirrorConfigurationInstance";
\r
2260 enum "DeletePortMirrorConfigurationInstance";
\r
2261 enum "ChangePortMirrorConfigurationInstance";
\r
2262 enum "CreateGenericConfigurationInstance";
\r
2263 enum "DeleteGenericConfigurationInstance";
\r
2264 enum "PreloadVfModuleRequest";
\r
2265 enum "DeletePreloadVfModuleRequest";
\r
2266 enum "PreloadNetworkRequest";
\r
2267 enum "DeletePreloadNetworkRequest";
\r
2268 enum "CreateForwardingPathInstance";
\r
2269 enum "DeleteForwardingPathInstance";
\r
2270 enum "UpdateForwardingPathInstance";
\r
2271 enum "CreateSDWANConnectivityInstance";
\r
2272 enum "ActivateSDWANConnectivityInstance";
\r
2273 enum "DeactivateSDWANConnectivityInstance";
\r
2274 enum "DeleteSDWANConnectivityInstance";
\r
2275 enum "CreateSDWANDeviceInstance";
\r
2276 enum "ActivateSDWANDeviceInstance";
\r
2277 enum "DeactivateSDWANDeviceInstance";
\r
2278 enum "DeleteSDWANDeviceInstance";
\r
2279 enum "CreateSDWANPortInstance";
\r
2280 enum "ActivateSDWANPortInstance";
\r
2281 enum "DeactivateSDWANPortInstance";
\r
2282 enum "DeleteSDWANPortInstance";
\r
2283 enum "CreateSDWANAttachmentInstance";
\r
2284 enum "ActivateSDWANAttachmentInstance";
\r
2285 enum "DeactivateSDWANAttachmentInstance";
\r
2286 enum "DeleteSDWANAttachmentInstance";
\r
2292 leaf notification-url {
\r
2295 leaf order-number {
\r
2298 leaf order-version {
\r
2303 grouping service-information {
\r
2304 container service-information {
\r
2306 description "This maps to the product-family-id in A&AI";
\r
2309 leaf subscription-service-type {
\r
2310 description "used to reference a&ai subscription-service-type. For example, we show as vIPR-ATM in example.";
\r
2313 uses onap-model-information;
\r
2314 leaf service-instance-id {
\r
2317 leaf global-customer-id {
\r
2318 description "need for put of data to AnAI (MSO provides)";
\r
2321 leaf subscriber-name {
\r
2322 description "Would not be expected for vIPR-ATM or mobility services.";
\r
2327 grouping onap-model-information {
\r
2328 container onap-model-information {
\r
2329 leaf model-invariant-uuid {
\r
2330 description "identifies the invariant uuid for this service or resource";
\r
2333 leaf model-customization-uuid {
\r
2334 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
2338 description "identifies the uuid for this service or resource, which is version specific";
\r
2341 leaf model-version {
\r
2349 grouping region-identifier {
\r
2353 leaf aic-cloud-region {
\r
2354 description "The AIC cloud region which maps to contrail versions";
\r
2358 description "Not expected to be used";
\r
2371 container resource-resolution-data {
\r
2372 list resource-key {
\r
2382 description "SUCCESS, FAILED, or PENDING - RA returned data as capability";
\r
2385 leaf capability-name {
\r
2386 description "Resource assignment resolution Capability name";
\r
2392 grouping ip-addresses {
\r
2393 container ip-addresses {
\r
2394 leaf ipv4-address {
\r
2395 type inet:ip-address;
\r
2397 leaf ipv6-address {
\r
2398 type inet:ip-address;
\r
2400 leaf vipv4-address {
\r
2401 description "Virtual v4";
\r
2402 type inet:ip-address;
\r
2404 leaf vipv6-address {
\r
2405 description "Virtual v6";
\r
2406 type inet:ip-address;
\r
2410 grouping instance-reference {
\r
2411 leaf instance-id {
\r
2414 leaf object-path {
\r
2415 description "restconf retrieval path to this particular objectE.g. restconf/config/GENERIC-RESOURCE-API:services/service/$service-instance-id/service-data/service-topology/";
\r
2419 grouping oper-status-data {
\r
2420 leaf order-status {
\r
2421 description "TBD - do we need Request failed statuses? RequestFailed | InProgressTimeout";
\r
2422 type enumeration {
\r
2424 enum "PendingAssignment";
\r
2425 enum "PendingCreate";
\r
2426 enum "PendingUpdate";
\r
2427 enum "PendingDelete";
\r
2432 leaf last-rpc-action {
\r
2433 type enumeration {
\r
2438 enum "deactivate";
\r
2440 enum "changeassign";
\r
2443 leaf last-action {
\r
2444 description "should be list of possible request-actions";
\r
2445 type enumeration {
\r
2446 enum "CreateNetworkInstance";
\r
2447 enum "ActivateNetworkInstance";
\r
2448 enum "CreateServiceInstance";
\r
2449 enum "DeleteServiceInstance";
\r
2450 enum "DeleteNetworkInstance";
\r
2451 enum "CreateVnfInstance";
\r
2452 enum "ActivateVnfInstance";
\r
2453 enum "DeleteVnfInstance";
\r
2454 enum "CreateVfModuleInstance";
\r
2455 enum "ActivateVfModuleInstance";
\r
2456 enum "DeleteVfModuleInstance";
\r
2457 enum "CreateContrailRouteInstance";
\r
2458 enum "DeleteContrailRouteInstance";
\r
2459 enum "CreateSecurityZoneInstance";
\r
2460 enum "DeleteSecurityZoneInstance";
\r
2461 enum "ActivateDCINetworkInstance";
\r
2462 enum "DeActivateDCINetworkInstance";
\r
2463 enum "CreateTunnelXConnInstance";
\r
2464 enum "DeleteTunnelXConnInstance";
\r
2465 enum "CreateBRGInstance";
\r
2466 enum "DeleteBRGInstance";
\r
2467 enum "CreateSOTNConnectivityInstance";
\r
2468 enum "ActivateSOTNConnectivityInstance";
\r
2469 enum "DeactivateSOTNConnectivityInstance";
\r
2470 enum "DeleteSOTNConnectivityInstance";
\r
2471 enum "CreateSOTNAttachmentInstance";
\r
2472 enum "ActivateSOTNAttachmentInstance";
\r
2473 enum "DeactivateSOTNAttachmentInstance";
\r
2474 enum "DeleteSOTNAttachmentInstance";
\r
2475 enum "CreateSiteInstance";
\r
2476 enum "ActivateSiteInstance";
\r
2477 enum "DeactivateSiteInstance";
\r
2478 enum "DeleteSiteInstance";
\r
2479 enum "CreatePortMirrorConfigurationInstance";
\r
2480 enum "DeletePortMirrorConfigurationInstance";
\r
2481 enum "ChangePortMirrorConfigurationInstance";
\r
2482 enum "CreateGenericConfigurationInstance";
\r
2483 enum "DeleteGenericConfigurationInstance";
\r
2484 enum "PreloadVfModuleRequest";
\r
2485 enum "DeletePreloadVfModuleRequest";
\r
2486 enum "PreloadNetworkRequest";
\r
2487 enum "DeletePreloadNetworkRequest";
\r
2488 enum "CreateForwardingPathInstance";
\r
2489 enum "DeleteForwardingPathInstance";
\r
2490 enum "UpdateForwardingPathInstance";
\r
2491 enum "CreateSDWANConnectivityInstance";
\r
2492 enum "ActivateSDWANConnectivityInstance";
\r
2493 enum "DeactivateSDWANConnectivityInstance";
\r
2494 enum "DeleteSDWANConnectivityInstance";
\r
2495 enum "CreateSDWANDeviceInstance";
\r
2496 enum "ActivateSDWANDeviceInstance";
\r
2497 enum "DeactivateSDWANDeviceInstance";
\r
2498 enum "DeleteSDWANDeviceInstance";
\r
2499 enum "CreateSDWANPortInstance";
\r
2500 enum "ActivateSDWANPortInstance";
\r
2501 enum "DeactivateSDWANPortInstance";
\r
2502 enum "DeleteSDWANPortInstance";
\r
2503 enum "CreateSDWANAttachmentInstance";
\r
2504 enum "ActivateSDWANAttachmentInstance";
\r
2505 enum "DeactivateSDWANAttachmentInstance";
\r
2506 enum "DeleteSDWANAttachmentInstance";
\r
2509 leaf last-svc-request-id {
\r
2510 description "Not currently populated in service data.";
\r
2513 leaf last-order-status {
\r
2514 type enumeration {
\r
2516 enum "PendingAssignment";
\r
2517 enum "PendingCreate";
\r
2518 enum "PendingUpdate";
\r
2519 enum "PendingDelete";
\r
2524 leaf create-timestamp {
\r
2525 description "Not currently populated in service data.";
\r
2528 leaf modify-timestamp {
\r
2532 grouping service-response-information {
\r
2533 container service-response-information {
\r
2534 uses instance-reference;
\r
2537 grouping network-response-information {
\r
2538 container network-response-information {
\r
2539 uses instance-reference;
\r
2542 grouping vnf-response-information {
\r
2543 container vnf-response-information {
\r
2544 uses instance-reference;
\r
2547 grouping vf-module-response-information {
\r
2548 container vf-module-response-information {
\r
2549 uses instance-reference;
\r
2552 grouping contrail-route-response-information {
\r
2553 container contrail-route-response-information {
\r
2554 uses instance-reference;
\r
2557 grouping security-zone-response-information {
\r
2558 container security-zone-response-information {
\r
2559 uses instance-reference;
\r
2562 grouping getpathsegment-response-information {
\r
2563 container getpathsegment-response-information {
\r
2564 uses instance-reference;
\r
2567 grouping port-mirror-response-information {
\r
2568 container port-mirror-response-information {
\r
2569 uses instance-reference;
\r
2572 grouping gc-response-information {
\r
2573 container gc-response-information {
\r
2574 uses instance-reference;
\r
2577 grouping tunnelxconn-response-information {
\r
2578 container tunnelxconn-response-information {
\r
2579 uses instance-reference;
\r
2582 grouping brg-response-information {
\r
2583 container brg-response-information {
\r
2584 uses instance-reference;
\r
2587 grouping connection-attachment-response-information {
\r
2588 container connection-attachment-response-information {
\r
2589 uses instance-reference;
\r
2592 grouping preload-model-information {
\r
2593 list preload-list {
\r
2594 key "preload-id preload-type";
\r
2596 description "vf-module-name or network name";
\r
2600 leaf preload-type {
\r
2601 description "network or vf-module";
\r
2605 uses preload-data;
\r
2608 grouping preload-data {
\r
2609 container preload-data {
\r
2610 uses preload-vf-module-topology-information;
\r
2611 uses preload-network-topology-information;
\r
2612 uses preload-oper-status;
\r
2615 grouping preload-vf-module-topology-information {
\r
2616 container preload-vf-module-topology-information {
\r
2617 uses vnf-topology-identifier-structure;
\r
2618 uses vnf-resource-assignments;
\r
2619 uses vf-module-topology;
\r
2622 grouping preload-network-topology-information {
\r
2623 container preload-network-topology-information {
\r
2624 uses network-topology-identifier-structure;
\r
2626 uses vpn-bindings;
\r
2627 uses network-policy;
\r
2628 uses route-table-reference;
\r
2630 uses provider-network-information;
\r
2633 grouping subnets {
\r
2635 key "start-address";
\r
2636 leaf start-address {
\r
2637 type inet:ip-address;
\r
2639 leaf gateway-address {
\r
2640 type inet:ip-address;
\r
2648 leaf dhcp-enabled {
\r
2649 type enumeration {
\r
2654 leaf dhcp-start-address {
\r
2657 leaf dhcp-end-address {
\r
2660 leaf addr-from-start {
\r
2661 description "Default is N";
\r
2662 type enumeration {
\r
2667 leaf subnet-name {
\r
2670 leaf subnet-role {
\r
2673 leaf subnet-sequence {
\r
2678 grouping vpn-bindings {
\r
2679 list vpn-bindings {
\r
2680 key "vpn-binding-id";
\r
2681 leaf vpn-binding-id {
\r
2687 leaf global-route-target {
\r
2690 leaf route-target-role {
\r
2694 description "AIC Zone the route target associated with";
\r
2699 grouping network-policy {
\r
2700 list network-policy {
\r
2701 key "network-policy-fqdn";
\r
2702 leaf network-policy-fqdn {
\r
2705 leaf network-policy-id {
\r
2710 grouping route-table-reference {
\r
2711 list route-table-reference {
\r
2712 key "route-table-reference-fqdn";
\r
2713 leaf route-table-reference-fqdn {
\r
2717 leaf route-table-reference-id {
\r
2722 grouping provider-network-information {
\r
2723 leaf physical-network-name {
\r
2726 leaf is-provider-network {
\r
2729 leaf is-shared-network {
\r
2732 leaf is-external-network {
\r
2736 grouping host-routes {
\r
2737 list host-routes {
\r
2738 key "route-prefix";
\r
2739 leaf route-prefix {
\r
2743 description "Could be ip-address or hostname or service-instance";
\r
2748 grouping preload-oper-status {
\r
2749 container preload-oper-status {
\r
2750 leaf order-status {
\r
2751 type enumeration {
\r
2753 enum "PendingAssignment";
\r
2754 enum "PendingCreate";
\r
2755 enum "PendingUpdate";
\r
2756 enum "PendingDelete";
\r
2760 leaf last-action {
\r
2761 type enumeration {
\r
2762 enum "PreloadVfModuleRequest";
\r
2763 enum "DeletePreloadVfModuleRequest";
\r
2764 enum "PreloadNetworkRequest";
\r
2765 enum "DeletePreloadNetworkRequest";
\r
2768 leaf last-svc-request-id {
\r
2771 leaf last-order-status {
\r
2772 type enumeration {
\r
2774 enum "PendingAssignment";
\r
2775 enum "PendingCreate";
\r
2776 enum "PendingUpdate";
\r
2777 enum "PendingDelete";
\r
2781 leaf create-timestamp {
\r
2784 leaf modify-timestamp {
\r
2787 leaf maintenance-indicator {
\r
2788 type enumeration {
\r
2795 grouping preload-topology-response-body {
\r
2796 leaf svc-request-id {
\r
2799 leaf response-code {
\r
2802 leaf response-message {
\r
2805 leaf ack-final-indicator {
\r
2809 rpc generic-configuration-notification {
\r
2811 uses sdnc-request-header;
\r
2812 uses request-information;
\r
2813 uses service-information;
\r
2814 uses configuration-information;
\r
2815 uses topology-response-common;
\r
2816 leaf configuration-topology-link {
\r
2817 description "Returns URL to generic-configuration-topology ";
\r
2820 uses vnr-parameters;
\r
2823 container services {
\r
2824 uses service-model-infrastructure;
\r
2826 container contrail-route-allotted-resources {
\r
2827 list contrail-route-allotted-resource {
\r
2828 key "allotted-resource-id";
\r
2829 leaf allotted-resource-id {
\r
2833 container allotted-resource-data {
\r
2834 container allotted-resource-operation-information {
\r
2835 uses contrail-route-operation-information;
\r
2837 uses contrail-route-topology;
\r
2838 uses allotted-resource-oper-status;
\r
2840 uses allotted-resource-status;
\r
2843 container security-zone-allotted-resources {
\r
2844 list security-zone-allotted-resource {
\r
2845 key "allotted-resource-id";
\r
2846 leaf allotted-resource-id {
\r
2850 container allotted-resource-data {
\r
2851 container allotted-resource-operation-information {
\r
2852 uses security-zone-operation-information;
\r
2854 uses security-zone-topology;
\r
2855 container security-zone-parameters {
\r
2858 uses allotted-resource-oper-status;
\r
2860 uses allotted-resource-status;
\r
2863 container tunnelxconn-allotted-resources {
\r
2864 list tunnelxconn-allotted-resource {
\r
2865 key "allotted-resource-id";
\r
2866 leaf allotted-resource-id {
\r
2870 container allotted-resource-data {
\r
2871 container allotted-resource-operation-information {
\r
2872 uses tunnelxconn-operation-information;
\r
2874 uses tunnelxconn-topology;
\r
2875 container tunnelxconn-parameters {
\r
2878 uses allotted-resource-oper-status;
\r
2880 uses allotted-resource-status;
\r
2883 container brg-allotted-resources {
\r
2884 list brg-allotted-resource {
\r
2885 key "allotted-resource-id";
\r
2886 leaf allotted-resource-id {
\r
2890 container allotted-resource-data {
\r
2891 container allotted-resource-operation-information {
\r
2892 uses brg-operation-information;
\r
2894 uses brg-topology;
\r
2895 container brg-parameters {
\r
2898 uses allotted-resource-oper-status;
\r
2900 uses allotted-resource-status;
\r
2903 container connection-attachment-allotted-resources {
\r
2904 list connection-attachment-allotted-resource {
\r
2905 key "allotted-resource-id";
\r
2906 leaf allotted-resource-id {
\r
2910 container allotted-resource-data {
\r
2911 container allotted-resource-operation-information {
\r
2912 uses connection-attachment-operation-information;
\r
2914 uses connection-attachment-topology;
\r
2915 container connection-attachment-parameters {
\r
2918 uses allotted-resource-oper-status;
\r
2920 uses allotted-resource-status;
\r
2923 container port-mirror-configurations {
\r
2924 list port-mirror-configuration {
\r
2925 key "configuration-id";
\r
2926 leaf configuration-id {
\r
2930 container configuration-data {
\r
2931 container configuration-operation-information {
\r
2932 uses port-mirror-topology-operation-information;
\r
2934 uses port-mirror-configuration-topology;
\r
2935 uses configuration-oper-status;
\r
2937 uses configuration-status;
\r
2940 container generic-configurations {
\r
2941 list gc-configuration {
\r
2942 key "configuration-id";
\r
2943 leaf configuration-id {
\r
2947 container configuration-data {
\r
2948 container configuration-operation-information {
\r
2949 uses gc-topology-operation-information;
\r
2951 uses configuration-oper-status;
\r
2953 uses configuration-status;
\r
2956 rpc service-topology-operation {
\r
2958 uses service-operation-information;
\r
2961 uses topology-response-common;
\r
2962 uses service-response-information;
\r
2965 rpc network-topology-operation {
\r
2967 uses network-operation-information;
\r
2970 uses topology-response-common;
\r
2971 uses network-response-information;
\r
2972 uses service-response-information;
\r
2975 rpc vnf-topology-operation {
\r
2977 uses vnf-operation-information;
\r
2980 uses topology-response-common;
\r
2981 uses vnf-response-information;
\r
2982 uses service-response-information;
\r
2985 rpc vf-module-topology-operation {
\r
2987 uses vf-module-operation-information;
\r
2990 uses topology-response-common;
\r
2991 uses vf-module-response-information;
\r
2992 uses vnf-response-information;
\r
2993 uses service-response-information;
\r
2996 rpc contrail-route-topology-operation {
\r
2998 uses contrail-route-operation-information;
\r
3001 uses topology-response-common;
\r
3002 uses contrail-route-response-information;
\r
3003 uses service-response-information;
\r
3006 rpc security-zone-topology-operation {
\r
3008 uses security-zone-operation-information;
\r
3011 uses topology-response-common;
\r
3012 uses security-zone-response-information;
\r
3013 uses service-response-information;
\r
3016 rpc tunnelxconn-topology-operation {
\r
3018 uses tunnelxconn-operation-information;
\r
3021 uses topology-response-common;
\r
3022 uses tunnelxconn-response-information;
\r
3023 uses service-response-information;
\r
3026 rpc brg-topology-operation {
\r
3028 uses brg-operation-information;
\r
3031 uses topology-response-common;
\r
3032 uses brg-response-information;
\r
3033 uses service-response-information;
\r
3036 rpc policy-update-notify-operation {
\r
3038 leaf policy-name {
\r
3043 description "Map JSON versionNo to version-id";
\r
3047 leaf update-type {
\r
3061 rpc getpathsegment-topology-operation {
\r
3063 uses forwarding-path-operation-information;
\r
3066 uses topology-response-common;
\r
3067 uses getpathsegment-response-information;
\r
3068 uses service-response-information;
\r
3071 rpc port-mirror-topology-operation {
\r
3073 uses port-mirror-topology-operation-information;
\r
3076 uses topology-response-common;
\r
3077 uses port-mirror-response-information;
\r
3078 uses service-response-information;
\r
3081 rpc generic-configuration-topology-operation {
\r
3083 uses gc-topology-operation-information;
\r
3086 uses topology-response-common;
\r
3087 uses gc-response-information;
\r
3088 uses service-response-information;
\r
3091 rpc vnf-get-resource-request {
\r
3093 uses sdnc-request-header;
\r
3094 uses request-information;
\r
3095 uses service-information;
\r
3096 uses vnf-get-resource-request-input-data;
\r
3099 container vnf-get-resource-response-information {
\r
3100 uses vnf-cloud-param;
\r
3104 container preload-information {
\r
3105 uses preload-model-information;
\r
3107 rpc preload-vf-module-topology-operation {
\r
3109 uses sdnc-request-header;
\r
3110 uses request-information;
\r
3111 uses preload-vf-module-topology-information;
\r
3114 uses preload-topology-response-body;
\r
3117 rpc preload-network-topology-operation {
\r
3119 uses sdnc-request-header;
\r
3120 uses request-information;
\r
3121 uses preload-network-topology-information;
\r
3124 uses preload-topology-response-body;
\r
3128 rpc connection-attachment-topology-operation {
\r
3130 uses connection-attachment-operation-information;
\r
3133 uses topology-response-common;
\r
3134 uses connection-attachment-response-information;
\r
3135 uses service-response-information;
\r
3139 } ////closes the module
\r
Code Review / sdnc / northbound.git / blob