summaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorosgn422w <gervais-martial.ngueko@intl.att.com>2019-05-28 12:59:41 +0200
committerosgn422w <gervais-martial.ngueko@intl.att.com>2019-05-28 12:59:41 +0200
commitac76315dc36a8083d06b997512581170dcf35e7b (patch)
tree9302939ba9fab54e96fdfaa2294df0add5d63dba /docs
parentef9aed4b3a69128fa10feaa9ab787a57ef6772d7 (diff)
Doc update
Update of some docs for Dublin features Issue-ID: CLAMP-396 Change-Id: I3179bc1c549ae0921f2bb4ad36751d304c8c45a4 Signed-off-by: osgn422w <gervais-martial.ngueko@intl.att.com>
Diffstat (limited to 'docs')
-rw-r--r--docs/architecture.rst6
-rw-r--r--docs/images/architecture/distdepl.pngbin38514 -> 44714 bytes
-rw-r--r--docs/index.rst2
3 files changed, 5 insertions, 3 deletions
diff --git a/docs/architecture.rst b/docs/architecture.rst
index fc9e6c322..c98680a2b 100644
--- a/docs/architecture.rst
+++ b/docs/architecture.rst
@@ -12,10 +12,12 @@ update the loop with new parameters during runtime, as well as suspending and
restarting it.
It interacts with other systems to deploy and execute the control loop. For
-example, it gets the control loop blueprint from SDC - DCAE-DS.
+example, it extracts the control loop blueprint and Policy Model(Model Driven Control Loop)
+from CSAR distributed by SDC/DCAE-DS.
It requests from DCAE the instantiation of microservices
to manage the control loop flow. Furthermore, it creates and updates multiple
-policies in the Policy Engine that define the closed loop flow.
+policies (for DCAE mS configuration and actual Control Operations) in the Policy Engine
+that define the closed loop flow.
|clamp-flow|
diff --git a/docs/images/architecture/distdepl.png b/docs/images/architecture/distdepl.png
index 5593f4986..0016a859c 100644
--- a/docs/images/architecture/distdepl.png
+++ b/docs/images/architecture/distdepl.png
Binary files differ
diff --git a/docs/index.rst b/docs/index.rst
index fc0118ac9..4915722e9 100644
--- a/docs/index.rst
+++ b/docs/index.rst
@@ -36,7 +36,7 @@ CLAMP uses the API's exposed by the following ONAP components:
- SDC : REST based interface exposed by the SDC, Distribution of service to DCAE
- DCAE: REST based interface exposed by DCAE, Common Controller Framework, DCAE microservices onboarded (TCA, Stringmatch, Holmes (optional))
-- Policy: REST based interface (the Policy team provide a "jar" to handle the communication), both XACML and Drools PDP, APIs to App-C/VF-C/SDN-C
+- Policy: REST based interface, Policy engine target both XACML and Drools PDP, Policy Engine trigger operations to App-C/VF-C/SDN-C
Delivery