blob: e526fb064213cb43196ff8ea00805034586fda48 [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
ChrisC2c0ec042018-06-06 17:11:31 +020015example, it gets the control loop blueprint from SDC - DCAE-DS.
ChrisC8ec1b912018-03-27 03:12:59 -070016It requests from DCAE the instantiation of microservices
17to manage the control loop flow. Furthermore, it creates and updates multiple
Rich Bennettc58f8462017-10-24 08:26:42 -040018policies in the Policy Engine that define the closed loop flow.
19
ChrisC2c0ec042018-06-06 17:11:31 +020020|clamp-flow|
21
Rich Bennettc58f8462017-10-24 08:26:42 -040022The ONAP CLAMP platform abstracts the details of these systems under the concept
23of a control loop model. The design of a control loop and its management is
24represented by a workflow in which all relevant system interactions take
25place. This is essential for a self-service model of creating and managing
26control loops, where no low-level user interaction with other components is
27required.
28
ChrisC8ec1b912018-03-27 03:12:59 -070029CLAMP also allows to visualize control loop metrics through a dashboard, in order
30to help operations understand how and when a control loop is triggered and takes action.
31
ChrisC2c0ec042018-06-06 17:11:31 +020032|dashboard-flow|
33
Rich Bennettc58f8462017-10-24 08:26:42 -040034At a higher level, CLAMP is about supporting and managing the broad operational
35life cycle of VNFs/VMs and ultimately ONAP components itself. It will offer the
36ability to design, test, deploy and update control loop automation - both closed
37and open. Automating these functions would represent a significant saving on
38operational costs compared to traditional methods.
ChrisC2c0ec042018-06-06 17:11:31 +020039
40|closed-loop|
41
42.. |clamp-flow| image:: images/distdepl.png
43.. |dashboard-flow| image:: images/monitoring.png
44.. |closed-loop| image:: images/ONAP-closedloop.png