summaryrefslogtreecommitdiffstats
path: root/docs/development/devtools
diff options
context:
space:
mode:
authorLiam Fallon <liam.fallon@est.tech>2022-04-11 08:41:34 +0000
committerGerrit Code Review <gerrit@onap.org>2022-04-11 08:41:34 +0000
commit4236d55e6df1c17318995a65ad0a6e9411462456 (patch)
treec6a15d454197468cfe5a1335a5369bb7f4438296 /docs/development/devtools
parentc2e24ec6c9a3dab70f707744aa5bfda4f078b92e (diff)
parent12a315f76a189a4d3a00d6f0335dccf979b9608a (diff)
Merge "Updating Clamp documentation"
Diffstat (limited to 'docs/development/devtools')
-rw-r--r--docs/development/devtools/clamp-dcae.rst2
-rw-r--r--docs/development/devtools/clamp-policy.rst6
-rw-r--r--docs/development/devtools/devtools.rst2
3 files changed, 5 insertions, 5 deletions
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 <tosca/pairwise-testing.yml>`
@@ -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