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. |
Rich Bennett | c58f846 | 2017-10-24 08:26:42 -0400 | [diff] [blame] | 4 | |
Rich Bennett | c58f846 | 2017-10-24 08:26:42 -0400 | [diff] [blame] | 5 | Clamp in ONAP Architecture |
| 6 | -------------------------- |
| 7 | |
ChrisC | 8ec1b91 | 2018-03-27 03:12:59 -0700 | [diff] [blame] | 8 | CLAMP is a platform for designing and managing control loops. It is used to visualize |
| 9 | a control loop, configure it with specific parameters for a particular network |
Rich Bennett | c58f846 | 2017-10-24 08:26:42 -0400 | [diff] [blame] | 10 | service, then deploying and undeploying it. Once deployed, the user can also |
| 11 | update the loop with new parameters during runtime, as well as suspending and |
| 12 | restarting it. |
| 13 | |
ChrisC | 8ec1b91 | 2018-03-27 03:12:59 -0700 | [diff] [blame] | 14 | It interacts with other systems to deploy and execute the control loop. For |
ChrisC | 64988b2 | 2018-06-06 18:06:53 +0200 | [diff] [blame^] | 15 | example, it gets the control loop blueprint from SDC - DCAE-DS. |
ChrisC | 8ec1b91 | 2018-03-27 03:12:59 -0700 | [diff] [blame] | 16 | It requests from DCAE the instantiation of microservices |
| 17 | to manage the control loop flow. Furthermore, it creates and updates multiple |
Rich Bennett | c58f846 | 2017-10-24 08:26:42 -0400 | [diff] [blame] | 18 | policies in the Policy Engine that define the closed loop flow. |
| 19 | |
ChrisC | 64988b2 | 2018-06-06 18:06:53 +0200 | [diff] [blame^] | 20 | |clamp-flow| |
| 21 | |
Rich Bennett | c58f846 | 2017-10-24 08:26:42 -0400 | [diff] [blame] | 22 | The ONAP CLAMP platform abstracts the details of these systems under the concept |
| 23 | of a control loop model. The design of a control loop and its management is |
| 24 | represented by a workflow in which all relevant system interactions take |
| 25 | place. This is essential for a self-service model of creating and managing |
| 26 | control loops, where no low-level user interaction with other components is |
| 27 | required. |
| 28 | |
ChrisC | 8ec1b91 | 2018-03-27 03:12:59 -0700 | [diff] [blame] | 29 | CLAMP also allows to visualize control loop metrics through a dashboard, in order |
| 30 | to help operations understand how and when a control loop is triggered and takes action. |
| 31 | |
ChrisC | 64988b2 | 2018-06-06 18:06:53 +0200 | [diff] [blame^] | 32 | |dashboard-flow| |
| 33 | |
Rich Bennett | c58f846 | 2017-10-24 08:26:42 -0400 | [diff] [blame] | 34 | At a higher level, CLAMP is about supporting and managing the broad operational |
| 35 | life cycle of VNFs/VMs and ultimately ONAP components itself. It will offer the |
| 36 | ability to design, test, deploy and update control loop automation - both closed |
| 37 | and open. Automating these functions would represent a significant saving on |
| 38 | operational costs compared to traditional methods. |
ChrisC | 64988b2 | 2018-06-06 18:06:53 +0200 | [diff] [blame^] | 39 | |
| 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 |