From 12a315f76a189a4d3a00d6f0335dccf979b9608a Mon Sep 17 00:00:00 2001 From: "adheli.tavares" Date: Tue, 5 Apr 2022 14:21:40 +0100 Subject: Updating Clamp documentation - update rest apis definitions with renaming of control loop to acm - rename control loop to automation composition - fix a few cross-references missed Issue-ID: POLICY-4063 Change-Id: Ib88074e1d2d08fe38da244b5e1eb2e5783c84a86 Signed-off-by: adheli.tavares --- docs/development/devtools/clamp-dcae.rst | 2 +- docs/development/devtools/clamp-policy.rst | 6 +++--- docs/development/devtools/devtools.rst | 2 +- 3 files changed, 5 insertions(+), 5 deletions(-) (limited to 'docs/development/devtools') diff --git a/docs/development/devtools/clamp-dcae.rst b/docs/development/devtools/clamp-dcae.rst index 679db69d..2eaa8c93 100644 --- a/docs/development/devtools/clamp-dcae.rst +++ b/docs/development/devtools/clamp-dcae.rst @@ -54,7 +54,7 @@ The test set focused on the following use cases: - Undeployment of PMSH Creation of the Automation Composition: ------------------------------ +--------------------------------------- A Automation Composition is created by commissioning a Tosca template with Automation Composition definitions and instantiating the Automation Composition with the state "UNINITIALISED". - Upload a TOSCA template from the POLICY GUI. The definitions includes a kubernetes participant and control loop elements that deploys and configures a microservice in the kubernetes cluster. diff --git a/docs/development/devtools/clamp-policy.rst b/docs/development/devtools/clamp-policy.rst index 50fb10cf..3b3b90f5 100644 --- a/docs/development/devtools/clamp-policy.rst +++ b/docs/development/devtools/clamp-policy.rst @@ -44,7 +44,7 @@ The test set focused on the following use cases: - Deployment/Undeployment of policies Creation of the Automation Composition: ------------------------------ +--------------------------------------- A Automation Composition is created by commissioning a Tosca template with Automation Composition definitions and instantiating the Automation Composition with the state "UNINITIALISED". - Upload a TOSCA template from the POLICY GUI. The definitions includes a policy participant and a Automation Composition element that creates and deploys required policies. :download:`Sample Tosca template ` @@ -67,7 +67,7 @@ A Automation Composition is created by commissioning a Tosca template with Autom Creation and deployment of policies: ---------------------- +------------------------------------ The Automation Composition state is changed from "UNINITIALISED" to "PASSIVE" from the Policy Gui. Verify the POLICY API endpoint for the creation of policy types that are defined in the TOSCA template. Verify the PAP endpoint for the deployment of policies. .. image:: images/cl-passive.png @@ -85,7 +85,7 @@ Verification: .. image:: images/cl-create.png Undeployment and deletion of Policies: ---------------------- +-------------------------------------- The Automation Composition state is changed from "PASSIVE" to "UNINITIALISED" from the Policy Gui. Verification: diff --git a/docs/development/devtools/devtools.rst b/docs/development/devtools/devtools.rst index 6ea36899..e3a34941 100644 --- a/docs/development/devtools/devtools.rst +++ b/docs/development/devtools/devtools.rst @@ -275,7 +275,7 @@ familiar with the Policy Framework components and test any local changes. policy-gui-acm-smoke.rst db-migrator-smoke.rst - cl-participants-smoke.rst + acm-participants-smoke.rst clamp-smoke.rst clamp-cl-participant-protocol-smoke.rst policy-participant-smoke.rst -- cgit 1.2.3-korg