diff options
| author |   adheli.tavares <adheli.tavares@est.tech> | 2021-09-23 14:56:49 +0100 |
|---|---|---|
| committer | Adheli Tavares <adheli.tavares@est.tech> | 2021-09-27 19:14:50 +0000 |
| commit | 3548284f347e126ddef8f4df67eb468fbef09358 (patch) | |
| tree | 5ea7d947d348769955ac694f9d9cfbb346fe938b /docs/clamp/controlloop/controlloop.rst | |
| parent | e994ece5d7262651a815c6c1affe44431007817c (diff) | |
Defining Control Loops documentation.
Issue-ID: POLICY-3363
Change-Id: I11cc75800a78c67295d7286804158786ffd4e651
Signed-off-by: adheli.tavares <adheli.tavares@est.tech>
Diffstat (limited to 'docs/clamp/controlloop/controlloop.rst')
| -rw-r--r-- | docs/clamp/controlloop/controlloop.rst | 7 |
1 files changed, 5 insertions, 2 deletions
diff --git a/docs/clamp/controlloop/controlloop.rst b/docs/clamp/controlloop/controlloop.rst index aa6bbedc..a505abfe 100644 --- a/docs/clamp/controlloop/controlloop.rst +++ b/docs/clamp/controlloop/controlloop.rst @@ -222,6 +222,7 @@ At Run Time, the following Control Loop Life Cycle management capabilities are s The system dialogues for run time capabilities are described in detail on the :ref:`System Level Dialogues <system-level-label>` page. +.. _controlloop-instance-states: 2.1 Control Loop Instance States -------------------------------- @@ -312,6 +313,8 @@ partake in control loops. 4. Other Considerations ======================= +.. _management-cl-instance-configs: + 4.1 Management of Control Loop Instance Configurations ------------------------------------------------------ @@ -395,7 +398,7 @@ of many types across themselves using a mechanism such as a Kubernetes cluster. At runtime, interaction between ONAP platform services and application microservices are relatively unconstrained, so interactions between Control Loop Elements for a given Control Loop Instance remain relatively unconstrained. A -`proposal to support access-controlled accessto and between ONAP services +`proposal to support access-controlled access to and between ONAP services <https://wiki.onap.org/pages/viewpage.action?pageId=103417456>`_ will improve this. This can be complemented by intercepting and controlling services accesses between Control Loop Elements for Control Loop Instances for some/all Control @@ -449,7 +452,7 @@ in isolated namespaces or in dedicated workers/clusters; etc.. The APIs and Protocols used by CLAMP for Control Loops are described on the pages below: #. :ref:`System Level Dialogues <system-level-label>` -#. Defining Control Loops in TOSCA for CLAMP +#. :ref:`Defining Control Loops in TOSCA for CLAMP <defining-controlloops-label>` #. REST APIs for CLAMP Control Loops #. The CLAMP Control Loop Participant Protocol |