blob: c98680a2bde98a240b83f19fd7c8a98cf77b00f5 [file] [log] [blame]
Rich Bennettc58f8462017-10-24 08:26:42 -04001.. This work is licensed under a Creative Commons Attribution 4.0 International License.
2.. http://creativecommons.org/licenses/by/4.0
ChrisC8ec1b912018-03-27 03:12:59 -07003.. Copyright (c) 2017-2018 AT&T Intellectual Property. All rights reserved.
Rich Bennettc58f8462017-10-24 08:26:42 -04004
Rich Bennettc58f8462017-10-24 08:26:42 -04005Clamp in ONAP Architecture
6--------------------------
7
ChrisC8ec1b912018-03-27 03:12:59 -07008CLAMP is a platform for designing and managing control loops. It is used to visualize
9a control loop, configure it with specific parameters for a particular network
Rich Bennettc58f8462017-10-24 08:26:42 -040010service, then deploying and undeploying it. Once deployed, the user can also
11update the loop with new parameters during runtime, as well as suspending and
12restarting it.
13
ChrisC8ec1b912018-03-27 03:12:59 -070014It interacts with other systems to deploy and execute the control loop. For
osgn422wac763152019-05-28 12:59:41 +020015example, it extracts the control loop blueprint and Policy Model(Model Driven Control Loop)
16from CSAR distributed by SDC/DCAE-DS.
ChrisC8ec1b912018-03-27 03:12:59 -070017It requests from DCAE the instantiation of microservices
18to manage the control loop flow. Furthermore, it creates and updates multiple
osgn422wac763152019-05-28 12:59:41 +020019policies (for DCAE mS configuration and actual Control Operations) in the Policy Engine
20that define the closed loop flow.
Rich Bennettc58f8462017-10-24 08:26:42 -040021
ChrisC2c0ec042018-06-06 17:11:31 +020022|clamp-flow|
23
Rich Bennettc58f8462017-10-24 08:26:42 -040024The ONAP CLAMP platform abstracts the details of these systems under the concept
25of a control loop model. The design of a control loop and its management is
26represented by a workflow in which all relevant system interactions take
27place. This is essential for a self-service model of creating and managing
28control loops, where no low-level user interaction with other components is
29required.
30
ChrisC8ec1b912018-03-27 03:12:59 -070031CLAMP also allows to visualize control loop metrics through a dashboard, in order
32to help operations understand how and when a control loop is triggered and takes action.
33
ChrisC2c0ec042018-06-06 17:11:31 +020034|dashboard-flow|
35
Rich Bennettc58f8462017-10-24 08:26:42 -040036At a higher level, CLAMP is about supporting and managing the broad operational
37life cycle of VNFs/VMs and ultimately ONAP components itself. It will offer the
38ability to design, test, deploy and update control loop automation - both closed
39and open. Automating these functions would represent a significant saving on
40operational costs compared to traditional methods.
ChrisC2c0ec042018-06-06 17:11:31 +020041
42|closed-loop|
43
sebdet5dea2222019-01-11 13:11:03 +010044.. |clamp-flow| image:: images/architecture/distdepl.png
45.. |dashboard-flow| image:: images/architecture/monitoring.png
46.. |closed-loop| image:: images/architecture/ONAP-closedloop.png