1 module GENERIC-RESOURCE-API {
\r
3 namespace "org:onap:sdnc:northbound:generic-resource";
\r
5 prefix generic-resource-api;
\r
7 import ietf-inet-types { prefix "inet"; revision-date "2013-07-15"; }
\r
9 import ietf-yang-types { prefix yang; }
\r
11 revision "2017-08-24" {
\r
13 "ONAP Amsterdam version";
\r
16 grouping service-model-infrastructure {
\r
18 key "service-instance-id";
\r
19 leaf service-instance-id {
\r
20 description "Keep as M";
\r
25 uses service-status;
\r
28 grouping service-data {
\r
29 container service-data {
\r
30 uses service-operation-information;
\r
31 uses service-topology;
\r
32 uses service-level-oper-status;
\r
33 container networks {
\r
40 container network-data {
\r
41 uses network-operation-information;
\r
42 uses network-topology;
\r
43 container network-provided-allotted-resources {
\r
44 leaf-list network-provided-ar-id {
\r
45 description "List of allotted resources using capacity from this network";
\r
50 uses network-level-oper-status;
\r
61 container pnf-data {
\r
62 uses pnf-operation-information;
\r
64 uses pnf-level-oper-status;
\r
75 container vnf-data {
\r
76 uses vnf-operation-information;
\r
78 container vnf-network-collections {
\r
79 uses vnf-network-collection;
\r
81 container vnf-sub-interface-groups {
\r
82 uses vnf-sub-interface-group;
\r
84 container vnf-provided-allotted-resources {
\r
85 leaf-list vnf-provided-ar-id {
\r
86 description "List of allotted resources using capacity from this vnf";
\r
91 uses vnf-level-oper-status;
\r
92 container vf-modules {
\r
99 container vf-module-data {
\r
100 uses vf-module-operation-information;
\r
101 uses vf-module-topology;
\r
102 uses vf-module-level-oper-status;
\r
109 container consumed-allotted-resources {
\r
110 list consumed-allotted-resource {
\r
111 key "allotted-resource-id";
\r
112 uses allotted-resource-info;
\r
115 container provided-allotted-resources {
\r
116 list provided-allotted-resource {
\r
117 key "allotted-resource-id";
\r
118 uses allotted-resource-info;
\r
121 container provided-configurations {
\r
122 list provided-configuration {
\r
123 key "configuration-id";
\r
124 uses configuration-info;
\r
127 container vnfc-instance-groups {
\r
128 uses vnfc-instance-group;
\r
130 container network-instance-groups {
\r
131 uses network-instance-group;
\r
133 container forwarding-paths {
\r
134 list forwarding-path {
\r
135 key "forwarding-path-id";
\r
136 leaf forwarding-path-id {
\r
137 description "Generated by SDNC";
\r
141 uses forwarding-path-information;
\r
146 grouping service-status {
\r
147 container service-status {
\r
148 leaf response-code {
\r
151 leaf response-message {
\r
154 leaf final-indicator {
\r
157 leaf request-status {
\r
159 enum "synccomplete";
\r
160 enum "asynccomplete";
\r
161 enum "notifycomplete";
\r
165 description "value would one of possible request-actions; match the list in service-data oper-status";
\r
172 description "this is the svc-action from the incoming request";
\r
183 leaf response-timestamp {
\r
188 grouping service-operation-information {
\r
189 uses sdnc-request-header;
\r
190 uses request-information;
\r
191 uses service-information;
\r
192 uses service-request-input;
\r
194 grouping service-request-input {
\r
195 container service-request-input {
\r
196 leaf service-instance-name {
\r
199 container service-input-parameters {
\r
204 grouping service-topology {
\r
205 container service-topology {
\r
206 uses service-topology-identifier;
\r
207 uses onap-model-information;
\r
208 uses service-assignments;
\r
209 uses service-parameters;
\r
212 grouping service-topology-identifier {
\r
213 container service-topology-identifier {
\r
214 leaf service-instance-id {
\r
215 description "repeated";
\r
218 leaf service-type {
\r
219 description "tag labeled subscription-service-type in the service-information input";
\r
223 description "from MSO input on STO assign";
\r
226 leaf service-instance-name {
\r
227 description "optionally comes from service-request-input container or is assigned by sdn-c";
\r
230 leaf global-customer-id {
\r
235 grouping service-assignments {
\r
236 container service-assignments {
\r
239 grouping service-parameters {
\r
240 container service-parameters {
\r
241 list service-parameter {
\r
242 key "service-parameter-name";
\r
243 leaf service-parameter-name {
\r
246 leaf service-parameter-value {
\r
252 grouping service-level-oper-status {
\r
253 container service-level-oper-status {
\r
254 uses oper-status-data;
\r
257 grouping network-operation-information {
\r
258 uses sdnc-request-header;
\r
259 uses request-information;
\r
260 uses service-information;
\r
261 uses network-information;
\r
262 uses network-request-input;
\r
264 grouping network-information {
\r
265 container network-information {
\r
269 leaf network-type {
\r
272 leaf network-technology {
\r
275 leaf from-preload {
\r
276 description "Indicates if source is preload data";
\r
279 uses onap-model-information;
\r
282 grouping network-request-input {
\r
283 container network-request-input {
\r
284 leaf network-name {
\r
287 uses region-identifier;
\r
288 container network-input-parameters {
\r
291 leaf network-instance-group-id {
\r
292 description "When network has instance-group role in service model";
\r
297 grouping network-topology {
\r
298 container network-topology {
\r
299 uses network-topology-identifier-structure;
\r
300 uses region-identifier;
\r
301 uses onap-model-information;
\r
302 uses network-assignments;
\r
303 uses network-parameters;
\r
306 grouping network-topology-identifier-structure {
\r
307 container network-topology-identifier-structure {
\r
311 leaf network-name {
\r
314 leaf network-role {
\r
317 leaf network-type {
\r
320 leaf network-instance-group-id {
\r
321 description "When network is part of network instance-Group-data & instance Group in A&AI";
\r
324 leaf network-technology {
\r
327 leaf eipam-v4-address-plan {
\r
330 leaf eipam-v6-address-plan {
\r
336 leaf segmentation-id {
\r
339 container related-networks {
\r
340 uses related-network;
\r
344 grouping network-assignments {
\r
345 container network-assignments {
\r
348 grouping network-parameters {
\r
349 container network-parameters {
\r
350 list network-parameter {
\r
351 key "network-parameter-name";
\r
352 leaf network-parameter-name {
\r
355 leaf network-parameter-value {
\r
361 grouping network-instance-group {
\r
362 list network-instance-group {
\r
363 key "network-instance-group-id";
\r
364 leaf network-instance-group-id {
\r
365 description "Also a Key in Network Instance Group in A&AI";
\r
369 leaf network-instance-group-function {
\r
372 leaf service-instance-id {
\r
375 uses onap-model-information;
\r
376 container subnet-assignment-policy {
\r
378 description "Current valid values - unique, shared (default)";
\r
382 container vpn-binding-policy {
\r
392 leaf vpn-platform {
\r
395 leaf global-route-target {
\r
398 leaf route-target-role {
\r
402 uses aggregate-routes;
\r
404 leaf subnet-key-value {
\r
405 description "key-value provided to EIPAM when creating shared subnet";
\r
408 container networks {
\r
412 description "Index into network-topology-identifier structure";
\r
416 leaf neutron-network-id {
\r
417 description "Neutron-network-id assigned by PO/RO";
\r
424 leaf network-status {
\r
425 description "assigned, unassigned";
\r
428 container customer-bonding-requests {
\r
429 list customer-bonding-request {
\r
430 key "configuration-id";
\r
431 leaf configuration-id {
\r
432 description "e.g. vlan network receptor configuration id";
\r
441 grouping network-level-oper-status {
\r
442 container network-level-oper-status {
\r
443 uses oper-status-data;
\r
446 grouping pnf-operation-information {
\r
447 uses sdnc-request-header;
\r
448 uses request-information;
\r
449 uses service-information;
\r
451 uses pnf-request-input;
\r
453 grouping pnf-details {
\r
454 container pnf-details {
\r
456 description "pnfId*Identifier of this Pnf information element. CORRELATIONID = PNF-NAME (A&AI)";
\r
461 description "pnfType (template)*Type of Resource. NEW type: PNF (pre-defined in SDC)";
\r
467 uses onap-model-information;
\r
470 grouping pnf-request-input {
\r
471 container pnf-request-input {
\r
472 leaf request-version {
\r
473 description "keep this? e.g. 1702";
\r
479 uses region-identifier;
\r
480 container pnf-input-parameters {
\r
485 grouping pnf-topology {
\r
486 container pnf-topology {
\r
487 uses pnf-topology-identifier-structure;
\r
488 uses region-identifier;
\r
489 uses onap-model-information;
\r
490 container pnf-parameters-data {
\r
493 leaf sdnc-generated-cloud-resources {
\r
494 description "Indicate if source is sdnc generated cloud param.When true, the parameters are literal HEAT template parameter names;When false, the parameters need to be converted to HEAT format";
\r
499 grouping pnf-topology-identifier-structure {
\r
500 container pnf-topology-identifier-structure {
\r
505 description "In preload tree, this label is used for the vf-module-type";
\r
509 description "optionally comes from pnf-request-input container or is assigned by sdn-c";
\r
514 grouping pnf-level-oper-status {
\r
515 container pnf-level-oper-status {
\r
516 uses oper-status-data;
\r
519 grouping vnf-operation-information {
\r
520 uses sdnc-request-header;
\r
521 uses request-information;
\r
522 uses service-information;
\r
523 uses vnf-information;
\r
524 uses vnf-request-input;
\r
525 uses license-information;
\r
527 grouping vnf-information {
\r
528 container vnf-information {
\r
538 uses onap-model-information;
\r
541 grouping vnf-request-input {
\r
542 container vnf-request-input {
\r
543 leaf request-version {
\r
549 uses region-identifier;
\r
550 container vnf-networks {
\r
552 key "network-role";
\r
553 uses vnf-network-data;
\r
556 list vnf-network-instance-group-ids {
\r
557 key "vnf-network-instance-group-id";
\r
558 leaf vnf-network-instance-group-id {
\r
559 description "List of vnf network-instance-group";
\r
563 container vnf-input-parameters {
\r
568 grouping vnf-topology {
\r
569 container vnf-topology {
\r
570 uses vnf-topology-identifier-structure;
\r
571 uses region-identifier;
\r
572 uses onap-model-information;
\r
573 uses vnf-resource-assignments;
\r
574 container vnf-parameters-data {
\r
577 leaf sdnc-generated-cloud-resources {
\r
578 description "Indicate if source is sdnc generated cloud param";
\r
583 grouping vnf-topology-identifier-structure {
\r
584 container vnf-topology-identifier-structure {
\r
589 description "In preload tree, this label is used for the vf-module-type";
\r
602 description "used in vnf naming";
\r
606 description "optionally comes from vnf-request-input container or is assigned by sdn-c";
\r
611 grouping vnf-resource-assignments {
\r
612 container vnf-resource-assignments {
\r
614 description "Orchestration status from AAI - to be set by SDNC";
\r
617 container availability-zones {
\r
618 leaf-list availability-zone {
\r
619 description "Openstack availability zone name or UUID";
\r
624 description "From the TOSCA data. Indicates the largest availability zone count needed by any vf-module in the VNF.";
\r
628 container vnf-networks {
\r
630 key "network-role";
\r
631 uses vnf-network-data;
\r
636 grouping vnf-network-data {
\r
637 leaf network-role {
\r
638 description "A Network Role to which a VNF must connect";
\r
641 leaf network-name {
\r
642 description "Unique Neutron UUID of an instance of the network role ";
\r
646 description "Unique Neutron UUID of an instance of the network role ";
\r
650 description "Unique Neutron UUID of an instance of the network role ";
\r
653 leaf contrail-network-fqdn {
\r
654 description "contrail network policy object";
\r
657 container subnets-data {
\r
659 key "sdnc-subnet-id";
\r
660 leaf sdnc-subnet-id {
\r
661 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
665 description "Subnet Role for the subnet";
\r
669 description "Populated for preload only";
\r
673 description "Should be ipv4 or ipv6";
\r
677 description "subnet UUID to be passed into the HEAT template";
\r
680 leaf dhcp-enabled {
\r
681 description "Indicator to use this subnet for DHCP ";
\r
687 leaf network-start-address {
\r
688 description "start-address of the subnet";
\r
689 type inet:ip-address;
\r
691 leaf gateway-address {
\r
692 description "subnet gateway address";
\r
693 type inet:ip-address;
\r
696 description "cidr mask";
\r
704 leaf segmentation-id {
\r
707 container related-networks {
\r
708 uses related-network;
\r
711 grouping vnf-level-oper-status {
\r
712 container vnf-level-oper-status {
\r
713 uses oper-status-data;
\r
716 grouping vf-module-operation-information {
\r
717 uses sdnc-request-header;
\r
718 uses request-information;
\r
719 uses service-information;
\r
720 uses vnf-information;
\r
721 uses vf-module-information;
\r
722 uses vf-module-request-input;
\r
724 grouping vf-module-information {
\r
725 container vf-module-information {
\r
726 leaf vf-module-id {
\r
729 leaf vf-module-type {
\r
732 leaf from-preload {
\r
733 description "Indicates if source is preload data";
\r
736 uses onap-model-information;
\r
739 grouping vf-module-request-input {
\r
740 container vf-module-request-input {
\r
741 leaf request-version {
\r
742 description "keep this?";
\r
745 leaf vf-module-name {
\r
748 uses region-identifier;
\r
749 container vf-module-input-parameters {
\r
754 grouping vf-module-topology {
\r
755 container vf-module-topology {
\r
756 uses vf-module-topology-identifier;
\r
757 uses region-identifier;
\r
758 uses onap-model-information;
\r
759 uses vf-module-assignments;
\r
760 container vf-module-parameters {
\r
763 leaf sdnc-generated-cloud-resources {
\r
764 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
769 grouping vf-module-topology-identifier {
\r
770 container vf-module-topology-identifier {
\r
771 leaf vf-module-id {
\r
772 description "vf-module id";
\r
775 leaf vf-module-name {
\r
776 description "vf-module-name";
\r
779 leaf vf-module-type {
\r
784 grouping vf-module-assignments {
\r
785 container vf-module-assignments {
\r
786 leaf vf-module-status {
\r
787 description "Orchestration status from AAI - to be set by SDNC";
\r
793 uses vm-topology-data;
\r
796 uses vlan-vnfc-instance-groups;
\r
797 container dhcp-subnet-assignments {
\r
798 list dhcp-subnet-assignment {
\r
799 key "neutron-subnet-id";
\r
800 leaf neutron-subnet-id {
\r
801 description "Same as subnet-id in subnet-data structure";
\r
804 leaf network-role {
\r
814 grouping vm-topology-data {
\r
819 uses onap-model-information;
\r
820 leaf nfc-naming-code {
\r
821 description "used in vm naming(draft 29: changed from nfc-code)";
\r
825 description "from tosca data on vfc";
\r
831 container vm-names {
\r
832 leaf-list vm-name {
\r
841 container vnfc-networks {
\r
842 uses vnfc-network-data;
\r
846 container vm-networks {
\r
848 key "network-role";
\r
849 uses vm-network-data;
\r
853 grouping vnfc-network-data {
\r
854 list vnfc-network-data {
\r
855 key "vnfc-network-role";
\r
856 leaf vnfc-network-role {
\r
863 uses connection-point;
\r
864 container vnfc-ports {
\r
866 key "vnfc-port-id";
\r
867 leaf vnfc-port-id {
\r
868 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
872 leaf common-sub-interface-role {
\r
873 description "If sub-interfaces have common interface role (network role)";
\r
876 container vnic-sub-interfaces {
\r
877 uses sub-interface-network-data;
\r
882 key "vnfc-subnet-role";
\r
883 leaf vnfc-subnet-role {
\r
884 description "Default value if subnet role is not defined.";
\r
888 list vnfc-ip-assignments {
\r
889 key "vnfc-address-family";
\r
890 leaf vnfc-address-family {
\r
891 description "indicates if this is IpV4 or IpV6";
\r
897 leaf vnfc-subnet-dhcp {
\r
898 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
904 leaf vnfc-subnet-ip-count {
\r
905 description "The number of IP addresses to be assigned per vnfc for this subnet role";
\r
908 list vnfc-subnet-ip {
\r
909 key "vnfc-ip-address";
\r
910 leaf vnfc-ip-address {
\r
911 description "Either IpV4 IP or IpV6 IP addresses should be present";
\r
912 type inet:ip-address;
\r
914 leaf vnfc-client-key {
\r
918 description "Capture what type of IP this is, if is virtual IP (AKA, floating IP) or Fixed IP. ";
\r
929 grouping vm-network-data {
\r
930 leaf network-role {
\r
931 description "network (identified by role) that this VM connects to. Should also be included in the vnf-networks for the containing VNF";
\r
935 leaf network-role-tag {
\r
938 container network-information-items {
\r
939 list network-information-item {
\r
942 description "Use ipv4 or ipv6";
\r
946 description "Indicator to use DHCP on this network for this VM";
\r
953 description "The number of ip addresses to be assigned per vm for this network role";
\r
956 container network-ips {
\r
957 leaf-list network-ip {
\r
958 description "List of assigned ip addresses of type ip-version on a network";
\r
965 container mac-addresses {
\r
966 leaf-list mac-address {
\r
967 description "List of network assignments for this vm-type";
\r
972 container floating-ips {
\r
973 leaf-list floating-ip-v4 {
\r
974 description "Floating ipv4 for VMs of a given type on this network";
\r
975 type inet:ip-address;
\r
978 leaf-list floating-ip-v6 {
\r
979 description "Floating ipv6 for VMs of a given type on this network";
\r
980 type inet:ipv6-address;
\r
984 container interface-route-prefixes {
\r
985 leaf-list interface-route-prefix {
\r
986 description "ordered-by: user";
\r
991 container sriov-parameters {
\r
992 container heat-vlan-filters {
\r
993 leaf-list heat-vlan-filter {
\r
998 container application-tags {
\r
1005 container s-tags {
\r
1016 leaf segmentation-id {
\r
1019 container related-networks {
\r
1020 uses related-network;
\r
1023 grouping vf-module-level-oper-status {
\r
1024 container vf-module-level-oper-status {
\r
1025 uses oper-status-data;
\r
1028 grouping allotted-resource-info {
\r
1029 leaf allotted-resource-id {
\r
1032 leaf allotted-resource-type {
\r
1033 description "Not an enum, but expected values are contrail-route and security-zone.";
\r
1036 leaf allotted-resource-pointer {
\r
1037 description "Pointer to the allotted-resources topology";
\r
1041 grouping forwarding-path-operation-information {
\r
1042 uses sdnc-request-header;
\r
1043 uses request-information;
\r
1044 uses service-information;
\r
1045 uses forwarding-path-request-input;
\r
1047 grouping forwarding-path-request-input {
\r
1048 container forwarding-path-request-input {
\r
1049 list forwarding-paths {
\r
1050 key "forwarding-path-name";
\r
1051 leaf forwarding-path-name {
\r
1052 description "Forwarding-path-name from tosca-model. ";
\r
1056 uses onap-model-information;
\r
1060 grouping forwarding-path-information {
\r
1061 leaf forwarding-path-name {
\r
1062 description "Fowarding-path name from TOSCA model, or name generated by SDNC";
\r
1065 leaf forwarding-path-type {
\r
1066 description "Based on MySQL Forwarding_Path tables path_type value from related TOSCA model";
\r
1067 type enumeration {
\r
1072 uses onap-model-information;
\r
1073 container service-paths {
\r
1074 list service-path {
\r
1075 key "service-path-instance-id";
\r
1076 uses service-path-information;
\r
1080 grouping service-path-information {
\r
1081 leaf service-path-instance-id {
\r
1082 description "Service path instance ID generated by SDNC. Identifies a service-path-instance within a forwarding-path definition";
\r
1085 leaf service-path-instance-name {
\r
1086 description "A unique name generated by SDNC ( forwarding-path-name + service-path-instance-id )";
\r
1090 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
1094 key "service-instance-id";
\r
1095 leaf service-instance-id {
\r
1096 description "service-instance-id of each service-instance in the service-path-instance";
\r
1099 leaf service-path-sequence-id {
\r
1100 description "e.g. S1S2S3S5seq id=1 S1-S2seq id=2 S2S3seq id=3 S3S5Incremental integer value";
\r
1105 key "vnf-instance-id";
\r
1106 uses vnf-path-information;
\r
1111 grouping vnf-path-information {
\r
1112 leaf vnf-instance-id {
\r
1113 description "VNF instance ID in the path";
\r
1116 leaf vnf-path-sequence-id {
\r
1117 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
1120 leaf left-network-name {
\r
1121 description "Every VNF instance in the path is connected to one or two VNFs.";
\r
1124 leaf left-network-role {
\r
1127 leaf right-network-name {
\r
1130 leaf right-network-role {
\r
1133 container vf-module-instance {
\r
1134 leaf vf-module-id {
\r
1137 leaf vf-module-name {
\r
1142 grouping forwarding-path-level-oper-status {
\r
1143 container forwarding-path-level-oper-status {
\r
1144 uses oper-status-data;
\r
1147 grouping configuration-info {
\r
1148 leaf configuration-id {
\r
1151 leaf configuration-type {
\r
1152 description "Not an enum, but expected values are port-mirror-configuration, , vlan-network-receptor";
\r
1155 leaf configuration-sub-type {
\r
1156 description "Not an enum, but expected values are vprobe and pprobe";
\r
1159 leaf configuration-topology-link {
\r
1160 description "Pointer to the configurations topology";
\r
1164 grouping vnfc-instance-group {
\r
1165 list vnfc-instance-group {
\r
1166 key "instance-group-role nfc-naming-code configuration-id";
\r
1167 leaf instance-group-role {
\r
1168 description "i.e.TSBC_VNFC_group";
\r
1172 leaf nfc-naming-code {
\r
1173 description "Set to nfc-naming-code from A&AI";
\r
1177 leaf configuration-id {
\r
1182 description " port-mirror-source or port-mirror-dest";
\r
1185 uses vnfc-objects;
\r
1188 grouping vnfc-objects {
\r
1189 container vnfc-objects {
\r
1190 list vnfc-object {
\r
1196 description "Vnfc name as key in A&AI";
\r
1205 leaf vserver-name {
\r
1213 key "vnic-port-name";
\r
1214 leaf vnic-port-name {
\r
1217 leaf vnic-port-id {
\r
1220 container capacity {
\r
1221 leaf vnic-capacity {
\r
1224 leaf used-capacity {
\r
1225 description "Updated for destination port when source port is mapped/unmapped.";
\r
1229 container vnic-ip-addresses {
\r
1230 uses ip-addresses;
\r
1242 description "Vnfc name as key in A&AI";
\r
1245 leaf vserver-name {
\r
1258 key "vnic-port-name";
\r
1259 leaf vnic-port-name {
\r
1262 leaf vnic-port-id {
\r
1265 uses sub-interfaces;
\r
1269 grouping sub-interfaces {
\r
1270 container sub-interfaces {
\r
1271 list sub-interface {
\r
1272 key "sub-interface-port-name";
\r
1273 leaf sub-interface-port-name {
\r
1276 leaf sub-interface-port-id {
\r
1279 container sub-interface-ip-addresses {
\r
1280 uses ip-addresses;
\r
1283 container sub-interface-network {
\r
1284 leaf network-name {
\r
1291 leaf sub-interface-status {
\r
1292 description "NULL, unassigned, assigned";
\r
1298 grouping vlan-tags {
\r
1299 container vlan-tags {
\r
1300 leaf vlan-interface {
\r
1301 description "A&AI Key";
\r
1304 leaf upper-tag-id {
\r
1307 leaf lower-tag-id {
\r
1315 grouping vlan-vnfc-instance-groups {
\r
1316 container vlan-vnfc-instance-groups {
\r
1317 list vlan-vnfc-instance-group {
\r
1318 key "instance-group-id";
\r
1319 leaf instance-group-id {
\r
1320 description "A&AI ID";
\r
1324 leaf instance-group-function {
\r
1342 grouping vnic-groups {
\r
1343 container vnic-groups {
\r
1345 key "vnic-interface-role";
\r
1346 leaf vnic-interface-role {
\r
1347 description "Same as network-role of network where vnic is connected";
\r
1351 leaf network-instance-group-function {
\r
1352 description "network-instance-Group-function for network collection where vnics with vnic-interface-role will connect";
\r
1355 leaf vlan-assignment-policy-name {
\r
1356 description "Policy name in ASDC model & policy definition in Policy Engine";
\r
1359 leaf vlan-tag-index-next {
\r
1360 description "Next tag to be assigned";
\r
1363 container vlan-common-ip-addresses {
\r
1364 uses ip-addresses;
\r
1366 container vlan-vnics {
\r
1368 key "vnic-port-id";
\r
1369 leaf vnic-port-id {
\r
1373 container vnic-sub-interfaces {
\r
1374 uses sub-interface-network-data;
\r
1381 grouping vnf-network-collection {
\r
1382 list vnf-network-collection {
\r
1383 key "network-instance-group-function";
\r
1384 leaf network-instance-group-function {
\r
1385 description "Network Instance-Group function in A&AI";
\r
1389 leaf network-instance-group-id {
\r
1390 description "Network Instance-Group id in A&AI";
\r
1393 leaf network-collection-service-instance-id {
\r
1394 description "Service-instance-id of service that created the network collection";
\r
1397 leaf network-collection-customization-uuid {
\r
1398 description "network-collection-customization-uuid stored in Network IsntanceGroup.customization-uuid in A&AI";
\r
1401 container networks {
\r
1405 description "Index into network-topology-identifier structure";
\r
1409 leaf neutron-network-id {
\r
1410 description "Neutron-network-id assigned by PO/RO";
\r
1415 container vnf-floating-ip {
\r
1416 uses ip-addresses;
\r
1420 grouping vnf-sub-interface-group {
\r
1421 list vnf-sub-interface-group {
\r
1422 key "vnfc-instance-group-function network-instance-group-function parent-port-role";
\r
1423 leaf vnfc-instance-group-function {
\r
1427 leaf network-instance-group-function {
\r
1431 leaf parent-port-role {
\r
1436 container customer-bonding-requests {
\r
1437 list customer-bonding-request {
\r
1438 key "configuration-id";
\r
1439 leaf configuration-id {
\r
1440 description "e.g. vlan network receptor configuration id";
\r
1447 grouping sub-interface-network-data {
\r
1448 list sub-interface-network-data {
\r
1451 description "Subinterface network id (UUID in A&AI)";
\r
1455 leaf neutron-network-id {
\r
1456 description "Neutron network id assigned by PO/RP";
\r
1459 leaf network-name {
\r
1460 description "Subinterface network name";
\r
1463 leaf vlan-tag-id {
\r
1464 description "Vlan tag assigned to subinterface port";
\r
1467 leaf network-role {
\r
1468 description "e.g. untrusted ";
\r
1471 leaf network-role-tag {
\r
1472 description "Assuming HEAT template network role tag parameter - not used";
\r
1475 container network-information-items {
\r
1476 list network-information-item {
\r
1479 description "Use ipv4 or ipv6";
\r
1483 description "Indicator to use DHCP on this network for this VM - set to N for Vlan tagging";
\r
1484 type enumeration {
\r
1490 description "The number of ip addresses to be assigned per vm for this network role";
\r
1493 container network-ips {
\r
1494 leaf-list network-ip {
\r
1495 description "List of assigned ip addresses of type ip-version on a network.";
\r
1496 type inet:ip-address;
\r
1502 container floating-ips {
\r
1503 leaf-list floating-ip-v4 {
\r
1504 description "Floating ipv4 for VMs of a given type on this network";
\r
1505 type inet:ip-address;
\r
1508 leaf-list floating-ip-v6 {
\r
1509 description "Floating ipv6 for VMs of a given type on this network";
\r
1510 type inet:ipv6-address;
\r
1516 grouping vnf-cloud-param {
\r
1517 leaf service-instance-id {
\r
1520 leaf service-instance-name {
\r
1533 key "vf-module-id";
\r
1534 leaf vf-module-id {
\r
1541 grouping vnf-get-resource-request-input-data {
\r
1548 key "vf-module-id";
\r
1549 leaf vf-module-id {
\r
1555 grouping license-information {
\r
1556 container license-information {
\r
1557 list entitlement-pool-list {
\r
1558 key "entitlement-pool-uuid action";
\r
1559 leaf entitlement-pool-uuid {
\r
1567 leaf entitlement-pool-invariant-uuid {
\r
1570 leaf entitlement-uuid {
\r
1571 description "assigned by ALTS";
\r
1575 list license-key-group-list {
\r
1576 key "license-key-group-uuid action";
\r
1577 leaf license-key-group-uuid {
\r
1585 leaf license-key-group-invariant-uuid {
\r
1588 leaf license-key {
\r
1589 description "assigned by ALTS";
\r
1592 leaf license-uuid {
\r
1593 description "assigned by ALTS";
\r
1599 grouping related-network {
\r
1600 list related-network {
\r
1603 description "Key to l3-network object";
\r
1606 leaf network-role {
\r
1612 grouping connection-point {
\r
1613 container connection-point {
\r
1614 leaf connection-point-id {
\r
1615 description "Key to CP object in A&AI";
\r
1619 description "port-index when multiple CPs connect to same network. Default zero (0)";
\r
1625 description "Key to vlan-tag uuid object in A&AI Generated by vlan mS";
\r
1628 leaf vlan-tag-id {
\r
1631 leaf vlan-tag-description {
\r
1635 description "Inner/Outer roles";
\r
1641 grouping aggregate-routes {
\r
1642 list aggregate-routes {
\r
1645 description "Unique id";
\r
1648 leaf start-address {
\r
1649 type inet:ip-address;
\r
1655 description "Use values 4 or 6.";
\r
1660 grouping pnf-information {
\r
1661 container pnf-information {
\r
1663 description "Key for A&AI query";
\r
1669 uses onap-model-information;
\r
1672 grouping contrail-route-operation-information {
\r
1673 uses sdnc-request-header;
\r
1674 uses request-information;
\r
1675 uses service-information;
\r
1676 uses allotted-resource-information;
\r
1677 uses contrail-route-request-input;
\r
1679 grouping contrail-route-request-input {
\r
1680 container contrail-route-request-input {
\r
1681 container source-network {
\r
1682 uses network-info;
\r
1684 container dest-network {
\r
1685 uses network-info;
\r
1687 container contrail-applied-service-info {
\r
1688 leaf service-instance-id {
\r
1689 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
1692 leaf contrail-fqdn {
\r
1693 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
1697 container contrail-route-input-parameters {
\r
1702 grouping network-info {
\r
1706 leaf network-role {
\r
1710 grouping contrail-route-topology {
\r
1711 container contrail-route-topology {
\r
1712 uses allotted-resource-identifiers;
\r
1713 uses onap-model-information;
\r
1714 uses contrail-route-assignments;
\r
1715 container contrail-route-parameters {
\r
1720 grouping contrail-route-assignments {
\r
1721 container contrail-route-assignments {
\r
1723 description "The Contrail fq-name of the network policy";
\r
1726 leaf contrail-id {
\r
1727 description "The ID assigned by Contrail to the network-policy (one for one with the fq-name)";
\r
1730 container source-network {
\r
1731 uses network-info;
\r
1733 container dest-network {
\r
1734 uses network-info;
\r
1736 container contrail-applied-service {
\r
1737 leaf service-instance-id {
\r
1738 description "The service-instance-id of the vnf from which the contrail applied service is coming";
\r
1742 description "The vnf representing the contrail applied service";
\r
1745 leaf contrail-fqdn {
\r
1746 description "This is the fq-name of the Contrail service instance through which the route is passing.";
\r
1751 description "Contrail-assigned vlan-tag to the vipr vm interface for this route.";
\r
1756 grouping security-zone-operation-information {
\r
1757 uses sdnc-request-header;
\r
1758 uses request-information;
\r
1759 uses service-information;
\r
1760 uses allotted-resource-information;
\r
1761 uses security-zone-request-input;
\r
1763 grouping security-zone-request-input {
\r
1764 container security-zone-request-input {
\r
1768 leaf trusted-network-role {
\r
1769 description "In the case of vIPR, this is the landing networks network-role; used in naming";
\r
1772 leaf untrusted-network-role {
\r
1773 description "In the case of vIPR, this is the tenant oam networks network-role; used in naming";
\r
1776 container security-zone-input-parameters {
\r
1781 grouping security-zone-topology {
\r
1782 container security-zone-topology {
\r
1783 uses allotted-resource-identifiers;
\r
1784 uses onap-model-information;
\r
1785 uses security-zone-assignments;
\r
1786 container security-zone-parameters {
\r
1791 grouping security-zone-assignments {
\r
1792 container security-zone-assignments {
\r
1793 leaf trusted-network-role {
\r
1794 description "In the case of vIPR, this is the landing networks network-role; used in naming";
\r
1797 leaf security-zone-name-trusted {
\r
1800 leaf untrusted-network-role {
\r
1801 description "In the case of vIPR, this is the tenant oam networks network-role; used in naming";
\r
1804 leaf security-zone-name-untrusted {
\r
1807 leaf security-zone-service-instance-id {
\r
1808 description "Will be the same as the parent-service-instance-id";
\r
1811 leaf security-zone-vnf-id {
\r
1812 description "Selected by SDNC from the security-zone-service-instance-id";
\r
1820 grouping port-mirror-topology-operation-information {
\r
1821 uses sdnc-request-header;
\r
1822 uses request-information;
\r
1823 uses service-information;
\r
1824 uses configuration-information;
\r
1825 uses port-mirror-configuration-request-input;
\r
1827 grouping port-mirror-configuration-request-input {
\r
1828 container port-mirror-configuration-request-input {
\r
1829 container source-port {
\r
1831 leaf source-port-id {
\r
1832 description "needed for srv-action=disable/enable";
\r
1836 container dest-port {
\r
1839 uses region-identifier;
\r
1840 container port-mirror-configuration-input-parameters {
\r
1845 grouping port-info {
\r
1846 leaf service-instance-id {
\r
1847 description "May not be need.";
\r
1850 uses pnf-information;
\r
1851 uses vnf-information;
\r
1853 grouping port-mirror-configuration-topology {
\r
1854 container port-mirror-configuration-topology {
\r
1855 uses configuration-identifiers;
\r
1856 uses onap-model-information;
\r
1857 uses port-mirror-configuration-assignments;
\r
1858 container port-mirror-configuration-parameters {
\r
1863 grouping port-mirror-configuration-assignments {
\r
1864 container port-mirror-configuration-assignments {
\r
1865 container contrail-vmi-params {
\r
1868 leaf vnics-group-id {
\r
1871 leaf owning-entity {
\r
1874 leaf tenant-context {
\r
1875 description "From tenant object in A&AI";
\r
1879 description "Tenant name from A&AI for source VNF";
\r
1883 description "tenant-id from A&AI for source VNF";
\r
1886 leaf dest-tenant {
\r
1887 description "Tenant name from A&AI for destination VNF";
\r
1890 leaf dest-tenant-id {
\r
1891 description "tenant-id from A&AI for destination VNF";
\r
1894 leaf cloud-region-id {
\r
1897 leaf cloud-owner {
\r
1900 leaf dest-network-fqdn {
\r
1903 leaf source-network-fqdn {
\r
1906 leaf source-capacity {
\r
1907 description "Source port pps (packets per second) rating from tosca model";
\r
1910 leaf source-vnf-id {
\r
1913 leaf dest-vnf-id {
\r
1914 description "For vProbe";
\r
1917 leaf dest-pnf-name {
\r
1918 description "For pProbe";
\r
1921 leaf dest-p-interface {
\r
1922 description "For pProbe; from policy manager";
\r
1925 leaf dest-pnf-port-policy-name {
\r
1926 description "For pProbe; from tosca model";
\r
1930 description "vprobe or pprobe; derived from configuration-information.configuration-sub-type";
\r
1933 leaf route-allotted-resource-id {
\r
1934 description "For vProbe";
\r
1937 container source-vnfc-instance-group-id {
\r
1938 leaf service-instance-id {
\r
1941 leaf nfc-naming-code {
\r
1944 leaf instance-group-role {
\r
1947 leaf configuration-id {
\r
1951 container dest-vnfc-instance-group-id {
\r
1952 leaf service-instance-id {
\r
1955 leaf nfc-naming-code {
\r
1958 leaf instance-group-role {
\r
1961 leaf configuration-id {
\r
1965 container source-to-dest-maps {
\r
1966 list source-to-dest-map {
\r
1967 key "source-port-id";
\r
1968 leaf source-port-id {
\r
1972 leaf source-port-name {
\r
1975 leaf source-vserver-id {
\r
1978 leaf dest-vserver-id {
\r
1981 leaf dest-port-id {
\r
1984 leaf dest-port-name {
\r
1990 container dest-ip-addresses {
\r
1991 uses ip-addresses;
\r
1997 grouping gc-topology-operation-information {
\r
1998 uses sdnc-request-header;
\r
1999 uses request-information;
\r
2000 uses service-information;
\r
2001 uses configuration-information;
\r
2002 uses gc-request-input;
\r
2004 grouping gc-request-input {
\r
2005 container gc-request-input {
\r
2009 leaf vf-module-id {
\r
2010 description "This is mandatory in case of rebuild";
\r
2013 container input-parameters {
\r
2017 description "Value will indicate what to rebuild";
\r
2020 list configuration-ids {
\r
2021 key "configuration-id";
\r
2022 leaf configuration-id {
\r
2028 grouping vnr-parameters {
\r
2029 container vnr-parameters {
\r
2033 leaf vf-module-id {
\r
2034 description "This is mandatory in case of rebuild";
\r
2037 leaf vnf-service-instance-id {
\r
2040 leaf network-collection-service-instance-id {
\r
2041 description "service instance id that created network-collection";
\r
2044 leaf network-instance-group-id {
\r
2050 leaf vnfc-instance-group-function {
\r
2053 leaf network-instance-group-function {
\r
2056 leaf parent-port-role {
\r
2059 leaf upper-tag-id {
\r
2062 leaf lower-tag-id {
\r
2067 grouping tunnelxconn-operation-information {
\r
2068 uses sdnc-request-header;
\r
2069 uses request-information;
\r
2070 uses service-information;
\r
2071 uses allotted-resource-information;
\r
2072 uses tunnelxconn-request-input;
\r
2074 grouping tunnelxconn-request-input {
\r
2076 container tunnelxconn-request-input {
\r
2077 leaf brg-wan-mac-address {
\r
2082 grouping tunnelxconn-topology {
\r
2083 container tunnelxconn-topology {
\r
2084 uses allotted-resource-identifiers;
\r
2085 uses onap-model-information;
\r
2086 uses tunnelxconn-assignments;
\r
2087 container tunnelxconn-parameters {
\r
2092 grouping tunnelxconn-assignments {
\r
2093 container tunnelxconn-assignments {
\r
2095 description "The Network Controller will assign a VNI value from the associated vGMUX VNI pool";
\r
2098 leaf vgmux-bearer-ip {
\r
2099 description "The Network Controller will look up the vgmux bearer ip from the vgmux vf module";
\r
2100 type inet:ip-address;
\r
2102 leaf vgmux-lan-ip {
\r
2103 description "The Network Controller will look up the vgmux lan ip from the vgmux vg module";
\r
2104 type inet:ip-address;
\r
2107 description "The Network Controller will assign the VG IP address from local inventory";
\r
2108 type inet:ip-address;
\r
2112 grouping brg-operation-information {
\r
2113 uses sdnc-request-header;
\r
2114 uses request-information;
\r
2115 uses service-information;
\r
2116 uses allotted-resource-information;
\r
2117 uses brg-request-input;
\r
2119 grouping brg-request-input {
\r
2120 container brg-request-input {
\r
2121 leaf vgmux-bearer-ip {
\r
2122 type inet:ip-address;
\r
2127 leaf brg-wan-mac-address {
\r
2132 grouping brg-topology {
\r
2133 container brg-topology {
\r
2134 uses allotted-resource-identifiers;
\r
2135 uses onap-model-information;
\r
2136 uses brg-assignments;
\r
2137 container brg-parameters {
\r
2142 grouping brg-assignments {
\r
2143 container brg-assignments {
\r
2144 leaf vbrg-wan-ip {
\r
2145 type inet:ip-address;
\r
2149 grouping connection-attachment-operation-information {
\r
2150 uses sdnc-request-header;
\r
2151 uses request-information;
\r
2152 uses service-information;
\r
2153 uses allotted-resource-information;
\r
2154 uses connection-attachment-request-input;
\r
2157 grouping connection-attachment-request-input {
\r
2158 container connection-attachment-request-input {
\r
2163 grouping connection-attachment-topology {
\r
2164 container connection-attachment-topology {
\r
2165 uses allotted-resource-identifiers;
\r
2166 uses onap-model-information;
\r
2167 uses connection-attachment-assignments;
\r
2168 container connection-attachment-parameters {
\r
2174 grouping connection-attachment-assignments {
\r
2175 container connection-attachment-assignments {
\r
2179 grouping vnf-vnr-rebuild-data {
\r
2180 container vnf-vnr-rebuild-data {
\r
2184 leaf vnf-service-instance-id {
\r
2188 key "configuration-id";
\r
2189 leaf configuration-id {
\r
2192 leaf network-instance-group-id {
\r
2198 leaf vnfc-instance-group-function {
\r
2201 leaf network-instance-group-function {
\r
2204 leaf parent-port-role {
\r
2207 leaf upper-tag-id {
\r
2210 leaf lower-tag-id {
\r
2216 grouping allotted-resource-information {
\r
2217 container allotted-resource-information {
\r
2218 leaf allotted-resource-id {
\r
2221 leaf allotted-resource-type {
\r
2222 description "Not an enum, but expected values are contrail-route and security-zone.";
\r
2225 leaf parent-service-instance-id {
\r
2226 description "Service-instance-id of the parent service to which this allotted resource belongs.";
\r
2229 uses onap-model-information;
\r
2232 grouping allotted-resource-identifiers {
\r
2233 container allotted-resource-identifiers {
\r
2234 leaf allotted-resource-id {
\r
2237 leaf allotted-resource-name {
\r
2238 description "For a contrail-route, the network policy name.";
\r
2241 leaf allotted-resource-type {
\r
2242 description "(Added in draft 32)Expected to be contrail-route or security-zone.";
\r
2245 leaf consuming-service-instance-id {
\r
2246 description "The service-instance-id of the consuming service of this allotted resource";
\r
2249 leaf parent-service-instance-id {
\r
2250 description "Service-instance-id of the parent service to which this allotted resource belongs.";
\r
2255 grouping allotted-resource-oper-status {
\r
2256 container allotted-resource-oper-status {
\r
2257 uses oper-status-data;
\r
2260 grouping allotted-resource-status {
\r
2261 container allotted-resource-status {
\r
2262 leaf response-code {
\r
2265 leaf response-message {
\r
2268 leaf final-indicator {
\r
2271 leaf request-status {
\r
2272 type enumeration {
\r
2273 enum "synccomplete";
\r
2274 enum "asynccomplete";
\r
2275 enum "notifycomplete";
\r
2279 description "value would one of possible request-actions; match the list in service-data oper-status";
\r
2286 description "this is the svc-action from the incoming request";
\r
2287 type enumeration {
\r
2293 enum "deactivate";
\r
2296 leaf response-timestamp {
\r
2301 grouping configuration-information {
\r
2302 container configuration-information {
\r
2303 leaf configuration-id {
\r
2306 leaf configuration-name {
\r
2309 leaf configuration-type {
\r
2310 description "Not an enum, but expected values are port-mirror-configuration, vlan-network-receptor";
\r
2313 leaf configuration-sub-type {
\r
2314 description "e.g. vprobe and pprobe when configuration-type=port-mirror-configuration";
\r
2317 uses onap-model-information;
\r
2320 grouping configuration-identifiers {
\r
2321 container configuration-identifiers {
\r
2322 leaf configuration-id {
\r
2325 leaf configuration-name {
\r
2328 leaf configuration-type {
\r
2329 description "Not an enum, but expected values are port-mirror-configuration.";
\r
2332 leaf configuration-sub-type {
\r
2333 description " vprobe and pprobe";
\r
2336 leaf parent-service-instance-id {
\r
2337 description "Service-instance-id of the parent service to which this resource belongs.";
\r
2342 grouping configuration-oper-status {
\r
2343 container configuration-oper-status {
\r
2344 uses oper-status-data;
\r
2347 grouping configuration-status {
\r
2348 container configuration-status {
\r
2349 leaf response-code {
\r
2352 leaf response-message {
\r
2355 leaf final-indicator {
\r
2358 leaf request-status {
\r
2359 type enumeration {
\r
2360 enum "synccomplete";
\r
2361 enum "asynccomplete";
\r
2362 enum "notifycomplete";
\r
2366 description "value would one of possible request-actions; match the list in service-data oper-status";
\r
2373 description "this is the svc-action from the incoming request";
\r
2374 type enumeration {
\r
2382 enum "deactivate";
\r
2385 leaf response-timestamp {
\r
2390 grouping topology-response-common {
\r
2391 leaf svc-request-id {
\r
2392 description "the request id from the request message for which this is the responseKeep as M";
\r
2395 leaf response-code {
\r
2396 description "a success code or an defined error codeKeep as M";
\r
2399 leaf response-message {
\r
2400 description "message included for error code";
\r
2403 leaf ack-final-indicator {
\r
2404 description "Expected to be Y or N.";
\r
2408 grouping sdnc-request-header {
\r
2409 container sdnc-request-header {
\r
2410 leaf svc-request-id {
\r
2411 description "Uniquely generated by calling system (e.g. MSO or SDN-GP)";
\r
2415 description "This is the rpcAction";
\r
2416 type enumeration {
\r
2421 enum "changeassign";
\r
2422 enum "changedelete";
\r
2424 enum "deactivate";
\r
2430 enum "reoptimize";
\r
2434 leaf svc-notification-url {
\r
2435 description "Contains URL for asynchronous response";
\r
2440 grouping request-information {
\r
2441 container request-information {
\r
2443 description "Request ID generated upstream of MSO";
\r
2446 leaf request-action {
\r
2447 description "still need to work Disconnect";
\r
2448 type enumeration {
\r
2449 enum "CreateNetworkInstance";
\r
2450 enum "ActivateNetworkInstance";
\r
2451 enum "DeActivateNetworkInstance";
\r
2452 enum "CreateServiceInstance";
\r
2453 enum "DeleteServiceInstance";
\r
2454 enum "DeleteNetworkInstance";
\r
2455 enum "CreateVnfInstance";
\r
2456 enum "ActivateVnfInstance";
\r
2457 enum "DeleteVnfInstance";
\r
2458 enum "CreatePnfInstance";
\r
2459 enum "ActivatePnfInstance";
\r
2460 enum "DeletePnfInstance";
\r
2461 enum "CreateVfModuleInstance";
\r
2462 enum "ActivateVfModuleInstance";
\r
2463 enum "DeleteVfModuleInstance";
\r
2464 enum "CreateContrailRouteInstance";
\r
2465 enum "DeleteContrailRouteInstance";
\r
2466 enum "CreateSecurityZoneInstance";
\r
2467 enum "DeleteSecurityZoneInstance";
\r
2468 enum "ActivateDCINetworkInstance";
\r
2469 enum "DeActivateDCINetworkInstance";
\r
2470 enum "CreateTunnelXConnInstance";
\r
2471 enum "DeleteTunnelXConnInstance";
\r
2472 enum "CreateBRGInstance";
\r
2473 enum "DeleteBRGInstance";
\r
2474 enum "CreateSOTNConnectivityInstance";
\r
2475 enum "ActivateSOTNConnectivityInstance";
\r
2476 enum "DeactivateSOTNConnectivityInstance";
\r
2477 enum "DeleteSOTNConnectivityInstance";
\r
2478 enum "CreateSOTNAttachmentInstance";
\r
2479 enum "ActivateSOTNAttachmentInstance";
\r
2480 enum "DeactivateSOTNAttachmentInstance";
\r
2481 enum "DeleteSOTNAttachmentInstance";
\r
2482 enum "CreateSiteInstance";
\r
2483 enum "ActivateSiteInstance";
\r
2484 enum "DeactivateSiteInstance";
\r
2485 enum "DeleteSiteInstance";
\r
2486 enum "CreatePortMirrorConfigurationInstance";
\r
2487 enum "DeletePortMirrorConfigurationInstance";
\r
2488 enum "ChangePortMirrorConfigurationInstance";
\r
2489 enum "CreateGenericConfigurationInstance";
\r
2490 enum "RebuildGenericConfigurationInstance";
\r
2491 enum "DeleteGenericConfigurationInstance";
\r
2492 enum "PreloadVfModuleRequest";
\r
2493 enum "DeletePreloadVfModuleRequest";
\r
2494 enum "PreloadNetworkRequest";
\r
2495 enum "DeletePreloadNetworkRequest";
\r
2496 enum "CreateForwardingPathInstance";
\r
2497 enum "DeleteForwardingPathInstance";
\r
2498 enum "UpdateForwardingPathInstance";
\r
2499 enum "CreateSDWANDeviceInstance";
\r
2500 enum "ActivateSDWANDeviceInstance";
\r
2501 enum "DeactivateSDWANDeviceInstance";
\r
2502 enum "DeleteSDWANDeviceInstance";
\r
2503 enum "CreateSDWANPortInstance";
\r
2504 enum "ActivateSDWANPortInstance";
\r
2505 enum "DeactivateSDWANPortInstance";
\r
2506 enum "DeleteSDWANPortInstance";
\r
2507 enum "ReoptimizeSOTNInstance";
\r
2508 enum "CreateSDWANLanPortInstance";
\r
2509 enum "ActivateSDWANLanPortInstance";
\r
2510 enum "DeactivateSDWANLanPortInstance";
\r
2511 enum "DeleteSDWANLanPortInstance";
\r
2512 enum "CreateSDWANVpnInstance";
\r
2513 enum "ActivateSDWANVpnInstance";
\r
2514 enum "DeactivateSDWANVpnInstance";
\r
2515 enum "DeleteSDWANVpnInstance";
\r
2516 enum "CreateSDWANSiteInstance";
\r
2517 enum "ActivateSDWANSiteInstance";
\r
2518 enum "DeactivateSDWANSiteInstance";
\r
2519 enum "DeleteSDWANSiteInstance";
\r
2520 enum "SdwanBandwidthChange";
\r
2526 leaf notification-url {
\r
2529 leaf order-number {
\r
2532 leaf order-version {
\r
2537 grouping service-information {
\r
2538 container service-information {
\r
2540 description "This maps to the product-family-id in A&AI";
\r
2543 leaf subscription-service-type {
\r
2544 description "used to reference a&ai subscription-service-type. For example, we show as vIPR-ATM in example.";
\r
2547 uses onap-model-information;
\r
2548 leaf service-instance-id {
\r
2551 leaf global-customer-id {
\r
2552 description "need for put of data to AnAI (MSO provides)";
\r
2555 leaf subscriber-name {
\r
2556 description "Would not be expected for vIPR-ATM or mobility services.";
\r
2561 grouping onap-model-information {
\r
2562 container onap-model-information {
\r
2563 leaf model-invariant-uuid {
\r
2564 description "identifies the invariant uuid for this service or resource";
\r
2567 leaf model-customization-uuid {
\r
2568 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
2572 description "identifies the uuid for this service or resource, which is version specific";
\r
2575 leaf model-version {
\r
2583 grouping region-identifier {
\r
2587 leaf aic-cloud-region {
\r
2588 description "The AIC cloud region which maps to contrail versions";
\r
2591 leaf cloud-owner {
\r
2592 description "The cloud owner provided by the caller";
\r
2596 description "Not expected to be used";
\r
2609 container resource-resolution-data {
\r
2610 list resource-key {
\r
2620 description "SUCCESS, FAILED, or PENDING - RA returned data as capability";
\r
2623 leaf capability-name {
\r
2624 description "Resource assignment resolution Capability name";
\r
2630 grouping ip-addresses {
\r
2631 container ip-addresses {
\r
2632 leaf ipv4-address {
\r
2633 type inet:ip-address;
\r
2635 leaf ipv6-address {
\r
2636 type inet:ip-address;
\r
2638 leaf vipv4-address {
\r
2639 description "Virtual v4";
\r
2640 type inet:ip-address;
\r
2642 leaf vipv6-address {
\r
2643 description "Virtual v6";
\r
2644 type inet:ip-address;
\r
2648 grouping instance-reference {
\r
2649 leaf instance-id {
\r
2652 leaf object-path {
\r
2653 description "restconf retrieval path to this particular objectE.g. restconf/config/GENERIC-RESOURCE-API:services/service/$service-instance-id/service-data/service-topology/";
\r
2657 grouping oper-status-data {
\r
2658 leaf order-status {
\r
2659 description "TBD - do we need Request failed statuses? RequestFailed | InProgressTimeout";
\r
2660 type enumeration {
\r
2662 enum "PendingAssignment";
\r
2663 enum "PendingCreate";
\r
2664 enum "PendingUpdate";
\r
2665 enum "PendingDelete";
\r
2670 leaf last-rpc-action {
\r
2671 type enumeration {
\r
2676 enum "deactivate";
\r
2678 enum "changeassign";
\r
2679 enum "reoptimize";
\r
2682 leaf last-action {
\r
2683 description "should be list of possible request-actions";
\r
2684 type enumeration {
\r
2685 enum "CreateNetworkInstance";
\r
2686 enum "ActivateNetworkInstance";
\r
2687 enum "DeActivateNetworkInstance";
\r
2688 enum "DeleteNetworkInstance";
\r
2689 enum "CreateServiceInstance";
\r
2690 enum "DeleteServiceInstance";
\r
2691 enum "CreateVnfInstance";
\r
2692 enum "ActivateVnfInstance";
\r
2693 enum "DeleteVnfInstance";
\r
2694 enum "CreatePnfInstance";
\r
2695 enum "ActivatePnfInstance";
\r
2696 enum "DeletePnfInstance";
\r
2697 enum "CreateVfModuleInstance";
\r
2698 enum "ActivateVfModuleInstance";
\r
2699 enum "DeleteVfModuleInstance";
\r
2700 enum "CreateContrailRouteInstance";
\r
2701 enum "DeleteContrailRouteInstance";
\r
2702 enum "CreateSecurityZoneInstance";
\r
2703 enum "DeleteSecurityZoneInstance";
\r
2704 enum "ActivateDCINetworkInstance";
\r
2705 enum "DeActivateDCINetworkInstance";
\r
2706 enum "CreateTunnelXConnInstance";
\r
2707 enum "DeleteTunnelXConnInstance";
\r
2708 enum "CreateBRGInstance";
\r
2709 enum "DeleteBRGInstance";
\r
2710 enum "CreateSOTNConnectivityInstance";
\r
2711 enum "ActivateSOTNConnectivityInstance";
\r
2712 enum "DeactivateSOTNConnectivityInstance";
\r
2713 enum "DeleteSOTNConnectivityInstance";
\r
2714 enum "CreateSOTNAttachmentInstance";
\r
2715 enum "ActivateSOTNAttachmentInstance";
\r
2716 enum "DeactivateSOTNAttachmentInstance";
\r
2717 enum "DeleteSOTNAttachmentInstance";
\r
2718 enum "CreateSiteInstance";
\r
2719 enum "ActivateSiteInstance";
\r
2720 enum "DeactivateSiteInstance";
\r
2721 enum "DeleteSiteInstance";
\r
2722 enum "CreatePortMirrorConfigurationInstance";
\r
2723 enum "DeletePortMirrorConfigurationInstance";
\r
2724 enum "ChangePortMirrorConfigurationInstance";
\r
2725 enum "CreateGenericConfigurationInstance";
\r
2726 enum "DeleteGenericConfigurationInstance";
\r
2727 enum "PreloadVfModuleRequest";
\r
2728 enum "DeletePreloadVfModuleRequest";
\r
2729 enum "PreloadNetworkRequest";
\r
2730 enum "DeletePreloadNetworkRequest";
\r
2731 enum "CreateForwardingPathInstance";
\r
2732 enum "DeleteForwardingPathInstance";
\r
2733 enum "UpdateForwardingPathInstance";
\r
2734 enum "CreateSDWANDeviceInstance";
\r
2735 enum "ActivateSDWANDeviceInstance";
\r
2736 enum "DeactivateSDWANDeviceInstance";
\r
2737 enum "DeleteSDWANDeviceInstance";
\r
2738 enum "CreateSDWANPortInstance";
\r
2739 enum "ActivateSDWANPortInstance";
\r
2740 enum "DeactivateSDWANPortInstance";
\r
2741 enum "DeleteSDWANPortInstance";
\r
2742 enum "ReoptimizeSOTNInstance";
\r
2743 enum "CreateSDWANLanPortInstance";
\r
2744 enum "ActivateSDWANLanPortInstance";
\r
2745 enum "DeactivateSDWANLanPortInstance";
\r
2746 enum "DeleteSDWANLanPortInstance";
\r
2747 enum "CreateSDWANVpnInstance";
\r
2748 enum "ActivateSDWANVpnInstance";
\r
2749 enum "DeactivateSDWANVpnInstance";
\r
2750 enum "DeleteSDWANVpnInstance";
\r
2751 enum "CreateSDWANSiteInstance";
\r
2752 enum "ActivateSDWANSiteInstance";
\r
2753 enum "DeactivateSDWANSiteInstance";
\r
2754 enum "DeleteSDWANSiteInstance";
\r
2755 enum "SdwanBandwidthChange";
\r
2758 leaf last-svc-request-id {
\r
2759 description "Not currently populated in service data.";
\r
2762 leaf last-order-status {
\r
2763 type enumeration {
\r
2765 enum "PendingAssignment";
\r
2766 enum "PendingCreate";
\r
2767 enum "PendingUpdate";
\r
2768 enum "PendingDelete";
\r
2773 leaf create-timestamp {
\r
2774 description "Not currently populated in service data.";
\r
2777 leaf modify-timestamp {
\r
2781 grouping service-response-information {
\r
2782 container service-response-information {
\r
2783 uses instance-reference;
\r
2786 grouping network-response-information {
\r
2787 container network-response-information {
\r
2788 uses instance-reference;
\r
2791 grouping vnf-response-information {
\r
2792 container vnf-response-information {
\r
2793 uses instance-reference;
\r
2796 grouping vf-module-response-information {
\r
2797 container vf-module-response-information {
\r
2798 uses instance-reference;
\r
2801 grouping pnf-response-information {
\r
2802 container pnf-response-information {
\r
2803 uses instance-reference;
\r
2806 grouping contrail-route-response-information {
\r
2807 container contrail-route-response-information {
\r
2808 uses instance-reference;
\r
2811 grouping security-zone-response-information {
\r
2812 container security-zone-response-information {
\r
2813 uses instance-reference;
\r
2816 grouping getpathsegment-response-information {
\r
2817 container getpathsegment-response-information {
\r
2818 uses instance-reference;
\r
2821 grouping port-mirror-response-information {
\r
2822 container port-mirror-response-information {
\r
2823 uses instance-reference;
\r
2826 grouping gc-response-information {
\r
2827 container gc-response-information {
\r
2828 uses instance-reference;
\r
2831 grouping tunnelxconn-response-information {
\r
2832 container tunnelxconn-response-information {
\r
2833 uses instance-reference;
\r
2836 grouping brg-response-information {
\r
2837 container brg-response-information {
\r
2838 uses instance-reference;
\r
2841 grouping connection-attachment-response-information {
\r
2842 container connection-attachment-response-information {
\r
2843 uses instance-reference;
\r
2846 grouping preload-model-information {
\r
2847 list preload-list {
\r
2848 key "preload-id preload-type";
\r
2850 description "vf-module-name or network name";
\r
2854 leaf preload-type {
\r
2855 description "network or vf-module";
\r
2859 uses preload-data;
\r
2862 grouping preload-data {
\r
2863 container preload-data {
\r
2864 uses preload-vf-module-topology-information;
\r
2865 uses preload-network-topology-information;
\r
2866 uses preload-oper-status;
\r
2869 grouping preload-vf-module-topology-information {
\r
2870 container preload-vf-module-topology-information {
\r
2871 uses vnf-topology-identifier-structure;
\r
2872 uses vnf-resource-assignments;
\r
2873 uses vf-module-topology;
\r
2876 grouping preload-network-topology-information {
\r
2877 container preload-network-topology-information {
\r
2878 uses network-topology-identifier-structure;
\r
2880 uses vpn-bindings;
\r
2881 uses network-policy;
\r
2882 uses route-table-reference;
\r
2884 uses provider-network-information;
\r
2887 grouping subnets {
\r
2889 key "start-address";
\r
2890 leaf start-address {
\r
2891 type inet:ip-address;
\r
2893 leaf gateway-address {
\r
2894 type inet:ip-address;
\r
2902 leaf dhcp-enabled {
\r
2903 type enumeration {
\r
2908 leaf dhcp-start-address {
\r
2911 leaf dhcp-end-address {
\r
2914 leaf addr-from-start {
\r
2915 description "Default is N";
\r
2916 type enumeration {
\r
2921 leaf subnet-name {
\r
2924 leaf subnet-role {
\r
2927 leaf subnet-sequence {
\r
2932 grouping vpn-bindings {
\r
2933 list vpn-bindings {
\r
2934 key "vpn-binding-id";
\r
2935 leaf vpn-binding-id {
\r
2941 leaf global-route-target {
\r
2944 leaf route-target-role {
\r
2948 description "AIC Zone the route target associated with";
\r
2953 grouping network-policy {
\r
2954 list network-policy {
\r
2955 key "network-policy-fqdn";
\r
2956 leaf network-policy-fqdn {
\r
2959 leaf network-policy-id {
\r
2964 grouping route-table-reference {
\r
2965 list route-table-reference {
\r
2966 key "route-table-reference-fqdn";
\r
2967 leaf route-table-reference-fqdn {
\r
2971 leaf route-table-reference-id {
\r
2976 grouping provider-network-information {
\r
2977 leaf physical-network-name {
\r
2980 leaf is-provider-network {
\r
2983 leaf is-shared-network {
\r
2986 leaf is-external-network {
\r
2990 grouping host-routes {
\r
2991 list host-routes {
\r
2992 key "route-prefix";
\r
2993 leaf route-prefix {
\r
2997 description "Could be ip-address or hostname or service-instance";
\r
3002 grouping preload-oper-status {
\r
3003 container preload-oper-status {
\r
3004 leaf order-status {
\r
3005 type enumeration {
\r
3007 enum "PendingAssignment";
\r
3008 enum "PendingCreate";
\r
3009 enum "PendingUpdate";
\r
3010 enum "PendingDelete";
\r
3014 leaf last-action {
\r
3015 type enumeration {
\r
3016 enum "PreloadVfModuleRequest";
\r
3017 enum "DeletePreloadVfModuleRequest";
\r
3018 enum "PreloadNetworkRequest";
\r
3019 enum "DeletePreloadNetworkRequest";
\r
3022 leaf last-svc-request-id {
\r
3025 leaf last-order-status {
\r
3026 type enumeration {
\r
3028 enum "PendingAssignment";
\r
3029 enum "PendingCreate";
\r
3030 enum "PendingUpdate";
\r
3031 enum "PendingDelete";
\r
3035 leaf create-timestamp {
\r
3038 leaf modify-timestamp {
\r
3041 leaf maintenance-indicator {
\r
3042 type enumeration {
\r
3049 grouping preload-topology-response-body {
\r
3050 leaf svc-request-id {
\r
3053 leaf response-code {
\r
3056 leaf response-message {
\r
3059 leaf ack-final-indicator {
\r
3063 rpc generic-configuration-notification {
\r
3065 uses sdnc-request-header;
\r
3066 uses request-information;
\r
3067 uses service-information;
\r
3068 uses configuration-information;
\r
3069 uses topology-response-common;
\r
3070 leaf configuration-topology-link {
\r
3071 description "Returns URL to generic-configuration-topology ";
\r
3074 uses vnr-parameters;
\r
3075 uses vnf-vnr-rebuild-data;
\r
3078 container services {
\r
3079 uses service-model-infrastructure;
\r
3081 container contrail-route-allotted-resources {
\r
3082 list contrail-route-allotted-resource {
\r
3083 key "allotted-resource-id";
\r
3084 leaf allotted-resource-id {
\r
3088 container allotted-resource-data {
\r
3089 container allotted-resource-operation-information {
\r
3090 uses contrail-route-operation-information;
\r
3092 uses contrail-route-topology;
\r
3093 uses allotted-resource-oper-status;
\r
3095 uses allotted-resource-status;
\r
3098 container security-zone-allotted-resources {
\r
3099 list security-zone-allotted-resource {
\r
3100 key "allotted-resource-id";
\r
3101 leaf allotted-resource-id {
\r
3105 container allotted-resource-data {
\r
3106 container allotted-resource-operation-information {
\r
3107 uses security-zone-operation-information;
\r
3109 uses security-zone-topology;
\r
3110 container security-zone-parameters {
\r
3113 uses allotted-resource-oper-status;
\r
3115 uses allotted-resource-status;
\r
3118 container tunnelxconn-allotted-resources {
\r
3119 list tunnelxconn-allotted-resource {
\r
3120 key "allotted-resource-id";
\r
3121 leaf allotted-resource-id {
\r
3125 container allotted-resource-data {
\r
3126 container allotted-resource-operation-information {
\r
3127 uses tunnelxconn-operation-information;
\r
3129 uses tunnelxconn-topology;
\r
3130 container tunnelxconn-parameters {
\r
3133 uses allotted-resource-oper-status;
\r
3135 uses allotted-resource-status;
\r
3138 container brg-allotted-resources {
\r
3139 list brg-allotted-resource {
\r
3140 key "allotted-resource-id";
\r
3141 leaf allotted-resource-id {
\r
3145 container allotted-resource-data {
\r
3146 container allotted-resource-operation-information {
\r
3147 uses brg-operation-information;
\r
3149 uses brg-topology;
\r
3150 container brg-parameters {
\r
3153 uses allotted-resource-oper-status;
\r
3155 uses allotted-resource-status;
\r
3158 container connection-attachment-allotted-resources {
\r
3159 list connection-attachment-allotted-resource {
\r
3160 key "allotted-resource-id";
\r
3161 leaf allotted-resource-id {
\r
3165 container allotted-resource-data {
\r
3166 container allotted-resource-operation-information {
\r
3167 uses connection-attachment-operation-information;
\r
3169 uses connection-attachment-topology;
\r
3170 container connection-attachment-parameters {
\r
3173 uses allotted-resource-oper-status;
\r
3175 uses allotted-resource-status;
\r
3178 container port-mirror-configurations {
\r
3179 list port-mirror-configuration {
\r
3180 key "configuration-id";
\r
3181 leaf configuration-id {
\r
3185 container configuration-data {
\r
3186 container configuration-operation-information {
\r
3187 uses port-mirror-topology-operation-information;
\r
3189 uses port-mirror-configuration-topology;
\r
3190 uses configuration-oper-status;
\r
3192 uses configuration-status;
\r
3195 container generic-configurations {
\r
3196 list gc-configuration {
\r
3197 key "configuration-id";
\r
3198 leaf configuration-id {
\r
3202 container configuration-data {
\r
3203 container configuration-operation-information {
\r
3204 uses gc-topology-operation-information;
\r
3206 uses configuration-oper-status;
\r
3208 uses configuration-status;
\r
3211 rpc service-topology-operation {
\r
3213 uses service-operation-information;
\r
3216 uses topology-response-common;
\r
3217 uses service-response-information;
\r
3220 rpc network-topology-operation {
\r
3222 uses network-operation-information;
\r
3225 uses topology-response-common;
\r
3226 uses network-response-information;
\r
3227 uses service-response-information;
\r
3230 rpc vnf-topology-operation {
\r
3232 uses vnf-operation-information;
\r
3235 uses topology-response-common;
\r
3236 uses vnf-response-information;
\r
3237 uses service-response-information;
\r
3240 rpc vf-module-topology-operation {
\r
3242 uses vf-module-operation-information;
\r
3245 uses topology-response-common;
\r
3246 uses vf-module-response-information;
\r
3247 uses vnf-response-information;
\r
3248 uses service-response-information;
\r
3251 rpc pnf-topology-operation {
\r
3253 uses pnf-operation-information;
\r
3256 uses topology-response-common;
\r
3257 uses pnf-response-information;
\r
3258 uses service-response-information;
\r
3261 rpc contrail-route-topology-operation {
\r
3263 uses contrail-route-operation-information;
\r
3266 uses topology-response-common;
\r
3267 uses contrail-route-response-information;
\r
3268 uses service-response-information;
\r
3271 rpc security-zone-topology-operation {
\r
3273 uses security-zone-operation-information;
\r
3276 uses topology-response-common;
\r
3277 uses security-zone-response-information;
\r
3278 uses service-response-information;
\r
3281 rpc tunnelxconn-topology-operation {
\r
3283 uses tunnelxconn-operation-information;
\r
3286 uses topology-response-common;
\r
3287 uses tunnelxconn-response-information;
\r
3288 uses service-response-information;
\r
3291 rpc brg-topology-operation {
\r
3293 uses brg-operation-information;
\r
3296 uses topology-response-common;
\r
3297 uses brg-response-information;
\r
3298 uses service-response-information;
\r
3301 rpc policy-update-notify-operation {
\r
3303 leaf policy-name {
\r
3308 description "Map JSON versionNo to version-id";
\r
3312 leaf update-type {
\r
3326 rpc getpathsegment-topology-operation {
\r
3328 uses forwarding-path-operation-information;
\r
3331 uses topology-response-common;
\r
3332 uses getpathsegment-response-information;
\r
3333 uses service-response-information;
\r
3336 rpc port-mirror-topology-operation {
\r
3338 uses port-mirror-topology-operation-information;
\r
3341 uses topology-response-common;
\r
3342 uses port-mirror-response-information;
\r
3343 uses service-response-information;
\r
3346 rpc generic-configuration-topology-operation {
\r
3348 uses gc-topology-operation-information;
\r
3351 uses topology-response-common;
\r
3352 uses gc-response-information;
\r
3353 uses service-response-information;
\r
3356 rpc vnf-get-resource-request {
\r
3358 uses sdnc-request-header;
\r
3359 uses request-information;
\r
3360 uses service-information;
\r
3361 uses vnf-get-resource-request-input-data;
\r
3364 container vnf-get-resource-response-information {
\r
3365 uses vnf-cloud-param;
\r
3369 container preload-information {
\r
3370 uses preload-model-information;
\r
3372 rpc preload-vf-module-topology-operation {
\r
3374 uses sdnc-request-header;
\r
3375 uses request-information;
\r
3376 uses preload-vf-module-topology-information;
\r
3379 uses preload-topology-response-body;
\r
3382 rpc preload-network-topology-operation {
\r
3384 uses sdnc-request-header;
\r
3385 uses request-information;
\r
3386 uses preload-network-topology-information;
\r
3389 uses preload-topology-response-body;
\r
3393 rpc connection-attachment-topology-operation {
\r
3395 uses connection-attachment-operation-information;
\r
3398 uses topology-response-common;
\r
3399 uses connection-attachment-response-information;
\r
3400 uses service-response-information;
\r
3404 } ////closes the module
\r