1 # ============LICENSE_START=======================================================
2 # Copyright (C) 2021 Nordix Foundation.
3 # ================================================================================
4 # Licensed under the Apache License, Version 2.0 (the "License");
5 # you may not use this file except in compliance with the License.
6 # You may obtain a copy of the License at
8 # http://www.apache.org/licenses/LICENSE-2.0
10 # Unless required by applicable law or agreed to in writing, software
11 # distributed under the License is distributed on an "AS IS" BASIS,
12 # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
13 # See the License for the specific language governing permissions and
14 # limitations under the License.
16 # SPDX-License-Identifier: Apache-2.0
17 # ============LICENSE_END=========================================================
19 tosca_definitions_version: tosca_simple_yaml_1_3
21 org.onap.EventProducer:
23 carrier_protocol_type:
28 - DMAAP_message_router
52 - all valid values should be added here
53 - if not specified, events of any config key may be generated
54 - 'examples for config_key: ves-measurement, ves-syslog, tca_handle_out,
57 derived_from: tosca.capabilities.Root
58 org.onap.EventConsumer:
60 responding_capability:
63 carrier_protocol_type:
68 - DMAAP_message_router
79 - all valid values should be added here
82 description: 'examples for event_format: Ves_specification, LinkUp, VnfConfigured,
87 description: 'examples for event_format_version: 5.28.4, 7.30.1, etc.'
96 - all valid values should be added here
97 - if not specified, events of any config key may be generated
98 - 'examples for config_key: ves-measurement, ves-syslog, tca_handle_out,
101 derived_from: tosca.capabilities.Root
103 org.onap.DynamicConfig:
107 description: Value used to tie the config to an application ? should we be
108 using a relationship here instead?
113 application_provider:
123 derived_from: tosca.nodes.Root
128 description: Human readable name for the application Product
132 description: Provider of the application and of the descriptor
136 description: Software version of the application
140 description: A reference to the app blueprint
144 description: A reference to the monitoring policy
148 capability: org.onap.EventProducer
149 relationship: org.onap.PropagateEvent
154 capability: org.onap.EventConsumer
155 relationship: org.onap.PropagateEvent
160 derived_from: tosca.nodes.Root
165 description: 'examples for event_format: Ves_specification, etc.'
167 event_format_version:
169 description: 'examples for event_format_version: 5.28.4, 7.30.1, etc.'
178 - all valid values should be added here
179 - if not specified, events of any config key is relayed
180 - 'examples for config_key: ves-measurement, ves-syslog, tca_handle_out,
182 supported_carrier_protocols:
184 description: 'A map describing supported carrier protocols and translations.
185 The tuples define what protocol combinations are supported on the producer
186 and consumer side: e.g. { REST: REST, DMAAP: REST, DMAAP: DMAAP}'
192 - DMAAP_message_router
195 - all valid values should be added here
200 - DMAAP_message_router
203 - all valid values should be added here
204 supported_data_formats:
206 description: 'Is a map describing supported data formats and translation.
207 The tuples define what protocol combinations are supported on the producer
208 and consumer side: e.g. { JSON: JSON, JMS: JSON, YAML:YAML }'
218 - all valid values should be added here
227 - all valid values should be added here
230 capability: org.onap.EventProducer
231 relationship: org.onap.PropagateEvent
236 capability: org.onap.EventConsumer
237 relationship: org.onap.PropagateEvent
242 derived_from: tosca.nodes.Root
244 org.onap.PropagateEvent:
248 description: The relationship type used on requirements to org.onap.EventProducer
249 and org.onap.EventConsumer capabilities. Filters events by specific config_keys
250 to be transferred by this relationship. That is, any event with a specific
251 config_key found in the list is transferred. If list is not defined or is
252 empty, events with all config_keys are transferred.
257 derived_from: tosca.relationships.Root
260 pm_subscription_topic:
262 pm_subscription_response_topic:
264 pm_subscription_handler_blueprint_id:
266 pm_subscription_operational_policy_id:
268 pm_subscription_cds_blueprint_id:
273 org.onap.PM_Subscription_Handler:
274 type: org.onap.polcy.clamp.ControlLoopElement
276 application_name: PM Subscription Handler
278 application_version: 1.0.0
280 get_input: pm_subscription_handler_blueprint_id
281 description: Is this a reference to the DCAE Cloudify Blueprint that is
282 already stored(or will be stored before CL configuration & instatiation)
286 get_input: enable_tls
287 pmsh_publish_topic_name:
288 get_input: pm_subscription_topic
290 pm-subscription-event-publisher:
292 carrier_protocol_type: DMAAP_message_router
294 event_format: pm-subscription-event-format
295 event_format_version: 1.0.0
297 type: org.onap.EventProducer
301 pm-subscription-event-receiver:
303 carrier_protocol_type: DMAAP_message_router
305 event_format: pm-subscription-event-response-format
306 event_format_version: 1.0.0
308 - type: tosca.relationships.DependsOn
309 - description: any ideas on a better realtionship ? or is it better to
310 just use the root realtionship ?
311 - target: org.onap.PM_Monitoring_Policy
313 type: org.onap.EventConsumer
317 org.onap.PM_Monitoring_Policy:
318 type: org.onap.DynamicConfig
320 application_name: PM Subscription Handler
321 application_version: 1.0.0
346 type: measurementType
347 managedObjectDNsBasic:
370 type: measurementGroup
371 description: Should I be showing a dependency between PM Subscription Handler
372 and the PM Monitoring Policy
376 application_name: PM Subscription Operational Policy
378 application_version: 1.0.0
380 get_input: pm_subscription_operational_policy_id
381 artifact_config: NOT_DEFINED
384 capability: pm-subscription-event-publisher
385 node: org.onap.PM_Subscription_Handler
386 relationship: NOT_DEFINED
390 get_input: pm_subscription_topic
392 capability: cds-rest-receive
395 capability: cds-rest-response
398 capability: pm-subscription-event-receiver
399 node: org.onap.PM_Subscription_Handler
400 relationship: NOT_DEFINED
404 get_input: pm_subscription_response_topic
406 pm-subscription-response-event-publisher:
408 type: org.onap.EventProducer
409 carrier_protocol_type: DMAAP_message_router
411 event_format: pm-subscription-event-response-format
412 event_format_version: 1.0.0
416 org.onap.PM_CDS_Blueprint:
419 application_name: PM Subscription CDS Blueprint
421 application_version: 1.0.0
423 get_input: pm_subscription_cds_blueprint_id
427 type: org.onap.EventConsumer
430 event_format: cds_action_format
431 event_format_version: 1.0.0
432 responding_capability: cds-rest-response
438 type: org.onap.EventProducer
441 event_format: cds_action_response_format
442 event_format_version: 1.0.0
445 org.onap.controlloop0:
447 type: org.onap.policy.clamp.ControlLoop
449 application_name: Test Control Loop
451 application_version: 1.0.0
454 element1: org.onap.PM_Monitoring_Policy