Rich Bennett | c58f846 | 2017-10-24 08:26:42 -0400 | [diff] [blame] | 1 | .. This work is licensed under a Creative Commons Attribution 4.0 International License. |
| 2 | .. http://creativecommons.org/licenses/by/4.0 |
ChrisC | 8ec1b91 | 2018-03-27 03:12:59 -0700 | [diff] [blame] | 3 | .. Copyright (c) 2017-2018 AT&T Intellectual Property. All rights reserved. |
LF Jenkins CI | d2e5008 | 2020-04-08 20:22:11 +0000 | [diff] [blame] | 4 | .. _architecture: |
Rich Bennett | c58f846 | 2017-10-24 08:26:42 -0400 | [diff] [blame] | 5 | |
Rich Bennett | c58f846 | 2017-10-24 08:26:42 -0400 | [diff] [blame] | 6 | Clamp in ONAP Architecture |
| 7 | -------------------------- |
| 8 | |
ChrisC | 8ec1b91 | 2018-03-27 03:12:59 -0700 | [diff] [blame] | 9 | CLAMP is a platform for designing and managing control loops. It is used to visualize |
| 10 | a control loop, configure it with specific parameters for a particular network |
Rich Bennett | c58f846 | 2017-10-24 08:26:42 -0400 | [diff] [blame] | 11 | service, then deploying and undeploying it. Once deployed, the user can also |
| 12 | update the loop with new parameters during runtime, as well as suspending and |
| 13 | restarting it. |
| 14 | |
ChrisC | 8ec1b91 | 2018-03-27 03:12:59 -0700 | [diff] [blame] | 15 | It interacts with other systems to deploy and execute the control loop. For |
osgn422w | ac76315 | 2019-05-28 12:59:41 +0200 | [diff] [blame] | 16 | example, it extracts the control loop blueprint and Policy Model(Model Driven Control Loop) |
| 17 | from CSAR distributed by SDC/DCAE-DS. |
ChrisC | 8ec1b91 | 2018-03-27 03:12:59 -0700 | [diff] [blame] | 18 | It requests from DCAE the instantiation of microservices |
| 19 | to manage the control loop flow. Furthermore, it creates and updates multiple |
osgn422w | ac76315 | 2019-05-28 12:59:41 +0200 | [diff] [blame] | 20 | policies (for DCAE mS configuration and actual Control Operations) in the Policy Engine |
| 21 | that define the closed loop flow. |
Rich Bennett | c58f846 | 2017-10-24 08:26:42 -0400 | [diff] [blame] | 22 | |
ChrisC | 2c0ec04 | 2018-06-06 17:11:31 +0200 | [diff] [blame] | 23 | |clamp-flow| |
| 24 | |
Rich Bennett | c58f846 | 2017-10-24 08:26:42 -0400 | [diff] [blame] | 25 | The ONAP CLAMP platform abstracts the details of these systems under the concept |
| 26 | of a control loop model. The design of a control loop and its management is |
| 27 | represented by a workflow in which all relevant system interactions take |
| 28 | place. This is essential for a self-service model of creating and managing |
| 29 | control loops, where no low-level user interaction with other components is |
| 30 | required. |
| 31 | |
ChrisC | 8ec1b91 | 2018-03-27 03:12:59 -0700 | [diff] [blame] | 32 | CLAMP also allows to visualize control loop metrics through a dashboard, in order |
| 33 | to help operations understand how and when a control loop is triggered and takes action. |
| 34 | |
ChrisC | 2c0ec04 | 2018-06-06 17:11:31 +0200 | [diff] [blame] | 35 | |dashboard-flow| |
| 36 | |
Rich Bennett | c58f846 | 2017-10-24 08:26:42 -0400 | [diff] [blame] | 37 | At a higher level, CLAMP is about supporting and managing the broad operational |
| 38 | life cycle of VNFs/VMs and ultimately ONAP components itself. It will offer the |
| 39 | ability to design, test, deploy and update control loop automation - both closed |
| 40 | and open. Automating these functions would represent a significant saving on |
| 41 | operational costs compared to traditional methods. |
ChrisC | 2c0ec04 | 2018-06-06 17:11:31 +0200 | [diff] [blame] | 42 | |
| 43 | |closed-loop| |
| 44 | |
sebdet | 5dea222 | 2019-01-11 13:11:03 +0100 | [diff] [blame] | 45 | .. |clamp-flow| image:: images/architecture/distdepl.png |
| 46 | .. |dashboard-flow| image:: images/architecture/monitoring.png |
LF Jenkins CI | d2e5008 | 2020-04-08 20:22:11 +0000 | [diff] [blame] | 47 | .. |closed-loop| image:: images/architecture/ONAP-closedloop.png |