1 tosca_definitions_version: tosca_simple_yaml_1_3
3 onap.policies.Monitoring:
4 derived_from: tosca.policies.Root
6 name: onap.policies.Monitoring
7 description: a base policy type for all policies that govern monitoring provisioning
8 onap.policies.monitoring.dcae-pm-subscription-handler:
9 derived_from: onap.policies.Monitoring
14 description: PM Subscription Handler Subscription
16 type: onap.datatypes.monitoring.subscription
18 onap.datatypes.monitoring.subscription:
19 derived_from: tosca.datatypes.Root
23 description: Name of the subscription
27 description: State of the subscription
35 description: File based granularity period
39 description: ROP file location
41 nfTypeModelInvariantId:
43 description: Network function invariant ID
47 description: Network function filter
50 type: onap.datatypes.monitoring.nfFilter
53 description: Measurement Groups
56 type: onap.datatypes.monitoring.measurementGroups
57 onap.datatypes.monitoring.nfFilter:
58 derived_from: tosca.datatypes.Root
62 description: List of network functions
69 description: List of software versions
74 onap.datatypes.monitoring.measurementGroups:
75 derived_from: tosca.datatypes.Root
79 description: Measurement Group
82 type: onap.datatypes.monitoring.measurementGroup
83 onap.datatypes.monitoring.measurementGroup:
84 derived_from: tosca.datatypes.Root
88 description: List of measurement types
92 type: onap.datatypes.monitoring.measurementTypes
93 managedObjectDNsBasic:
95 description: List of managed object distinguished names
99 type: onap.datatypes.monitoring.managedObjectDNsBasics
100 onap.datatypes.monitoring.measurementTypes:
101 derived_from: tosca.datatypes.Root
105 description: Measurement type object
108 type: onap.datatypes.monitoring.measurementType
109 onap.datatypes.monitoring.measurementType:
110 derived_from: tosca.datatypes.Root
114 description: Measurement type
116 onap.datatypes.monitoring.managedObjectDNsBasics:
117 derived_from: tosca.datatypes.Root
119 managedObjectDNsBasic:
121 description: Managed object distinguished name object
124 type: onap.datatypes.monitoring.managedObjectDNsBasic
125 onap.datatypes.monitoring.managedObjectDNsBasic:
126 derived_from: tosca.datatypes.Root
130 description: Managed object distinguished name
133 org.onap.EventProducer:
135 carrier_protocol_type:
140 - DMAAP_message_router
154 event_format_version:
164 - all valid values should be added here
165 - if not specified, events of any config key may be generated
166 - 'examples for config_key: ves-measurement, ves-syslog, tca_handle_out,
169 derived_from: tosca.capabilities.Root
170 org.onap.EventConsumer:
172 responding_capability:
175 carrier_protocol_type:
180 - DMAAP_message_router
191 - all valid values should be added here
194 description: 'examples for event_format: Ves_specification, LinkUp, VnfConfigured,
197 event_format_version:
199 description: 'examples for event_format_version: 5.28.4, 7.30.1, etc.'
208 - all valid values should be added here
209 - if not specified, events of any config key may be generated
210 - 'examples for config_key: ves-measurement, ves-syslog, tca_handle_out,
213 derived_from: tosca.capabilities.Root
215 org.onap.DynamicConfig:
219 description: Value used to tie the config to an application ? should we be
220 using a relationship here instead?
225 application_provider:
235 derived_from: tosca.nodes.Root
240 description: Human readable name for the application Product
244 description: Provider of the application and of the descriptor
248 description: Software version of the application
252 description: A reference to the app blueprint
256 description: A reference to the monitoring policy
260 capability: org.onap.EventProducer
261 relationship: org.onap.PropagateEvent
269 capability: org.onap.EventConsumer
270 relationship: org.onap.PropagateEvent
278 derived_from: tosca.nodes.Root
283 description: 'examples for event_format: Ves_specification, etc.'
285 event_format_version:
287 description: 'examples for event_format_version: 5.28.4, 7.30.1, etc.'
296 - all valid values should be added here
297 - if not specified, events of any config key is relayed
298 - 'examples for config_key: ves-measurement, ves-syslog, tca_handle_out,
300 supported_carrier_protocols:
302 description: 'A map describing supported carrier protocols and translations.
303 The tuples define what protocol combinations are supported on the producer
304 and consumer side: e.g. { REST: REST, DMAAP: REST, DMAAP: DMAAP}'
310 - DMAAP_message_router
313 - all valid values should be added here
318 - DMAAP_message_router
321 - all valid values should be added here
322 supported_data_formats:
324 description: 'Is a map describing supported data formats and translation.
325 The tuples define what protocol combinations are supported on the producer
326 and consumer side: e.g. { JSON: JSON, JMS: JSON, YAML:YAML }'
336 - all valid values should be added here
345 - all valid values should be added here
348 capability: org.onap.EventProducer
349 relationship: org.onap.PropagateEvent
357 capability: org.onap.EventConsumer
358 relationship: org.onap.PropagateEvent
366 derived_from: tosca.nodes.Root
368 org.onap.PropagateEvent:
372 description: The relationship type used on requirements to org.onap.EventProducer
373 and org.onap.EventConsumer capabilities. Filters events by specific config_keys
374 to be transferred by this relationship. That is, any event with a specific
375 config_key found in the list is transferred. If list is not defined or is
376 empty, events with all config_keys are transferred.
381 derived_from: tosca.relationships.Root
384 pm_subscription_topic:
386 pm_subscription_response_topic:
388 pm_subscription_handler_blueprint_id:
390 pm_subscription_operational_policy_id:
392 pm_subscription_cds_blueprint_id:
397 org.onap.PM_Subscription_Handler:
401 application_name: PM Subscription Handler
403 application_version: 1.0.0
405 get_input: pm_subscription_handler_blueprint_id
406 description: Is this a reference to the DCAE Cloudify Blueprint that is
407 already stored(or will be stored before CL configuration & instatiation)
411 get_input: enable_tls
412 pmsh_publish_topic_name:
413 get_input: pm_subscription_topic
415 pm-subscription-event-publisher:
417 carrier_protocol_type: DMAAP_message_router
419 event_format: pm-subscription-event-format
420 event_format_version: 1.0.0
422 type: org.onap.EventProducer
429 pm-subscription-event-receiver:
431 carrier_protocol_type: DMAAP_message_router
433 event_format: pm-subscription-event-response-format
434 event_format_version: 1.0.0
436 - type: tosca.relationships.DependsOn
437 - description: any ideas on a better realtionship ? or is it better to
438 just use the root realtionship ?
439 - target: org.onap.PM_Monitoring_Policy
441 type: org.onap.EventConsumer
449 org.onap.PM_Monitoring_Policy:
450 type: org.onap.DynamicConfig
453 application_name: PM Subscription Handler
454 application_version: 1.0.0
479 type: measurementType
480 managedObjectDNsBasic:
503 type: measurementGroup
505 description: Should I be showing a dependency between PM Subscription Handler
506 and the PM Monitoring Policy
511 application_name: PM Subscription Operational Policy
513 application_version: 1.0.0
515 get_input: pm_subscription_operational_policy_id
516 artifact_config: NOT_DEFINED
519 capability: pm-subscription-event-publisher
520 node: org.onap.PM_Subscription_Handler
521 relationship: NOT_DEFINED
525 get_input: pm_subscription_topic
530 capability: cds-rest-receive
536 capability: cds-rest-response
542 capability: pm-subscription-event-receiver
543 node: org.onap.PM_Subscription_Handler
544 relationship: NOT_DEFINED
548 get_input: pm_subscription_response_topic
553 pm-subscription-response-event-publisher:
555 type: org.onap.EventProducer
556 carrier_protocol_type: DMAAP_message_router
558 event_format: pm-subscription-event-response-format
559 event_format_version: 1.0.0
567 org.onap.PM_CDS_Blueprint:
571 application_name: PM Subscription CDS Blueprint
573 application_version: 1.0.0
575 get_input: pm_subscription_cds_blueprint_id
579 type: org.onap.EventConsumer
582 event_format: cds_action_format
583 event_format_version: 1.0.0
584 responding_capability: cds-rest-response
593 type: org.onap.EventProducer
596 event_format: cds_action_response_format
597 event_format_version: 1.0.0
604 org.onap.controlloop0:
608 application_name: Test Control Loop
610 application_version: 1.0.0