| ChrisC | fb62292 | 2017-09-05 07:36:32 -0700 | [diff] [blame] | 1 | .. This work is licensed under a Creative Commons Attribution 4.0 International License. |
| 2 | .. http://creativecommons.org/licenses/by/4.0 |
| 3 | .. Copyright © 2017 AT&T Intellectual Property. All rights reserved. |
| 4 | |
| 5 | Component Information Template |
| 6 | ============================== |
| 7 | .. High level architecture, design, and packaging information for release planning and delivery. |
| 8 | |
| 9 | CLAMP is a platform for designing and managing control loops. |
| 10 | |
| 11 | It is used to design a closed loop, configure it with specific parameters for a particular network service, then deploying and undeploying it. |
| 12 | Once deployed, the user can also update the loop with new parameters during runtime, as well as suspending and restarting it. |
| 13 | It interacts with other systems to deploy and execute the closed loop. For example, it pushes the control loop design to the SDC catalog, associating it with the VF resource. It requests from DCAE the instantiation of microservices to manage the closed loop flow. Further, it creates and updates multiple policies in the Policy Engine that define the closed loop flow. |
| 14 | The CLAMP platform abstracts the details of these systems under the concept of a control loop model. The design of a control loop and its management is represented by a workflow in which all relevant system interactions take place. |
| 15 | |
| 16 | CLAMP is delivered as a single container |
| 17 | |
| 18 | |
| 19 | .. toctree:: |
| 20 | :maxdepth: 1 |
| 21 | |
| 22 | |
| 23 | Delivery |
| 24 | -------- |
| 25 | CLAMP component is composed of a UI layer and a BackEND layer and packaged into a single container as illustrated in the following diagrams. |
| 26 | |
| 27 | .. blockdiag:: |
| 28 | |
| 29 | |
| 30 | blockdiag layers { |
| 31 | orientation = portrait |
| 32 | a -> m; |
| 33 | b -> n; |
| 34 | c -> x; |
| 35 | m -> y; |
| 36 | m -> z; |
| 37 | group l1 { |
| 38 | color = blue; |
| 39 | x; y; z; |
| 40 | } |
| 41 | group l2 { |
| 42 | color = yellow; |
| 43 | m; n; |
| 44 | } |
| 45 | group l3 { |
| 46 | color = orange; |
| 47 | a; b; c; |
| 48 | } |
| 49 | |
| 50 | } |
| 51 | |
| 52 | |
| 53 | Logging & Diagnostic Information |
| 54 | -------------------------------- |
| 55 | Description of how to interact with and diagnose problems with the components in the run-time packaging. |
| 56 | |
| 57 | |
| 58 | Installation |
| 59 | ------------ |
| 60 | Steps to Install |
| 61 | |
| 62 | |
| 63 | Configuration |
| 64 | ------------- |
| 65 | Where are they provided? |
| 66 | What are parameters and values? |
| 67 | |
| 68 | |
| 69 | Administration |
| 70 | -------------- |
| 71 | |
| 72 | How to run and manage the component. |
| 73 | |
| 74 | |
| 75 | Human Interfaces |
| 76 | ---------------- |
| 77 | Basic info on the interface type, ports/protocols provided over, etc. |