Fix GENERIC-RESOURCE-API yang validation issues
[sdnc/northbound.git] / generic-resource-api / model / src / main / yang / GENERIC-RESOURCE-API.yang
1 module GENERIC-RESOURCE-API {\r
2 \r
3    namespace "org:onap:sdnc:northbound:generic-resource";\r
4 \r
5    prefix generic-resource-api;\r
6 \r
7    import ietf-inet-types { prefix "inet"; revision-date "2010-09-24"; }\r
8 \r
9    import ietf-yang-types { prefix yang; }\r
10 \r
11    revision "2017-08-24" {\r
12      description\r
13         "ONAP Amsterdam version";\r
14    }\r
15 \r
16    grouping service-model-infrastructure {\r
17       list service {\r
18          key "service-instance-id";\r
19          leaf service-instance-id {\r
20             description "Keep as M";\r
21             type string;\r
22             mandatory true;\r
23          }\r
24          uses service-data;\r
25          uses service-status;\r
26       }\r
27    }\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
34             list network {\r
35                key "network-id";\r
36                leaf network-id {\r
37                   type string;\r
38                   mandatory true;\r
39                }\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
46                         type string;\r
47                         ordered-by user;\r
48                      }\r
49                   }\r
50                   uses network-level-oper-status;\r
51                }\r
52             }\r
53          }\r
54          container vnfs {\r
55             list vnf {\r
56                key "vnf-id";\r
57                leaf vnf-id {\r
58                   type string;\r
59                   mandatory true;\r
60                }\r
61                container vnf-data {\r
62                   uses vnf-operation-information;\r
63                   uses vnf-topology;\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
67                         type string;\r
68                         ordered-by user;\r
69                      }\r
70                   }\r
71                   uses vnf-level-oper-status;\r
72                   container vf-modules {\r
73                      list vf-module {\r
74                         key "vf-module-id";\r
75                         leaf vf-module-id {\r
76                            type string;\r
77                            mandatory true;\r
78                         }\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
83                         }\r
84                      }\r
85                   }\r
86                }\r
87             }\r
88          }\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
93             }\r
94          }\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
99             }\r
100          }\r
101       }\r
102    }\r
103    grouping service-status {\r
104       container service-status {\r
105          leaf response-code {\r
106             type string;\r
107          }\r
108          leaf response-message {\r
109             type string;\r
110          }\r
111          leaf final-indicator {\r
112             type string;\r
113          }\r
114          leaf request-status {\r
115             type enumeration {\r
116                enum "synccomplete";\r
117                enum "asynccomplete";\r
118                enum "notifycomplete";\r
119             }\r
120          }\r
121          leaf action {\r
122             description "value would one of possible request-actions; match the list in service-data oper-status";\r
123             type string;\r
124          }\r
125          leaf rpc-name {\r
126             type string;\r
127          }\r
128          leaf rpc-action {\r
129             description "this is the svc-action from the incoming request";\r
130             type enumeration {\r
131                enum "assign";\r
132                enum "activate";\r
133                enum "configure";\r
134                enum "delete";\r
135                enum "unassign";\r
136                enum "deactivate";\r
137             }\r
138          }\r
139          leaf response-timestamp {\r
140             type string;\r
141          }\r
142       }\r
143    }\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
149    }\r
150    grouping service-request-input {\r
151       container service-request-input {\r
152          leaf service-instance-name {\r
153             type string;\r
154          }\r
155          container service-input-parameters {\r
156             uses param;\r
157          }\r
158       }\r
159    }\r
160    grouping service-topology {\r
161       container service-topology {\r
162          uses service-topology-identifier;\r
163          uses ecomp-model-information;\r
164          uses service-assignments;\r
165          uses service-parameters;\r
166       }\r
167    }\r
168    grouping service-topology-identifier {\r
169       container service-topology-identifier {\r
170          leaf service-instance-id {\r
171             description "repeated";\r
172             type string;\r
173          }\r
174          leaf service-type {\r
175             description "tag labeled subscription-service-type in the service-information input";\r
176             type string;\r
177          }\r
178          leaf service-id {\r
179             description "from MSO input on STO assign";\r
180             type string;\r
181          }\r
182          leaf service-instance-name {\r
183             description "optionally comes from service-request-input container or is assigned by sdn-c";\r
184             type string;\r
185          }\r
186          leaf global-customer-id {\r
187             type string;\r
188          }\r
189       }\r
190    }\r
191    grouping service-assignments {\r
192       container service-assignments {\r
193       }\r
194    }\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
200                type string;\r
201             }\r
202             leaf service-parameter-value {\r
203                type string;\r
204             }\r
205          }\r
206       }\r
207    }\r
208    grouping service-level-oper-status {\r
209       container service-level-oper-status {\r
210          uses oper-status-data;\r
211       }\r
212    }\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
219    }\r
220    grouping network-information {\r
221       container network-information {\r
222          leaf network-id {\r
223             type string;\r
224          }\r
225          leaf network-type {\r
226             type string;\r
227          }\r
228          uses ecomp-model-information;\r
229       }\r
230    }\r
231    grouping network-request-input {\r
232       container network-request-input {\r
233          leaf network-name {\r
234             type string;\r
235          }\r
236          uses region-identifier;\r
237          container network-input-parameters {\r
238             uses param;\r
239          }\r
240       }\r
241    }\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 ecomp-model-information;\r
247          uses network-assignments;\r
248          uses network-parameters;\r
249       }\r
250    }\r
251    grouping network-topology-identifier-structure {\r
252       container network-topology-identifier-structure {\r
253          leaf network-id {\r
254             type string;\r
255          }\r
256          leaf network-name {\r
257             type string;\r
258          }\r
259          leaf network-role {\r
260             type string;\r
261          }\r
262          leaf network-type {\r
263             type string;\r
264          }\r
265          leaf network-technology {\r
266             description "should we keep this?";\r
267             type string;\r
268          }\r
269          leaf eipam-v4-address-plan {\r
270             description "??";\r
271             type string;\r
272          }\r
273          leaf eipam-v6-address-plan {\r
274             type string;\r
275          }\r
276       }\r
277    }\r
278    grouping network-assignments {\r
279       container network-assignments {\r
280       }\r
281    }\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
287                type string;\r
288             }\r
289             leaf network-parameter-value {\r
290                type string;\r
291             }\r
292          }\r
293       }\r
294    }\r
295    grouping network-level-oper-status {\r
296       container network-level-oper-status {\r
297          uses oper-status-data;\r
298       }\r
299    }\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
306    }\r
307    grouping vnf-information {\r
308       container vnf-information {\r
309          leaf vnf-id {\r
310             type string;\r
311          }\r
312          leaf vnf-type {\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
314             type string;\r
315          }\r
316          uses ecomp-model-information;\r
317       }\r
318    }\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
323             type string;\r
324          }\r
325          leaf vnf-name {\r
326             description "in Pats vnf submodule, contained within vnf-instance-topology-identifier (along with vnf-model-id and vnf-instance-id)";\r
327             type string;\r
328          }\r
329          uses region-identifier;\r
330          container vnf-networks {\r
331             list vnf-network {\r
332                key "network-role";\r
333                uses vnf-network-data;\r
334             }\r
335          }\r
336          container vnf-input-parameters {\r
337             uses param;\r
338          }\r
339       }\r
340    }\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 ecomp-model-information;\r
346          uses vnf-resource-assignments;\r
347          container vnf-parameters-data {\r
348             uses param;\r
349          }\r
350       }\r
351    }\r
352    grouping vnf-topology-identifier-structure {\r
353       container vnf-topology-identifier-structure {\r
354          leaf vnf-id {\r
355             type string;\r
356          }\r
357          leaf vnf-type {\r
358             description "In preload tree, this label is used for the vf-module-type";\r
359             type string;\r
360          }\r
361          leaf nf-type {\r
362             type string;\r
363          }\r
364          leaf nf-role {\r
365             type string;\r
366          }\r
367          leaf nf-function {\r
368             type string;\r
369          }\r
370          leaf nf-code {\r
371             description "used in vnf naming";\r
372             type string;\r
373          }\r
374          leaf vnf-name {\r
375             description "optionally comes from vnf-request-input container or is assigned by sdn-c";\r
376             type string;\r
377          }\r
378       }\r
379    }\r
380    grouping vnf-resource-assignments {\r
381       container vnf-resource-assignments {\r
382          leaf vnf-status {\r
383             description "Do we need this?Orchestration status from AAI - to be set by SDNCWill not be used for vIPR.";\r
384             type string;\r
385          }\r
386          container availability-zones {\r
387             leaf-list availability-zone {\r
388                description "Openstack availability zone name or UUID";\r
389                type string;\r
390                ordered-by user;\r
391             }\r
392             leaf max-count {\r
393                description "From the TOSCA data. Indicates the largest availability zone count needed by any vf-module in the VNF.";\r
394                type uint8;\r
395             }\r
396          }\r
397          container vnf-networks {\r
398             list vnf-network {\r
399                key "network-role";\r
400                uses vnf-network-data;\r
401             }\r
402          }\r
403       }\r
404    }\r
405    grouping vnf-network-data {\r
406       leaf network-role {\r
407          description "A Network Role to which a VNF must connect";\r
408          type string;\r
409       }\r
410       leaf network-name {\r
411          description "Unique Neutron UUID of an instance of the network role ";\r
412          type string;\r
413       }\r
414       leaf neutron-id {\r
415          description "Unique Neutron UUID of an instance of the network role ";\r
416          type string;\r
417       }\r
418       leaf network-id {\r
419          description "Unique Neutron UUID of an instance of the network role ";\r
420          type string;\r
421       }\r
422       leaf contrail-network-fqdn {\r
423          description "contrail network policy object";\r
424          type string;\r
425       }\r
426       container subnets-data {\r
427          list subnet-data {\r
428             key "ip-version";\r
429             leaf ip-version {\r
430                description "Should be ipv4 or ipv6";\r
431                type string;\r
432             }\r
433             leaf subnet-id {\r
434                description "subnet UUID to be passed into the HEAT template";\r
435                type string;\r
436             }\r
437          }\r
438       }\r
439    }\r
440    grouping vnf-level-oper-status {\r
441       container vnf-level-oper-status {\r
442          uses oper-status-data;\r
443       }\r
444    }\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
452    }\r
453    grouping vf-module-information {\r
454       container vf-module-information {\r
455          leaf vf-module-id {\r
456             type string;\r
457          }\r
458          leaf vf-module-type {\r
459             type string;\r
460          }\r
461          uses ecomp-model-information;\r
462       }\r
463    }\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
468             type string;\r
469          }\r
470          leaf vf-module-name {\r
471             type string;\r
472          }\r
473          uses region-identifier;\r
474          container vf-module-input-parameters {\r
475             uses param;\r
476          }\r
477       }\r
478    }\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 ecomp-model-information;\r
484          uses vf-module-assignments;\r
485          container vf-module-parameters {\r
486             uses param;\r
487          }\r
488       }\r
489    }\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
494             type string;\r
495          }\r
496          leaf vf-module-name {\r
497             description "vf-module-name";\r
498             type string;\r
499          }\r
500          leaf vf-module-type {\r
501             description "In Pats model referred to as model-id";\r
502             type string;\r
503          }\r
504       }\r
505    }\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
510             type string;\r
511          }\r
512          container vms {\r
513             list vm {\r
514                key "vm-type";\r
515                uses vm-topology-data;\r
516             }\r
517          }\r
518       }\r
519    }\r
520    grouping vm-topology-data {\r
521       leaf vm-type {\r
522          type string;\r
523          mandatory true;\r
524       }\r
525       leaf nfc-naming-code {\r
526          description "used in vm naming(draft 29: changed from nfc-code)";\r
527          type string;\r
528       }\r
529       leaf vm-type-tag {\r
530          description "from tosca data on vfc";\r
531          type string;\r
532       }\r
533       leaf vm-count {\r
534          type uint8;\r
535       }\r
536       container vm-names {\r
537          leaf-list vm-name {\r
538             description "ordered-by: user";\r
539             type string;\r
540             ordered-by user;\r
541          }\r
542       }\r
543       container vm-networks {\r
544          list vm-network {\r
545             key "network-role";\r
546             uses vm-network-data;\r
547          }\r
548       }\r
549    }\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
553          type string;\r
554          mandatory true;\r
555       }\r
556       leaf network-role-tag {\r
557          type string;\r
558       }\r
559       container network-information-items {\r
560          list network-information-item {\r
561             key "ip-version";\r
562             leaf ip-version {\r
563                description "Use ipv4 or ipv6";\r
564                type string;\r
565             }\r
566             leaf use-dhcp {\r
567                description "Indicator to use DHCP on this network for this VM";\r
568                type enumeration {\r
569                   enum "Y";\r
570                   enum "N";\r
571                }\r
572             }\r
573             leaf ip-count {\r
574                description "The number of ip addresses to be assigned per vm for this network role";\r
575                type uint8;\r
576             }\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
580                   type string;\r
581                   ordered-by user;\r
582                }\r
583             }\r
584          }\r
585       }\r
586       container mac-addresses {\r
587          leaf-list mac-address {\r
588             description "List of network assignments for this vm-type";\r
589             type string;\r
590             ordered-by user;\r
591          }\r
592       }\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
597             ordered-by user;\r
598          }\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
602             ordered-by user;\r
603          }\r
604       }\r
605       container interface-route-prefixes {\r
606          leaf-list interface-route-prefix {\r
607             description "ordered-by: user";\r
608             type string;\r
609             ordered-by user;\r
610          }\r
611       }\r
612       container sriov-parameters {\r
613          container heat-vlan-filters {\r
614             leaf-list heat-vlan-filter {\r
615                type string;\r
616                ordered-by user;\r
617             }\r
618          }\r
619          container application-tags {\r
620             container c-tags {\r
621                leaf-list c-tag {\r
622                   type string;\r
623                   ordered-by user;\r
624                }\r
625             }\r
626             container s-tags {\r
627                leaf-list s-tag {\r
628                   type string;\r
629                   ordered-by user;\r
630                }\r
631             }\r
632          }\r
633       }\r
634    }\r
635    grouping vf-module-level-oper-status {\r
636       container vf-module-level-oper-status {\r
637          uses oper-status-data;\r
638       }\r
639    }\r
640    grouping allotted-resource-info {\r
641       leaf allotted-resource-id {\r
642          type string;\r
643       }\r
644       leaf allotted-resource-type {\r
645          description "Not an enum, but expected values are contrail-route and security-zone.";\r
646          type string;\r
647       }\r
648       leaf allotted-resource-pointer {\r
649          description "Pointer to the allotted-resources topology";\r
650          type string;\r
651       }\r
652    }\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
659    }\r
660    grouping contrail-route-request-input {\r
661       container contrail-route-request-input {\r
662          container source-network {\r
663             uses network-info;\r
664          }\r
665          container dest-network {\r
666             uses network-info;\r
667          }\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
671                type string;\r
672             }\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
675                type string;\r
676             }\r
677          }\r
678          container contrail-route-input-parameters {\r
679             uses param;\r
680          }\r
681       }\r
682    }\r
683    grouping network-info {\r
684       leaf network-id {\r
685          type string;\r
686       }\r
687       leaf network-role {\r
688          type string;\r
689       }\r
690    }\r
691    grouping contrail-route-topology {\r
692       container contrail-route-topology {\r
693          uses allotted-resource-identifiers;\r
694          uses ecomp-model-information;\r
695          uses contrail-route-assignments;\r
696          container contrail-route-parameters {\r
697             uses param;\r
698          }\r
699       }\r
700    }\r
701    grouping contrail-route-assignments {\r
702       container contrail-route-assignments {\r
703          leaf fq-name {\r
704             description "The Contrail fq-name of the network policy";\r
705             type string;\r
706          }\r
707          leaf contrail-id {\r
708             description "The ID assigned by Contrail to the network-policy (one for one with the fq-name)";\r
709             type string;\r
710          }\r
711          container source-network {\r
712             uses network-info;\r
713          }\r
714          container dest-network {\r
715             uses network-info;\r
716          }\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
720                type string;\r
721             }\r
722             leaf vnf-id {\r
723                description "The vnf representing the contrail applied service";\r
724                type string;\r
725             }\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
728                type string;\r
729             }\r
730          }\r
731          leaf vlan-tag {\r
732             description "Contrail-assigned vlan-tag to the vipr vm interface for this route.";\r
733             type string;\r
734          }\r
735       }\r
736    }\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
743    }\r
744    grouping security-zone-request-input {\r
745       container security-zone-request-input {\r
746          leaf vlan-tag {\r
747             type string;\r
748          }\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
751             type string;\r
752          }\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
755             type string;\r
756          }\r
757          container security-zone-input-parameters {\r
758             uses param;\r
759          }\r
760       }\r
761    }\r
762    grouping security-zone-topology {\r
763       container security-zone-topology {\r
764          uses allotted-resource-identifiers;\r
765          uses ecomp-model-information;\r
766          uses security-zone-assignments;\r
767          container security-zone-parameters {\r
768             uses param;\r
769          }\r
770       }\r
771    }\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
776             type string;\r
777          }\r
778          leaf security-zone-name-trusted {\r
779             type string;\r
780          }\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
783             type string;\r
784          }\r
785          leaf security-zone-name-untrusted {\r
786             type string;\r
787          }\r
788          leaf security-zone-service-instance-id {\r
789             description "Will be the same as the parent-service-instance-id";\r
790             type string;\r
791          }\r
792          leaf security-zone-vnf-id {\r
793             description "Selected by SDNC from the security-zone-service-instance-id";\r
794             type string;\r
795          }\r
796          leaf vlan-tag {\r
797             type string;\r
798          }\r
799       }\r
800    }\r
801    grouping allotted-resource-information {\r
802       container allotted-resource-information {\r
803          leaf allotted-resource-id {\r
804             type string;\r
805          }\r
806          leaf allotted-resource-type {\r
807             description "Not an enum, but expected values are contrail-route and security-zone.";\r
808             type string;\r
809          }\r
810          leaf parent-service-instance-id {\r
811             description "Service-instance-id of the parent service to which this allotted resource belongs.";\r
812             type string;\r
813          }\r
814          uses ecomp-model-information;\r
815       }\r
816    }\r
817    grouping allotted-resource-identifiers {\r
818       container allotted-resource-identifiers {\r
819          leaf allotted-resource-id {\r
820             type string;\r
821          }\r
822          leaf allotted-resource-name {\r
823             description "For a contrail-route, the network policy name.";\r
824             type string;\r
825          }\r
826          leaf allotted-resource-type {\r
827             description "(Added in draft 32)Expected to be contrail-route or security-zone.";\r
828             type string;\r
829          }\r
830          leaf consuming-service-instance-id {\r
831             description "The service-instance-id of the consuming service of this allotted resource";\r
832             type string;\r
833          }\r
834          leaf parent-service-instance-id {\r
835             description "Service-instance-id of the parent service to which this allotted resource belongs.";\r
836             type string;\r
837          }\r
838       }\r
839    }\r
840    grouping allotted-resource-oper-status {\r
841       container allotted-resource-oper-status {\r
842          uses oper-status-data;\r
843       }\r
844    }\r
845    grouping allotted-resource-status {\r
846       container allotted-resource-status {\r
847          leaf response-code {\r
848             type string;\r
849          }\r
850          leaf response-message {\r
851             type string;\r
852          }\r
853          leaf final-indicator {\r
854             type string;\r
855          }\r
856          leaf request-status {\r
857             type enumeration {\r
858                enum "synccomplete";\r
859                enum "asynccomplete";\r
860                enum "notifycomplete";\r
861             }\r
862          }\r
863          leaf action {\r
864             description "value would one of possible request-actions; match the list in service-data oper-status";\r
865             type string;\r
866          }\r
867          leaf rpc-name {\r
868             type string;\r
869          }\r
870          leaf rpc-action {\r
871             description "this is the svc-action from the incoming request";\r
872             type enumeration {\r
873                enum "assign";\r
874                enum "activate";\r
875                enum "create";\r
876                enum "delete";\r
877                enum "unassign";\r
878                enum "deactivate";\r
879             }\r
880          }\r
881          leaf response-timestamp {\r
882             type string;\r
883          }\r
884       }\r
885    }\r
886    grouping topology-response-common {\r
887       leaf svc-request-id {\r
888          description "the request id from the request message for which this is the responseKeep as M";\r
889          type string;\r
890       }\r
891       leaf response-code {\r
892          description "a success code or an defined error codeKeep as M";\r
893          type string;\r
894       }\r
895       leaf response-message {\r
896          description "message included for error code";\r
897          type string;\r
898       }\r
899       leaf ack-final-indicator {\r
900          description "Expected to be Y or N.";\r
901          type string;\r
902       }\r
903    }\r
904    grouping sdnc-request-header {\r
905       container sdnc-request-header {\r
906          leaf svc-request-id {\r
907             description "Uniquely generated by calling system (e.g. MSO or SDN-GP)";\r
908             type string;\r
909          }\r
910          leaf svc-action {\r
911             description "Enumerated listThis is the rpcAction";\r
912             type enumeration {\r
913                enum "reserve";\r
914                enum "assign";\r
915                enum "activate";\r
916                enum "delete";\r
917                enum "changeassign";\r
918                enum "changedelete";\r
919                enum "rollback";\r
920                enum "deactivate";\r
921                enum "unassign";\r
922                enum "create";\r
923             }\r
924          }\r
925          leaf svc-notification-url {\r
926             description "Contains URL for asynchronous response";\r
927             type string;\r
928          }\r
929       }\r
930    }\r
931    grouping request-information {\r
932       container request-information {\r
933          leaf request-id {\r
934             description "Request ID generated upstream of MSO";\r
935             type string;\r
936          }\r
937          leaf request-action {\r
938             description "still need to work Disconnect";\r
939             type enumeration {\r
940                enum "CreateNetworkInstance";\r
941                enum "ActivateNetworkInstance";\r
942                enum "CreateServiceInstance";\r
943                enum "DeleteServiceInstance";\r
944                enum "DeleteNetworkInstance";\r
945                enum "CreateVnfInstance";\r
946                enum "ActivateVnfInstance";\r
947                enum "DeleteVnfInstance";\r
948                enum "CreateVfModuleInstance";\r
949                enum "ActivateVfModuleInstance";\r
950                enum "DeleteVfModuleInstance";\r
951                enum "CreateContrailRouteInstance";\r
952                enum "DeleteContrailRouteInstance";\r
953                enum "CreateSecurityZoneInstance";\r
954                enum "DeleteSecurityZoneInstance";\r
955             }\r
956          }\r
957          leaf source {\r
958             type string;\r
959          }\r
960          leaf notification-url {\r
961             type string;\r
962          }\r
963          leaf order-number {\r
964             type string;\r
965          }\r
966          leaf order-version {\r
967             type string;\r
968          }\r
969       }\r
970    }\r
971    grouping service-information {\r
972       container service-information {\r
973          leaf service-id {\r
974             description "This maps to the product-family-id in A&AI";\r
975             type string;\r
976          }\r
977          leaf subscription-service-type {\r
978             description "used to reference a&ai subscription-service-type. For example, we show as vIPR-ATM in example.";\r
979             type string;\r
980          }\r
981          uses ecomp-model-information;\r
982          leaf service-instance-id {\r
983             type string;\r
984          }\r
985          leaf global-customer-id {\r
986             description "need for put of data to AnAI (MSO provides)";\r
987             type string;\r
988          }\r
989          leaf subscriber-name {\r
990             description "Would not be expected for vIPR-ATM or mobility services.";\r
991             type string;\r
992          }\r
993       }\r
994    }\r
995    grouping ecomp-model-information {\r
996       container ecomp-model-information {\r
997          leaf model-invariant-uuid {\r
998             description "identifies the invariant uuid for this service or resource";\r
999             type string;\r
1000          }\r
1001          leaf model-customization-uuid {\r
1002             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
1003             type string;\r
1004          }\r
1005          leaf model-uuid {\r
1006             description "identifies the uuid for this service or resource, which is version specific";\r
1007             type string;\r
1008          }\r
1009          leaf model-version {\r
1010             type string;\r
1011          }\r
1012          leaf model-name {\r
1013             type string;\r
1014          }\r
1015       }\r
1016    }\r
1017    grouping region-identifier {\r
1018       leaf tenant {\r
1019          type string;\r
1020       }\r
1021       leaf aic-cloud-region {\r
1022          description "The AIC cloud region which maps to contrail versions";\r
1023          type string;\r
1024       }\r
1025       leaf aic-clli {\r
1026          description "Not expected to be used";\r
1027          type string;\r
1028       }\r
1029    }\r
1030    grouping param {\r
1031       list param {\r
1032          key "name";\r
1033          leaf name {\r
1034             type string;\r
1035          }\r
1036          leaf value {\r
1037             type string;\r
1038          }\r
1039       }\r
1040    }\r
1041    grouping instance-reference {\r
1042       leaf instance-id {\r
1043          type string;\r
1044       }\r
1045       leaf object-path {\r
1046          description "restconf retrieval path to this particular objectE.g. restconf/config/GENERIC-RESOURCE-API:services/service/$service-instance-id/service-data/service-topology/";\r
1047          type string;\r
1048       }\r
1049    }\r
1050    grouping oper-status-data {\r
1051       leaf order-status {\r
1052          description "TBD - do we need Request failed statuses? RequestFailed | InProgressTimeout";\r
1053          type enumeration {\r
1054             enum "Active";\r
1055             enum "PendingAssignment";\r
1056             enum "PendingCreate";\r
1057             enum "PendingUpdate";\r
1058             enum "PendingDelete";\r
1059             enum "Deleted";\r
1060             enum "Created";\r
1061          }\r
1062       }\r
1063       leaf last-rpc-action {\r
1064          type enumeration {\r
1065             enum "assign";\r
1066             enum "activate";\r
1067             enum "delete";\r
1068             enum "unassign";\r
1069             enum "deactivate";\r
1070             enum "create";\r
1071          }\r
1072       }\r
1073       leaf last-action {\r
1074          description "should be list of possible request-actions";\r
1075          type enumeration {\r
1076             enum "CreateNetworkInstance";\r
1077             enum "ActivateNetworkInstance";\r
1078             enum "CreateServiceInstance";\r
1079             enum "DeleteServiceInstance";\r
1080             enum "DeleteNetworkInstance";\r
1081             enum "CreateVnfInstance";\r
1082             enum "ActivateVnfInstance";\r
1083             enum "DeleteVnfInstance";\r
1084             enum "CreateVfModuleInstance";\r
1085             enum "ActivateVfModuleInstance";\r
1086             enum "DeleteVfModuleInstance";\r
1087             enum "CreateContrailRouteInstance";\r
1088             enum "DeleteContrailRouteInstance";\r
1089             enum "CreateSecurityZoneInstance";\r
1090             enum "DeleteSecurityZoneInstance";\r
1091          }\r
1092       }\r
1093       leaf last-svc-request-id {\r
1094          description "Not currently populated in service data.";\r
1095          type string;\r
1096       }\r
1097       leaf last-order-status {\r
1098          description "fieldused by generic-resource-api";\r
1099          type enumeration {\r
1100             enum "Active";\r
1101             enum "PendingAssignment";\r
1102             enum "PendingCreate";\r
1103             enum "PendingUpdate";\r
1104             enum "PendingDelete";\r
1105             enum "Deleted";\r
1106             enum "Created";\r
1107          }\r
1108       }\r
1109       leaf create-timestamp {\r
1110          description "Not currently populated in service data.";\r
1111          type string;\r
1112       }\r
1113       leaf modify-timestamp {\r
1114          type string;\r
1115       }\r
1116    }\r
1117    grouping service-response-information {\r
1118       container service-response-information {\r
1119          uses instance-reference;\r
1120       }\r
1121    }\r
1122    grouping network-response-information {\r
1123       container network-response-information {\r
1124          uses instance-reference;\r
1125       }\r
1126    }\r
1127    grouping vnf-response-information {\r
1128       container vnf-response-information {\r
1129          uses instance-reference;\r
1130       }\r
1131    }\r
1132    grouping vf-module-response-information {\r
1133       container vf-module-response-information {\r
1134          uses instance-reference;\r
1135       }\r
1136    }\r
1137    grouping contrail-route-response-information {\r
1138       container contrail-route-response-information {\r
1139          uses instance-reference;\r
1140       }\r
1141    }\r
1142    grouping security-zone-response-information {\r
1143       container security-zone-response-information {\r
1144          uses instance-reference;\r
1145       }\r
1146    }\r
1147    grouping preload-model-information {\r
1148       list vnf-preload-list {\r
1149          key "vnf-name vnf-type";\r
1150          leaf vnf-name {\r
1151             description "vf-module-name or network name";\r
1152             type string;\r
1153             mandatory true;\r
1154          }\r
1155          leaf vnf-type {\r
1156             description "vf-module-type or network type";\r
1157             type string;\r
1158             mandatory true;\r
1159          }\r
1160          uses preload-data;\r
1161       }\r
1162    }\r
1163    grouping vnf-topology-response-body {\r
1164       leaf svc-request-id {\r
1165          type string;\r
1166       }\r
1167       leaf response-code {\r
1168          type string;\r
1169       }\r
1170       leaf response-message {\r
1171          type string;\r
1172       }\r
1173       leaf ack-final-indicator {\r
1174          type string;\r
1175       }\r
1176    }\r
1177    grouping preload-data {\r
1178       container preload-data {\r
1179          uses vnf-topology-information;\r
1180          uses network-topology-information;\r
1181          uses oper-status;\r
1182       }\r
1183    }\r
1184    grouping vnf-topology-information {\r
1185       container vnf-topology-information {\r
1186          uses vnf-topology-identifier;\r
1187          uses vnf-assignments;\r
1188          uses vnf-parameters;\r
1189       }\r
1190    }\r
1191    grouping vnf-topology-identifier {\r
1192       container vnf-topology-identifier {\r
1193          leaf service-type {\r
1194             type string;\r
1195          }\r
1196          leaf service-id {\r
1197             type string;\r
1198          }\r
1199          leaf vnf-name {\r
1200             description "vf-module-name";\r
1201             type string;\r
1202          }\r
1203          leaf vnf-type {\r
1204             description "vf-module-type";\r
1205             type string;\r
1206          }\r
1207          leaf generic-vnf-name {\r
1208             type string;\r
1209          }\r
1210          leaf generic-vnf-type {\r
1211             type string;\r
1212          }\r
1213          leaf generic-vnf-id {\r
1214             type string;\r
1215          }\r
1216       }\r
1217    }\r
1218    grouping vnf-assignments {\r
1219       container vnf-assignments {\r
1220          leaf vnf-status {\r
1221             description "Orchestration Status from AAI - to be set by SDNC";\r
1222             type string;\r
1223          }\r
1224          list availability-zones {\r
1225             key "availability-zone";\r
1226             leaf availability-zone {\r
1227                description "Openstack availability zone name or UUID";\r
1228                type string;\r
1229             }\r
1230          }\r
1231          list vnf-networks {\r
1232             key "network-role";\r
1233             uses vnf-network;\r
1234             uses sriov-vlan-filter-list;\r
1235          }\r
1236          uses vm-topology;\r
1237       }\r
1238    }\r
1239    grouping vm-topology {\r
1240       list vnf-vms {\r
1241          key "vm-type";\r
1242          leaf vm-type {\r
1243             type string;\r
1244             mandatory true;\r
1245          }\r
1246          leaf vm-count {\r
1247             type uint8;\r
1248          }\r
1249          list vm-names {\r
1250             key "vm-name";\r
1251             leaf vm-name {\r
1252                type string;\r
1253             }\r
1254          }\r
1255          list vm-networks {\r
1256             key "network-role";\r
1257             uses vm-network;\r
1258          }\r
1259       }\r
1260    }\r
1261    grouping vnf-network {\r
1262       leaf network-role {\r
1263          description "A Network Role to which a VNF must connect";\r
1264          type string;\r
1265          mandatory true;\r
1266       }\r
1267       leaf network-name {\r
1268          description "Unique Neutron UUID of an instance of the network role ";\r
1269          type string;\r
1270       }\r
1271       leaf neutron-id {\r
1272          description "Unique Neutron UUID of an instance of the network role ";\r
1273          type string;\r
1274       }\r
1275       leaf network-id {\r
1276          description "Unique Neutron UUID of an instance of the network role ";\r
1277          type string;\r
1278       }\r
1279       leaf subnet-id {\r
1280          description "ipv4 subnet UUID to be passed into the HEAT template";\r
1281          type string;\r
1282       }\r
1283       leaf subnet-name {\r
1284          description "ipv4 subnet-name that corresponds to the ipv4 subnet-id";\r
1285          type string;\r
1286       }\r
1287       leaf contrail-network-fqdn {\r
1288          description "contrail network policy object";\r
1289          type string;\r
1290       }\r
1291       leaf ipv6-subnet-id {\r
1292          description "ipv6 subnet UUID to be passed into the HEAT template";\r
1293          type string;\r
1294       }\r
1295       leaf ipv6-subnet-name {\r
1296          description "ipv6 subnet-name that corresponds to the ipv6 subnet-id";\r
1297          type string;\r
1298       }\r
1299    }\r
1300    grouping sriov-vlan-filter-list {\r
1301       list sriov-vlan-filter-list {\r
1302          key "sriov-vlan-filter";\r
1303          leaf sriov-vlan-filter {\r
1304             type string;\r
1305          }\r
1306       }\r
1307    }\r
1308    grouping vm-network {\r
1309       leaf network-role {\r
1310          description "network (identified by role) that this VM connects to.  Should also be included in the vnf-networks for the containing VNF";\r
1311          type string;\r
1312       }\r
1313       leaf use-dhcp {\r
1314          description "Indicator to use DHCP on this network for this VM";\r
1315          type enumeration {\r
1316             enum "Y";\r
1317             enum "N";\r
1318          }\r
1319       }\r
1320       leaf ip-count {\r
1321          description "The number of ip addresses to be assigned per vm for this network role";\r
1322          type uint8;\r
1323       }\r
1324       list network-ips {\r
1325          key "ip-address";\r
1326          leaf ip-address {\r
1327             description "List of assigned ipv4 addresses on a network";\r
1328             type inet:ip-address;\r
1329          }\r
1330       }\r
1331       list network-ips-v6 {\r
1332          key "ip-address-ipv6";\r
1333          leaf ip-address-ipv6 {\r
1334             description "List of assigned ipv6 addresses on a network";\r
1335             type inet:ipv6-address;\r
1336          }\r
1337       }\r
1338       list network-macs {\r
1339          key "mac-address";\r
1340          leaf mac-address {\r
1341             description "List of network assignments for this VM (one per network)";\r
1342             type string;\r
1343          }\r
1344       }\r
1345       leaf floating-ip {\r
1346          description "Floating ipv4 for VMs of a given type on this network";\r
1347          type inet:ip-address;\r
1348       }\r
1349       leaf floating-ip-v6 {\r
1350          description "Floating ipv6 for VMs of a given type on this network";\r
1351          type inet:ipv6-address;\r
1352       }\r
1353       list interface-route-prefixes {\r
1354          key "interface-route-prefix-cidr";\r
1355          leaf interface-route-prefix-cidr {\r
1356             description "route prefixes (CIDRs) in ip/cidr format to be provided to MSO in vnf-topology as a list of static routes";\r
1357             type string;\r
1358             mandatory true;\r
1359          }\r
1360          leaf interface-route-prefix {\r
1361             description "route prefixes (CIDRs) to be provided to MSO in vnf-topology as a list of static routes";\r
1362             type inet:ip-address;\r
1363          }\r
1364       }\r
1365    }\r
1366    grouping vnf-parameters {\r
1367       list vnf-parameters {\r
1368          key "vnf-parameter-name";\r
1369          leaf vnf-parameter-name {\r
1370             description "The name of an arbitrary instance-specific vnf-parameters";\r
1371             type string;\r
1372          }\r
1373          leaf vnf-parameter-value {\r
1374             description "The value of an arbitrary instance-specific vnf-parameters ";\r
1375             type string;\r
1376          }\r
1377       }\r
1378    }\r
1379    grouping network-topology-information {\r
1380       container network-topology-information {\r
1381          uses network-topology-identifier;\r
1382          uses subnets;\r
1383          uses vpn-bindings;\r
1384          uses network-policy;\r
1385          uses route-table-reference;\r
1386          uses provider-network-information;\r
1387       }\r
1388    }\r
1389    grouping network-topology-identifier {\r
1390       container network-topology-identifier {\r
1391          leaf service-type {\r
1392             type string;\r
1393          }\r
1394          leaf network-name {\r
1395             type string;\r
1396          }\r
1397          leaf network-role {\r
1398             type string;\r
1399          }\r
1400          leaf network-type {\r
1401             type string;\r
1402          }\r
1403          leaf network-technology {\r
1404             type string;\r
1405          }\r
1406       }\r
1407    }\r
1408    grouping subnets {\r
1409       list subnets {\r
1410          key "start-address";\r
1411          leaf start-address {\r
1412             type inet:ip-address;\r
1413          }\r
1414          leaf gateway-address {\r
1415             type inet:ip-address;\r
1416          }\r
1417          leaf cidr-mask {\r
1418             type string;\r
1419          }\r
1420          leaf ip-version {\r
1421             type string;\r
1422          }\r
1423          leaf dhcp-enabled {\r
1424             type enumeration {\r
1425                enum "Y";\r
1426                enum "N";\r
1427             }\r
1428          }\r
1429          leaf dhcp-start-address {\r
1430             type string;\r
1431          }\r
1432          leaf dhcp-end-address {\r
1433             type string;\r
1434          }\r
1435          leaf subnet-name {\r
1436             type string;\r
1437          }\r
1438       }\r
1439    }\r
1440    grouping vpn-bindings {\r
1441       list vpn-bindings {\r
1442          key "vpn-binding-id";\r
1443          leaf vpn-binding-id {\r
1444             type string;\r
1445          }\r
1446          leaf global-route-target {\r
1447             type string;\r
1448          }\r
1449       }\r
1450    }\r
1451    grouping network-policy {\r
1452       list network-policy {\r
1453          key "network-policy-fqdn";\r
1454          leaf network-policy-fqdn {\r
1455             type string;\r
1456          }\r
1457          leaf network-policy-id {\r
1458             type string;\r
1459          }\r
1460       }\r
1461    }\r
1462    grouping route-table-reference {\r
1463       list route-table-reference {\r
1464          key "route-table-reference-fqdn";\r
1465          leaf route-table-reference-fqdn {\r
1466             type string;\r
1467             mandatory true;\r
1468          }\r
1469          leaf route-table-reference-id {\r
1470             type string;\r
1471          }\r
1472       }\r
1473    }\r
1474    grouping provider-network-information {\r
1475       leaf physical-network-name {\r
1476          type string;\r
1477       }\r
1478       leaf is-provider-network {\r
1479          type boolean;\r
1480       }\r
1481       leaf is-shared-network {\r
1482          type boolean;\r
1483       }\r
1484       leaf is-external-network {\r
1485          type boolean;\r
1486       }\r
1487    }\r
1488    grouping oper-status {\r
1489       container oper-status {\r
1490          leaf order-status {\r
1491             type enumeration {\r
1492                enum "Active";\r
1493                enum "PendingAssignment";\r
1494                enum "PendingCreate";\r
1495                enum "PendingUpdate";\r
1496                enum "PendingDelete";\r
1497                enum "Deleted";\r
1498             }\r
1499          }\r
1500          leaf last-action {\r
1501             description "this is preload request actions";\r
1502             type enumeration {\r
1503                enum "VNFActivateRequest";\r
1504                enum "ChangeVNFActivateRequest";\r
1505                enum "VnfInstanceActivateRequest";\r
1506                enum "ChangeVnfInstanceActivateRequest";\r
1507                enum "VfModuleActivateRequest";\r
1508                enum "ChangeVfModuleActivateRequest";\r
1509                enum "DisconnectVNFRequest";\r
1510                enum "DisconnectVnfInstanceRequest";\r
1511                enum "DisconnectVfModuleRequest";\r
1512                enum "PreloadVNFRequest";\r
1513                enum "DeletePreloadVNFRequest";\r
1514                enum "PreloadVnfInstanceRequest";\r
1515                enum "DeletePreloadVnfInstanceRequest";\r
1516                enum "PreloadVfModuleRequest";\r
1517                enum "DeletePreloadVfModuleRequest";\r
1518             }\r
1519          }\r
1520          leaf last-svc-request-id {\r
1521             type string;\r
1522          }\r
1523          leaf last-order-status {\r
1524             type enumeration {\r
1525                enum "Active";\r
1526                enum "PendingAssignment";\r
1527                enum "PendingCreate";\r
1528                enum "PendingUpdate";\r
1529                enum "PendingDelete";\r
1530                enum "Deleted";\r
1531             }\r
1532          }\r
1533          leaf create-timestamp {\r
1534             type string;\r
1535          }\r
1536          leaf modify-timestamp {\r
1537             type string;\r
1538          }\r
1539          leaf maintenance-indicator {\r
1540             type enumeration {\r
1541                enum "Y";\r
1542                enum "N";\r
1543             }\r
1544          }\r
1545       }\r
1546    }\r
1547    container services {\r
1548       uses service-model-infrastructure;\r
1549    }\r
1550    container contrail-route-allotted-resources {\r
1551       list contrail-route-allotted-resource {\r
1552          key "allotted-resource-id";\r
1553          leaf allotted-resource-id {\r
1554             type string;\r
1555             mandatory true;\r
1556          }\r
1557          container allotted-resource-data {\r
1558             container allotted-resource-operation-information {\r
1559                uses contrail-route-operation-information;\r
1560             }\r
1561             uses contrail-route-topology;\r
1562             uses allotted-resource-oper-status;\r
1563          }\r
1564          uses allotted-resource-status;\r
1565       }\r
1566    }\r
1567    container security-zone-allotted-resources {\r
1568       list security-zone-allotted-resource {\r
1569          key "allotted-resource-id";\r
1570          leaf allotted-resource-id {\r
1571             type string;\r
1572             mandatory true;\r
1573          }\r
1574          container allotted-resource-data {\r
1575             container allotted-resource-operation-information {\r
1576                uses security-zone-operation-information;\r
1577             }\r
1578             uses security-zone-topology;\r
1579             container security-zone-parameters {\r
1580                uses param;\r
1581             }\r
1582             uses allotted-resource-oper-status;\r
1583          }\r
1584          uses allotted-resource-status;\r
1585       }\r
1586    }\r
1587    rpc service-topology-operation {\r
1588       input {\r
1589          uses service-operation-information;\r
1590       }\r
1591       output {\r
1592          uses topology-response-common;\r
1593          uses service-response-information;\r
1594       }\r
1595    }\r
1596    rpc network-topology-operation {\r
1597       input {\r
1598          uses network-operation-information;\r
1599       }\r
1600       output {\r
1601          uses topology-response-common;\r
1602          uses network-response-information;\r
1603          uses service-response-information;\r
1604       }\r
1605    }\r
1606    rpc vnf-topology-operation {\r
1607       input {\r
1608          uses vnf-operation-information;\r
1609       }\r
1610       output {\r
1611          uses topology-response-common;\r
1612          uses vnf-response-information;\r
1613          uses service-response-information;\r
1614       }\r
1615    }\r
1616    rpc vf-module-topology-operation {\r
1617       input {\r
1618          uses vf-module-operation-information;\r
1619       }\r
1620       output {\r
1621          uses topology-response-common;\r
1622          uses vf-module-response-information;\r
1623          uses vnf-response-information;\r
1624          uses service-response-information;\r
1625       }\r
1626    }\r
1627    rpc contrail-route-topology-operation {\r
1628       input {\r
1629          uses contrail-route-operation-information;\r
1630       }\r
1631       output {\r
1632          uses topology-response-common;\r
1633          uses contrail-route-response-information;\r
1634          uses service-response-information;\r
1635       }\r
1636    }\r
1637    rpc security-zone-topology-operation {\r
1638       input {\r
1639          uses security-zone-operation-information;\r
1640       }\r
1641       output {\r
1642          uses topology-response-common;\r
1643          uses security-zone-response-information;\r
1644          uses service-response-information;\r
1645       }\r
1646    }\r
1647    container preload-vnfs {\r
1648       uses preload-model-information;\r
1649    }\r
1650    rpc preload-vnf-topology-operation {\r
1651       input {\r
1652          uses sdnc-request-header;\r
1653          uses request-information;\r
1654          uses vnf-topology-information;\r
1655       }\r
1656       output {\r
1657          uses vnf-topology-response-body;\r
1658       }\r
1659    }\r
1660    rpc preload-network-topology-operation {\r
1661       input {\r
1662          uses sdnc-request-header;\r
1663          uses request-information;\r
1664          uses network-topology-information;\r
1665       }\r
1666       output {\r
1667          uses vnf-topology-response-body;\r
1668       }\r
1669    }\r
1670 } ////closes the module\r