diff options
| author |   adheli.tavares <adheli.tavares@est.tech> | 2022-03-31 10:31:36 +0100 |
|---|---|---|
| committer | adheli.tavares <adheli.tavares@est.tech> | 2022-03-31 10:32:07 +0100 |
| commit | 96f544440333fb59fcc45fb9f53346e2320bc9bb (patch) | |
| tree | 32584ae289aeb76dd416d8c7299af61a0e57e00d /docs/clamp/controlloop/design-impl/participants/participants.rst | |
| parent | 178dea1eb3eb979994d8b99f317f536b85435b60 (diff) | |
Reestructuring the clamp doc tree
Issue-ID: POLICY-3941
Change-Id: I116742a732789a2737a00250849914aa30ad2fbf
Signed-off-by: adheli.tavares <adheli.tavares@est.tech>
Diffstat (limited to 'docs/clamp/controlloop/design-impl/participants/participants.rst')
| -rw-r--r-- | docs/clamp/controlloop/design-impl/participants/participants.rst | 39 |
1 files changed, 0 insertions, 39 deletions
diff --git a/docs/clamp/controlloop/design-impl/participants/participants.rst b/docs/clamp/controlloop/design-impl/participants/participants.rst deleted file mode 100644 index 230c9888..00000000 --- a/docs/clamp/controlloop/design-impl/participants/participants.rst +++ /dev/null @@ -1,39 +0,0 @@ -.. This work is licensed under a Creative Commons Attribution 4.0 International License. - -.. _clamp-controlloop-participants: - -Control Loop Participants -######################### - -A Participant is a component that acts as a bridge between the CLAMP COntrol Loop runtime and components such as -the Policy Framework, DCAE, or a Kubernetes cluster that are taking part in control loops. It listens -to DMaaP to receive messages from the CLAMP runtime and performs operations towards components that -are taking part in control loops. A participant has a Control Loop Element for each control loop in -which it is taking part. - -The implementation of a participant may use a common -:ref:`Participant Intermediary library <clamp-controlloop-participant-intermediary>`, which carries out common -message and state handling for Control Loop Elements in participants. The *ParticipantImpelementation* is the -component specific implementation of a participant, which is specifically developed for each component that -wishes to take part in control loops. - -.. image:: ../../images/participants/participants.png - -The figure above shows participants for various components that may take part in control loops. - -.. note:: The figure above is for illustration. Not all the participants mentioned above - have realizations in ONAP. Some of the participants in the figure above represent - a type of participant. For example, a controller participant would be written for - a specific controller such as CDS and a participant for an existing system would be - written towards that existing system. - -The detailed implementation of the CLAMP Participant ecosystem is described on the following pages: - -.. toctree:: - :maxdepth: 1 - - participant-intermediary - http-participant - k8s-participant - policy-framework-participant - participant-simulator |