A Participant is a component that acts as a bridge between the Automation Composition Management runtime and components such as the Kserve, A1PMS, DME, or a Kubernetes cluster that are taking part in automation composition management. It listens to DMaaP to receive messages from the ACM runtime and performs operations towards components that are taking part in acms. A participant has an Automation Composition Management Element for each automation composition in which it is taking part.

More information about ACM can be found here.

The DME participant receives Information Type/Data Producer/Data Consumer information from the ACM runtime and creates it in ICS(NONRTRIC). The participant acts as a wrapper around the ICS and creates the entities.

Supported message Broker are DMaap and Strimzi-Kafka.

Architecture

Image Added

When an automation composition is initialized, the DME participant starts a DME Automation Composition element for the automation composition. It reads the configuration information sent from the Automation Composition Runtime and runs a REST client to talk to the ICS(DME) endpoint receiving the REST requests.

Prerequisites for using A1PMS participant

• A running ICS(DME). ICS(DME) base url should be configured in DME participant to make REST calls.

Supported Element Types

Supported Element Types for DME participant will be used to define the DME participant Element Definition Types in tosca template. Participant Supported Element Types is defined in DME participant application.yaml.

participantSupportedElementTypes:
  -
    typeName: org.onap.policy.clamp.acm.DMEAutomationCompositionElement
    typeVersion: 1.0.1