blob: 79c8e06f5ff6b8934af0dd204a493da246395fc1 [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.
LF Jenkins CId2e50082020-04-08 20:22:11 +00004.. _architecture:
Rich Bennettc58f8462017-10-24 08:26:42 -04005
Rich Bennettc58f8462017-10-24 08:26:42 -04006Clamp in ONAP Architecture
7--------------------------
8
ChrisC8ec1b912018-03-27 03:12:59 -07009CLAMP is a platform for designing and managing control loops. It is used to visualize
10a control loop, configure it with specific parameters for a particular network
Rich Bennettc58f8462017-10-24 08:26:42 -040011service, then deploying and undeploying it. Once deployed, the user can also
12update the loop with new parameters during runtime, as well as suspending and
13restarting it.
14
ChrisC8ec1b912018-03-27 03:12:59 -070015It interacts with other systems to deploy and execute the control loop. For
osgn422wac763152019-05-28 12:59:41 +020016example, it extracts the control loop blueprint and Policy Model(Model Driven Control Loop)
17from CSAR distributed by SDC/DCAE-DS.
ChrisC8ec1b912018-03-27 03:12:59 -070018It requests from DCAE the instantiation of microservices
19to manage the control loop flow. Furthermore, it creates and updates multiple
osgn422wac763152019-05-28 12:59:41 +020020policies (for DCAE mS configuration and actual Control Operations) in the Policy Engine
21that define the closed loop flow.
Rich Bennettc58f8462017-10-24 08:26:42 -040022
ChrisC2c0ec042018-06-06 17:11:31 +020023|clamp-flow|
24
Rich Bennettc58f8462017-10-24 08:26:42 -040025The ONAP CLAMP platform abstracts the details of these systems under the concept
26of a control loop model. The design of a control loop and its management is
27represented by a workflow in which all relevant system interactions take
28place. This is essential for a self-service model of creating and managing
29control loops, where no low-level user interaction with other components is
30required.
31
ChrisC8ec1b912018-03-27 03:12:59 -070032CLAMP also allows to visualize control loop metrics through a dashboard, in order
33to help operations understand how and when a control loop is triggered and takes action.
34
ChrisC2c0ec042018-06-06 17:11:31 +020035|dashboard-flow|
36
Rich Bennettc58f8462017-10-24 08:26:42 -040037At a higher level, CLAMP is about supporting and managing the broad operational
38life cycle of VNFs/VMs and ultimately ONAP components itself. It will offer the
39ability to design, test, deploy and update control loop automation - both closed
40and open. Automating these functions would represent a significant saving on
41operational costs compared to traditional methods.
ChrisC2c0ec042018-06-06 17:11:31 +020042
43|closed-loop|
44
sebdet5dea2222019-01-11 13:11:03 +010045.. |clamp-flow| image:: images/architecture/distdepl.png
46.. |dashboard-flow| image:: images/architecture/monitoring.png
LF Jenkins CId2e50082020-04-08 20:22:11 +000047.. |closed-loop| image:: images/architecture/ONAP-closedloop.png