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-provided-allotted-resources {
\r
65 leaf-list vnf-provided-ar-id {
\r
66 description "List of allotted resources using capacity from this vnf";
\r
71 uses vnf-level-oper-status;
\r
72 container vf-modules {
\r
79 container vf-module-data {
\r
80 uses vf-module-operation-information;
\r
81 uses vf-module-topology;
\r
82 uses vf-module-level-oper-status;
\r
89 container consumed-allotted-resources {
\r
90 list consumed-allotted-resource {
\r
91 key "allotted-resource-id";
\r
92 uses allotted-resource-info;
\r
95 container provided-allotted-resources {
\r
96 list provided-allotted-resource {
\r
97 key "allotted-resource-id";
\r
98 uses allotted-resource-info;
\r
103 grouping service-status {
\r
104 container service-status {
\r
105 leaf response-code {
\r
108 leaf response-message {
\r
111 leaf final-indicator {
\r
114 leaf request-status {
\r
116 enum "synccomplete";
\r
117 enum "asynccomplete";
\r
118 enum "notifycomplete";
\r
122 description "value would one of possible request-actions; match the list in service-data oper-status";
\r
129 description "this is the svc-action from the incoming request";
\r
139 leaf response-timestamp {
\r
144 grouping service-operation-information {
\r
145 uses sdnc-request-header;
\r
146 uses request-information;
\r
147 uses service-information;
\r
148 uses service-request-input;
\r
150 grouping service-request-input {
\r
151 container service-request-input {
\r
152 leaf service-instance-name {
\r
155 container service-input-parameters {
\r
160 grouping service-topology {
\r
161 container service-topology {
\r
162 uses service-topology-identifier;
\r
163 uses onap-model-information;
\r
164 uses service-assignments;
\r
165 uses service-parameters;
\r
168 grouping service-topology-identifier {
\r
169 container service-topology-identifier {
\r
170 leaf service-instance-id {
\r
171 description "repeated";
\r
174 leaf service-type {
\r
175 description "tag labeled subscription-service-type in the service-information input";
\r
179 description "from MSO input on STO assign";
\r
182 leaf service-instance-name {
\r
183 description "optionally comes from service-request-input container or is assigned by sdn-c";
\r
186 leaf global-customer-id {
\r
191 grouping service-assignments {
\r
192 container service-assignments {
\r
195 grouping service-parameters {
\r
196 container service-parameters {
\r
197 list service-parameter {
\r
198 key "service-parameter-name";
\r
199 leaf service-parameter-name {
\r
202 leaf service-parameter-value {
\r
208 grouping service-level-oper-status {
\r
209 container service-level-oper-status {
\r
210 uses oper-status-data;
\r
213 grouping network-operation-information {
\r
214 uses sdnc-request-header;
\r
215 uses request-information;
\r
216 uses service-information;
\r
217 uses network-information;
\r
218 uses network-request-input;
\r
220 grouping network-information {
\r
221 container network-information {
\r
225 leaf network-type {
\r
228 uses onap-model-information;
\r
231 grouping network-request-input {
\r
232 container network-request-input {
\r
233 leaf network-name {
\r
236 uses region-identifier;
\r
237 container network-input-parameters {
\r
242 grouping network-topology {
\r
243 container network-topology {
\r
244 uses network-topology-identifier-structure;
\r
245 uses region-identifier;
\r
246 uses onap-model-information;
\r
247 uses network-assignments;
\r
248 uses network-parameters;
\r
251 grouping network-topology-identifier-structure {
\r
252 container network-topology-identifier-structure {
\r
256 leaf network-name {
\r
259 leaf network-role {
\r
262 leaf network-type {
\r
265 leaf network-technology {
\r
266 description "should we keep this?";
\r
269 leaf eipam-v4-address-plan {
\r
273 leaf eipam-v6-address-plan {
\r
278 grouping network-assignments {
\r
279 container network-assignments {
\r
282 grouping network-parameters {
\r
283 container network-parameters {
\r
284 list network-parameter {
\r
285 key "network-parameter-name";
\r
286 leaf network-parameter-name {
\r
289 leaf network-parameter-value {
\r
295 grouping network-level-oper-status {
\r
296 container network-level-oper-status {
\r
297 uses oper-status-data;
\r
300 grouping vnf-operation-information {
\r
301 uses sdnc-request-header;
\r
302 uses request-information;
\r
303 uses service-information;
\r
304 uses vnf-information;
\r
305 uses vnf-request-input;
\r
307 grouping vnf-information {
\r
308 container vnf-information {
\r
313 description "vnf-model-id in Pats model?in Pats vnf submodule, contained within vnf-instance-topology-identifier grouping (along with vnf-name and vnf-instance-id)";
\r
316 uses onap-model-information;
\r
319 grouping vnf-request-input {
\r
320 container vnf-request-input {
\r
321 leaf request-version {
\r
322 description "keep this? e.g. 1702";
\r
326 description "in Pats vnf submodule, contained within vnf-instance-topology-identifier (along with vnf-model-id and vnf-instance-id)";
\r
329 uses region-identifier;
\r
330 container vnf-networks {
\r
332 key "network-role";
\r
333 uses vnf-network-data;
\r
336 container vnf-input-parameters {
\r
341 grouping vnf-topology {
\r
342 container vnf-topology {
\r
343 uses vnf-topology-identifier-structure;
\r
344 uses region-identifier;
\r
345 uses onap-model-information;
\r
346 uses vnf-resource-assignments;
\r
347 container vnf-parameters-data {
\r
352 grouping vnf-topology-identifier-structure {
\r
353 container vnf-topology-identifier-structure {
\r
358 description "In preload tree, this label is used for the vf-module-type";
\r
371 description "used in vnf naming";
\r
375 description "optionally comes from vnf-request-input container or is assigned by sdn-c";
\r
380 grouping vnf-resource-assignments {
\r
381 container vnf-resource-assignments {
\r
383 description "Do we need this?Orchestration status from AAI - to be set by SDNCWill not be used for vIPR.";
\r
386 container availability-zones {
\r
387 leaf-list availability-zone {
\r
388 description "Openstack availability zone name or UUID";
\r
393 description "From the TOSCA data. Indicates the largest availability zone count needed by any vf-module in the VNF.";
\r
397 container vnf-networks {
\r
399 key "network-role";
\r
400 uses vnf-network-data;
\r
405 grouping vnf-network-data {
\r
406 leaf network-role {
\r
407 description "A Network Role to which a VNF must connect";
\r
410 leaf network-name {
\r
411 description "Unique Neutron UUID of an instance of the network role ";
\r
415 description "Unique Neutron UUID of an instance of the network role ";
\r
419 description "Unique Neutron UUID of an instance of the network role ";
\r
422 leaf contrail-network-fqdn {
\r
423 description "contrail network policy object";
\r
426 container subnets-data {
\r
430 description "Should be ipv4 or ipv6";
\r
434 description "subnet UUID to be passed into the HEAT template";
\r
440 grouping vnf-level-oper-status {
\r
441 container vnf-level-oper-status {
\r
442 uses oper-status-data;
\r
445 grouping vf-module-operation-information {
\r
446 uses sdnc-request-header;
\r
447 uses request-information;
\r
448 uses service-information;
\r
449 uses vnf-information;
\r
450 uses vf-module-information;
\r
451 uses vf-module-request-input;
\r
453 grouping vf-module-information {
\r
454 container vf-module-information {
\r
455 leaf vf-module-id {
\r
458 leaf vf-module-type {
\r
461 uses onap-model-information;
\r
464 grouping vf-module-request-input {
\r
465 container vf-module-request-input {
\r
466 leaf request-version {
\r
467 description "keep this?";
\r
470 leaf vf-module-name {
\r
473 uses region-identifier;
\r
474 container vf-module-input-parameters {
\r
479 grouping vf-module-topology {
\r
480 container vf-module-topology {
\r
481 uses vf-module-topology-identifier;
\r
482 uses region-identifier;
\r
483 uses onap-model-information;
\r
484 uses vf-module-assignments;
\r
485 container vf-module-parameters {
\r
490 grouping vf-module-topology-identifier {
\r
491 container vf-module-topology-identifier {
\r
492 leaf vf-module-id {
\r
493 description "vf-module id";
\r
496 leaf vf-module-name {
\r
497 description "vf-module-name";
\r
500 leaf vf-module-type {
\r
501 description "In Pats model referred to as model-id";
\r
506 grouping vf-module-assignments {
\r
507 container vf-module-assignments {
\r
508 leaf vf-module-status {
\r
509 description "Do we need this?Orchestration status from AAI - to be set by SDNCNot being used for vIPR.";
\r
515 uses vm-topology-data;
\r
520 grouping vm-topology-data {
\r
525 leaf nfc-naming-code {
\r
526 description "used in vm naming(draft 29: changed from nfc-code)";
\r
530 description "from tosca data on vfc";
\r
536 container vm-names {
\r
537 leaf-list vm-name {
\r
538 description "ordered-by: user";
\r
543 container vm-networks {
\r
545 key "network-role";
\r
546 uses vm-network-data;
\r
550 grouping vm-network-data {
\r
551 leaf network-role {
\r
552 description "network (identified by role) that this VM connects to. Should also be included in the vnf-networks for the containing VNF";
\r
556 leaf network-role-tag {
\r
559 container network-information-items {
\r
560 list network-information-item {
\r
563 description "Use ipv4 or ipv6";
\r
567 description "Indicator to use DHCP on this network for this VM";
\r
574 description "The number of ip addresses to be assigned per vm for this network role";
\r
577 container network-ips {
\r
578 leaf-list network-ip {
\r
579 description "List of assigned ip addresses of type ip-version on a network. Is there a way to specify format to indicate ipv4 or ipv6 format?";
\r
586 container mac-addresses {
\r
587 leaf-list mac-address {
\r
588 description "List of network assignments for this vm-type";
\r
593 container floating-ips {
\r
594 leaf-list floating-ip-v4 {
\r
595 description "Floating ipv4 for VMs of a given type on this network";
\r
596 type inet:ip-address;
\r
599 leaf-list floating-ip-v6 {
\r
600 description "Floating ipv6 for VMs of a given type on this network";
\r
601 type inet:ipv6-address;
\r
605 container interface-route-prefixes {
\r
606 leaf-list interface-route-prefix {
\r
607 description "ordered-by: user";
\r
612 container sriov-parameters {
\r
613 container heat-vlan-filters {
\r
614 leaf-list heat-vlan-filter {
\r
619 container application-tags {
\r
635 grouping vf-module-level-oper-status {
\r
636 container vf-module-level-oper-status {
\r
637 uses oper-status-data;
\r
640 grouping allotted-resource-info {
\r
641 leaf allotted-resource-id {
\r
644 leaf allotted-resource-type {
\r
645 description "Not an enum, but expected values are contrail-route and security-zone.";
\r
648 leaf allotted-resource-pointer {
\r
649 description "Pointer to the allotted-resources topology";
\r
653 grouping contrail-route-operation-information {
\r
654 uses sdnc-request-header;
\r
655 uses request-information;
\r
656 uses service-information;
\r
657 uses allotted-resource-information;
\r
658 uses contrail-route-request-input;
\r
660 grouping contrail-route-request-input {
\r
661 container contrail-route-request-input {
\r
662 container source-network {
\r
665 container dest-network {
\r
668 container contrail-applied-service-info {
\r
669 leaf service-instance-id {
\r
670 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
673 leaf contrail-fqdn {
\r
674 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
678 container contrail-route-input-parameters {
\r
683 grouping network-info {
\r
687 leaf network-role {
\r
691 grouping contrail-route-topology {
\r
692 container contrail-route-topology {
\r
693 uses allotted-resource-identifiers;
\r
694 uses onap-model-information;
\r
695 uses contrail-route-assignments;
\r
696 container contrail-route-parameters {
\r
701 grouping contrail-route-assignments {
\r
702 container contrail-route-assignments {
\r
704 description "The Contrail fq-name of the network policy";
\r
708 description "The ID assigned by Contrail to the network-policy (one for one with the fq-name)";
\r
711 container source-network {
\r
714 container dest-network {
\r
717 container contrail-applied-service {
\r
718 leaf service-instance-id {
\r
719 description "The service-instance-id of the vnf from which the contrail applied service is coming";
\r
723 description "The vnf representing the contrail applied service";
\r
726 leaf contrail-fqdn {
\r
727 description "This is the fq-name of the Contrail service instance through which the route is passing.";
\r
732 description "Contrail-assigned vlan-tag to the vipr vm interface for this route.";
\r
737 grouping security-zone-operation-information {
\r
738 uses sdnc-request-header;
\r
739 uses request-information;
\r
740 uses service-information;
\r
741 uses allotted-resource-information;
\r
742 uses security-zone-request-input;
\r
744 grouping security-zone-request-input {
\r
745 container security-zone-request-input {
\r
749 leaf trusted-network-role {
\r
750 description "In the case of vIPR, this is the landing networks network-role; used in naming";
\r
753 leaf untrusted-network-role {
\r
754 description "In the case of vIPR, this is the tenant oam networks network-role; used in naming";
\r
757 container security-zone-input-parameters {
\r
762 grouping security-zone-topology {
\r
763 container security-zone-topology {
\r
764 uses allotted-resource-identifiers;
\r
765 uses onap-model-information;
\r
766 uses security-zone-assignments;
\r
767 container security-zone-parameters {
\r
772 grouping security-zone-assignments {
\r
773 container security-zone-assignments {
\r
774 leaf trusted-network-role {
\r
775 description "In the case of vIPR, this is the landing networks network-role; used in naming";
\r
778 leaf security-zone-name-trusted {
\r
781 leaf untrusted-network-role {
\r
782 description "In the case of vIPR, this is the tenant oam networks network-role; used in naming";
\r
785 leaf security-zone-name-untrusted {
\r
788 leaf security-zone-service-instance-id {
\r
789 description "Will be the same as the parent-service-instance-id";
\r
792 leaf security-zone-vnf-id {
\r
793 description "Selected by SDNC from the security-zone-service-instance-id";
\r
801 grouping tunnelxconn-operation-information {
\r
802 uses sdnc-request-header;
\r
803 uses request-information;
\r
804 uses service-information;
\r
805 uses allotted-resource-information;
\r
806 uses tunnelxconn-request-input;
\r
808 grouping tunnelxconn-request-input {
\r
810 container tunnelxconn-request-input {
\r
811 leaf brg-wan-mac-address {
\r
816 grouping tunnelxconn-topology {
\r
817 container tunnelxconn-topology {
\r
818 uses allotted-resource-identifiers;
\r
819 uses onap-model-information;
\r
820 uses tunnelxconn-assignments;
\r
821 container tunnelxconn-parameters {
\r
826 grouping tunnelxconn-assignments {
\r
827 container tunnelxconn-assignments {
\r
829 description "The Network Controller will assign a VNI value from the associated vGMUX VNI pool";
\r
832 leaf vgmux-bearer-ip {
\r
833 description "The Network Controller will look up the vgmux bearer ip from the vgmux vf module";
\r
834 type inet:ip-address;
\r
836 leaf vgmux-lan-ip {
\r
837 description "The Network Controller will look up the vgmux lan ip from the vgmux vg module";
\r
838 type inet:ip-address;
\r
841 description "The Network Controller will assign the VG IP address from local inventory";
\r
842 type inet:ip-address;
\r
846 grouping brg-operation-information {
\r
847 uses sdnc-request-header;
\r
848 uses request-information;
\r
849 uses service-information;
\r
850 uses allotted-resource-information;
\r
851 uses brg-request-input;
\r
853 grouping brg-request-input {
\r
854 container brg-request-input {
\r
855 leaf vgmux-bearer-ip {
\r
856 type inet:ip-address;
\r
861 leaf brg-wan-mac-address {
\r
866 grouping brg-topology {
\r
867 container brg-topology {
\r
868 uses allotted-resource-identifiers;
\r
869 uses onap-model-information;
\r
870 uses brg-assignments;
\r
871 container brg-parameters {
\r
876 grouping brg-assignments {
\r
877 container brg-assignments {
\r
879 type inet:ip-address;
\r
884 grouping connection-attachment-operation-information {
\r
885 uses sdnc-request-header;
\r
886 uses request-information;
\r
887 uses service-information;
\r
888 uses allotted-resource-information;
\r
889 uses connection-attachment-request-input;
\r
892 grouping connection-attachment-request-input {
\r
893 container connection-attachment-request-input {
\r
898 grouping connection-attachment-topology {
\r
899 container brg-topology {
\r
900 uses allotted-resource-identifiers;
\r
901 uses onap-model-information;
\r
902 uses connection-attachment-assignments;
\r
903 container connection-attachment-parameters {
\r
909 grouping connection-attachment-assignments {
\r
910 container connection-attachment-assignments {
\r
914 grouping allotted-resource-information {
\r
915 container allotted-resource-information {
\r
916 leaf allotted-resource-id {
\r
919 leaf allotted-resource-type {
\r
920 description "Not an enum, but expected values are contrail-route and security-zone.";
\r
923 leaf parent-service-instance-id {
\r
924 description "Service-instance-id of the parent service to which this allotted resource belongs.";
\r
927 uses onap-model-information;
\r
930 grouping allotted-resource-identifiers {
\r
931 container allotted-resource-identifiers {
\r
932 leaf allotted-resource-id {
\r
935 leaf allotted-resource-name {
\r
936 description "For a contrail-route, the network policy name.";
\r
939 leaf allotted-resource-type {
\r
940 description "(Added in draft 32)Expected to be contrail-route or security-zone.";
\r
943 leaf consuming-service-instance-id {
\r
944 description "The service-instance-id of the consuming service of this allotted resource";
\r
947 leaf parent-service-instance-id {
\r
948 description "Service-instance-id of the parent service to which this allotted resource belongs.";
\r
953 grouping allotted-resource-oper-status {
\r
954 container allotted-resource-oper-status {
\r
955 uses oper-status-data;
\r
958 grouping allotted-resource-status {
\r
959 container allotted-resource-status {
\r
960 leaf response-code {
\r
963 leaf response-message {
\r
966 leaf final-indicator {
\r
969 leaf request-status {
\r
971 enum "synccomplete";
\r
972 enum "asynccomplete";
\r
973 enum "notifycomplete";
\r
977 description "value would one of possible request-actions; match the list in service-data oper-status";
\r
984 description "this is the svc-action from the incoming request";
\r
994 leaf response-timestamp {
\r
999 grouping topology-response-common {
\r
1000 leaf svc-request-id {
\r
1001 description "the request id from the request message for which this is the responseKeep as M";
\r
1004 leaf response-code {
\r
1005 description "a success code or an defined error codeKeep as M";
\r
1008 leaf response-message {
\r
1009 description "message included for error code";
\r
1012 leaf ack-final-indicator {
\r
1013 description "Expected to be Y or N.";
\r
1017 grouping sdnc-request-header {
\r
1018 container sdnc-request-header {
\r
1019 leaf svc-request-id {
\r
1020 description "Uniquely generated by calling system (e.g. MSO or SDN-GP)";
\r
1024 description "Enumerated listThis is the rpcAction";
\r
1025 type enumeration {
\r
1030 enum "changeassign";
\r
1031 enum "changedelete";
\r
1033 enum "deactivate";
\r
1038 leaf svc-notification-url {
\r
1039 description "Contains URL for asynchronous response";
\r
1044 grouping request-information {
\r
1045 container request-information {
\r
1047 description "Request ID generated upstream of MSO";
\r
1050 leaf request-action {
\r
1051 description "still need to work Disconnect";
\r
1052 type enumeration {
\r
1053 enum "CreateNetworkInstance";
\r
1054 enum "ActivateNetworkInstance";
\r
1055 enum "CreateServiceInstance";
\r
1056 enum "DeleteServiceInstance";
\r
1057 enum "DeleteNetworkInstance";
\r
1058 enum "CreateVnfInstance";
\r
1059 enum "ActivateVnfInstance";
\r
1060 enum "DeleteVnfInstance";
\r
1061 enum "CreateVfModuleInstance";
\r
1062 enum "ActivateVfModuleInstance";
\r
1063 enum "DeleteVfModuleInstance";
\r
1064 enum "CreateContrailRouteInstance";
\r
1065 enum "DeleteContrailRouteInstance";
\r
1066 enum "CreateSecurityZoneInstance";
\r
1067 enum "DeleteSecurityZoneInstance";
\r
1068 enum "ActivateDCINetworkInstance";
\r
1069 enum "DeActivateDCINetworkInstance";
\r
1070 enum "CreateTunnelXConnInstance";
\r
1071 enum "DeleteTunnelXConnInstance";
\r
1072 enum "CreateBRGInstance";
\r
1073 enum "DeleteBRGInstance";
\r
1074 enum "CreateSOTNConnectivityInstance";
\r
1075 enum "ActivateSOTNConnectivityInstance";
\r
1076 enum "DeactivateSOTNConnectivityInstance";
\r
1077 enum "DeleteSOTNConnectivityInstance";
\r
1078 enum "CreateSOTNAttachmentInstance";
\r
1079 enum "ActivateSOTNAttachmentInstance";
\r
1080 enum "DeactivateSOTNAttachmentInstance";
\r
1081 enum "DeleteSOTNAttachmentInstance";
\r
1082 enum "CreateSiteInstance";
\r
1083 enum "ActivateSiteInstance";
\r
1084 enum "DeactivateSiteInstance";
\r
1085 enum "DeleteSiteInstance";
\r
1091 leaf notification-url {
\r
1094 leaf order-number {
\r
1097 leaf order-version {
\r
1102 grouping service-information {
\r
1103 container service-information {
\r
1105 description "This maps to the product-family-id in A&AI";
\r
1108 leaf subscription-service-type {
\r
1109 description "used to reference a&ai subscription-service-type. For example, we show as vIPR-ATM in example.";
\r
1112 uses onap-model-information;
\r
1113 leaf service-instance-id {
\r
1116 leaf global-customer-id {
\r
1117 description "need for put of data to AnAI (MSO provides)";
\r
1120 leaf subscriber-name {
\r
1121 description "Would not be expected for vIPR-ATM or mobility services.";
\r
1126 grouping onap-model-information {
\r
1127 container onap-model-information {
\r
1128 leaf model-invariant-uuid {
\r
1129 description "identifies the invariant uuid for this service or resource";
\r
1132 leaf model-customization-uuid {
\r
1133 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
1137 description "identifies the uuid for this service or resource, which is version specific";
\r
1140 leaf model-version {
\r
1148 grouping region-identifier {
\r
1152 leaf aic-cloud-region {
\r
1153 description "The AIC cloud region which maps to contrail versions";
\r
1157 description "Not expected to be used";
\r
1172 grouping instance-reference {
\r
1173 leaf instance-id {
\r
1176 leaf object-path {
\r
1177 description "restconf retrieval path to this particular objectE.g. restconf/config/GENERIC-RESOURCE-API:services/service/$service-instance-id/service-data/service-topology/";
\r
1181 grouping oper-status-data {
\r
1182 leaf order-status {
\r
1183 description "TBD - do we need Request failed statuses? RequestFailed | InProgressTimeout";
\r
1184 type enumeration {
\r
1186 enum "PendingAssignment";
\r
1187 enum "PendingCreate";
\r
1188 enum "PendingUpdate";
\r
1189 enum "PendingDelete";
\r
1194 leaf last-rpc-action {
\r
1195 type enumeration {
\r
1200 enum "deactivate";
\r
1204 leaf last-action {
\r
1205 description "should be list of possible request-actions";
\r
1206 type enumeration {
\r
1207 enum "CreateNetworkInstance";
\r
1208 enum "ActivateNetworkInstance";
\r
1209 enum "CreateServiceInstance";
\r
1210 enum "DeleteServiceInstance";
\r
1211 enum "DeleteNetworkInstance";
\r
1212 enum "CreateVnfInstance";
\r
1213 enum "ActivateVnfInstance";
\r
1214 enum "DeleteVnfInstance";
\r
1215 enum "CreateVfModuleInstance";
\r
1216 enum "ActivateVfModuleInstance";
\r
1217 enum "DeleteVfModuleInstance";
\r
1218 enum "CreateContrailRouteInstance";
\r
1219 enum "DeleteContrailRouteInstance";
\r
1220 enum "CreateSecurityZoneInstance";
\r
1221 enum "DeleteSecurityZoneInstance";
\r
1222 enum "ActivateDCINetworkInstance";
\r
1223 enum "DeActivateDCINetworkInstance";
\r
1224 enum "CreateTunnelXConnInstance";
\r
1225 enum "DeleteTunnelXConnInstance";
\r
1226 enum "CreateBRGInstance";
\r
1227 enum "DeleteBRGInstance";
\r
1228 enum "CreateSOTNConnectivityInstance";
\r
1229 enum "ActivateSOTNConnectivityInstance";
\r
1230 enum "DeactivateSOTNConnectivityInstance";
\r
1231 enum "DeleteSOTNConnectivityInstance";
\r
1232 enum "CreateSOTNAttachmentInstance";
\r
1233 enum "ActivateSOTNAttachmentInstance";
\r
1234 enum "DeactivateSOTNAttachmentInstance";
\r
1235 enum "DeleteSOTNAttachmentInstance";
\r
1236 enum "CreateSiteInstance";
\r
1237 enum "ActivateSiteInstance";
\r
1238 enum "DeactivateSiteInstance";
\r
1239 enum "DeleteSiteInstance";
\r
1242 leaf last-svc-request-id {
\r
1243 description "Not currently populated in service data.";
\r
1246 leaf last-order-status {
\r
1247 description "fieldused by generic-resource-api";
\r
1248 type enumeration {
\r
1250 enum "PendingAssignment";
\r
1251 enum "PendingCreate";
\r
1252 enum "PendingUpdate";
\r
1253 enum "PendingDelete";
\r
1258 leaf create-timestamp {
\r
1259 description "Not currently populated in service data.";
\r
1262 leaf modify-timestamp {
\r
1266 grouping service-response-information {
\r
1267 container service-response-information {
\r
1268 uses instance-reference;
\r
1271 grouping network-response-information {
\r
1272 container network-response-information {
\r
1273 uses instance-reference;
\r
1276 grouping vnf-response-information {
\r
1277 container vnf-response-information {
\r
1278 uses instance-reference;
\r
1281 grouping vf-module-response-information {
\r
1282 container vf-module-response-information {
\r
1283 uses instance-reference;
\r
1286 grouping contrail-route-response-information {
\r
1287 container contrail-route-response-information {
\r
1288 uses instance-reference;
\r
1291 grouping security-zone-response-information {
\r
1292 container security-zone-response-information {
\r
1293 uses instance-reference;
\r
1296 grouping tunnelxconn-response-information {
\r
1297 container tunnelxconn-response-information {
\r
1298 uses instance-reference;
\r
1301 grouping brg-response-information {
\r
1302 container brg-response-information {
\r
1303 uses instance-reference;
\r
1306 grouping connection-attachment-response-information {
\r
1307 container connection-attachment-response-information {
\r
1308 uses instance-reference;
\r
1311 grouping preload-model-information {
\r
1312 list vnf-preload-list {
\r
1313 key "vnf-name vnf-type";
\r
1315 description "vf-module-name or network name";
\r
1320 description "vf-module-type or network type";
\r
1324 uses preload-data;
\r
1327 grouping vnf-topology-response-body {
\r
1328 leaf svc-request-id {
\r
1331 leaf response-code {
\r
1334 leaf response-message {
\r
1337 leaf ack-final-indicator {
\r
1341 grouping preload-data {
\r
1342 container preload-data {
\r
1343 uses vnf-topology-information;
\r
1344 uses network-topology-information;
\r
1348 grouping vnf-topology-information {
\r
1349 container vnf-topology-information {
\r
1350 uses vnf-topology-identifier;
\r
1351 uses vnf-assignments;
\r
1352 uses vnf-parameters;
\r
1355 grouping vnf-topology-identifier {
\r
1356 container vnf-topology-identifier {
\r
1357 leaf service-type {
\r
1364 description "vf-module-name";
\r
1368 description "vf-module-type";
\r
1371 leaf generic-vnf-name {
\r
1374 leaf generic-vnf-type {
\r
1377 leaf generic-vnf-id {
\r
1382 grouping vnf-assignments {
\r
1383 container vnf-assignments {
\r
1385 description "Orchestration Status from AAI - to be set by SDNC";
\r
1388 list availability-zones {
\r
1389 key "availability-zone";
\r
1390 leaf availability-zone {
\r
1391 description "Openstack availability zone name or UUID";
\r
1395 list vnf-networks {
\r
1396 key "network-role";
\r
1398 uses sriov-vlan-filter-list;
\r
1403 grouping vm-topology {
\r
1419 list vm-networks {
\r
1420 key "network-role";
\r
1425 grouping vnf-network {
\r
1426 leaf network-role {
\r
1427 description "A Network Role to which a VNF must connect";
\r
1431 leaf network-name {
\r
1432 description "Unique Neutron UUID of an instance of the network role ";
\r
1436 description "Unique Neutron UUID of an instance of the network role ";
\r
1440 description "Unique Neutron UUID of an instance of the network role ";
\r
1444 description "ipv4 subnet UUID to be passed into the HEAT template";
\r
1447 leaf subnet-name {
\r
1448 description "ipv4 subnet-name that corresponds to the ipv4 subnet-id";
\r
1451 leaf contrail-network-fqdn {
\r
1452 description "contrail network policy object";
\r
1455 leaf ipv6-subnet-id {
\r
1456 description "ipv6 subnet UUID to be passed into the HEAT template";
\r
1459 leaf ipv6-subnet-name {
\r
1460 description "ipv6 subnet-name that corresponds to the ipv6 subnet-id";
\r
1464 grouping sriov-vlan-filter-list {
\r
1465 list sriov-vlan-filter-list {
\r
1466 key "sriov-vlan-filter";
\r
1467 leaf sriov-vlan-filter {
\r
1472 grouping vm-network {
\r
1473 leaf network-role {
\r
1474 description "network (identified by role) that this VM connects to. Should also be included in the vnf-networks for the containing VNF";
\r
1478 description "Indicator to use DHCP on this network for this VM";
\r
1479 type enumeration {
\r
1485 description "The number of ip addresses to be assigned per vm for this network role";
\r
1488 list network-ips {
\r
1491 description "List of assigned ipv4 addresses on a network";
\r
1492 type inet:ip-address;
\r
1495 list network-ips-v6 {
\r
1496 key "ip-address-ipv6";
\r
1497 leaf ip-address-ipv6 {
\r
1498 description "List of assigned ipv6 addresses on a network";
\r
1499 type inet:ipv6-address;
\r
1502 list network-macs {
\r
1503 key "mac-address";
\r
1504 leaf mac-address {
\r
1505 description "List of network assignments for this VM (one per network)";
\r
1509 leaf floating-ip {
\r
1510 description "Floating ipv4 for VMs of a given type on this network";
\r
1511 type inet:ip-address;
\r
1513 leaf floating-ip-v6 {
\r
1514 description "Floating ipv6 for VMs of a given type on this network";
\r
1515 type inet:ipv6-address;
\r
1517 list interface-route-prefixes {
\r
1518 key "interface-route-prefix-cidr";
\r
1519 leaf interface-route-prefix-cidr {
\r
1520 description "route prefixes (CIDRs) in ip/cidr format to be provided to MSO in vnf-topology as a list of static routes";
\r
1524 leaf interface-route-prefix {
\r
1525 description "route prefixes (CIDRs) to be provided to MSO in vnf-topology as a list of static routes";
\r
1526 type inet:ip-address;
\r
1530 grouping vnf-parameters {
\r
1531 list vnf-parameters {
\r
1532 key "vnf-parameter-name";
\r
1533 leaf vnf-parameter-name {
\r
1534 description "The name of an arbitrary instance-specific vnf-parameters";
\r
1537 leaf vnf-parameter-value {
\r
1538 description "The value of an arbitrary instance-specific vnf-parameters ";
\r
1543 grouping network-topology-information {
\r
1544 container network-topology-information {
\r
1545 uses network-topology-identifier;
\r
1547 uses vpn-bindings;
\r
1548 uses network-policy;
\r
1549 uses route-table-reference;
\r
1550 uses provider-network-information;
\r
1553 grouping network-topology-identifier {
\r
1554 container network-topology-identifier {
\r
1555 leaf service-type {
\r
1558 leaf network-name {
\r
1561 leaf network-role {
\r
1564 leaf network-type {
\r
1567 leaf network-technology {
\r
1572 grouping subnets {
\r
1574 key "start-address";
\r
1575 leaf start-address {
\r
1576 type inet:ip-address;
\r
1578 leaf gateway-address {
\r
1579 type inet:ip-address;
\r
1587 leaf dhcp-enabled {
\r
1588 type enumeration {
\r
1593 leaf dhcp-start-address {
\r
1596 leaf dhcp-end-address {
\r
1599 leaf subnet-name {
\r
1604 grouping vpn-bindings {
\r
1605 list vpn-bindings {
\r
1606 key "vpn-binding-id";
\r
1607 leaf vpn-binding-id {
\r
1610 leaf global-route-target {
\r
1615 grouping network-policy {
\r
1616 list network-policy {
\r
1617 key "network-policy-fqdn";
\r
1618 leaf network-policy-fqdn {
\r
1621 leaf network-policy-id {
\r
1626 grouping route-table-reference {
\r
1627 list route-table-reference {
\r
1628 key "route-table-reference-fqdn";
\r
1629 leaf route-table-reference-fqdn {
\r
1633 leaf route-table-reference-id {
\r
1638 grouping provider-network-information {
\r
1639 leaf physical-network-name {
\r
1642 leaf is-provider-network {
\r
1645 leaf is-shared-network {
\r
1648 leaf is-external-network {
\r
1652 grouping oper-status {
\r
1653 container oper-status {
\r
1654 leaf order-status {
\r
1655 type enumeration {
\r
1657 enum "PendingAssignment";
\r
1658 enum "PendingCreate";
\r
1659 enum "PendingUpdate";
\r
1660 enum "PendingDelete";
\r
1664 leaf last-action {
\r
1665 description "this is preload request actions";
\r
1666 type enumeration {
\r
1667 enum "VNFActivateRequest";
\r
1668 enum "ChangeVNFActivateRequest";
\r
1669 enum "VnfInstanceActivateRequest";
\r
1670 enum "ChangeVnfInstanceActivateRequest";
\r
1671 enum "VfModuleActivateRequest";
\r
1672 enum "ChangeVfModuleActivateRequest";
\r
1673 enum "DisconnectVNFRequest";
\r
1674 enum "DisconnectVnfInstanceRequest";
\r
1675 enum "DisconnectVfModuleRequest";
\r
1676 enum "PreloadVNFRequest";
\r
1677 enum "DeletePreloadVNFRequest";
\r
1678 enum "PreloadVnfInstanceRequest";
\r
1679 enum "DeletePreloadVnfInstanceRequest";
\r
1680 enum "PreloadVfModuleRequest";
\r
1681 enum "DeletePreloadVfModuleRequest";
\r
1684 leaf last-svc-request-id {
\r
1687 leaf last-order-status {
\r
1688 type enumeration {
\r
1690 enum "PendingAssignment";
\r
1691 enum "PendingCreate";
\r
1692 enum "PendingUpdate";
\r
1693 enum "PendingDelete";
\r
1697 leaf create-timestamp {
\r
1700 leaf modify-timestamp {
\r
1703 leaf maintenance-indicator {
\r
1704 type enumeration {
\r
1711 container services {
\r
1712 uses service-model-infrastructure;
\r
1714 container contrail-route-allotted-resources {
\r
1715 list contrail-route-allotted-resource {
\r
1716 key "allotted-resource-id";
\r
1717 leaf allotted-resource-id {
\r
1721 container allotted-resource-data {
\r
1722 container allotted-resource-operation-information {
\r
1723 uses contrail-route-operation-information;
\r
1725 uses contrail-route-topology;
\r
1726 uses allotted-resource-oper-status;
\r
1728 uses allotted-resource-status;
\r
1731 container security-zone-allotted-resources {
\r
1732 list security-zone-allotted-resource {
\r
1733 key "allotted-resource-id";
\r
1734 leaf allotted-resource-id {
\r
1738 container allotted-resource-data {
\r
1739 container allotted-resource-operation-information {
\r
1740 uses security-zone-operation-information;
\r
1742 uses security-zone-topology;
\r
1743 container security-zone-parameters {
\r
1746 uses allotted-resource-oper-status;
\r
1748 uses allotted-resource-status;
\r
1751 container tunnelxconn-allotted-resources {
\r
1752 list tunnelxconn-allotted-resource {
\r
1753 key "allotted-resource-id";
\r
1754 leaf allotted-resource-id {
\r
1758 container allotted-resource-data {
\r
1759 container allotted-resource-operation-information {
\r
1760 uses tunnelxconn-operation-information;
\r
1762 uses tunnelxconn-topology;
\r
1763 container tunnelxconn-parameters {
\r
1766 uses allotted-resource-oper-status;
\r
1768 uses allotted-resource-status;
\r
1771 container brg-allotted-resources {
\r
1772 list brg-allotted-resource {
\r
1773 key "allotted-resource-id";
\r
1774 leaf allotted-resource-id {
\r
1778 container allotted-resource-data {
\r
1779 container allotted-resource-operation-information {
\r
1780 uses brg-operation-information;
\r
1782 uses brg-topology;
\r
1783 container brg-parameters {
\r
1786 uses allotted-resource-oper-status;
\r
1788 uses allotted-resource-status;
\r
1791 container connection-attachment-allotted-resources {
\r
1792 list connection-attachment-allotted-resource {
\r
1793 key "allotted-resource-id";
\r
1794 leaf allotted-resource-id {
\r
1798 container allotted-resource-data {
\r
1799 container allotted-resource-operation-information {
\r
1800 uses connection-attachment-operation-information;
\r
1802 uses connection-attachment-topology;
\r
1803 container connection-attachment-parameters {
\r
1806 uses allotted-resource-oper-status;
\r
1808 uses allotted-resource-status;
\r
1811 rpc service-topology-operation {
\r
1813 uses service-operation-information;
\r
1816 uses topology-response-common;
\r
1817 uses service-response-information;
\r
1820 rpc network-topology-operation {
\r
1822 uses network-operation-information;
\r
1825 uses topology-response-common;
\r
1826 uses network-response-information;
\r
1827 uses service-response-information;
\r
1830 rpc vnf-topology-operation {
\r
1832 uses vnf-operation-information;
\r
1835 uses topology-response-common;
\r
1836 uses vnf-response-information;
\r
1837 uses service-response-information;
\r
1840 rpc vf-module-topology-operation {
\r
1842 uses vf-module-operation-information;
\r
1845 uses topology-response-common;
\r
1846 uses vf-module-response-information;
\r
1847 uses vnf-response-information;
\r
1848 uses service-response-information;
\r
1851 rpc contrail-route-topology-operation {
\r
1853 uses contrail-route-operation-information;
\r
1856 uses topology-response-common;
\r
1857 uses contrail-route-response-information;
\r
1858 uses service-response-information;
\r
1861 rpc security-zone-topology-operation {
\r
1863 uses security-zone-operation-information;
\r
1866 uses topology-response-common;
\r
1867 uses security-zone-response-information;
\r
1868 uses service-response-information;
\r
1871 rpc tunnelxconn-topology-operation {
\r
1873 uses tunnelxconn-operation-information;
\r
1876 uses topology-response-common;
\r
1877 uses tunnelxconn-response-information;
\r
1878 uses service-response-information;
\r
1881 rpc brg-topology-operation {
\r
1883 uses brg-operation-information;
\r
1886 uses topology-response-common;
\r
1887 uses brg-response-information;
\r
1888 uses service-response-information;
\r
1891 container preload-vnfs {
\r
1892 uses preload-model-information;
\r
1894 rpc preload-vnf-topology-operation {
\r
1896 uses sdnc-request-header;
\r
1897 uses request-information;
\r
1898 uses vnf-topology-information;
\r
1901 uses vnf-topology-response-body;
\r
1904 rpc preload-network-topology-operation {
\r
1906 uses sdnc-request-header;
\r
1907 uses request-information;
\r
1908 uses network-topology-information;
\r
1911 uses vnf-topology-response-body;
\r
1915 rpc connection-attachment-topology-operation {
\r
1917 uses connection-attachment-operation-information;
\r
1920 uses topology-response-common;
\r
1921 uses connection-attachment-response-information;
\r
1922 uses service-response-information;
\r
1926 } ////closes the module
\r