99dd0ed68a3fff9885f6145a4acd0ae01e3b5807
[policy/clamp.git] /
1 tosca_definitions_version: tosca_simple_yaml_1_3
2 capability_types:
3   org.onap.EventProducer:
4     properties:
5       carrier_protocol_type:
6         type: string
7         required: true
8         constraints:
9         - valid_values:
10           - DMAAP_message_router
11           - SOMETHING_ELSE
12           - REST
13       data_format:
14         type: string
15         required: true
16         constraints:
17         - valid_values:
18           - JSON
19           - YAML
20           - JMS
21       event_format:
22         type: string
23         required: true
24       event_format_version:
25         type: string
26         required: false
27       config_keys:
28         type: list
29         required: false
30         entry_schema:
31           type: string
32           constraints:
33           - valid_values:
34             - all valid values should be added here
35             - if not specified, events of any config key may be generated
36             - 'examples for config_key: ves-measurement, ves-syslog, tca_handle_out,
37               etc.'
38     version: 0.0.1
39     derived_from: tosca.capabilities.Root
40   org.onap.EventConsumer:
41     properties:
42       responding_capability:
43         type: string
44         required: false
45       carrier_protocol_type:
46         type: string
47         required: true
48         constraints:
49         - valid_values:
50           - DMAAP_message_router
51           - SOMETHING_ELSE
52           - REST
53       data_format:
54         type: string
55         required: true
56         constraints:
57         - valid_values:
58           - JSON
59           - YAML
60           - JMS
61           - all valid values should be added here
62       event_format:
63         type: string
64         description: 'examples for event_format: Ves_specification, LinkUp, VnfConfigured,
65           etc.'
66         required: true
67       event_format_version:
68         type: string
69         description: 'examples for event_format_version: 5.28.4, 7.30.1, etc.'
70         required: false
71       config_keys:
72         type: list
73         required: false
74         entry_schema:
75           type: string
76           constraints:
77           - valid_values:
78             - all valid values should be added here
79             - if not specified, events of any config key may be generated
80             - 'examples for config_key: ves-measurement, ves-syslog, tca_handle_out,
81               etc.'
82     version: 0.0.1
83     derived_from: tosca.capabilities.Root
84 node_types:
85   org.onap.DynamicConfig:
86     properties:
87       application_name:
88         type: string
89         description: Value used to tie the config to an application ? should we be
90           using a relationship here instead?
91         required: true
92       application_version:
93         type: string
94         required: true
95       application_provider:
96         type: string
97         required: false
98       data_types:
99         type: object
100         required: false
101       schema:
102         type: object
103         required: false
104     version: 0.0.1
105     derived_from: tosca.nodes.Root
106   org.onap.APP:
107     properties:
108       application_name:
109         type: string
110         description: Human readable name for the application Product
111         required: false
112       provider:
113         type: string
114         description: Provider of the application and of the descriptor
115         required: true
116       application_version:
117         type: string
118         description: Software version of the application
119         required: true
120       blueprint_id:
121         type: string
122         description: A reference to the app blueprint
123         required: false
124       monitoring_policy:
125         type: string
126         description: A reference to the monitoring policy
127         required: false
128     requirements:
129     - receive:
130         capability: org.onap.EventProducer
131         relationship: org.onap.PropagateEvent
132         occurrences:
133         - 0.0
134         - UNBOUNDED
135         version: 0.0.0
136     - send:
137         capability: org.onap.EventConsumer
138         relationship: org.onap.PropagateEvent
139         occurrences:
140         - 0.0
141         - UNBOUNDED
142         version: 0.0.0
143     version: 0.0.1
144     derived_from: tosca.nodes.Root
145   org.onap.EventRelay:
146     properties:
147       event_format:
148         type: string
149         description: 'examples for event_format: Ves_specification, etc.'
150         required: true
151       event_format_version:
152         type: string
153         description: 'examples for event_format_version: 5.28.4, 7.30.1, etc.'
154         required: true
155       config_keys:
156         type: list
157         required: false
158         entry_schema:
159           type: string
160           constraints:
161           - valid_values:
162             - all valid values should be added here
163             - if not specified, events of any config key is relayed
164             - 'examples for config_key: ves-measurement, ves-syslog, tca_handle_out,
165               etc.'
166       supported_carrier_protocols:
167         type: map
168         description: 'A map describing supported carrier protocols and translations.
169           The tuples define what protocol combinations are supported on the producer
170           and consumer side: e.g. { REST: REST, DMAAP: REST, DMAAP: DMAAP}'
171         required: true
172         key_schema:
173           type: string
174           constraints:
175           - valid_values:
176             - DMAAP_message_router
177             - SOMETHING_ELSE
178             - REST
179             - all valid values should be added here
180         entry_schema:
181           type: string
182           constraints:
183           - valid_values:
184             - DMAAP_message_router
185             - SOMETHING_ELSE
186             - REST
187             - all valid values should be added here
188       supported_data_formats:
189         type: map
190         description: 'Is a map describing supported data formats and translation.
191           The tuples define what protocol combinations are supported on the producer
192           and consumer side: e.g. { JSON: JSON, JMS: JSON, YAML:YAML }'
193         required: true
194         key_schema:
195           type: string
196           constraints:
197           - valid_values:
198             - JSON
199             - JMS
200             - YAML
201             - etc
202             - all valid values should be added here
203         entry_schema:
204           type: string
205           constraints:
206           - valid_values:
207             - JSON
208             - JMS
209             - YAML
210             - etc
211             - all valid values should be added here
212     requirements:
213     - receive:
214         capability: org.onap.EventProducer
215         relationship: org.onap.PropagateEvent
216         occurrences:
217         - 0.0
218         - UNBOUNDED
219         version: 0.0.0
220     - send:
221         capability: org.onap.EventConsumer
222         relationship: org.onap.PropagateEvent
223         occurrences:
224         - 0.0
225         - UNBOUNDED
226         version: 0.0.0
227     version: 0.0.1
228     derived_from: tosca.nodes.Root
229 relationship_types:
230   org.onap.PropagateEvent:
231     properties:
232       config_keys:
233         type: list
234         description: The relationship type used on requirements to org.onap.EventProducer
235           and org.onap.EventConsumer capabilities. Filters events by specific config_keys
236           to be transferred by this relationship. That is, any event with a specific
237           config_key found in the list is transferred. If list is not defined or is
238           empty, events with all config_keys are transferred.
239         required: false
240         entry_schema:
241           type: string
242     version: 0.0.1
243     derived_from: tosca.relationships.Root
244 topology_template:
245   inputs:
246     pm_subscription_topic:
247       type: string
248     pm_subscription_response_topic:
249       type: string
250     pm_subscription_handler_blueprint_id:
251       type: string
252     pm_subscription_operational_policy_id:
253       type: string
254     pm_subscription_cds_blueprint_id:
255       type: string
256     enable_tls:
257       type: string
258   node_templates:
259     org.onap.PM_Subscription_Handler:
260       type: org.onap.APP
261       properties:
262         application_name: PM Subscription Handler
263         provider: Ericsson
264         application_version: 1.0.0
265         artifact_id:
266           get_input: pm_subscription_handler_blueprint_id
267           description: Is this a reference to the DCAE Cloudify Blueprint that is
268             already stored(or will be stored before CL configuration & instatiation)
269             in DCAE Inventory?
270         artifact_config:
271           enable_tls:
272             get_input: enable_tls
273           pmsh_publish_topic_name:
274             get_input: pm_subscription_topic
275       capabilities:
276         pm-subscription-event-publisher:
277           properties:
278             carrier_protocol_type: DMAAP_message_router
279             data_format: JSON
280             event_format: pm-subscription-event-format
281             event_format_version: 1.0.0
282           attributes:
283             type: org.onap.EventProducer
284           occurrences:
285           - 0.0
286           - UNBOUNDED
287           version: 0.0.0
288         pm-subscription-event-receiver:
289           properties:
290             carrier_protocol_type: DMAAP_message_router
291             data_format: JSON
292             event_format: pm-subscription-event-response-format
293             event_format_version: 1.0.0
294             relationships:
295             - type: tosca.relationships.DependsOn
296             - description: any ideas on a better realtionship ? or is it better to
297                 just use the root realtionship ?
298             - target: org.onap.PM_Monitoring_Policy
299           attributes:
300             type: org.onap.EventConsumer
301           occurrences:
302           - 0.0
303           - UNBOUNDED
304           version: 0.0.0
305       version: 0.0.0
306     org.onap.PM_Monitoring_Policy:
307       type: org.onap.DynamicConfig
308       properties:
309         application_name: PM Subscription Handler
310         application_version: 1.0.0
311         provider: Ericsson
312         data_types:
313           measurementType:
314             type: string
315           DN:
316             type: string
317           nfFilter:
318             properties:
319               nfNames:
320                 type: list
321                 entry_schema: string
322               modelInvariantIDs:
323                 type: list
324                 entry_schema:
325                   type: string
326               modelVersionIDs:
327                 type: list
328                 entry_schema:
329                   type: string
330           measurementGroup:
331             properties:
332               masurementTypes:
333                 type: list
334                 entry_schema:
335                   type: measurementType
336               managedObjectDNsBasic:
337                 type: list
338                 entry_schema:
339                   type: DN
340         schema:
341           subscription:
342             subscriptionName:
343               type: string
344               required: true
345             administrativeState:
346               type: string
347               required: true
348             filebasedGP:
349               type: integer
350               required: true
351             fileLocation:
352               type: string
353               required: true
354             nfFilter:
355               type: nfFilter
356             measurementGroups:
357               type: list
358               entry_schema:
359                 type: measurementGroup
360       version: 0.0.0
361       description: Should I be showing a dependency between PM Subscription Handler
362         and the PM Monitoring Policy
363     org.onap.PM_Policy:
364       type: org.onap.APP
365       properties:
366         application_name: PM Subscription Operational Policy
367         provider: Ericsson
368         application_version: 1.0.0
369         artifact_id:
370           get_input: pm_subscription_operational_policy_id
371         artifact_config: NOT_DEFINED
372       requirements:
373       - receive_0:
374           capability: pm-subscription-event-publisher
375           node: org.onap.PM_Subscription_Handler
376           relationship: NOT_DEFINED
377           properties:
378             config_keys:
379             - topic_name:
380                 get_input: pm_subscription_topic
381           version: 0.0.0
382       - send_0:
383           capability: cds-rest-receive
384           node: org.onap.CDS
385           version: 0.0.0
386       - receive_1:
387           capability: cds-rest-response
388           node: org.onap.CDS
389           version: 0.0.0
390       - send_1:
391           capability: pm-subscription-event-receiver
392           node: org.onap.PM_Subscription_Handler
393           relationship: NOT_DEFINED
394           properties:
395             config_keys:
396             - topic_name:
397                 get_input: pm_subscription_response_topic
398           version: 0.0.0
399       capabilities:
400         pm-subscription-response-event-publisher:
401           properties:
402             type: org.onap.EventProducer
403             carrier_protocol_type: DMAAP_message_router
404             data_format: JSON
405             event_format: pm-subscription-event-response-format
406             event_format_version: 1.0.0
407           occurrences:
408           - 0.0
409           - UNBOUNDED
410           version: 0.0.0
411       version: 0.0.0
412     org.onap.PM_CDS_Blueprint:
413       type: org.onap.APP
414       properties:
415         application_name: PM Subscription CDS Blueprint
416         provider: Ericsson
417         application_version: 1.0.0
418         artifact_id:
419           get_input: pm_subscription_cds_blueprint_id
420       capabilities:
421         cds-rest-receive:
422           properties:
423             type: org.onap.EventConsumer
424             protocol_type: REST
425             data_format: JSON
426             event_format: cds_action_format
427             event_format_version: 1.0.0
428             responding_capability: cds-rest-response
429           occurrences:
430           - 0.0
431           - UNBOUNDED
432           version: 0.0.0
433         cds-rest-response:
434           properties:
435             type: org.onap.EventProducer
436             protocol_type: REST
437             data_format: JSON
438             event_format: cds_action_response_format
439             event_format_version: 1.0.0
440           occurrences:
441           - 0.0
442           version: 0.0.0
443       version: 1.0.0
444     org.onap.controlloop0:
445       type: org.onap.APP
446       properties:
447         application_name: Test Control Loop
448         provider: Ericsson
449         application_version: 1.0.0
450         status: NOT_DEPLOYED
451       version: 0.0.0
452 version: 0.0.0