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