Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Code Block
languageyml
titleLoop Definition
linenumberstrue
collapsetrue
tosca_definitions_version: tosca_simple_yaml_1_3
data_types:
  onap.datatypes.ToscaConceptIdentifier:
    derived_from: tosca.datatypes.Root
    properties:
      name:
        type: string
        required: true
      version:
        type: string
        required: true
node_types:
  org.onap.policy.clamp.controlloop.Participant:
    version: 1.0.1
    derived_from: tosca.nodetypes.Root
    properties:
      provider:
        type: string
        requred: false
  org.onap.policy.clamp.controlloop.ControlLoopElement:
    version: 1.0.1
    derived_from: tosca.nodetypes.Root
    properties:
      provider:
        type: string
        requred: false
      participant_id:
        type: onap.datatypes.ToscaConceptIdentifier
        requred: true
  org.onap.policy.clamp.controlloop.ControlLoop:
    version: 1.0.1
    derived_from: tosca.nodetypes.Root
    properties:
      provider:
        type: string
        requred: false
      elements:
        type: list
        required: true
        entry_schema:
          type: onap.datatypes.ToscaConceptIdentifier
  org.onap.policy.clamp.controlloop.DCAEMicroserviceControlLoopElement:
    version: 1.0.1
    derived_from: org.onap.policy.clamp.controlloop.ControlLoopElement
    properties:
      dcae_blueprint_id:
        type: onap.datatypes.ToscaConceptIdentifier
        requred: true
  org.onap.policy.clamp.controlloop.PolicyTypeControlLoopElement:
    version: 1.0.1
    derived_from: org.onap.policy.clamp.controlloop.ControlLoopElement
    properties:
      policy_type_id:
        type: onap.datatypes.ToscaConceptIdentifier
        requred: true
  org.onap.policy.clamp.controlloop.CDSControlLoopElement:
    version: 1.0.1
    derived_from: org.onap.policy.clamp.controlloop.ControlLoopElement
    properties:
      cds_blueprint_id:
        type: onap.datatypes.ToscaConceptIdentifier
        requred: true
topology_template:
  node_templates:
    org.onap.dcae.controlloop.DCAEMicroserviceControlLoopParticipant:
      version: 2.3.4
      type: org.onap.policy.clamp.controlloop.Participant
      type_version: 1.0.1
      description: Participant for DCAE microservices
      properties:
        provider: ONAP
    org.onap.policy.controlloop.MonitoringPolicyControlLoopParticipant:
      version: 2.3.1
      type: org.onap.policy.clamp.controlloop.Participant
      type_version: 1.0.1
      description: Participant for DCAE microservices
      properties:
        provider: ONAP
    org.onap.policy.controlloop.OperationalPolicyControlLoopParticipant:
      version: 3.2.1
      type: org.onap.policy.clamp.controlloop.Participant
      type_version: 1.0.1
      description: Participant for DCAE microservices
      properties:
        provider: ONAP
    org.onap.ccsdk.cds.controlloop.CdsControlLoopParticipant:
      version: 2.2.1
      type: org.onap.policy.clamp.controlloop.Participant
      type_version: 1.0.1
      description: Participant for DCAE microservices
      properties:
        provider: ONAP
    org.onap.domain.pmsh.PMSH_DCAEMicroservice:
      version: 1.2.3
      type: org.onap.policy.clamp.controlloop.DCAEMicroserviceControlLoopElement
      type_version: 1.0.0
      description: Control loop element for the DCAE microservice for Performance Management Subscription Handling
      properties:
        provider: Ericsson
        participant_id:
          name: org.onap.dcae.controlloop.DCAEMicroserviceControlLoopParticipant
          version: 2.3.4
        dcae_blueprint_id:
          name: org.onap.dcae.blueprints.PMSHBlueprint
          version: 1.0.0
    org.onap.domain.pmsh.PMSH_MonitoringPolicyControlLoopElement:
      version: 1.2.3
      type: org.onap.policy.clamp.controlloop.PolicyTypeControlLoopElement
      type_version: 1.0.0
      description: Control loop element for the monitoring policy for Performance Management Subscription Handling
      properties:
        provider: Ericsson
        participant_id:
          name: org.onap.policy.controlloop.PolicyControlLoopParticipant
          version: 2.3.1
        policy_type_id:
          name: onap.policies.monitoring.pm-subscription-handler
          version: 1.0.0
    org.onap.domain.pmsh.PMSH_OperationalPolicyControlLoopElement:
      version: 1.2.3
      type: org.onap.policy.clamp.controlloop.PolicyTypeControlLoopElement
      type_version: 1.0.0
      description: Control loop element for the operational policy for Performance Management Subscription Handling
      properties:
        provider: Ericsson
        participant_id:
          name: org.onap.policy.controlloop.PolicyControlLoopParticipant
          version: 2.3.1
        policy_type_id:
          name: onap.policies.operational.pm-subscription-handler
          version: 1.0.0
    org.onap.domain.pmsh.PMSH_CDS_ControlLoopElement:
      version: 1.2.3
      type: org.onap.policy.clamp.controlloop.ControlLoopElement
      type_version: 1.0.0
      description: Control loop element for CDS for Performance Management Subscription Handling
      properties:
        provider: Ericsson
        participant_Id:
          name: org.onap.ccsdk.cds.controlloop.CdsControlLoopParticipant
          version: 3.2.1
        cds_blueprint_id:
          name: org.onap.ccsdk.cds.PMSHCdsBlueprint
          version: 1.0.0
    org.onap.domain.pmsh.PMSHControlLoopDefinition:
      version: 1.2.3
      type: org.onap.policy.clamp.controlloop.ControlLoop
      type_version: 1.0.0
      description: Control loop for Performance Management Subscription Handling
      properties:
        provider: Ericsson
        elements:
        - name: org.onap.domain.pmsh.PMSH_DCAEMicroservice
          version: 1.2.3
        - name: org.onap.domain.pmsh.PMSH_MonitoringPolicyControlLoopElement
          version: 1.2.3
        - name: org.onap.domain.pmsh.PMSH_OperationalPolicyControlLoopElement
          version: 1.2.3
        - name: org.onap.domain.pmsh.PMSH_CDS_ControlLoopElement
          version: 1.2.3

2.1.3 Example of two Control Loop instances

Code Block
languageyml
titleExample Control Loop Instances
linenumberstrue
collapsetrue
tosca_definitions_version: tosca_simple_yaml_1_3
capability_types:
  org.onap.EventProducer:
{
    "controlLoops": [
      properties:
  {
    carrier_protocol_type:
        type"name": string"PMSHInstance0",
        required: true
   "version": "1.0.1",
    constraints:
        - valid_values:"definition": {
          - DMAAP_message_router
     "name": "org.onap.domain.pmsh.PMSHControlLoopDefinition",
    -  SOMETHING_ELSE
          - REST"version": "1.0.0"
      data_format:
      },
  type: string
        required: true "state": "UNINITIALISED",
        constraints:
    "orderedState": "UNINITIALISED",
   - valid_values:
        "description": "PMSH -control JSON
loop instance 0",
        - YAML
   "elements": [
      - JMS
      event_format:
   {
     type: string
        required: true
      event_format_version:
   "id": "709c62b3-8918-41b9-a747-d21eb79c6c20",
     type: string
        required: false
      config_keys:"definition": {
        type: list
        required: false
        entry_schema:
 "name": "org.onap.domain.pmsh.PMSH_DCAEMicroservice",
         type: string
          constraints:
    "version": "1.2.3"
     - valid_values:
            - all valid},
 values should be added here
            - if not specified, events of any config key may be generated
 "participantId": {
                   - 'examples for config_key: ves-measurement, ves-syslog, tca_handle_out "name": "DCAEParticipant0",
              etc.'
     version: 0.0.1
    derived_from"version": tosca"1.capabilities0.Root0"
  org.onap.EventConsumer:
    properties:
      responding_capability:
        type: string},
        required: false
      carrier_protocol_type:
        type"state": string"UNINITIALISED",
        required: true
        constraints:   "orderedState": "UNINITIALISED",
        - valid_values:
          - DMAAP_message_router
          - SOMETHING_ELSE "description": "DCAE Control Loop Element for the PMSH instance 0 control loop"
          - REST
      data_format:
},
         type: string
      {
  required: true
        constraints:
        - valid_values: "id": "709c62b3-8918-41b9-a747-d21eb79c6c21",
          - JSON
          - YAML"definition": {
          - JMS
          - all valid values should be added here
"name": "org.onap.domain.pmsh.PMSH_MonitoringPolicyControlLoopElement",
         event_format:
        type: string
        description: 'examples for event_format: Ves_specification, LinkUp, VnfConfigured,
"version": "1.2.3"
                 etc.'
   },
     required: true
      event_format_version:
        type"participantId": string{
        description:   'examples for event_format_version: 5.28.4, 7.30.1, etc.'
        required"name": false"PolicyParticipant0",
      config_keys:
         type: list
        required"version": false"1.0.0"
        entry_schema:
           type: string},
          constraints:
          - valid_values:"state": "UNINITIALISED",
            -   all valid values should be added here"orderedState": "UNINITIALISED",
            - if not specified, events of any config key may be generated
            - 'examples for config_key: ves-measurement, ves-syslog, tca_handle_out,
              etc.'
    version: 0.0.1
    derived_from: tosca.capabilities.Root
node_types:
  org.onap.DynamicConfig:
    properties:
"description": "Monitoring Policy Control Loop Element for the PMSH instance 0 control loop"
            application_name:
        type: string
        description: Value used to tie the config to an application ? should we be
          using a relationship here instead?
        required: true
      application_version:
        type: string
        required: true
      application_provider:
        type: string
        required: false
      data_types:
        type: object
        required: false
      schema:
        type: object
        required: false
    version: 0.0.1
    derived_from: tosca.nodes.Root
  org.onap.APP:
    properties:
      application_name:
        type: string
        description: Human readable name for the application Product
        required: false
      provider:
        type: string
        description: Provider of the application and of the descriptor
        required: true
      application_version:
        type: string
        description: Software version of the application
        required: true
      blueprint_id:
        type: string
        description: A reference to the app blueprint
        required: false
      monitoring_policy:
        type: string
        description: A reference to the monitoring policy
        required: false
    requirements:
    - receive:
        capability: org.onap.EventProducer
        relationship: org.onap.PropagateEvent
        occurrences:
        - 0.0
        - UNBOUNDED
    - send:
        capability: org.onap.EventConsumer
        relationship: org.onap.PropagateEvent
        occurrences:
        - 0.0
        - UNBOUNDED
    version: 0.0.1
    derived_from: tosca.nodes.Root
  org.onap.EventRelay:
    properties:
      event_format:
        type: string
        description: 'examples for event_format: Ves_specification, etc.'
        required: true
      event_format_version:
        type: string
        description: 'examples for event_format_version: 5.28.4, 7.30.1, etc.'
        required: true
      config_keys:
        type: list
        required: false
        entry_schema:
          type: string
          constraints:
          - valid_values:
            - all valid values should be added here
            - if not specified, events of any config key is relayed
            - 'examples for config_key: ves-measurement, ves-syslog, tca_handle_out,
              etc.'
      supported_carrier_protocols:
        type: map
        description: 'A map describing supported carrier protocols and translations.
          The tuples define what protocol combinations are supported on the producer
          and consumer side: e.g. { REST: REST, DMAAP: REST, DMAAP: DMAAP}'
        required: true
        key_schema:
          type: string
          constraints:
          - valid_values:
            - DMAAP_message_router
            - SOMETHING_ELSE
            - REST
            - all valid values should be added here
        entry_schema:
          type: string
          constraints:
          - valid_values:
            - DMAAP_message_router
            - SOMETHING_ELSE
            - REST
            - all valid values should be added here
      supported_data_formats:
        type: map
        description: 'Is a map describing supported data formats and translation.
          The tuples define what protocol combinations are supported on the producer
          and consumer side: e.g. { JSON: JSON, JMS: JSON, YAML:YAML }'
        required: true
        key_schema:
          type: string
          constraints:
          - valid_values:
            - JSON
            - JMS
            - YAML
            - etc
            - all valid values should be added here
        entry_schema:
          type: string
          constraints:
          - valid_values:
            - JSON
            - JMS
            - YAML
            - etc
            - all valid values should be added here
    requirements:
    - receive:
        capability: org.onap.EventProducer
        relationship: org.onap.PropagateEvent
        occurrences:
        - 0.0
        - UNBOUNDED
    - send:
        capability: org.onap.EventConsumer
        relationship: org.onap.PropagateEvent
        occurrences:
        - 0.0
        - UNBOUNDED
    version: 0.0.1
    derived_from: tosca.nodes.Root
relationship_types:
  org.onap.PropagateEvent:
    properties:
      config_keys:
        type: list
        description: The relationship type used on requirements to org.onap.EventProducer
          and org.onap.EventConsumer capabilities. Filters events by specific config_keys
          to be transferred by this relationship. That is, any event with a specific
          config_key found in the list is transferred. If list is not defined or is
          empty, events with all config_keys are transferred.
        required: false
        entry_schema:
          type: string
    version: 0.0.1
    derived_from: tosca.relationships.Root
topology_template:
  inputs:
    pm_subscription_topic:
      type: string
    pm_subscription_response_topic:
      type: string
    pm_subscription_handler_blueprint_id:
      type: string
    pm_subscription_operational_policy_id:
      type: string
    pm_subscription_cds_blueprint_id:
      type: string
    enable_tls:
      type: string
  node_templates:
    org.onap.PM_Subscription_Handler:
      type: org.onap.APP
      properties:
        application_name: PM Subscription Handler
        provider: Ericsson
        application_version: 1.0.0
        artifact_id:
          get_input: pm_subscription_handler_blueprint_id
          description: Is this a reference to the DCAE Cloudify Blueprint that is
            already stored(or will be stored before CL configuration & instatiation)
},
              in DCAE Inventory?{
        artifact_config:
          enable_tls:
  "id": "709c62b3-8918-41b9-a747-d21eb79c6c22",
         get_input: enable_tls
          pmsh_publish_topic_name:"definition": {
            get_input: pm_subscription_topic
      capabilities:
     "name":   pm-subscription-event-publisher:
"org.onap.domain.pmsh.PMSH_OperationalPolicyControlLoopElement",
            properties:
            carrier_protocol_type: DMAAP_message_router"version": "1.2.3"
            data_format: JSON
        },
       event_format: pm-subscription-event-format
            event_format_version"participantId": 1.0.0{
          attributes:
              type"name": org.onap.EventProducer
"PolicyParticipant0",
           occurrences:
             - "version": "1.0.0"
          -  UNBOUNDED
        pm-subscription-event-receiver:
},
           properties:
         "state": "UNINITIALISED",
  carrier_protocol_type: DMAAP_message_router
            data_format: JSON
    "orderedState": "UNINITIALISED",
       event_format: pm-subscription-event-response-format
            event_format_version: 1.0.0
            relationships:"description": "Operational Policy Control Loop Element for the PMSH instance 0 control loop"
            - type: tosca.relationships.DependsOn
  },
          - description: any ideas on a better{
 realtionship ? or is it better to
             "id": "709c62b3-8918-41b9-a747-d21eb79c6c23",
  just use the root realtionship ?
            - target"definition": org.onap.PM_Monitoring_Policy
{
           attributes:
             type"name": "org.onap.EventConsumerdomain.pmsh.PMSH_CDS_ControlLoopElement",
          occurrences:
          - 0.0
   "version": "1.2.3"
      - UNBOUNDED
    org.onap.PM_Monitoring_Policy:
      type: org.onap.DynamicConfig
      properties:},
        application_name: PM Subscription Handler
        application_version: 1.0.0
   "participantId": {
      provider: Ericsson
        data_types:
          measurementType:"name": "CDSParticipant0",
            type:  string
          DN:"version": "1.0.0"
            type: string
          nfFilter:},
            properties:
        "state": "UNINITIALISED",
     nfNames:
                type"orderedState": list"UNINITIALISED",
                entry_schema: string
   "description": "CDS Control Loop Element for the PMSH instance 0 control modelInvariantIDs:loop"
                type: list}
            ]
    entry_schema:
    },
        {
      type: string
     "name": "PMSHInstance1",
         modelVersionIDs:
   "version": "1.0.1",
            type"definition": list{
                entry_schema:"name": "org.onap.domain.pmsh.PMSHControlLoopDefinition",
                "version":  type: string
"1.0.0"
            measurementGroup:},
            properties:"state": "UNINITIALISED",
              masurementTypes:"orderedState": "UNINITIALISED",
            "description": "PMSH control loop type: listinstance 1",
            "elements": [
   entry_schema:
             {
     type: measurementType
              managedObjectDNsBasic:"id": "709c62b3-8918-41b9-a747-e21eb79c6c24",
                type: list
   "definition": {
            entry_schema:
            "name": "org.onap.domain.pmsh.PMSH_DCAEMicroservice",
     type: DN
        schema:
           subscription:"version": "1.2.3"
            subscriptionName:
        },
      type: string
              required"participantId": true{
            administrativeState:
            "name": "DCAEParticipant0",
  type: string
              required: true
      "version": "1.0.0"
     filebasedGP:
              type: integer},
              required: true
     "state": "UNINITIALISED",
      fileLocation:
              type"orderedState": string"UNINITIALISED",
              required: true
     "description": "DCAE Control Loop Element for the  nfFilter:
  PMSH instance 1 control loop"
            type: nfFilter
   },
         measurementGroups:
       {
       type: list
              entry_schema:"id": "709c62b3-8918-41b9-a747-e21eb79c6c25",
                type: measurementGroup
      description"definition": Should{
 I be showing a dependency between PM Subscription Handler
        and the PM Monitoring Policy
   "name": "org.onap.PM_Policy:domain.pmsh.PMSH_MonitoringPolicyControlLoopElement",
      type: org.onap.APP
      properties:
        application_name: PM Subscription Operational Policy"version": "1.2.3"
        provider:   Ericsson
        application_version: 1.0.0 },
        artifact_id:
            get_input: pm_subscription_operational_policy_id"participantId": {
        artifact_config: NOT_DEFINED
         requirements:
      - receive_0:
 "name": "PolicyParticipant0",
           capability: pm-subscription-event-publisher
             node"version": org"1.onap.PM_Subscription_Handler0.0"
          relationship: NOT_DEFINED
          properties:},
            config_keys:
        "state": "UNINITIALISED",
   - topic_name:
                get_input: pm_subscription_topic"orderedState": "UNINITIALISED",
      - send_0:
              capability"description": cds-rest-receive
          node: org.onap.CDS"Monitoring Policy Control Loop Element for the PMSH instance 1 control loop"
      - receive_1:
          capability: cds-rest-response
},
               node: org.onap.CDS {
      - send_1:
              capability"id": pm-subscription-event-receiver
 "709c62b3-8918-41b9-a747-e21eb79c6c26",
         node: org.onap.PM_Subscription_Handler
          relationship"definition": NOT_DEFINED{
          properties:
              config_keys:"name": "org.onap.domain.pmsh.PMSH_OperationalPolicyControlLoopElement",
            - topic_name:
           "version": "1.2.3"
    get_input: pm_subscription_response_topic
        capabilities:
        pm-subscription-response-event-publisher:},
          properties:
            type"participantId": org.onap.EventProducer{
            carrier_protocol_type: DMAAP_message_router
            data_format"name": JSON"PolicyParticipant0",
            event_format: pm-subscription-event-response-format
            event_format_"version": "1.0.0"
          occurrences:
           - 0.0
},
               - UNBOUNDED
    org.onap.PM_CDS_Blueprint:
"state": "UNINITIALISED",
            type: org.onap.APP
        properties:"orderedState": "UNINITIALISED",
        application_name: PM Subscription CDS Blueprint
        provider"description": Ericsson
"Operational Policy Control Loop Element for the PMSH application_version:instance 1.0.0
 control loop"
         artifact_id:       },
          get_input: pm_subscription_cds_blueprint_id
      {
           capabilities:
          cds-rest-receive:"id": "709c62b3-8918-41b9-a747-e21eb79c6c27",
          properties:
            type"definition": org.onap.EventConsumer{
            protocol_type: REST
            data_format: JSON"name": "org.onap.domain.pmsh.PMSH_CDS_ControlLoopElement",
            event_format: cds_action_format
            event_format_"version": "1.02.0
3"
                responding_capability: cds-rest-response    },
          occurrences:
          - 0.0"participantId": {
          - UNBOUNDED
              cds-rest-response:
"name": "CDSParticipant0",
            properties:
            type"version": org"1.onap0.EventProducer0"
              protocol_type: REST
     },
       data_format: JSON
            event_format: cds_action_response_format"state": "UNINITIALISED",
            event_format_version: 1.0.0
        "orderedState": "UNINITIALISED",
     occurrences:
          - 0.0
    org.onap.controlloop0:
      type: org.onap.APP
      properties:
"description": "CDS Control Loop Element for the PMSH instance 1 control loop"
          application_name: Test Control Loop
   }
     provider: Ericsson
      ]
  application_version: 1.0.0
     }
   status: NOT_DEPLOYED]
}


2.2: Modelling from TOSCA to Commissioned Data in Run Time Inventory

...