31582d8d6ff07287ad33c4875b42ebf628ea46e2
[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 onap-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 onap-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 onap-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 onap-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 onap-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 onap-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 onap-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 onap-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 onap-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 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
807    }\r
808    grouping tunnelxconn-request-input {\r
809        leaf brg-wan-mac-address {\r
810            type string;\r
811        }\r
812    }\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
819                uses param;\r
820            }\r
821        }\r
822    }\r
823    grouping tunnelxconn-assignments {\r
824        leaf vni {\r
825            description "The Network Controller will assign a VNI value from the associated vGMUX VNI pool";\r
826            type string;\r
827        }\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
831        }\r
832        leaf vgmux-lan-ip {\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
835        }\r
836    }\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
843    }\r
844    grouping brg-request-input {\r
845        leaf vgmux-bearer-ip {\r
846            type inet:ip-address;\r
847        }\r
848        leaf vni {\r
849            type string;\r
850        }\r
851        leaf brg-wan-ip-address {\r
852            type inet:ip-address;\r
853        }\r
854    }\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
861                uses param;\r
862            }\r
863        }\r
864    }\r
865    grouping brg-assignments {\r
866        leaf vbrg-wan-ip {\r
867            type inet:ip-address;\r
868        }\r
869    }\r
870    grouping allotted-resource-information {\r
871       container allotted-resource-information {\r
872          leaf allotted-resource-id {\r
873             type string;\r
874          }\r
875          leaf allotted-resource-type {\r
876             description "Not an enum, but expected values are contrail-route and security-zone.";\r
877             type string;\r
878          }\r
879          leaf parent-service-instance-id {\r
880             description "Service-instance-id of the parent service to which this allotted resource belongs.";\r
881             type string;\r
882          }\r
883          uses onap-model-information;\r
884       }\r
885    }\r
886    grouping allotted-resource-identifiers {\r
887       container allotted-resource-identifiers {\r
888          leaf allotted-resource-id {\r
889             type string;\r
890          }\r
891          leaf allotted-resource-name {\r
892             description "For a contrail-route, the network policy name.";\r
893             type string;\r
894          }\r
895          leaf allotted-resource-type {\r
896             description "(Added in draft 32)Expected to be contrail-route or security-zone.";\r
897             type string;\r
898          }\r
899          leaf consuming-service-instance-id {\r
900             description "The service-instance-id of the consuming service of this allotted resource";\r
901             type string;\r
902          }\r
903          leaf parent-service-instance-id {\r
904             description "Service-instance-id of the parent service to which this allotted resource belongs.";\r
905             type string;\r
906          }\r
907       }\r
908    }\r
909    grouping allotted-resource-oper-status {\r
910       container allotted-resource-oper-status {\r
911          uses oper-status-data;\r
912       }\r
913    }\r
914    grouping allotted-resource-status {\r
915       container allotted-resource-status {\r
916          leaf response-code {\r
917             type string;\r
918          }\r
919          leaf response-message {\r
920             type string;\r
921          }\r
922          leaf final-indicator {\r
923             type string;\r
924          }\r
925          leaf request-status {\r
926             type enumeration {\r
927                enum "synccomplete";\r
928                enum "asynccomplete";\r
929                enum "notifycomplete";\r
930             }\r
931          }\r
932          leaf action {\r
933             description "value would one of possible request-actions; match the list in service-data oper-status";\r
934             type string;\r
935          }\r
936          leaf rpc-name {\r
937             type string;\r
938          }\r
939          leaf rpc-action {\r
940             description "this is the svc-action from the incoming request";\r
941             type enumeration {\r
942                enum "assign";\r
943                enum "activate";\r
944                enum "create";\r
945                enum "delete";\r
946                enum "unassign";\r
947                enum "deactivate";\r
948             }\r
949          }\r
950          leaf response-timestamp {\r
951             type string;\r
952          }\r
953       }\r
954    }\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
958          type string;\r
959       }\r
960       leaf response-code {\r
961          description "a success code or an defined error codeKeep as M";\r
962          type string;\r
963       }\r
964       leaf response-message {\r
965          description "message included for error code";\r
966          type string;\r
967       }\r
968       leaf ack-final-indicator {\r
969          description "Expected to be Y or N.";\r
970          type string;\r
971       }\r
972    }\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
977             type string;\r
978          }\r
979          leaf svc-action {\r
980             description "Enumerated listThis is the rpcAction";\r
981             type enumeration {\r
982                enum "reserve";\r
983                enum "assign";\r
984                enum "activate";\r
985                enum "delete";\r
986                enum "changeassign";\r
987                enum "changedelete";\r
988                enum "rollback";\r
989                enum "deactivate";\r
990                enum "unassign";\r
991                enum "create";\r
992             }\r
993          }\r
994          leaf svc-notification-url {\r
995             description "Contains URL for asynchronous response";\r
996             type string;\r
997          }\r
998       }\r
999    }\r
1000    grouping request-information {\r
1001       container request-information {\r
1002          leaf request-id {\r
1003             description "Request ID generated upstream of MSO";\r
1004             type string;\r
1005          }\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
1024                enum "ActivateDCINetworkInstance";\r
1025                enum "DeActivateDCINetworkInstance";\r
1026             }\r
1027          }\r
1028          leaf source {\r
1029             type string;\r
1030          }\r
1031          leaf notification-url {\r
1032             type string;\r
1033          }\r
1034          leaf order-number {\r
1035             type string;\r
1036          }\r
1037          leaf order-version {\r
1038             type string;\r
1039          }\r
1040       }\r
1041    }\r
1042    grouping service-information {\r
1043       container service-information {\r
1044          leaf service-id {\r
1045             description "This maps to the product-family-id in A&AI";\r
1046             type string;\r
1047          }\r
1048          leaf subscription-service-type {\r
1049             description "used to reference a&ai subscription-service-type. For example, we show as vIPR-ATM in example.";\r
1050             type string;\r
1051          }\r
1052          uses onap-model-information;\r
1053          leaf service-instance-id {\r
1054             type string;\r
1055          }\r
1056          leaf global-customer-id {\r
1057             description "need for put of data to AnAI (MSO provides)";\r
1058             type string;\r
1059          }\r
1060          leaf subscriber-name {\r
1061             description "Would not be expected for vIPR-ATM or mobility services.";\r
1062             type string;\r
1063          }\r
1064       }\r
1065    }\r
1066    grouping onap-model-information {\r
1067       container onap-model-information {\r
1068          leaf model-invariant-uuid {\r
1069             description "identifies the invariant uuid for this service or resource";\r
1070             type string;\r
1071          }\r
1072          leaf model-customization-uuid {\r
1073             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
1074             type string;\r
1075          }\r
1076          leaf model-uuid {\r
1077             description "identifies the uuid for this service or resource, which is version specific";\r
1078             type string;\r
1079          }\r
1080          leaf model-version {\r
1081             type string;\r
1082          }\r
1083          leaf model-name {\r
1084             type string;\r
1085          }\r
1086       }\r
1087    }\r
1088    grouping region-identifier {\r
1089       leaf tenant {\r
1090          type string;\r
1091       }\r
1092       leaf aic-cloud-region {\r
1093          description "The AIC cloud region which maps to contrail versions";\r
1094          type string;\r
1095       }\r
1096       leaf aic-clli {\r
1097          description "Not expected to be used";\r
1098          type string;\r
1099       }\r
1100    }\r
1101    grouping param {\r
1102       list param {\r
1103          key "name";\r
1104          leaf name {\r
1105             type string;\r
1106          }\r
1107          leaf value {\r
1108             type string;\r
1109          }\r
1110       }\r
1111    }\r
1112    grouping instance-reference {\r
1113       leaf instance-id {\r
1114          type string;\r
1115       }\r
1116       leaf object-path {\r
1117          description "restconf retrieval path to this particular objectE.g. restconf/config/GENERIC-RESOURCE-API:services/service/$service-instance-id/service-data/service-topology/";\r
1118          type string;\r
1119       }\r
1120    }\r
1121    grouping oper-status-data {\r
1122       leaf order-status {\r
1123          description "TBD - do we need Request failed statuses? RequestFailed | InProgressTimeout";\r
1124          type enumeration {\r
1125             enum "Active";\r
1126             enum "PendingAssignment";\r
1127             enum "PendingCreate";\r
1128             enum "PendingUpdate";\r
1129             enum "PendingDelete";\r
1130             enum "Deleted";\r
1131             enum "Created";\r
1132          }\r
1133       }\r
1134       leaf last-rpc-action {\r
1135          type enumeration {\r
1136             enum "assign";\r
1137             enum "activate";\r
1138             enum "delete";\r
1139             enum "unassign";\r
1140             enum "deactivate";\r
1141             enum "create";\r
1142          }\r
1143       }\r
1144       leaf last-action {\r
1145          description "should be list of possible request-actions";\r
1146          type enumeration {\r
1147             enum "CreateNetworkInstance";\r
1148             enum "ActivateNetworkInstance";\r
1149             enum "CreateServiceInstance";\r
1150             enum "DeleteServiceInstance";\r
1151             enum "DeleteNetworkInstance";\r
1152             enum "CreateVnfInstance";\r
1153             enum "ActivateVnfInstance";\r
1154             enum "DeleteVnfInstance";\r
1155             enum "CreateVfModuleInstance";\r
1156             enum "ActivateVfModuleInstance";\r
1157             enum "DeleteVfModuleInstance";\r
1158             enum "CreateContrailRouteInstance";\r
1159             enum "DeleteContrailRouteInstance";\r
1160             enum "CreateSecurityZoneInstance";\r
1161             enum "DeleteSecurityZoneInstance";\r
1162          }\r
1163       }\r
1164       leaf last-svc-request-id {\r
1165          description "Not currently populated in service data.";\r
1166          type string;\r
1167       }\r
1168       leaf last-order-status {\r
1169          description "fieldused by generic-resource-api";\r
1170          type enumeration {\r
1171             enum "Active";\r
1172             enum "PendingAssignment";\r
1173             enum "PendingCreate";\r
1174             enum "PendingUpdate";\r
1175             enum "PendingDelete";\r
1176             enum "Deleted";\r
1177             enum "Created";\r
1178          }\r
1179       }\r
1180       leaf create-timestamp {\r
1181          description "Not currently populated in service data.";\r
1182          type string;\r
1183       }\r
1184       leaf modify-timestamp {\r
1185          type string;\r
1186       }\r
1187    }\r
1188    grouping service-response-information {\r
1189       container service-response-information {\r
1190          uses instance-reference;\r
1191       }\r
1192    }\r
1193    grouping network-response-information {\r
1194       container network-response-information {\r
1195          uses instance-reference;\r
1196       }\r
1197    }\r
1198    grouping vnf-response-information {\r
1199       container vnf-response-information {\r
1200          uses instance-reference;\r
1201       }\r
1202    }\r
1203    grouping vf-module-response-information {\r
1204       container vf-module-response-information {\r
1205          uses instance-reference;\r
1206       }\r
1207    }\r
1208    grouping contrail-route-response-information {\r
1209       container contrail-route-response-information {\r
1210          uses instance-reference;\r
1211       }\r
1212    }\r
1213    grouping security-zone-response-information {\r
1214       container security-zone-response-information {\r
1215          uses instance-reference;\r
1216       }\r
1217    }\r
1218    grouping tunnelxconn-response-information {\r
1219        container tunnelxconn-response-information {\r
1220            uses instance-reference;\r
1221        }\r
1222    }\r
1223    grouping brg-response-information {\r
1224        container brg-response-information {\r
1225            uses instance-reference;\r
1226        }\r
1227    }\r
1228    grouping preload-model-information {\r
1229       list vnf-preload-list {\r
1230          key "vnf-name vnf-type";\r
1231          leaf vnf-name {\r
1232             description "vf-module-name or network name";\r
1233             type string;\r
1234             mandatory true;\r
1235          }\r
1236          leaf vnf-type {\r
1237             description "vf-module-type or network type";\r
1238             type string;\r
1239             mandatory true;\r
1240          }\r
1241          uses preload-data;\r
1242       }\r
1243    }\r
1244    grouping vnf-topology-response-body {\r
1245       leaf svc-request-id {\r
1246          type string;\r
1247       }\r
1248       leaf response-code {\r
1249          type string;\r
1250       }\r
1251       leaf response-message {\r
1252          type string;\r
1253       }\r
1254       leaf ack-final-indicator {\r
1255          type string;\r
1256       }\r
1257    }\r
1258    grouping preload-data {\r
1259       container preload-data {\r
1260          uses vnf-topology-information;\r
1261          uses network-topology-information;\r
1262          uses oper-status;\r
1263       }\r
1264    }\r
1265    grouping vnf-topology-information {\r
1266       container vnf-topology-information {\r
1267          uses vnf-topology-identifier;\r
1268          uses vnf-assignments;\r
1269          uses vnf-parameters;\r
1270       }\r
1271    }\r
1272    grouping vnf-topology-identifier {\r
1273       container vnf-topology-identifier {\r
1274          leaf service-type {\r
1275             type string;\r
1276          }\r
1277          leaf service-id {\r
1278             type string;\r
1279          }\r
1280          leaf vnf-name {\r
1281             description "vf-module-name";\r
1282             type string;\r
1283          }\r
1284          leaf vnf-type {\r
1285             description "vf-module-type";\r
1286             type string;\r
1287          }\r
1288          leaf generic-vnf-name {\r
1289             type string;\r
1290          }\r
1291          leaf generic-vnf-type {\r
1292             type string;\r
1293          }\r
1294          leaf generic-vnf-id {\r
1295             type string;\r
1296          }\r
1297       }\r
1298    }\r
1299    grouping vnf-assignments {\r
1300       container vnf-assignments {\r
1301          leaf vnf-status {\r
1302             description "Orchestration Status from AAI - to be set by SDNC";\r
1303             type string;\r
1304          }\r
1305          list availability-zones {\r
1306             key "availability-zone";\r
1307             leaf availability-zone {\r
1308                description "Openstack availability zone name or UUID";\r
1309                type string;\r
1310             }\r
1311          }\r
1312          list vnf-networks {\r
1313             key "network-role";\r
1314             uses vnf-network;\r
1315             uses sriov-vlan-filter-list;\r
1316          }\r
1317          uses vm-topology;\r
1318       }\r
1319    }\r
1320    grouping vm-topology {\r
1321       list vnf-vms {\r
1322          key "vm-type";\r
1323          leaf vm-type {\r
1324             type string;\r
1325             mandatory true;\r
1326          }\r
1327          leaf vm-count {\r
1328             type uint8;\r
1329          }\r
1330          list vm-names {\r
1331             key "vm-name";\r
1332             leaf vm-name {\r
1333                type string;\r
1334             }\r
1335          }\r
1336          list vm-networks {\r
1337             key "network-role";\r
1338             uses vm-network;\r
1339          }\r
1340       }\r
1341    }\r
1342    grouping vnf-network {\r
1343       leaf network-role {\r
1344          description "A Network Role to which a VNF must connect";\r
1345          type string;\r
1346          mandatory true;\r
1347       }\r
1348       leaf network-name {\r
1349          description "Unique Neutron UUID of an instance of the network role ";\r
1350          type string;\r
1351       }\r
1352       leaf neutron-id {\r
1353          description "Unique Neutron UUID of an instance of the network role ";\r
1354          type string;\r
1355       }\r
1356       leaf network-id {\r
1357          description "Unique Neutron UUID of an instance of the network role ";\r
1358          type string;\r
1359       }\r
1360       leaf subnet-id {\r
1361          description "ipv4 subnet UUID to be passed into the HEAT template";\r
1362          type string;\r
1363       }\r
1364       leaf subnet-name {\r
1365          description "ipv4 subnet-name that corresponds to the ipv4 subnet-id";\r
1366          type string;\r
1367       }\r
1368       leaf contrail-network-fqdn {\r
1369          description "contrail network policy object";\r
1370          type string;\r
1371       }\r
1372       leaf ipv6-subnet-id {\r
1373          description "ipv6 subnet UUID to be passed into the HEAT template";\r
1374          type string;\r
1375       }\r
1376       leaf ipv6-subnet-name {\r
1377          description "ipv6 subnet-name that corresponds to the ipv6 subnet-id";\r
1378          type string;\r
1379       }\r
1380    }\r
1381    grouping sriov-vlan-filter-list {\r
1382       list sriov-vlan-filter-list {\r
1383          key "sriov-vlan-filter";\r
1384          leaf sriov-vlan-filter {\r
1385             type string;\r
1386          }\r
1387       }\r
1388    }\r
1389    grouping vm-network {\r
1390       leaf network-role {\r
1391          description "network (identified by role) that this VM connects to.  Should also be included in the vnf-networks for the containing VNF";\r
1392          type string;\r
1393       }\r
1394       leaf use-dhcp {\r
1395          description "Indicator to use DHCP on this network for this VM";\r
1396          type enumeration {\r
1397             enum "Y";\r
1398             enum "N";\r
1399          }\r
1400       }\r
1401       leaf ip-count {\r
1402          description "The number of ip addresses to be assigned per vm for this network role";\r
1403          type uint8;\r
1404       }\r
1405       list network-ips {\r
1406          key "ip-address";\r
1407          leaf ip-address {\r
1408             description "List of assigned ipv4 addresses on a network";\r
1409             type inet:ip-address;\r
1410          }\r
1411       }\r
1412       list network-ips-v6 {\r
1413          key "ip-address-ipv6";\r
1414          leaf ip-address-ipv6 {\r
1415             description "List of assigned ipv6 addresses on a network";\r
1416             type inet:ipv6-address;\r
1417          }\r
1418       }\r
1419       list network-macs {\r
1420          key "mac-address";\r
1421          leaf mac-address {\r
1422             description "List of network assignments for this VM (one per network)";\r
1423             type string;\r
1424          }\r
1425       }\r
1426       leaf floating-ip {\r
1427          description "Floating ipv4 for VMs of a given type on this network";\r
1428          type inet:ip-address;\r
1429       }\r
1430       leaf floating-ip-v6 {\r
1431          description "Floating ipv6 for VMs of a given type on this network";\r
1432          type inet:ipv6-address;\r
1433       }\r
1434       list interface-route-prefixes {\r
1435          key "interface-route-prefix-cidr";\r
1436          leaf interface-route-prefix-cidr {\r
1437             description "route prefixes (CIDRs) in ip/cidr format to be provided to MSO in vnf-topology as a list of static routes";\r
1438             type string;\r
1439             mandatory true;\r
1440          }\r
1441          leaf interface-route-prefix {\r
1442             description "route prefixes (CIDRs) to be provided to MSO in vnf-topology as a list of static routes";\r
1443             type inet:ip-address;\r
1444          }\r
1445       }\r
1446    }\r
1447    grouping vnf-parameters {\r
1448       list vnf-parameters {\r
1449          key "vnf-parameter-name";\r
1450          leaf vnf-parameter-name {\r
1451             description "The name of an arbitrary instance-specific vnf-parameters";\r
1452             type string;\r
1453          }\r
1454          leaf vnf-parameter-value {\r
1455             description "The value of an arbitrary instance-specific vnf-parameters ";\r
1456             type string;\r
1457          }\r
1458       }\r
1459    }\r
1460    grouping network-topology-information {\r
1461       container network-topology-information {\r
1462          uses network-topology-identifier;\r
1463          uses subnets;\r
1464          uses vpn-bindings;\r
1465          uses network-policy;\r
1466          uses route-table-reference;\r
1467          uses provider-network-information;\r
1468       }\r
1469    }\r
1470    grouping network-topology-identifier {\r
1471       container network-topology-identifier {\r
1472          leaf service-type {\r
1473             type string;\r
1474          }\r
1475          leaf network-name {\r
1476             type string;\r
1477          }\r
1478          leaf network-role {\r
1479             type string;\r
1480          }\r
1481          leaf network-type {\r
1482             type string;\r
1483          }\r
1484          leaf network-technology {\r
1485             type string;\r
1486          }\r
1487       }\r
1488    }\r
1489    grouping subnets {\r
1490       list subnets {\r
1491          key "start-address";\r
1492          leaf start-address {\r
1493             type inet:ip-address;\r
1494          }\r
1495          leaf gateway-address {\r
1496             type inet:ip-address;\r
1497          }\r
1498          leaf cidr-mask {\r
1499             type string;\r
1500          }\r
1501          leaf ip-version {\r
1502             type string;\r
1503          }\r
1504          leaf dhcp-enabled {\r
1505             type enumeration {\r
1506                enum "Y";\r
1507                enum "N";\r
1508             }\r
1509          }\r
1510          leaf dhcp-start-address {\r
1511             type string;\r
1512          }\r
1513          leaf dhcp-end-address {\r
1514             type string;\r
1515          }\r
1516          leaf subnet-name {\r
1517             type string;\r
1518          }\r
1519       }\r
1520    }\r
1521    grouping vpn-bindings {\r
1522       list vpn-bindings {\r
1523          key "vpn-binding-id";\r
1524          leaf vpn-binding-id {\r
1525             type string;\r
1526          }\r
1527          leaf global-route-target {\r
1528             type string;\r
1529          }\r
1530       }\r
1531    }\r
1532    grouping network-policy {\r
1533       list network-policy {\r
1534          key "network-policy-fqdn";\r
1535          leaf network-policy-fqdn {\r
1536             type string;\r
1537          }\r
1538          leaf network-policy-id {\r
1539             type string;\r
1540          }\r
1541       }\r
1542    }\r
1543    grouping route-table-reference {\r
1544       list route-table-reference {\r
1545          key "route-table-reference-fqdn";\r
1546          leaf route-table-reference-fqdn {\r
1547             type string;\r
1548             mandatory true;\r
1549          }\r
1550          leaf route-table-reference-id {\r
1551             type string;\r
1552          }\r
1553       }\r
1554    }\r
1555    grouping provider-network-information {\r
1556       leaf physical-network-name {\r
1557          type string;\r
1558       }\r
1559       leaf is-provider-network {\r
1560          type boolean;\r
1561       }\r
1562       leaf is-shared-network {\r
1563          type boolean;\r
1564       }\r
1565       leaf is-external-network {\r
1566          type boolean;\r
1567       }\r
1568    }\r
1569    grouping oper-status {\r
1570       container oper-status {\r
1571          leaf order-status {\r
1572             type enumeration {\r
1573                enum "Active";\r
1574                enum "PendingAssignment";\r
1575                enum "PendingCreate";\r
1576                enum "PendingUpdate";\r
1577                enum "PendingDelete";\r
1578                enum "Deleted";\r
1579             }\r
1580          }\r
1581          leaf last-action {\r
1582             description "this is preload request actions";\r
1583             type enumeration {\r
1584                enum "VNFActivateRequest";\r
1585                enum "ChangeVNFActivateRequest";\r
1586                enum "VnfInstanceActivateRequest";\r
1587                enum "ChangeVnfInstanceActivateRequest";\r
1588                enum "VfModuleActivateRequest";\r
1589                enum "ChangeVfModuleActivateRequest";\r
1590                enum "DisconnectVNFRequest";\r
1591                enum "DisconnectVnfInstanceRequest";\r
1592                enum "DisconnectVfModuleRequest";\r
1593                enum "PreloadVNFRequest";\r
1594                enum "DeletePreloadVNFRequest";\r
1595                enum "PreloadVnfInstanceRequest";\r
1596                enum "DeletePreloadVnfInstanceRequest";\r
1597                enum "PreloadVfModuleRequest";\r
1598                enum "DeletePreloadVfModuleRequest";\r
1599             }\r
1600          }\r
1601          leaf last-svc-request-id {\r
1602             type string;\r
1603          }\r
1604          leaf last-order-status {\r
1605             type enumeration {\r
1606                enum "Active";\r
1607                enum "PendingAssignment";\r
1608                enum "PendingCreate";\r
1609                enum "PendingUpdate";\r
1610                enum "PendingDelete";\r
1611                enum "Deleted";\r
1612             }\r
1613          }\r
1614          leaf create-timestamp {\r
1615             type string;\r
1616          }\r
1617          leaf modify-timestamp {\r
1618             type string;\r
1619          }\r
1620          leaf maintenance-indicator {\r
1621             type enumeration {\r
1622                enum "Y";\r
1623                enum "N";\r
1624             }\r
1625          }\r
1626       }\r
1627    }\r
1628    container services {\r
1629       uses service-model-infrastructure;\r
1630    }\r
1631    container contrail-route-allotted-resources {\r
1632       list contrail-route-allotted-resource {\r
1633          key "allotted-resource-id";\r
1634          leaf allotted-resource-id {\r
1635             type string;\r
1636             mandatory true;\r
1637          }\r
1638          container allotted-resource-data {\r
1639             container allotted-resource-operation-information {\r
1640                uses contrail-route-operation-information;\r
1641             }\r
1642             uses contrail-route-topology;\r
1643             uses allotted-resource-oper-status;\r
1644          }\r
1645          uses allotted-resource-status;\r
1646       }\r
1647    }\r
1648    container security-zone-allotted-resources {\r
1649       list security-zone-allotted-resource {\r
1650          key "allotted-resource-id";\r
1651          leaf allotted-resource-id {\r
1652             type string;\r
1653             mandatory true;\r
1654          }\r
1655          container allotted-resource-data {\r
1656             container allotted-resource-operation-information {\r
1657                uses security-zone-operation-information;\r
1658             }\r
1659             uses security-zone-topology;\r
1660             container security-zone-parameters {\r
1661                uses param;\r
1662             }\r
1663             uses allotted-resource-oper-status;\r
1664          }\r
1665          uses allotted-resource-status;\r
1666       }\r
1667    }\r
1668    container tunnelxconn-allotted-resources {\r
1669        list tunnelxconn-allotted-resource {\r
1670            key "allotted-resource-id";\r
1671            leaf allotted-resource-id {\r
1672                type string;\r
1673                mandatory true;\r
1674            }\r
1675            container allotted-resource-data {\r
1676                container allotted-resource-operation-information {\r
1677                    uses tunnelxconn-operation-information;\r
1678                }\r
1679                uses tunnelxconn-topology;\r
1680                container tunnelxconn-parameters {\r
1681                    uses param;\r
1682                }\r
1683                uses allotted-resource-oper-status;\r
1684            }\r
1685            uses allotted-resource-status;\r
1686        }\r
1687    }\r
1688    container brg-allotted-resources {\r
1689        list brg-allotted-resource {\r
1690            key "allotted-resource-id";\r
1691            leaf allotted-resource-id {\r
1692                type string;\r
1693                mandatory true;\r
1694            }\r
1695            container allotted-resource-data {\r
1696                container allotted-resource-operation-information {\r
1697                    uses brg-operation-information;\r
1698                }\r
1699                uses brg-topology;\r
1700                container brg-parameters {\r
1701                    uses param;\r
1702                }\r
1703                uses allotted-resource-oper-status;\r
1704            }\r
1705            uses allotted-resource-status;\r
1706        }\r
1707    }\r
1708    rpc service-topology-operation {\r
1709       input {\r
1710          uses service-operation-information;\r
1711       }\r
1712       output {\r
1713          uses topology-response-common;\r
1714          uses service-response-information;\r
1715       }\r
1716    }\r
1717    rpc network-topology-operation {\r
1718       input {\r
1719          uses network-operation-information;\r
1720       }\r
1721       output {\r
1722          uses topology-response-common;\r
1723          uses network-response-information;\r
1724          uses service-response-information;\r
1725       }\r
1726    }\r
1727    rpc vnf-topology-operation {\r
1728       input {\r
1729          uses vnf-operation-information;\r
1730       }\r
1731       output {\r
1732          uses topology-response-common;\r
1733          uses vnf-response-information;\r
1734          uses service-response-information;\r
1735       }\r
1736    }\r
1737    rpc vf-module-topology-operation {\r
1738       input {\r
1739          uses vf-module-operation-information;\r
1740       }\r
1741       output {\r
1742          uses topology-response-common;\r
1743          uses vf-module-response-information;\r
1744          uses vnf-response-information;\r
1745          uses service-response-information;\r
1746       }\r
1747    }\r
1748    rpc contrail-route-topology-operation {\r
1749       input {\r
1750          uses contrail-route-operation-information;\r
1751       }\r
1752       output {\r
1753          uses topology-response-common;\r
1754          uses contrail-route-response-information;\r
1755          uses service-response-information;\r
1756       }\r
1757    }\r
1758    rpc security-zone-topology-operation {\r
1759       input {\r
1760          uses security-zone-operation-information;\r
1761       }\r
1762       output {\r
1763          uses topology-response-common;\r
1764          uses security-zone-response-information;\r
1765          uses service-response-information;\r
1766       }\r
1767    }\r
1768    rpc tunnelxconn-topology-operation {\r
1769        input {\r
1770            uses tunnelxconn-operation-information;\r
1771        }\r
1772        output {\r
1773            uses topology-response-common;\r
1774            uses tunnelxconn-response-information;\r
1775            uses service-response-information;\r
1776        }\r
1777    }\r
1778    rpc brg-topology-operation {\r
1779        input {\r
1780            uses brg-operation-information;\r
1781        }\r
1782        output {\r
1783            uses topology-response-common;\r
1784            uses brg-response-information;\r
1785            uses service-response-information;\r
1786        }\r
1787    }\r
1788    container preload-vnfs {\r
1789       uses preload-model-information;\r
1790    }\r
1791    rpc preload-vnf-topology-operation {\r
1792       input {\r
1793          uses sdnc-request-header;\r
1794          uses request-information;\r
1795          uses vnf-topology-information;\r
1796       }\r
1797       output {\r
1798          uses vnf-topology-response-body;\r
1799       }\r
1800    }\r
1801    rpc preload-network-topology-operation {\r
1802       input {\r
1803          uses sdnc-request-header;\r
1804          uses request-information;\r
1805          uses network-topology-information;\r
1806       }\r
1807       output {\r
1808          uses vnf-topology-response-body;\r
1809       }\r
1810    }\r
1811 \r
1812 } ////closes the module\r