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 from-preload {
\r
259 description "Indicates if source is preload data";
\r
262 uses onap-model-information;
\r
265 grouping network-request-input {
\r
266 container network-request-input {
\r
267 leaf network-name {
\r
270 uses region-identifier;
\r
271 container network-input-parameters {
\r
274 leaf network-instance-group-id {
\r
275 description "When network has instance-group role in service model";
\r
280 grouping network-topology {
\r
281 container network-topology {
\r
282 uses network-topology-identifier-structure;
\r
283 uses region-identifier;
\r
284 uses onap-model-information;
\r
285 uses network-assignments;
\r
286 uses network-parameters;
\r
289 grouping network-topology-identifier-structure {
\r
290 container network-topology-identifier-structure {
\r
294 leaf network-name {
\r
297 leaf network-role {
\r
300 leaf network-type {
\r
303 leaf network-instance-group-id {
\r
304 description "When network is part of network instance-Group-data & instance Group in A&AI";
\r
307 leaf network-technology {
\r
310 leaf eipam-v4-address-plan {
\r
313 leaf eipam-v6-address-plan {
\r
318 grouping network-assignments {
\r
319 container network-assignments {
\r
322 grouping network-parameters {
\r
323 container network-parameters {
\r
324 list network-parameter {
\r
325 key "network-parameter-name";
\r
326 leaf network-parameter-name {
\r
329 leaf network-parameter-value {
\r
335 grouping network-instance-group {
\r
336 list network-instance-group {
\r
337 key "network-instance-group-id";
\r
338 leaf network-instance-group-id {
\r
339 description "Also a Key in Network Instance Group in A&AI";
\r
343 leaf network-instance-group-function {
\r
346 leaf service-instance-id {
\r
349 uses onap-model-information;
\r
350 container subnet-assignment-policy {
\r
352 description "Current valid values - unique, shared (default)";
\r
356 container vpn-binding-policy {
\r
366 leaf vpn-platform {
\r
369 leaf global-route-target {
\r
372 leaf route-target-role {
\r
377 leaf subnet-key-value {
\r
378 description "key-value provided to EIPAM when creating shared subnet";
\r
381 container networks {
\r
385 description "Index into network-topology-identifier structure";
\r
393 leaf network-status {
\r
394 description "assigned, unassigned";
\r
397 container customer-bonding-requests {
\r
398 list customer-bonding-request {
\r
399 key "configuration-id";
\r
400 leaf configuration-id {
\r
401 description "e.g. vlan network receptor configuration id";
\r
410 grouping network-level-oper-status {
\r
411 container network-level-oper-status {
\r
412 uses oper-status-data;
\r
415 grouping vnf-operation-information {
\r
416 uses sdnc-request-header;
\r
417 uses request-information;
\r
418 uses service-information;
\r
419 uses vnf-information;
\r
420 uses vnf-request-input;
\r
422 grouping vnf-information {
\r
423 container vnf-information {
\r
433 uses onap-model-information;
\r
436 grouping vnf-request-input {
\r
437 container vnf-request-input {
\r
438 leaf request-version {
\r
444 uses region-identifier;
\r
445 container vnf-networks {
\r
447 key "network-role";
\r
448 uses vnf-network-data;
\r
451 list vnf-network-instance-group-ids {
\r
452 key "vnf-network-instance-group-id";
\r
453 leaf vnf-network-instance-group-id {
\r
454 description "List of vnf network-instance-group";
\r
458 container vnf-input-parameters {
\r
463 grouping vnf-topology {
\r
464 container vnf-topology {
\r
465 uses vnf-topology-identifier-structure;
\r
466 uses region-identifier;
\r
467 uses onap-model-information;
\r
468 uses vnf-resource-assignments;
\r
469 container vnf-parameters-data {
\r
472 leaf sdnc-generated-cloud-resources {
\r
473 description "Indicate if source is sdnc generated cloud param";
\r
478 grouping vnf-topology-identifier-structure {
\r
479 container vnf-topology-identifier-structure {
\r
484 description "In preload tree, this label is used for the vf-module-type";
\r
497 description "used in vnf naming";
\r
501 description "optionally comes from vnf-request-input container or is assigned by sdn-c";
\r
506 grouping vnf-resource-assignments {
\r
507 container vnf-resource-assignments {
\r
509 description "Orchestration status from AAI - to be set by SDNC";
\r
512 container availability-zones {
\r
513 leaf-list availability-zone {
\r
514 description "Openstack availability zone name or UUID";
\r
519 description "From the TOSCA data. Indicates the largest availability zone count needed by any vf-module in the VNF.";
\r
523 container vnf-networks {
\r
525 key "network-role";
\r
526 uses vnf-network-data;
\r
531 grouping vnf-network-data {
\r
532 leaf network-role {
\r
533 description "A Network Role to which a VNF must connect";
\r
536 leaf network-name {
\r
537 description "Unique Neutron UUID of an instance of the network role ";
\r
541 description "Unique Neutron UUID of an instance of the network role ";
\r
545 description "Unique Neutron UUID of an instance of the network role ";
\r
548 leaf contrail-network-fqdn {
\r
549 description "contrail network policy object";
\r
552 container subnets-data {
\r
554 key "sdnc-subnet-id";
\r
555 leaf sdnc-subnet-id {
\r
556 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
560 description "Subnet Role for the subnet";
\r
564 description "Populated for preload only";
\r
568 description "Should be ipv4 or ipv6";
\r
572 description "subnet UUID to be passed into the HEAT template";
\r
575 leaf dhcp-enabled {
\r
576 description "Indicator to use this subnet for DHCP ";
\r
585 grouping vnf-level-oper-status {
\r
586 container vnf-level-oper-status {
\r
587 uses oper-status-data;
\r
590 grouping vf-module-operation-information {
\r
591 uses sdnc-request-header;
\r
592 uses request-information;
\r
593 uses service-information;
\r
594 uses vnf-information;
\r
595 uses vf-module-information;
\r
596 uses vf-module-request-input;
\r
598 grouping vf-module-information {
\r
599 container vf-module-information {
\r
600 leaf vf-module-id {
\r
603 leaf vf-module-type {
\r
606 leaf from-preload {
\r
607 description "Indicates if source is preload data";
\r
610 uses onap-model-information;
\r
613 grouping vf-module-request-input {
\r
614 container vf-module-request-input {
\r
615 leaf request-version {
\r
616 description "keep this?";
\r
619 leaf vf-module-name {
\r
622 uses region-identifier;
\r
623 container vf-module-input-parameters {
\r
628 grouping vf-module-topology {
\r
629 container vf-module-topology {
\r
630 uses vf-module-topology-identifier;
\r
631 uses region-identifier;
\r
632 uses onap-model-information;
\r
633 uses vf-module-assignments;
\r
634 container vf-module-parameters {
\r
637 leaf sdnc-generated-cloud-resources {
\r
638 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
643 grouping vf-module-topology-identifier {
\r
644 container vf-module-topology-identifier {
\r
645 leaf vf-module-id {
\r
646 description "vf-module id";
\r
649 leaf vf-module-name {
\r
650 description "vf-module-name";
\r
653 leaf vf-module-type {
\r
658 grouping vf-module-assignments {
\r
659 container vf-module-assignments {
\r
660 leaf vf-module-status {
\r
661 description "Orchestration status from AAI - to be set by SDNC";
\r
667 uses vm-topology-data;
\r
670 uses vlan-vnfc-instance-groups;
\r
673 grouping vm-topology-data {
\r
678 leaf nfc-naming-code {
\r
679 description "used in vm naming(draft 29: changed from nfc-code)";
\r
683 description "from tosca data on vfc";
\r
689 container vm-names {
\r
690 leaf-list vm-name {
\r
699 container vnfc-networks {
\r
700 uses vnfc-network-data;
\r
704 container vm-networks {
\r
706 key "network-role";
\r
707 uses vm-network-data;
\r
711 grouping vnfc-network-data {
\r
712 list vnfc-network-data {
\r
713 key "vnfc-network-role";
\r
714 leaf vnfc-network-role {
\r
715 description "e.g. dummy net - parent port network role ";
\r
720 description "Vm-type e.g. FW,";
\r
723 container vnfc-ports {
\r
725 key "vnfc-port-id";
\r
726 leaf vnfc-port-id {
\r
727 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
731 leaf common-sub-interface-role {
\r
732 description "If sub-interfaces have common interface role (network role)";
\r
735 container vnic-sub-interfaces {
\r
736 uses sub-interface-network-data;
\r
741 key "vnfc-subnet-role";
\r
742 leaf vnfc-subnet-role {
\r
743 description "Default value if subnet role is not defined.";
\r
747 list vnfc-ip-assignments {
\r
748 key "vnfc-address-family";
\r
749 leaf vnfc-address-family {
\r
750 description "indicates if this is IpV4 or IpV6";
\r
756 leaf vnfc-subnet-dhcp {
\r
757 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
763 leaf vnfc-subnet-ip-count {
\r
764 description "The number of IP addresses to be assigned per vnfc for this subnet role";
\r
767 list vnfc-subnet-ip {
\r
768 key "vnfc-ip-address";
\r
769 leaf vnfc-ip-address {
\r
770 description "Either IpV4 IP or IpV6 IP addresses should be present";
\r
771 type inet:ip-address;
\r
773 leaf vnfc-client-key {
\r
777 description "Capture what type of IP this is, if is virtual IP (AKA, floating IP) or Fixed IP. ";
\r
788 grouping vm-network-data {
\r
789 leaf network-role {
\r
790 description "network (identified by role) that this VM connects to. Should also be included in the vnf-networks for the containing VNF";
\r
794 leaf network-role-tag {
\r
797 container network-information-items {
\r
798 list network-information-item {
\r
801 description "Use ipv4 or ipv6";
\r
805 description "Indicator to use DHCP on this network for this VM";
\r
812 description "The number of ip addresses to be assigned per vm for this network role";
\r
815 container network-ips {
\r
816 leaf-list network-ip {
\r
817 description "List of assigned ip addresses of type ip-version on a network";
\r
824 container mac-addresses {
\r
825 leaf-list mac-address {
\r
826 description "List of network assignments for this vm-type";
\r
831 container floating-ips {
\r
832 leaf-list floating-ip-v4 {
\r
833 description "Floating ipv4 for VMs of a given type on this network";
\r
834 type inet:ip-address;
\r
837 leaf-list floating-ip-v6 {
\r
838 description "Floating ipv6 for VMs of a given type on this network";
\r
839 type inet:ipv6-address;
\r
843 container interface-route-prefixes {
\r
844 leaf-list interface-route-prefix {
\r
845 description "ordered-by: user";
\r
850 container sriov-parameters {
\r
851 container heat-vlan-filters {
\r
852 leaf-list heat-vlan-filter {
\r
857 container application-tags {
\r
873 grouping vf-module-level-oper-status {
\r
874 container vf-module-level-oper-status {
\r
875 uses oper-status-data;
\r
878 grouping allotted-resource-info {
\r
879 leaf allotted-resource-id {
\r
882 leaf allotted-resource-type {
\r
883 description "Not an enum, but expected values are contrail-route and security-zone.";
\r
886 leaf allotted-resource-pointer {
\r
887 description "Pointer to the allotted-resources topology";
\r
891 grouping forwarding-path-operation-information {
\r
892 uses sdnc-request-header;
\r
893 uses request-information;
\r
894 uses service-information;
\r
895 uses forwarding-path-request-input;
\r
897 grouping forwarding-path-request-input {
\r
898 container forwarding-path-request-input {
\r
899 list forwarding-paths {
\r
900 key "forwarding-path-name";
\r
901 leaf forwarding-path-name {
\r
902 description "Forwarding-path-name from tosca-model. ";
\r
906 uses onap-model-information;
\r
910 grouping forwarding-path-information {
\r
911 leaf forwarding-path-name {
\r
912 description "Fowarding-path name from TOSCA model, or name generated by SDNC";
\r
915 leaf forwarding-path-type {
\r
916 description "Based on MySQL Forwarding_Path tables path_type value from related TOSCA model";
\r
922 uses onap-model-information;
\r
923 container service-paths {
\r
924 list service-path {
\r
925 key "service-path-instance-id";
\r
926 uses service-path-information;
\r
930 grouping service-path-information {
\r
931 leaf service-path-instance-id {
\r
932 description "Service path instance ID generated by SDNC. Identifies a service-path-instance within a forwarding-path definition";
\r
935 leaf service-path-instance-name {
\r
936 description "A unique name generated by SDNC ( forwarding-path-name + service-path-instance-id )";
\r
940 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
944 key "service-instance-id";
\r
945 leaf service-instance-id {
\r
946 description "service-instance-id of each service-instance in the service-path-instance";
\r
949 leaf service-path-sequence-id {
\r
950 description "e.g. S1S2S3S5seq id=1 S1-S2seq id=2 S2S3seq id=3 S3S5Incremental integer value";
\r
955 key "vnf-instance-id";
\r
956 uses vnf-path-information;
\r
961 grouping vnf-path-information {
\r
962 leaf vnf-instance-id {
\r
963 description "VNF instance ID in the path";
\r
966 leaf vnf-path-sequence-id {
\r
967 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
970 leaf left-network-name {
\r
971 description "Every VNF instance in the path is connected to one or two VNFs.";
\r
974 leaf left-network-role {
\r
977 leaf right-network-name {
\r
980 leaf right-network-role {
\r
983 container vf-module-instance {
\r
984 leaf vf-module-id {
\r
987 leaf vf-module-name {
\r
992 grouping forwarding-path-level-oper-status {
\r
993 container forwarding-path-level-oper-status {
\r
994 uses oper-status-data;
\r
997 grouping configuration-info {
\r
998 leaf configuration-id {
\r
1001 leaf configuration-type {
\r
1002 description "Not an enum, but expected values are port-mirror-configuration, , vlan-network-receptor";
\r
1005 leaf configuration-sub-type {
\r
1006 description "Not an enum, but expected values are vprobe and pprobe";
\r
1009 leaf configuration-topology-link {
\r
1010 description "Pointer to the configurations topology";
\r
1014 grouping vnfc-instance-group {
\r
1015 list vnfc-instance-group {
\r
1016 key "instance-group-role nfc-naming-code configuration-id";
\r
1017 leaf instance-group-role {
\r
1018 description "i.e.TSBC_VNFC_group";
\r
1022 leaf nfc-naming-code {
\r
1023 description "Set to nfc-naming-code from A&AI";
\r
1027 leaf configuration-id {
\r
1032 description " port-mirror-source or port-mirror-dest";
\r
1035 uses vnfc-objects;
\r
1038 grouping vnfc-objects {
\r
1039 container vnfc-objects {
\r
1040 list vnfc-object {
\r
1046 description "Vnfc name as key in A&AI";
\r
1055 leaf vserver-name {
\r
1063 key "vnic-port-name";
\r
1064 leaf vnic-port-name {
\r
1067 leaf vnic-port-id {
\r
1070 container capacity {
\r
1071 leaf vnic-capacity {
\r
1074 leaf used-capacity {
\r
1075 description "Updated for destination port when source port is mapped/unmapped.";
\r
1079 container vnic-ip-addresses {
\r
1080 uses ip-addresses;
\r
1092 description "Vnfc name as key in A&AI";
\r
1095 leaf vserver-name {
\r
1108 key "vnic-port-name";
\r
1109 leaf vnic-port-name {
\r
1112 leaf vnic-port-id {
\r
1115 uses sub-interfaces;
\r
1119 grouping sub-interfaces {
\r
1120 container sub-interfaces {
\r
1121 list sub-interface {
\r
1122 key "sub-interface-port-name";
\r
1123 leaf sub-interface-port-name {
\r
1126 leaf sub-interface-port-id {
\r
1129 container sub-interface-ip-addresses {
\r
1130 uses ip-addresses;
\r
1133 container sub-interface-network {
\r
1134 leaf network-name {
\r
1141 leaf sub-interface-status {
\r
1142 description "NULL, unassigned, assigned";
\r
1148 grouping vlan-tags {
\r
1149 container vlan-tags {
\r
1150 leaf vlan-interface {
\r
1151 description "A&AI Key";
\r
1154 leaf upper-tag-id {
\r
1157 leaf lower-tag-id {
\r
1162 grouping vlan-vnfc-instance-groups {
\r
1163 container vlan-vnfc-instance-groups {
\r
1164 list vlan-vnfc-instance-group {
\r
1165 key "instance-group-id";
\r
1166 leaf instance-group-id {
\r
1167 description "A&AI ID";
\r
1171 leaf instance-group-function {
\r
1189 grouping vnic-groups {
\r
1190 container vnic-groups {
\r
1192 key "vnic-interface-role";
\r
1193 leaf vnic-interface-role {
\r
1194 description "Same as network-role of network where vnic is connected";
\r
1198 leaf network-instance-group-function {
\r
1199 description "network-instance-Group-function for network collection where vnics with vnic-interface-role will connect";
\r
1202 leaf vlan-assignment-policy-name {
\r
1203 description "Policy name in ASDC model & policy definition in Policy Engine";
\r
1206 leaf vlan-tag-index-next {
\r
1207 description "Next tag to be assigned";
\r
1210 container vlan-common-ip-addresses {
\r
1211 uses ip-addresses;
\r
1213 container vlan-vnics {
\r
1215 key "vnic-port-id";
\r
1216 leaf vnic-port-id {
\r
1220 container vnic-sub-interfaces {
\r
1221 uses sub-interface-network-data;
\r
1228 grouping vnf-network-collection {
\r
1229 list vnf-network-collection {
\r
1230 key "network-instance-group-function";
\r
1231 leaf network-instance-group-function {
\r
1232 description "Network Instance-Group function in A&AI";
\r
1236 leaf network-instance-group-id {
\r
1237 description "Network Instance-Group id in A&AI";
\r
1240 leaf network-collection-service-instance-id {
\r
1241 description "Service-instance-id of service that created the network collection";
\r
1244 leaf network-collection-customization-uuid {
\r
1245 description "network-collection-customization-uuid stored in Network IsntanceGroup.customization-uuid in A&AI";
\r
1248 container vnf-floating-ip {
\r
1249 uses ip-addresses;
\r
1253 grouping vnf-sub-interface-group {
\r
1254 list vnf-sub-interface-group {
\r
1255 key "vnfc-instance-group-function network-instance-group-function parent-port-role";
\r
1256 leaf vnfc-instance-group-function {
\r
1260 leaf network-instance-group-function {
\r
1264 leaf parent-port-role {
\r
1269 container customer-bonding-requests {
\r
1270 list customer-bonding-request {
\r
1271 key "configuration-id";
\r
1272 leaf configuration-id {
\r
1273 description "e.g. vlan network receptor configuration id";
\r
1280 grouping sub-interface-network-data {
\r
1281 list sub-interface-network-data {
\r
1284 description "Subinterface network id (UUID in A&AI)";
\r
1288 leaf network-name {
\r
1289 description "Subinterface network name";
\r
1292 leaf vlan-tag-id {
\r
1293 description "Vlan tag assigned to subinterface port";
\r
1296 leaf network-role {
\r
1297 description "e.g. untrusted ";
\r
1300 leaf network-role-tag {
\r
1301 description "Assuming HEAT template network role tag parameter - not used";
\r
1304 container network-information-items {
\r
1305 list network-information-item {
\r
1308 description "Use ipv4 or ipv6";
\r
1312 description "Indicator to use DHCP on this network for this VM - set to N for Vlan tagging";
\r
1313 type enumeration {
\r
1319 description "The number of ip addresses to be assigned per vm for this network role";
\r
1322 container network-ips {
\r
1323 leaf-list network-ip {
\r
1324 description "List of assigned ip addresses of type ip-version on a network.";
\r
1325 type inet:ip-address;
\r
1331 container floating-ips {
\r
1332 leaf-list floating-ip-v4 {
\r
1333 description "Floating ipv4 for VMs of a given type on this network";
\r
1334 type inet:ip-address;
\r
1337 leaf-list floating-ip-v6 {
\r
1338 description "Floating ipv6 for VMs of a given type on this network";
\r
1339 type inet:ipv6-address;
\r
1345 grouping vnf-cloud-param {
\r
1346 leaf service-instance-id {
\r
1349 leaf service-instance-name {
\r
1362 key "vf-module-id";
\r
1363 leaf vf-module-id {
\r
1370 grouping vnf-get-resource-request-input-data {
\r
1377 key "vf-module-id";
\r
1378 leaf vf-module-id {
\r
1384 grouping pnf-information {
\r
1385 container pnf-information {
\r
1387 description "Key for A&AI query";
\r
1393 uses onap-model-information;
\r
1396 grouping contrail-route-operation-information {
\r
1397 uses sdnc-request-header;
\r
1398 uses request-information;
\r
1399 uses service-information;
\r
1400 uses allotted-resource-information;
\r
1401 uses contrail-route-request-input;
\r
1403 grouping contrail-route-request-input {
\r
1404 container contrail-route-request-input {
\r
1405 container source-network {
\r
1406 uses network-info;
\r
1408 container dest-network {
\r
1409 uses network-info;
\r
1411 container contrail-applied-service-info {
\r
1412 leaf service-instance-id {
\r
1413 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
1416 leaf contrail-fqdn {
\r
1417 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
1421 container contrail-route-input-parameters {
\r
1426 grouping network-info {
\r
1430 leaf network-role {
\r
1434 grouping contrail-route-topology {
\r
1435 container contrail-route-topology {
\r
1436 uses allotted-resource-identifiers;
\r
1437 uses onap-model-information;
\r
1438 uses contrail-route-assignments;
\r
1439 container contrail-route-parameters {
\r
1444 grouping contrail-route-assignments {
\r
1445 container contrail-route-assignments {
\r
1447 description "The Contrail fq-name of the network policy";
\r
1450 leaf contrail-id {
\r
1451 description "The ID assigned by Contrail to the network-policy (one for one with the fq-name)";
\r
1454 container source-network {
\r
1455 uses network-info;
\r
1457 container dest-network {
\r
1458 uses network-info;
\r
1460 container contrail-applied-service {
\r
1461 leaf service-instance-id {
\r
1462 description "The service-instance-id of the vnf from which the contrail applied service is coming";
\r
1466 description "The vnf representing the contrail applied service";
\r
1469 leaf contrail-fqdn {
\r
1470 description "This is the fq-name of the Contrail service instance through which the route is passing.";
\r
1475 description "Contrail-assigned vlan-tag to the vipr vm interface for this route.";
\r
1480 grouping security-zone-operation-information {
\r
1481 uses sdnc-request-header;
\r
1482 uses request-information;
\r
1483 uses service-information;
\r
1484 uses allotted-resource-information;
\r
1485 uses security-zone-request-input;
\r
1487 grouping security-zone-request-input {
\r
1488 container security-zone-request-input {
\r
1492 leaf trusted-network-role {
\r
1493 description "In the case of vIPR, this is the landing networks network-role; used in naming";
\r
1496 leaf untrusted-network-role {
\r
1497 description "In the case of vIPR, this is the tenant oam networks network-role; used in naming";
\r
1500 container security-zone-input-parameters {
\r
1505 grouping security-zone-topology {
\r
1506 container security-zone-topology {
\r
1507 uses allotted-resource-identifiers;
\r
1508 uses onap-model-information;
\r
1509 uses security-zone-assignments;
\r
1510 container security-zone-parameters {
\r
1515 grouping security-zone-assignments {
\r
1516 container security-zone-assignments {
\r
1517 leaf trusted-network-role {
\r
1518 description "In the case of vIPR, this is the landing networks network-role; used in naming";
\r
1521 leaf security-zone-name-trusted {
\r
1524 leaf untrusted-network-role {
\r
1525 description "In the case of vIPR, this is the tenant oam networks network-role; used in naming";
\r
1528 leaf security-zone-name-untrusted {
\r
1531 leaf security-zone-service-instance-id {
\r
1532 description "Will be the same as the parent-service-instance-id";
\r
1535 leaf security-zone-vnf-id {
\r
1536 description "Selected by SDNC from the security-zone-service-instance-id";
\r
1544 grouping port-mirror-topology-operation-information {
\r
1545 uses sdnc-request-header;
\r
1546 uses request-information;
\r
1547 uses service-information;
\r
1548 uses configuration-information;
\r
1549 uses port-mirror-configuration-request-input;
\r
1551 grouping port-mirror-configuration-request-input {
\r
1552 container port-mirror-configuration-request-input {
\r
1553 container source-port {
\r
1555 leaf source-port-id {
\r
1556 description "needed for srv-action=disable/enable";
\r
1560 container dest-port {
\r
1563 uses region-identifier;
\r
1564 container port-mirror-configuration-input-parameters {
\r
1569 grouping port-info {
\r
1570 leaf service-instance-id {
\r
1571 description "May not be need.";
\r
1574 uses pnf-information;
\r
1575 uses vnf-information;
\r
1577 grouping port-mirror-configuration-topology {
\r
1578 container port-mirror-configuration-topology {
\r
1579 uses configuration-identifiers;
\r
1580 uses onap-model-information;
\r
1581 uses port-mirror-configuration-assignments;
\r
1582 container port-mirror-configuration-parameters {
\r
1587 grouping port-mirror-configuration-assignments {
\r
1588 container port-mirror-configuration-assignments {
\r
1589 container contrail-vmi-params {
\r
1592 leaf vnics-group-id {
\r
1595 leaf owning-entity {
\r
1598 leaf tenant-context {
\r
1599 description "From tenant object in A&AI";
\r
1603 description "Tenant name from A&AI for source VNF";
\r
1607 description "tenant-id from A&AI for source VNF";
\r
1610 leaf dest-tenant {
\r
1611 description "Tenant name from A&AI for destination VNF";
\r
1614 leaf dest-tenant-id {
\r
1615 description "tenant-id from A&AI for destination VNF";
\r
1618 leaf cloud-region-id {
\r
1621 leaf cloud-owner {
\r
1624 leaf dest-network-fqdn {
\r
1627 leaf source-network-fqdn {
\r
1630 leaf source-capacity {
\r
1631 description "Source port pps (packets per second) rating from tosca model";
\r
1634 leaf source-vnf-id {
\r
1637 leaf dest-vnf-id {
\r
1638 description "For vProbe";
\r
1641 leaf dest-pnf-name {
\r
1642 description "For pProbe";
\r
1645 leaf dest-p-interface {
\r
1646 description "For pProbe; from policy manager";
\r
1649 leaf dest-pnf-port-policy-name {
\r
1650 description "For pProbe; from tosca model";
\r
1654 description "vprobe or pprobe; derived from configuration-information.configuration-sub-type";
\r
1657 leaf route-allotted-resource-id {
\r
1658 description "For vProbe";
\r
1661 container source-vnfc-instance-group-id {
\r
1662 leaf service-instance-id {
\r
1665 leaf nfc-naming-code {
\r
1668 leaf instance-group-role {
\r
1671 leaf configuration-id {
\r
1675 container dest-vnfc-instance-group-id {
\r
1676 leaf service-instance-id {
\r
1679 leaf nfc-naming-code {
\r
1682 leaf instance-group-role {
\r
1685 leaf configuration-id {
\r
1689 container source-to-dest-maps {
\r
1690 list source-to-dest-map {
\r
1691 key "source-port-id";
\r
1692 leaf source-port-id {
\r
1696 leaf source-port-name {
\r
1699 leaf source-vserver-id {
\r
1702 leaf dest-vserver-id {
\r
1705 leaf dest-port-id {
\r
1708 leaf dest-port-name {
\r
1714 container dest-ip-addresses {
\r
1715 uses ip-addresses;
\r
1721 grouping gc-topology-operation-information {
\r
1722 uses sdnc-request-header;
\r
1723 uses request-information;
\r
1724 uses service-information;
\r
1725 uses configuration-information;
\r
1726 uses gc-request-input;
\r
1728 grouping gc-request-input {
\r
1729 container gc-request-input {
\r
1733 container input-parameters {
\r
1738 grouping vnr-parameters {
\r
1739 container vnr-parameters {
\r
1743 leaf vnf-service-instance-id {
\r
1746 leaf network-collection-service-instance-id {
\r
1747 description "service instance id that created network-collection";
\r
1750 leaf network-instance-group-id {
\r
1756 leaf vnfc-instance-group-function {
\r
1759 leaf network-instance-group-function {
\r
1762 leaf parent-port-role {
\r
1765 leaf upper-tag-id {
\r
1768 leaf lower-tag-id {
\r
1773 grouping tunnelxconn-operation-information {
\r
1774 uses sdnc-request-header;
\r
1775 uses request-information;
\r
1776 uses service-information;
\r
1777 uses allotted-resource-information;
\r
1778 uses tunnelxconn-request-input;
\r
1780 grouping tunnelxconn-request-input {
\r
1782 container tunnelxconn-request-input {
\r
1783 leaf brg-wan-mac-address {
\r
1788 grouping tunnelxconn-topology {
\r
1789 container tunnelxconn-topology {
\r
1790 uses allotted-resource-identifiers;
\r
1791 uses onap-model-information;
\r
1792 uses tunnelxconn-assignments;
\r
1793 container tunnelxconn-parameters {
\r
1798 grouping tunnelxconn-assignments {
\r
1799 container tunnelxconn-assignments {
\r
1801 description "The Network Controller will assign a VNI value from the associated vGMUX VNI pool";
\r
1804 leaf vgmux-bearer-ip {
\r
1805 description "The Network Controller will look up the vgmux bearer ip from the vgmux vf module";
\r
1806 type inet:ip-address;
\r
1808 leaf vgmux-lan-ip {
\r
1809 description "The Network Controller will look up the vgmux lan ip from the vgmux vg module";
\r
1810 type inet:ip-address;
\r
1813 description "The Network Controller will assign the VG IP address from local inventory";
\r
1814 type inet:ip-address;
\r
1818 grouping brg-operation-information {
\r
1819 uses sdnc-request-header;
\r
1820 uses request-information;
\r
1821 uses service-information;
\r
1822 uses allotted-resource-information;
\r
1823 uses brg-request-input;
\r
1825 grouping brg-request-input {
\r
1826 container brg-request-input {
\r
1827 leaf vgmux-bearer-ip {
\r
1828 type inet:ip-address;
\r
1833 leaf brg-wan-mac-address {
\r
1838 grouping brg-topology {
\r
1839 container brg-topology {
\r
1840 uses allotted-resource-identifiers;
\r
1841 uses onap-model-information;
\r
1842 uses brg-assignments;
\r
1843 container brg-parameters {
\r
1848 grouping brg-assignments {
\r
1849 container brg-assignments {
\r
1850 leaf vbrg-wan-ip {
\r
1851 type inet:ip-address;
\r
1855 grouping connection-attachment-operation-information {
\r
1856 uses sdnc-request-header;
\r
1857 uses request-information;
\r
1858 uses service-information;
\r
1859 uses allotted-resource-information;
\r
1860 uses connection-attachment-request-input;
\r
1863 grouping connection-attachment-request-input {
\r
1864 container connection-attachment-request-input {
\r
1869 grouping connection-attachment-topology {
\r
1870 container brg-topology {
\r
1871 uses allotted-resource-identifiers;
\r
1872 uses onap-model-information;
\r
1873 uses connection-attachment-assignments;
\r
1874 container connection-attachment-parameters {
\r
1880 grouping connection-attachment-assignments {
\r
1881 container connection-attachment-assignments {
\r
1885 grouping allotted-resource-information {
\r
1886 container allotted-resource-information {
\r
1887 leaf allotted-resource-id {
\r
1890 leaf allotted-resource-type {
\r
1891 description "Not an enum, but expected values are contrail-route and security-zone.";
\r
1894 leaf parent-service-instance-id {
\r
1895 description "Service-instance-id of the parent service to which this allotted resource belongs.";
\r
1898 uses onap-model-information;
\r
1901 grouping allotted-resource-identifiers {
\r
1902 container allotted-resource-identifiers {
\r
1903 leaf allotted-resource-id {
\r
1906 leaf allotted-resource-name {
\r
1907 description "For a contrail-route, the network policy name.";
\r
1910 leaf allotted-resource-type {
\r
1911 description "(Added in draft 32)Expected to be contrail-route or security-zone.";
\r
1914 leaf consuming-service-instance-id {
\r
1915 description "The service-instance-id of the consuming service of this allotted resource";
\r
1918 leaf parent-service-instance-id {
\r
1919 description "Service-instance-id of the parent service to which this allotted resource belongs.";
\r
1924 grouping allotted-resource-oper-status {
\r
1925 container allotted-resource-oper-status {
\r
1926 uses oper-status-data;
\r
1929 grouping allotted-resource-status {
\r
1930 container allotted-resource-status {
\r
1931 leaf response-code {
\r
1934 leaf response-message {
\r
1937 leaf final-indicator {
\r
1940 leaf request-status {
\r
1941 type enumeration {
\r
1942 enum "synccomplete";
\r
1943 enum "asynccomplete";
\r
1944 enum "notifycomplete";
\r
1948 description "value would one of possible request-actions; match the list in service-data oper-status";
\r
1955 description "this is the svc-action from the incoming request";
\r
1956 type enumeration {
\r
1962 enum "deactivate";
\r
1965 leaf response-timestamp {
\r
1970 grouping configuration-information {
\r
1971 container configuration-information {
\r
1972 leaf configuration-id {
\r
1975 leaf configuration-name {
\r
1978 leaf configuration-type {
\r
1979 description "Not an enum, but expected values are port-mirror-configuration, vlan-network-receptor";
\r
1982 leaf configuration-sub-type {
\r
1983 description "e.g. vprobe and pprobe when configuration-type=port-mirror-configuration";
\r
1986 uses onap-model-information;
\r
1989 grouping configuration-identifiers {
\r
1990 container configuration-identifiers {
\r
1991 leaf configuration-id {
\r
1994 leaf configuration-name {
\r
1997 leaf configuration-type {
\r
1998 description "Not an enum, but expected values are port-mirror-configuration.";
\r
2001 leaf configuration-sub-type {
\r
2002 description " vprobe and pprobe";
\r
2005 leaf parent-service-instance-id {
\r
2006 description "Service-instance-id of the parent service to which this resource belongs.";
\r
2011 grouping configuration-oper-status {
\r
2012 container configuration-oper-status {
\r
2013 uses oper-status-data;
\r
2016 grouping configuration-status {
\r
2017 container configuration-status {
\r
2018 leaf response-code {
\r
2021 leaf response-message {
\r
2024 leaf final-indicator {
\r
2027 leaf request-status {
\r
2028 type enumeration {
\r
2029 enum "synccomplete";
\r
2030 enum "asynccomplete";
\r
2031 enum "notifycomplete";
\r
2035 description "value would one of possible request-actions; match the list in service-data oper-status";
\r
2042 description "this is the svc-action from the incoming request";
\r
2043 type enumeration {
\r
2051 enum "deactivate";
\r
2054 leaf response-timestamp {
\r
2059 grouping topology-response-common {
\r
2060 leaf svc-request-id {
\r
2061 description "the request id from the request message for which this is the responseKeep as M";
\r
2064 leaf response-code {
\r
2065 description "a success code or an defined error codeKeep as M";
\r
2068 leaf response-message {
\r
2069 description "message included for error code";
\r
2072 leaf ack-final-indicator {
\r
2073 description "Expected to be Y or N.";
\r
2077 grouping sdnc-request-header {
\r
2078 container sdnc-request-header {
\r
2079 leaf svc-request-id {
\r
2080 description "Uniquely generated by calling system (e.g. MSO or SDN-GP)";
\r
2084 description "This is the rpcAction";
\r
2085 type enumeration {
\r
2090 enum "changeassign";
\r
2091 enum "changedelete";
\r
2093 enum "deactivate";
\r
2101 leaf svc-notification-url {
\r
2102 description "Contains URL for asynchronous response";
\r
2107 grouping request-information {
\r
2108 container request-information {
\r
2110 description "Request ID generated upstream of MSO";
\r
2113 leaf request-action {
\r
2114 description "still need to work Disconnect";
\r
2115 type enumeration {
\r
2116 enum "CreateNetworkInstance";
\r
2117 enum "ActivateNetworkInstance";
\r
2118 enum "CreateServiceInstance";
\r
2119 enum "DeleteServiceInstance";
\r
2120 enum "DeleteNetworkInstance";
\r
2121 enum "CreateVnfInstance";
\r
2122 enum "ActivateVnfInstance";
\r
2123 enum "DeleteVnfInstance";
\r
2124 enum "CreateVfModuleInstance";
\r
2125 enum "ActivateVfModuleInstance";
\r
2126 enum "DeleteVfModuleInstance";
\r
2127 enum "CreateContrailRouteInstance";
\r
2128 enum "DeleteContrailRouteInstance";
\r
2129 enum "CreateSecurityZoneInstance";
\r
2130 enum "DeleteSecurityZoneInstance";
\r
2131 enum "ActivateDCINetworkInstance";
\r
2132 enum "DeActivateDCINetworkInstance";
\r
2133 enum "CreateTunnelXConnInstance";
\r
2134 enum "DeleteTunnelXConnInstance";
\r
2135 enum "CreateBRGInstance";
\r
2136 enum "DeleteBRGInstance";
\r
2137 enum "CreateSOTNConnectivityInstance";
\r
2138 enum "ActivateSOTNConnectivityInstance";
\r
2139 enum "DeactivateSOTNConnectivityInstance";
\r
2140 enum "DeleteSOTNConnectivityInstance";
\r
2141 enum "CreateSOTNAttachmentInstance";
\r
2142 enum "ActivateSOTNAttachmentInstance";
\r
2143 enum "DeactivateSOTNAttachmentInstance";
\r
2144 enum "DeleteSOTNAttachmentInstance";
\r
2145 enum "CreateSiteInstance";
\r
2146 enum "ActivateSiteInstance";
\r
2147 enum "DeactivateSiteInstance";
\r
2148 enum "DeleteSiteInstance";
\r
2149 enum "CreatePortMirrorConfigurationInstance";
\r
2150 enum "DeletePortMirrorConfigurationInstance";
\r
2151 enum "ChangePortMirrorConfigurationInstance";
\r
2152 enum "CreateGenericConfigurationInstance";
\r
2153 enum "DeleteGenericConfigurationInstance";
\r
2154 enum "PreloadVfModuleRequest";
\r
2155 enum "DeletePreloadVfModuleRequest";
\r
2156 enum "PreloadNetworkRequest";
\r
2157 enum "DeletePreloadNetworkRequest";
\r
2158 enum "CreateForwardingPathInstance";
\r
2159 enum "DeleteForwardingPathInstance";
\r
2160 enum "UpdateForwardingPathInstance";
\r
2166 leaf notification-url {
\r
2169 leaf order-number {
\r
2172 leaf order-version {
\r
2177 grouping service-information {
\r
2178 container service-information {
\r
2180 description "This maps to the product-family-id in A&AI";
\r
2183 leaf subscription-service-type {
\r
2184 description "used to reference a&ai subscription-service-type. For example, we show as vIPR-ATM in example.";
\r
2187 uses onap-model-information;
\r
2188 leaf service-instance-id {
\r
2191 leaf global-customer-id {
\r
2192 description "need for put of data to AnAI (MSO provides)";
\r
2195 leaf subscriber-name {
\r
2196 description "Would not be expected for vIPR-ATM or mobility services.";
\r
2201 grouping onap-model-information {
\r
2202 container onap-model-information {
\r
2203 leaf model-invariant-uuid {
\r
2204 description "identifies the invariant uuid for this service or resource";
\r
2207 leaf model-customization-uuid {
\r
2208 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
2212 description "identifies the uuid for this service or resource, which is version specific";
\r
2215 leaf model-version {
\r
2223 grouping region-identifier {
\r
2227 leaf aic-cloud-region {
\r
2228 description "The AIC cloud region which maps to contrail versions";
\r
2232 description "Not expected to be used";
\r
2245 container resource-resolution-data {
\r
2246 list resource-key {
\r
2256 description "SUCCESS, FAILED, or PENDING - RA returned data as capability";
\r
2259 leaf capability-name {
\r
2260 description "Resource assignment resolution Capability name";
\r
2266 grouping ip-addresses {
\r
2267 container ip-addresses {
\r
2268 leaf ipv4-address {
\r
2269 type inet:ip-address;
\r
2271 leaf ipv6-address {
\r
2272 type inet:ip-address;
\r
2274 leaf vipv4-address {
\r
2275 description "Virtual v4";
\r
2276 type inet:ip-address;
\r
2278 leaf vipv6-address {
\r
2279 description "Virtual v6";
\r
2280 type inet:ip-address;
\r
2284 grouping instance-reference {
\r
2285 leaf instance-id {
\r
2288 leaf object-path {
\r
2289 description "restconf retrieval path to this particular objectE.g. restconf/config/GENERIC-RESOURCE-API:services/service/$service-instance-id/service-data/service-topology/";
\r
2293 grouping oper-status-data {
\r
2294 leaf order-status {
\r
2295 description "TBD - do we need Request failed statuses? RequestFailed | InProgressTimeout";
\r
2296 type enumeration {
\r
2298 enum "PendingAssignment";
\r
2299 enum "PendingCreate";
\r
2300 enum "PendingUpdate";
\r
2301 enum "PendingDelete";
\r
2306 leaf last-rpc-action {
\r
2307 type enumeration {
\r
2312 enum "deactivate";
\r
2314 enum "changeassign";
\r
2317 leaf last-action {
\r
2318 description "should be list of possible request-actions";
\r
2319 type enumeration {
\r
2320 enum "CreateNetworkInstance";
\r
2321 enum "ActivateNetworkInstance";
\r
2322 enum "CreateServiceInstance";
\r
2323 enum "DeleteServiceInstance";
\r
2324 enum "DeleteNetworkInstance";
\r
2325 enum "CreateVnfInstance";
\r
2326 enum "ActivateVnfInstance";
\r
2327 enum "DeleteVnfInstance";
\r
2328 enum "CreateVfModuleInstance";
\r
2329 enum "ActivateVfModuleInstance";
\r
2330 enum "DeleteVfModuleInstance";
\r
2331 enum "CreateContrailRouteInstance";
\r
2332 enum "DeleteContrailRouteInstance";
\r
2333 enum "CreateSecurityZoneInstance";
\r
2334 enum "DeleteSecurityZoneInstance";
\r
2335 enum "ActivateDCINetworkInstance";
\r
2336 enum "DeActivateDCINetworkInstance";
\r
2337 enum "CreateTunnelXConnInstance";
\r
2338 enum "DeleteTunnelXConnInstance";
\r
2339 enum "CreateBRGInstance";
\r
2340 enum "DeleteBRGInstance";
\r
2341 enum "CreateSOTNConnectivityInstance";
\r
2342 enum "ActivateSOTNConnectivityInstance";
\r
2343 enum "DeactivateSOTNConnectivityInstance";
\r
2344 enum "DeleteSOTNConnectivityInstance";
\r
2345 enum "CreateSOTNAttachmentInstance";
\r
2346 enum "ActivateSOTNAttachmentInstance";
\r
2347 enum "DeactivateSOTNAttachmentInstance";
\r
2348 enum "DeleteSOTNAttachmentInstance";
\r
2349 enum "CreateSiteInstance";
\r
2350 enum "ActivateSiteInstance";
\r
2351 enum "DeactivateSiteInstance";
\r
2352 enum "DeleteSiteInstance";
\r
2353 enum "CreatePortMirrorConfigurationInstance";
\r
2354 enum "DeletePortMirrorConfigurationInstance";
\r
2355 enum "ChangePortMirrorConfigurationInstance";
\r
2356 enum "CreateGenericConfigurationInstance";
\r
2357 enum "DeleteGenericConfigurationInstance";
\r
2358 enum "PreloadVfModuleRequest";
\r
2359 enum "DeletePreloadVfModuleRequest";
\r
2360 enum "PreloadNetworkRequest";
\r
2361 enum "DeletePreloadNetworkRequest";
\r
2362 enum "CreateForwardingPathInstance";
\r
2363 enum "DeleteForwardingPathInstance";
\r
2364 enum "UpdateForwardingPathInstance";
\r
2367 leaf last-svc-request-id {
\r
2368 description "Not currently populated in service data.";
\r
2371 leaf last-order-status {
\r
2372 type enumeration {
\r
2374 enum "PendingAssignment";
\r
2375 enum "PendingCreate";
\r
2376 enum "PendingUpdate";
\r
2377 enum "PendingDelete";
\r
2382 leaf create-timestamp {
\r
2383 description "Not currently populated in service data.";
\r
2386 leaf modify-timestamp {
\r
2390 grouping service-response-information {
\r
2391 container service-response-information {
\r
2392 uses instance-reference;
\r
2395 grouping network-response-information {
\r
2396 container network-response-information {
\r
2397 uses instance-reference;
\r
2400 grouping vnf-response-information {
\r
2401 container vnf-response-information {
\r
2402 uses instance-reference;
\r
2405 grouping vf-module-response-information {
\r
2406 container vf-module-response-information {
\r
2407 uses instance-reference;
\r
2410 grouping contrail-route-response-information {
\r
2411 container contrail-route-response-information {
\r
2412 uses instance-reference;
\r
2415 grouping security-zone-response-information {
\r
2416 container security-zone-response-information {
\r
2417 uses instance-reference;
\r
2420 grouping getpathsegment-response-information {
\r
2421 container getpathsegment-response-information {
\r
2422 uses instance-reference;
\r
2425 grouping port-mirror-response-information {
\r
2426 container port-mirror-response-information {
\r
2427 uses instance-reference;
\r
2430 grouping gc-response-information {
\r
2431 container gc-response-information {
\r
2432 uses instance-reference;
\r
2435 grouping tunnelxconn-response-information {
\r
2436 container tunnelxconn-response-information {
\r
2437 uses instance-reference;
\r
2440 grouping brg-response-information {
\r
2441 container brg-response-information {
\r
2442 uses instance-reference;
\r
2445 grouping connection-attachment-response-information {
\r
2446 container connection-attachment-response-information {
\r
2447 uses instance-reference;
\r
2450 grouping preload-model-information {
\r
2451 list preload-list {
\r
2452 key "preload-id preload-type";
\r
2454 description "vf-module-name or network name";
\r
2458 leaf preload-type {
\r
2459 description "network or vf-module";
\r
2463 uses preload-data;
\r
2466 grouping preload-data {
\r
2467 container preload-data {
\r
2468 uses preload-vf-module-topology-information;
\r
2469 uses preload-network-topology-information;
\r
2470 uses preload-oper-status;
\r
2473 grouping preload-vf-module-topology-information {
\r
2474 container preload-vf-module-topology-information {
\r
2475 uses vnf-topology-identifier-structure;
\r
2476 uses vnf-resource-assignments;
\r
2477 uses vf-module-topology;
\r
2480 grouping preload-network-topology-information {
\r
2481 container preload-network-topology-information {
\r
2482 uses network-topology-identifier-structure;
\r
2484 uses vpn-bindings;
\r
2485 uses network-policy;
\r
2486 uses route-table-reference;
\r
2488 uses provider-network-information;
\r
2491 grouping subnets {
\r
2493 key "start-address";
\r
2494 leaf start-address {
\r
2495 type inet:ip-address;
\r
2497 leaf gateway-address {
\r
2498 type inet:ip-address;
\r
2506 leaf dhcp-enabled {
\r
2507 type enumeration {
\r
2512 leaf dhcp-start-address {
\r
2515 leaf dhcp-end-address {
\r
2518 leaf addr-from-start {
\r
2519 description "Default is N";
\r
2520 type enumeration {
\r
2525 leaf subnet-name {
\r
2528 leaf subnet-role {
\r
2531 leaf subnet-sequence {
\r
2536 grouping vpn-bindings {
\r
2537 list vpn-bindings {
\r
2538 key "vpn-binding-id";
\r
2539 leaf vpn-binding-id {
\r
2545 leaf global-route-target {
\r
2548 leaf route-target-role {
\r
2552 description "AIC Zone the route target associated with";
\r
2557 grouping network-policy {
\r
2558 list network-policy {
\r
2559 key "network-policy-fqdn";
\r
2560 leaf network-policy-fqdn {
\r
2563 leaf network-policy-id {
\r
2568 grouping route-table-reference {
\r
2569 list route-table-reference {
\r
2570 key "route-table-reference-fqdn";
\r
2571 leaf route-table-reference-fqdn {
\r
2575 leaf route-table-reference-id {
\r
2580 grouping provider-network-information {
\r
2581 leaf physical-network-name {
\r
2584 leaf is-provider-network {
\r
2587 leaf is-shared-network {
\r
2590 leaf is-external-network {
\r
2594 grouping host-routes {
\r
2595 list host-routes {
\r
2596 key "route-prefix";
\r
2597 leaf route-prefix {
\r
2601 description "Could be ip-address or hostname or service-instance";
\r
2606 grouping preload-oper-status {
\r
2607 container preload-oper-status {
\r
2608 leaf order-status {
\r
2609 type enumeration {
\r
2611 enum "PendingAssignment";
\r
2612 enum "PendingCreate";
\r
2613 enum "PendingUpdate";
\r
2614 enum "PendingDelete";
\r
2618 leaf last-action {
\r
2619 type enumeration {
\r
2620 enum "PreloadVfModuleRequest";
\r
2621 enum "DeletePreloadVfModuleRequest";
\r
2622 enum "PreloadNetworkRequest";
\r
2623 enum "DeletePreloadNetworkRequest";
\r
2626 leaf last-svc-request-id {
\r
2629 leaf last-order-status {
\r
2630 type enumeration {
\r
2632 enum "PendingAssignment";
\r
2633 enum "PendingCreate";
\r
2634 enum "PendingUpdate";
\r
2635 enum "PendingDelete";
\r
2639 leaf create-timestamp {
\r
2642 leaf modify-timestamp {
\r
2645 leaf maintenance-indicator {
\r
2646 type enumeration {
\r
2653 grouping preload-topology-response-body {
\r
2654 leaf svc-request-id {
\r
2657 leaf response-code {
\r
2660 leaf response-message {
\r
2663 leaf ack-final-indicator {
\r
2667 rpc generic-configuration-notification {
\r
2669 uses sdnc-request-header;
\r
2670 uses request-information;
\r
2671 uses service-information;
\r
2672 uses configuration-information;
\r
2673 uses topology-response-common;
\r
2674 leaf configuration-topology-link {
\r
2675 description "Returns URL to generic-configuration-topology ";
\r
2678 uses vnr-parameters;
\r
2681 container services {
\r
2682 uses service-model-infrastructure;
\r
2684 container contrail-route-allotted-resources {
\r
2685 list contrail-route-allotted-resource {
\r
2686 key "allotted-resource-id";
\r
2687 leaf allotted-resource-id {
\r
2691 container allotted-resource-data {
\r
2692 container allotted-resource-operation-information {
\r
2693 uses contrail-route-operation-information;
\r
2695 uses contrail-route-topology;
\r
2696 uses allotted-resource-oper-status;
\r
2698 uses allotted-resource-status;
\r
2701 container security-zone-allotted-resources {
\r
2702 list security-zone-allotted-resource {
\r
2703 key "allotted-resource-id";
\r
2704 leaf allotted-resource-id {
\r
2708 container allotted-resource-data {
\r
2709 container allotted-resource-operation-information {
\r
2710 uses security-zone-operation-information;
\r
2712 uses security-zone-topology;
\r
2713 container security-zone-parameters {
\r
2716 uses allotted-resource-oper-status;
\r
2718 uses allotted-resource-status;
\r
2721 container tunnelxconn-allotted-resources {
\r
2722 list tunnelxconn-allotted-resource {
\r
2723 key "allotted-resource-id";
\r
2724 leaf allotted-resource-id {
\r
2728 container allotted-resource-data {
\r
2729 container allotted-resource-operation-information {
\r
2730 uses tunnelxconn-operation-information;
\r
2732 uses tunnelxconn-topology;
\r
2733 container tunnelxconn-parameters {
\r
2736 uses allotted-resource-oper-status;
\r
2738 uses allotted-resource-status;
\r
2741 container brg-allotted-resources {
\r
2742 list brg-allotted-resource {
\r
2743 key "allotted-resource-id";
\r
2744 leaf allotted-resource-id {
\r
2748 container allotted-resource-data {
\r
2749 container allotted-resource-operation-information {
\r
2750 uses brg-operation-information;
\r
2752 uses brg-topology;
\r
2753 container brg-parameters {
\r
2756 uses allotted-resource-oper-status;
\r
2758 uses allotted-resource-status;
\r
2761 container connection-attachment-allotted-resources {
\r
2762 list connection-attachment-allotted-resource {
\r
2763 key "allotted-resource-id";
\r
2764 leaf allotted-resource-id {
\r
2768 container allotted-resource-data {
\r
2769 container allotted-resource-operation-information {
\r
2770 uses connection-attachment-operation-information;
\r
2772 uses connection-attachment-topology;
\r
2773 container connection-attachment-parameters {
\r
2776 uses allotted-resource-oper-status;
\r
2778 uses allotted-resource-status;
\r
2781 container port-mirror-configurations {
\r
2782 list port-mirror-configuration {
\r
2783 key "configuration-id";
\r
2784 leaf configuration-id {
\r
2788 container configuration-data {
\r
2789 container configuration-operation-information {
\r
2790 uses port-mirror-topology-operation-information;
\r
2792 uses port-mirror-configuration-topology;
\r
2793 uses configuration-oper-status;
\r
2795 uses configuration-status;
\r
2798 container generic-configurations {
\r
2799 list gc-configuration {
\r
2800 key "configuration-id";
\r
2801 leaf configuration-id {
\r
2805 container configuration-data {
\r
2806 container configuration-operation-information {
\r
2807 uses gc-topology-operation-information;
\r
2809 uses configuration-oper-status;
\r
2811 uses configuration-status;
\r
2814 rpc service-topology-operation {
\r
2816 uses service-operation-information;
\r
2819 uses topology-response-common;
\r
2820 uses service-response-information;
\r
2823 rpc network-topology-operation {
\r
2825 uses network-operation-information;
\r
2828 uses topology-response-common;
\r
2829 uses network-response-information;
\r
2830 uses service-response-information;
\r
2833 rpc vnf-topology-operation {
\r
2835 uses vnf-operation-information;
\r
2838 uses topology-response-common;
\r
2839 uses vnf-response-information;
\r
2840 uses service-response-information;
\r
2843 rpc vf-module-topology-operation {
\r
2845 uses vf-module-operation-information;
\r
2848 uses topology-response-common;
\r
2849 uses vf-module-response-information;
\r
2850 uses vnf-response-information;
\r
2851 uses service-response-information;
\r
2854 rpc contrail-route-topology-operation {
\r
2856 uses contrail-route-operation-information;
\r
2859 uses topology-response-common;
\r
2860 uses contrail-route-response-information;
\r
2861 uses service-response-information;
\r
2864 rpc security-zone-topology-operation {
\r
2866 uses security-zone-operation-information;
\r
2869 uses topology-response-common;
\r
2870 uses security-zone-response-information;
\r
2871 uses service-response-information;
\r
2874 rpc tunnelxconn-topology-operation {
\r
2876 uses tunnelxconn-operation-information;
\r
2879 uses topology-response-common;
\r
2880 uses tunnelxconn-response-information;
\r
2881 uses service-response-information;
\r
2884 rpc brg-topology-operation {
\r
2886 uses brg-operation-information;
\r
2889 uses topology-response-common;
\r
2890 uses brg-response-information;
\r
2891 uses service-response-information;
\r
2894 rpc policy-update-notify-operation {
\r
2896 leaf policy-name {
\r
2901 description "Map JSON versionNo to version-id";
\r
2905 leaf update-type {
\r
2919 rpc getpathsegment-topology-operation {
\r
2921 uses forwarding-path-operation-information;
\r
2924 uses topology-response-common;
\r
2925 uses getpathsegment-response-information;
\r
2926 uses service-response-information;
\r
2929 rpc port-mirror-topology-operation {
\r
2931 uses port-mirror-topology-operation-information;
\r
2934 uses topology-response-common;
\r
2935 uses port-mirror-response-information;
\r
2936 uses service-response-information;
\r
2939 rpc generic-configuration-topology-operation {
\r
2941 uses gc-topology-operation-information;
\r
2944 uses topology-response-common;
\r
2945 uses gc-response-information;
\r
2946 uses service-response-information;
\r
2949 rpc vnf-get-resource-request {
\r
2951 uses sdnc-request-header;
\r
2952 uses request-information;
\r
2953 uses service-information;
\r
2954 uses vnf-get-resource-request-input-data;
\r
2957 container vnf-get-resource-response-information {
\r
2958 uses vnf-cloud-param;
\r
2962 container preload-information {
\r
2963 uses preload-model-information;
\r
2965 rpc preload-vf-module-topology-operation {
\r
2967 uses sdnc-request-header;
\r
2968 uses request-information;
\r
2969 uses preload-vf-module-topology-information;
\r
2972 uses preload-topology-response-body;
\r
2975 rpc preload-network-topology-operation {
\r
2977 uses sdnc-request-header;
\r
2978 uses request-information;
\r
2979 uses preload-network-topology-information;
\r
2982 uses preload-topology-response-body;
\r
2986 rpc connection-attachment-topology-operation {
\r
2988 uses connection-attachment-operation-information;
\r
2991 uses topology-response-common;
\r
2992 uses connection-attachment-response-information;
\r
2993 uses service-response-information;
\r
2997 } ////closes the module
\r