1 tosca_definitions_version: tosca_simple_yaml_1_3
3 org.onap.EventProducer:
10 - DMAAP_message_router
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,
39 derived_from: tosca.capabilities.Root
40 org.onap.EventConsumer:
42 responding_capability:
45 carrier_protocol_type:
50 - DMAAP_message_router
61 - all valid values should be added here
64 description: 'examples for event_format: Ves_specification, LinkUp, VnfConfigured,
69 description: 'examples for event_format_version: 5.28.4, 7.30.1, etc.'
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,
83 derived_from: tosca.capabilities.Root
85 org.onap.DynamicConfig:
89 description: Value used to tie the config to an application ? should we be
90 using a relationship here instead?
105 derived_from: tosca.nodes.Root
110 description: Human readable name for the application Product
114 description: Provider of the application and of the descriptor
118 description: Software version of the application
122 description: A reference to the app blueprint
126 description: A reference to the monitoring policy
130 capability: org.onap.EventProducer
131 relationship: org.onap.PropagateEvent
137 capability: org.onap.EventConsumer
138 relationship: org.onap.PropagateEvent
144 derived_from: tosca.nodes.Root
149 description: 'examples for event_format: Ves_specification, etc.'
151 event_format_version:
153 description: 'examples for event_format_version: 5.28.4, 7.30.1, etc.'
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,
166 supported_carrier_protocols:
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}'
176 - DMAAP_message_router
179 - all valid values should be added here
184 - DMAAP_message_router
187 - all valid values should be added here
188 supported_data_formats:
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 }'
202 - all valid values should be added here
211 - all valid values should be added here
214 capability: org.onap.EventProducer
215 relationship: org.onap.PropagateEvent
221 capability: org.onap.EventConsumer
222 relationship: org.onap.PropagateEvent
228 derived_from: tosca.nodes.Root
230 org.onap.PropagateEvent:
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.
243 derived_from: tosca.relationships.Root
246 pm_subscription_topic:
248 pm_subscription_response_topic:
250 pm_subscription_handler_blueprint_id:
252 pm_subscription_operational_policy_id:
254 pm_subscription_cds_blueprint_id:
259 org.onap.PM_Subscription_Handler:
262 application_name: PM Subscription Handler
264 application_version: 1.0.0
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)
272 get_input: enable_tls
273 pmsh_publish_topic_name:
274 get_input: pm_subscription_topic
276 pm-subscription-event-publisher:
278 carrier_protocol_type: DMAAP_message_router
280 event_format: pm-subscription-event-format
281 event_format_version: 1.0.0
283 type: org.onap.EventProducer
288 pm-subscription-event-receiver:
290 carrier_protocol_type: DMAAP_message_router
292 event_format: pm-subscription-event-response-format
293 event_format_version: 1.0.0
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
300 type: org.onap.EventConsumer
306 org.onap.PM_Monitoring_Policy:
307 type: org.onap.DynamicConfig
309 application_name: PM Subscription Handler
310 application_version: 1.0.0
335 type: measurementType
336 managedObjectDNsBasic:
359 type: measurementGroup
361 description: Should I be showing a dependency between PM Subscription Handler
362 and the PM Monitoring Policy
366 application_name: PM Subscription Operational Policy
368 application_version: 1.0.0
370 get_input: pm_subscription_operational_policy_id
371 artifact_config: NOT_DEFINED
374 capability: pm-subscription-event-publisher
375 node: org.onap.PM_Subscription_Handler
376 relationship: NOT_DEFINED
380 get_input: pm_subscription_topic
383 capability: cds-rest-receive
387 capability: cds-rest-response
391 capability: pm-subscription-event-receiver
392 node: org.onap.PM_Subscription_Handler
393 relationship: NOT_DEFINED
397 get_input: pm_subscription_response_topic
400 pm-subscription-response-event-publisher:
402 type: org.onap.EventProducer
403 carrier_protocol_type: DMAAP_message_router
405 event_format: pm-subscription-event-response-format
406 event_format_version: 1.0.0
412 org.onap.PM_CDS_Blueprint:
415 application_name: PM Subscription CDS Blueprint
417 application_version: 1.0.0
419 get_input: pm_subscription_cds_blueprint_id
423 type: org.onap.EventConsumer
426 event_format: cds_action_format
427 event_format_version: 1.0.0
428 responding_capability: cds-rest-response
435 type: org.onap.EventProducer
438 event_format: cds_action_response_format
439 event_format_version: 1.0.0
444 org.onap.controlloop0:
447 application_name: Test Control Loop
449 application_version: 1.0.0