summaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorChrisC <cc697w@intl.att.com>2018-06-06 17:11:31 +0200
committerChrisC <cc697w@intl.att.com>2018-06-06 17:14:16 +0200
commit2c0ec04d5978a0eaf9b13d9830d0398e8aed0e66 (patch)
tree8e0ee0741ef8ecd596f50384887eb1326b7822cc /docs
parent7a58af870eb9934dfec4b5353672d7c428208116 (diff)
Update Architecture
Add pictures to enrich the text Issue-ID: CLAMP-128 Change-Id: I9a1460a29222f8992ac39fc90a82cb4c5e96747b Signed-off-by: ChrisC <cc697w@intl.att.com>
Diffstat (limited to 'docs')
-rw-r--r--docs/architecture.rst13
-rw-r--r--docs/images/ONAP-closedloop.pngbin0 -> 220944 bytes
-rwxr-xr-xdocs/images/distdepl.pngbin0 -> 38514 bytes
-rwxr-xr-xdocs/images/monitoring.pngbin0 -> 60890 bytes
4 files changed, 11 insertions, 2 deletions
diff --git a/docs/architecture.rst b/docs/architecture.rst
index 19c9b7052..e526fb064 100644
--- 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.
-
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
-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.
+|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
@@ -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.
+|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.
+
+|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
index 000000000..7d3a2cac8
--- /dev/null
+++ b/docs/images/ONAP-closedloop.png
Binary files differ
diff --git a/docs/images/distdepl.png b/docs/images/distdepl.png
new file mode 100755
index 000000000..5593f4986
--- /dev/null
+++ b/docs/images/distdepl.png
Binary files differ
diff --git a/docs/images/monitoring.png b/docs/images/monitoring.png
new file mode 100755
index 000000000..6dbf75e45
--- /dev/null
+++ b/docs/images/monitoring.png
Binary files differ