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
809 leaf brg-wan-mac-address {
\r
813 grouping tunnelxconn-topology {
\r
814 container tunnelxconn-topology {
\r
815 uses allotted-resource-identifiers;
\r
816 uses onap-model-information;
\r
817 uses tunnelxconn-assignments;
\r
818 container tunnelxconn-parameters {
\r
823 grouping tunnelxconn-assignments {
\r
825 description "The Network Controller will assign a VNI value from the associated vGMUX VNI pool";
\r
828 leaf vgmux-bearer-ip {
\r
829 description "The Network Controller will look up the vgmux bearer ip from the vgmux vf module";
\r
830 type inet:ip-address;
\r
832 leaf vgmux-lan-up {
\r
833 description "The Network Controller will look up the vgmux lan ip from the vgmux vg module";
\r
834 type inet:ip-address;
\r
837 grouping brg-operation-information {
\r
838 uses sdnc-request-header;
\r
839 uses request-information;
\r
840 uses service-information;
\r
841 uses allotted-resource-information;
\r
842 uses brg-request-input;
\r
844 grouping brg-request-input {
\r
845 leaf vgmux-bearer-ip {
\r
846 type inet:ip-address;
\r
851 leaf brg-wan-ip-address {
\r
852 type inet:ip-address;
\r
855 grouping brg-topology {
\r
856 container brg-topology {
\r
857 uses allotted-resource-identifiers;
\r
858 uses onap-model-information;
\r
859 uses brg-assignments;
\r
860 container brg-parameters {
\r
865 grouping brg-assignments {
\r
867 type inet:ip-address;
\r
870 grouping allotted-resource-information {
\r
871 container allotted-resource-information {
\r
872 leaf allotted-resource-id {
\r
875 leaf allotted-resource-type {
\r
876 description "Not an enum, but expected values are contrail-route and security-zone.";
\r
879 leaf parent-service-instance-id {
\r
880 description "Service-instance-id of the parent service to which this allotted resource belongs.";
\r
883 uses onap-model-information;
\r
886 grouping allotted-resource-identifiers {
\r
887 container allotted-resource-identifiers {
\r
888 leaf allotted-resource-id {
\r
891 leaf allotted-resource-name {
\r
892 description "For a contrail-route, the network policy name.";
\r
895 leaf allotted-resource-type {
\r
896 description "(Added in draft 32)Expected to be contrail-route or security-zone.";
\r
899 leaf consuming-service-instance-id {
\r
900 description "The service-instance-id of the consuming service of this allotted resource";
\r
903 leaf parent-service-instance-id {
\r
904 description "Service-instance-id of the parent service to which this allotted resource belongs.";
\r
909 grouping allotted-resource-oper-status {
\r
910 container allotted-resource-oper-status {
\r
911 uses oper-status-data;
\r
914 grouping allotted-resource-status {
\r
915 container allotted-resource-status {
\r
916 leaf response-code {
\r
919 leaf response-message {
\r
922 leaf final-indicator {
\r
925 leaf request-status {
\r
927 enum "synccomplete";
\r
928 enum "asynccomplete";
\r
929 enum "notifycomplete";
\r
933 description "value would one of possible request-actions; match the list in service-data oper-status";
\r
940 description "this is the svc-action from the incoming request";
\r
950 leaf response-timestamp {
\r
955 grouping topology-response-common {
\r
956 leaf svc-request-id {
\r
957 description "the request id from the request message for which this is the responseKeep as M";
\r
960 leaf response-code {
\r
961 description "a success code or an defined error codeKeep as M";
\r
964 leaf response-message {
\r
965 description "message included for error code";
\r
968 leaf ack-final-indicator {
\r
969 description "Expected to be Y or N.";
\r
973 grouping sdnc-request-header {
\r
974 container sdnc-request-header {
\r
975 leaf svc-request-id {
\r
976 description "Uniquely generated by calling system (e.g. MSO or SDN-GP)";
\r
980 description "Enumerated listThis is the rpcAction";
\r
986 enum "changeassign";
\r
987 enum "changedelete";
\r
994 leaf svc-notification-url {
\r
995 description "Contains URL for asynchronous response";
\r
1000 grouping request-information {
\r
1001 container request-information {
\r
1003 description "Request ID generated upstream of MSO";
\r
1006 leaf request-action {
\r
1007 description "still need to work Disconnect";
\r
1008 type enumeration {
\r
1009 enum "CreateNetworkInstance";
\r
1010 enum "ActivateNetworkInstance";
\r
1011 enum "CreateServiceInstance";
\r
1012 enum "DeleteServiceInstance";
\r
1013 enum "DeleteNetworkInstance";
\r
1014 enum "CreateVnfInstance";
\r
1015 enum "ActivateVnfInstance";
\r
1016 enum "DeleteVnfInstance";
\r
1017 enum "CreateVfModuleInstance";
\r
1018 enum "ActivateVfModuleInstance";
\r
1019 enum "DeleteVfModuleInstance";
\r
1020 enum "CreateContrailRouteInstance";
\r
1021 enum "DeleteContrailRouteInstance";
\r
1022 enum "CreateSecurityZoneInstance";
\r
1023 enum "DeleteSecurityZoneInstance";
\r
1029 leaf notification-url {
\r
1032 leaf order-number {
\r
1035 leaf order-version {
\r
1040 grouping service-information {
\r
1041 container service-information {
\r
1043 description "This maps to the product-family-id in A&AI";
\r
1046 leaf subscription-service-type {
\r
1047 description "used to reference a&ai subscription-service-type. For example, we show as vIPR-ATM in example.";
\r
1050 uses onap-model-information;
\r
1051 leaf service-instance-id {
\r
1054 leaf global-customer-id {
\r
1055 description "need for put of data to AnAI (MSO provides)";
\r
1058 leaf subscriber-name {
\r
1059 description "Would not be expected for vIPR-ATM or mobility services.";
\r
1064 grouping onap-model-information {
\r
1065 container onap-model-information {
\r
1066 leaf model-invariant-uuid {
\r
1067 description "identifies the invariant uuid for this service or resource";
\r
1070 leaf model-customization-uuid {
\r
1071 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
1075 description "identifies the uuid for this service or resource, which is version specific";
\r
1078 leaf model-version {
\r
1086 grouping region-identifier {
\r
1090 leaf aic-cloud-region {
\r
1091 description "The AIC cloud region which maps to contrail versions";
\r
1095 description "Not expected to be used";
\r
1110 grouping instance-reference {
\r
1111 leaf instance-id {
\r
1114 leaf object-path {
\r
1115 description "restconf retrieval path to this particular objectE.g. restconf/config/GENERIC-RESOURCE-API:services/service/$service-instance-id/service-data/service-topology/";
\r
1119 grouping oper-status-data {
\r
1120 leaf order-status {
\r
1121 description "TBD - do we need Request failed statuses? RequestFailed | InProgressTimeout";
\r
1122 type enumeration {
\r
1124 enum "PendingAssignment";
\r
1125 enum "PendingCreate";
\r
1126 enum "PendingUpdate";
\r
1127 enum "PendingDelete";
\r
1132 leaf last-rpc-action {
\r
1133 type enumeration {
\r
1138 enum "deactivate";
\r
1142 leaf last-action {
\r
1143 description "should be list of possible request-actions";
\r
1144 type enumeration {
\r
1145 enum "CreateNetworkInstance";
\r
1146 enum "ActivateNetworkInstance";
\r
1147 enum "CreateServiceInstance";
\r
1148 enum "DeleteServiceInstance";
\r
1149 enum "DeleteNetworkInstance";
\r
1150 enum "CreateVnfInstance";
\r
1151 enum "ActivateVnfInstance";
\r
1152 enum "DeleteVnfInstance";
\r
1153 enum "CreateVfModuleInstance";
\r
1154 enum "ActivateVfModuleInstance";
\r
1155 enum "DeleteVfModuleInstance";
\r
1156 enum "CreateContrailRouteInstance";
\r
1157 enum "DeleteContrailRouteInstance";
\r
1158 enum "CreateSecurityZoneInstance";
\r
1159 enum "DeleteSecurityZoneInstance";
\r
1162 leaf last-svc-request-id {
\r
1163 description "Not currently populated in service data.";
\r
1166 leaf last-order-status {
\r
1167 description "fieldused by generic-resource-api";
\r
1168 type enumeration {
\r
1170 enum "PendingAssignment";
\r
1171 enum "PendingCreate";
\r
1172 enum "PendingUpdate";
\r
1173 enum "PendingDelete";
\r
1178 leaf create-timestamp {
\r
1179 description "Not currently populated in service data.";
\r
1182 leaf modify-timestamp {
\r
1186 grouping service-response-information {
\r
1187 container service-response-information {
\r
1188 uses instance-reference;
\r
1191 grouping network-response-information {
\r
1192 container network-response-information {
\r
1193 uses instance-reference;
\r
1196 grouping vnf-response-information {
\r
1197 container vnf-response-information {
\r
1198 uses instance-reference;
\r
1201 grouping vf-module-response-information {
\r
1202 container vf-module-response-information {
\r
1203 uses instance-reference;
\r
1206 grouping contrail-route-response-information {
\r
1207 container contrail-route-response-information {
\r
1208 uses instance-reference;
\r
1211 grouping security-zone-response-information {
\r
1212 container security-zone-response-information {
\r
1213 uses instance-reference;
\r
1216 grouping tunnelxconn-response-information {
\r
1217 container tunnelxconn-response-information {
\r
1218 uses instance-reference;
\r
1221 grouping brg-response-information {
\r
1222 container brg-response-information {
\r
1223 uses instance-reference;
\r
1226 grouping preload-model-information {
\r
1227 list vnf-preload-list {
\r
1228 key "vnf-name vnf-type";
\r
1230 description "vf-module-name or network name";
\r
1235 description "vf-module-type or network type";
\r
1239 uses preload-data;
\r
1242 grouping vnf-topology-response-body {
\r
1243 leaf svc-request-id {
\r
1246 leaf response-code {
\r
1249 leaf response-message {
\r
1252 leaf ack-final-indicator {
\r
1256 grouping preload-data {
\r
1257 container preload-data {
\r
1258 uses vnf-topology-information;
\r
1259 uses network-topology-information;
\r
1263 grouping vnf-topology-information {
\r
1264 container vnf-topology-information {
\r
1265 uses vnf-topology-identifier;
\r
1266 uses vnf-assignments;
\r
1267 uses vnf-parameters;
\r
1270 grouping vnf-topology-identifier {
\r
1271 container vnf-topology-identifier {
\r
1272 leaf service-type {
\r
1279 description "vf-module-name";
\r
1283 description "vf-module-type";
\r
1286 leaf generic-vnf-name {
\r
1289 leaf generic-vnf-type {
\r
1292 leaf generic-vnf-id {
\r
1297 grouping vnf-assignments {
\r
1298 container vnf-assignments {
\r
1300 description "Orchestration Status from AAI - to be set by SDNC";
\r
1303 list availability-zones {
\r
1304 key "availability-zone";
\r
1305 leaf availability-zone {
\r
1306 description "Openstack availability zone name or UUID";
\r
1310 list vnf-networks {
\r
1311 key "network-role";
\r
1313 uses sriov-vlan-filter-list;
\r
1318 grouping vm-topology {
\r
1334 list vm-networks {
\r
1335 key "network-role";
\r
1340 grouping vnf-network {
\r
1341 leaf network-role {
\r
1342 description "A Network Role to which a VNF must connect";
\r
1346 leaf network-name {
\r
1347 description "Unique Neutron UUID of an instance of the network role ";
\r
1351 description "Unique Neutron UUID of an instance of the network role ";
\r
1355 description "Unique Neutron UUID of an instance of the network role ";
\r
1359 description "ipv4 subnet UUID to be passed into the HEAT template";
\r
1362 leaf subnet-name {
\r
1363 description "ipv4 subnet-name that corresponds to the ipv4 subnet-id";
\r
1366 leaf contrail-network-fqdn {
\r
1367 description "contrail network policy object";
\r
1370 leaf ipv6-subnet-id {
\r
1371 description "ipv6 subnet UUID to be passed into the HEAT template";
\r
1374 leaf ipv6-subnet-name {
\r
1375 description "ipv6 subnet-name that corresponds to the ipv6 subnet-id";
\r
1379 grouping sriov-vlan-filter-list {
\r
1380 list sriov-vlan-filter-list {
\r
1381 key "sriov-vlan-filter";
\r
1382 leaf sriov-vlan-filter {
\r
1387 grouping vm-network {
\r
1388 leaf network-role {
\r
1389 description "network (identified by role) that this VM connects to. Should also be included in the vnf-networks for the containing VNF";
\r
1393 description "Indicator to use DHCP on this network for this VM";
\r
1394 type enumeration {
\r
1400 description "The number of ip addresses to be assigned per vm for this network role";
\r
1403 list network-ips {
\r
1406 description "List of assigned ipv4 addresses on a network";
\r
1407 type inet:ip-address;
\r
1410 list network-ips-v6 {
\r
1411 key "ip-address-ipv6";
\r
1412 leaf ip-address-ipv6 {
\r
1413 description "List of assigned ipv6 addresses on a network";
\r
1414 type inet:ipv6-address;
\r
1417 list network-macs {
\r
1418 key "mac-address";
\r
1419 leaf mac-address {
\r
1420 description "List of network assignments for this VM (one per network)";
\r
1424 leaf floating-ip {
\r
1425 description "Floating ipv4 for VMs of a given type on this network";
\r
1426 type inet:ip-address;
\r
1428 leaf floating-ip-v6 {
\r
1429 description "Floating ipv6 for VMs of a given type on this network";
\r
1430 type inet:ipv6-address;
\r
1432 list interface-route-prefixes {
\r
1433 key "interface-route-prefix-cidr";
\r
1434 leaf interface-route-prefix-cidr {
\r
1435 description "route prefixes (CIDRs) in ip/cidr format to be provided to MSO in vnf-topology as a list of static routes";
\r
1439 leaf interface-route-prefix {
\r
1440 description "route prefixes (CIDRs) to be provided to MSO in vnf-topology as a list of static routes";
\r
1441 type inet:ip-address;
\r
1445 grouping vnf-parameters {
\r
1446 list vnf-parameters {
\r
1447 key "vnf-parameter-name";
\r
1448 leaf vnf-parameter-name {
\r
1449 description "The name of an arbitrary instance-specific vnf-parameters";
\r
1452 leaf vnf-parameter-value {
\r
1453 description "The value of an arbitrary instance-specific vnf-parameters ";
\r
1458 grouping network-topology-information {
\r
1459 container network-topology-information {
\r
1460 uses network-topology-identifier;
\r
1462 uses vpn-bindings;
\r
1463 uses network-policy;
\r
1464 uses route-table-reference;
\r
1465 uses provider-network-information;
\r
1468 grouping network-topology-identifier {
\r
1469 container network-topology-identifier {
\r
1470 leaf service-type {
\r
1473 leaf network-name {
\r
1476 leaf network-role {
\r
1479 leaf network-type {
\r
1482 leaf network-technology {
\r
1487 grouping subnets {
\r
1489 key "start-address";
\r
1490 leaf start-address {
\r
1491 type inet:ip-address;
\r
1493 leaf gateway-address {
\r
1494 type inet:ip-address;
\r
1502 leaf dhcp-enabled {
\r
1503 type enumeration {
\r
1508 leaf dhcp-start-address {
\r
1511 leaf dhcp-end-address {
\r
1514 leaf subnet-name {
\r
1519 grouping vpn-bindings {
\r
1520 list vpn-bindings {
\r
1521 key "vpn-binding-id";
\r
1522 leaf vpn-binding-id {
\r
1525 leaf global-route-target {
\r
1530 grouping network-policy {
\r
1531 list network-policy {
\r
1532 key "network-policy-fqdn";
\r
1533 leaf network-policy-fqdn {
\r
1536 leaf network-policy-id {
\r
1541 grouping route-table-reference {
\r
1542 list route-table-reference {
\r
1543 key "route-table-reference-fqdn";
\r
1544 leaf route-table-reference-fqdn {
\r
1548 leaf route-table-reference-id {
\r
1553 grouping provider-network-information {
\r
1554 leaf physical-network-name {
\r
1557 leaf is-provider-network {
\r
1560 leaf is-shared-network {
\r
1563 leaf is-external-network {
\r
1567 grouping oper-status {
\r
1568 container oper-status {
\r
1569 leaf order-status {
\r
1570 type enumeration {
\r
1572 enum "PendingAssignment";
\r
1573 enum "PendingCreate";
\r
1574 enum "PendingUpdate";
\r
1575 enum "PendingDelete";
\r
1579 leaf last-action {
\r
1580 description "this is preload request actions";
\r
1581 type enumeration {
\r
1582 enum "VNFActivateRequest";
\r
1583 enum "ChangeVNFActivateRequest";
\r
1584 enum "VnfInstanceActivateRequest";
\r
1585 enum "ChangeVnfInstanceActivateRequest";
\r
1586 enum "VfModuleActivateRequest";
\r
1587 enum "ChangeVfModuleActivateRequest";
\r
1588 enum "DisconnectVNFRequest";
\r
1589 enum "DisconnectVnfInstanceRequest";
\r
1590 enum "DisconnectVfModuleRequest";
\r
1591 enum "PreloadVNFRequest";
\r
1592 enum "DeletePreloadVNFRequest";
\r
1593 enum "PreloadVnfInstanceRequest";
\r
1594 enum "DeletePreloadVnfInstanceRequest";
\r
1595 enum "PreloadVfModuleRequest";
\r
1596 enum "DeletePreloadVfModuleRequest";
\r
1599 leaf last-svc-request-id {
\r
1602 leaf last-order-status {
\r
1603 type enumeration {
\r
1605 enum "PendingAssignment";
\r
1606 enum "PendingCreate";
\r
1607 enum "PendingUpdate";
\r
1608 enum "PendingDelete";
\r
1612 leaf create-timestamp {
\r
1615 leaf modify-timestamp {
\r
1618 leaf maintenance-indicator {
\r
1619 type enumeration {
\r
1626 container services {
\r
1627 uses service-model-infrastructure;
\r
1629 container contrail-route-allotted-resources {
\r
1630 list contrail-route-allotted-resource {
\r
1631 key "allotted-resource-id";
\r
1632 leaf allotted-resource-id {
\r
1636 container allotted-resource-data {
\r
1637 container allotted-resource-operation-information {
\r
1638 uses contrail-route-operation-information;
\r
1640 uses contrail-route-topology;
\r
1641 uses allotted-resource-oper-status;
\r
1643 uses allotted-resource-status;
\r
1646 container security-zone-allotted-resources {
\r
1647 list security-zone-allotted-resource {
\r
1648 key "allotted-resource-id";
\r
1649 leaf allotted-resource-id {
\r
1653 container allotted-resource-data {
\r
1654 container allotted-resource-operation-information {
\r
1655 uses security-zone-operation-information;
\r
1657 uses security-zone-topology;
\r
1658 container security-zone-parameters {
\r
1661 uses allotted-resource-oper-status;
\r
1663 uses allotted-resource-status;
\r
1666 container tunnelxconn-allotted-resources {
\r
1667 list tunnelxconn-allotted-resource {
\r
1668 key "allotted-resource-id";
\r
1669 leaf allotted-resource-id {
\r
1673 container allotted-resource-data {
\r
1674 container allotted-resource-operation-information {
\r
1675 uses tunnelxconn-operation-information;
\r
1677 uses tunnelxconn-topology;
\r
1678 container tunnelxconn-parameters {
\r
1681 uses allotted-resource-oper-status;
\r
1683 uses allotted-resource-status;
\r
1686 container brg-allotted-respources {
\r
1687 list brg-allotted-resource {
\r
1688 key "allotted-resource-id";
\r
1689 leaf allotted-resource-id {
\r
1693 container allotted-resource-data {
\r
1694 container allotted-resource-operation-information {
\r
1695 uses brg-operation-information;
\r
1697 uses brg-topology;
\r
1698 container brg-parameters {
\r
1701 uses allotted-resource-oper-status;
\r
1703 uses allotted-resource-status;
\r
1706 rpc service-topology-operation {
\r
1708 uses service-operation-information;
\r
1711 uses topology-response-common;
\r
1712 uses service-response-information;
\r
1715 rpc network-topology-operation {
\r
1717 uses network-operation-information;
\r
1720 uses topology-response-common;
\r
1721 uses network-response-information;
\r
1722 uses service-response-information;
\r
1725 rpc vnf-topology-operation {
\r
1727 uses vnf-operation-information;
\r
1730 uses topology-response-common;
\r
1731 uses vnf-response-information;
\r
1732 uses service-response-information;
\r
1735 rpc vf-module-topology-operation {
\r
1737 uses vf-module-operation-information;
\r
1740 uses topology-response-common;
\r
1741 uses vf-module-response-information;
\r
1742 uses vnf-response-information;
\r
1743 uses service-response-information;
\r
1746 rpc contrail-route-topology-operation {
\r
1748 uses contrail-route-operation-information;
\r
1751 uses topology-response-common;
\r
1752 uses contrail-route-response-information;
\r
1753 uses service-response-information;
\r
1756 rpc security-zone-topology-operation {
\r
1758 uses security-zone-operation-information;
\r
1761 uses topology-response-common;
\r
1762 uses security-zone-response-information;
\r
1763 uses service-response-information;
\r
1766 rpc tunnelxconn-topology-operation {
\r
1768 uses tunnelxconn-operation-information;
\r
1771 uses topology-response-common;
\r
1772 uses tunnelxconn-response-information;
\r
1773 uses service-response-information;
\r
1776 rpc brg-topology-operation {
\r
1778 uses brg-operation-information;
\r
1781 uses topology-response-common;
\r
1782 uses brg-response-information;
\r
1783 uses service-response-information;
\r
1786 container preload-vnfs {
\r
1787 uses preload-model-information;
\r
1789 rpc preload-vnf-topology-operation {
\r
1791 uses sdnc-request-header;
\r
1792 uses request-information;
\r
1793 uses vnf-topology-information;
\r
1796 uses vnf-topology-response-body;
\r
1799 rpc preload-network-topology-operation {
\r
1801 uses sdnc-request-header;
\r
1802 uses request-information;
\r
1803 uses network-topology-information;
\r
1806 uses vnf-topology-response-body;
\r
1810 } ////closes the module
\r