Update Architecture

Add pictures to enrich the text
Cherry picked from 2c0ec04

Issue-ID: CLAMP-128
Change-Id: Ic7d6a84bd1ab2bcf3dcb5f3627e29d983c72be14
Signed-off-by: ChrisC <cc697w@intl.att.com>

diff --git a/docs/architecture.rst b/docs/architecture.rst
index 19c9b70..e526fb0 100644 (file)
--- a/docs/architecture.rst
+++ b/docs/architecture.rst
@@ -2,7 +2,6 @@
 .. http://creativecommons.org/licenses/by/4.0
 .. Copyright (c) 2017-2018 AT&T Intellectual Property.  All rights reserved.
 
 .. http://creativecommons.org/licenses/by/4.0
 .. Copyright (c) 2017-2018 AT&T Intellectual Property.  All rights reserved.
 

-

 Clamp in ONAP Architecture
 --------------------------
 
 Clamp in ONAP Architecture
 --------------------------
 


@@ -13,11 +12,13 @@ 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
 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-D.
+example, it gets the control loop blueprint from 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.
 
 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.
 

+|clamp-flow|
+

 The ONAP CLAMP platform abstracts the details of these systems under the concept
 of a control loop model.  The design of a control loop and its management is
 represented by a workflow in which all relevant system interactions take
 The ONAP CLAMP platform abstracts the details of these systems under the concept
 of a control loop model.  The design of a control loop and its management is
 represented by a workflow in which all relevant system interactions take


@@ -28,8 +29,16 @@ required.
 CLAMP also allows to visualize control loop metrics through a dashboard, in order
 to help operations understand how and when a control loop is triggered and takes action.
 
 CLAMP also allows to visualize control loop metrics through a dashboard, in order
 to help operations understand how and when a control loop is triggered and takes action.
 

+|dashboard-flow|
+

 At a higher level, CLAMP is about supporting and managing the broad operational
 life cycle of VNFs/VMs and ultimately ONAP components itself. It will offer the
 ability to design, test, deploy and update control loop automation - both closed
 and open. Automating these functions would represent a significant saving on
 operational costs compared to traditional methods.
 At a higher level, CLAMP is about supporting and managing the broad operational
 life cycle of VNFs/VMs and ultimately ONAP components itself. It will offer the
 ability to design, test, deploy and update control loop automation - both closed
 and open. Automating these functions would represent a significant saving on
 operational costs compared to traditional methods.

+
+|closed-loop|
+
+.. |clamp-flow| image:: images/distdepl.png
+.. |dashboard-flow| image:: images/monitoring.png
+.. |closed-loop| image:: images/ONAP-closedloop.png
\ No newline at end of file

diff --git a/docs/images/ONAP-closedloop.png b/docs/images/ONAP-closedloop.png
new file mode 100644 (file)
index 0000000..7d3a2ca
Binary files /dev/null and b/docs/images/ONAP-closedloop.png differ

diff --git a/docs/images/distdepl.png b/docs/images/distdepl.png
new file mode 100755 (executable)
index 0000000..5593f49
Binary files /dev/null and b/docs/images/distdepl.png differ

diff --git a/docs/images/monitoring.png b/docs/images/monitoring.png
new file mode 100755 (executable)
index 0000000..6dbf75e
Binary files /dev/null and b/docs/images/monitoring.png differ