Page Comparison

DRAFT  - as of 3/1 

1. Project Overview

   CLAMP is the place where you manage the runtime of the Control loop(distributed by SDC) in ONAP:
2. you can configure the parameters of the µS composing the Control Loop:
   1. this is achieved by creating/updating/deleting policies (configuration policies).
   2. the above policies will be associated to the deployed µS
3. you can configure the Operation to be taken by the Control Loop:
   1. this is achieved by creating/updating/deleting policies (operational policies).
4. you can deploy/un-deploy Control Loop flow(blueprint) to DCAE. 
in separated/independent Docker containers, you have the "Control Loop Dashboard" which is an ELK stack dedicated to display DMAAP messages related to runtime control loop messages (from DCAE/Policy/APPC).

DCAE includes number of components collectively fulfilling the role of Data Collection, Analytics, and Events generation for ONAP.  The architecture of DCAE targets flexible, plug-able, micros-service oriented, model based component deployment and service composition.  DCAE also support multi-site collection and analytics operations which are essential for large ONAP deployments. 

DCAE components generally fall into two categories: DCAE Platform Components and DCAE Services Components.

DCAE Platform refers the set of controller components which manages the deployment and LCM of the DCAE service components which include all the collectors, analytics and event processor MS. 

 

5. New component capabilities for Dublin, i.e. the functional enhancements

   1. introduction of the model driven approach for Control Loops

      1. add policy-model to the SDC distribution
      2. automatic rendering of configuration policy ui based on the distributed policy-model 
      3. better rendering of the display of the Control Loop flow based on the distributed blueprint
   2. enhance internal model to better support model driven approach
    

6. New or modified interfaces

   1. User interface generation will stay the same  even though its generation method will change.
   2. Some new internal interface will be created to support the new internal model. those new interface won't be backward compatible since they will be new
      and they are internal anyway(so it won't disturb any other project).
     

7. Interface naming

   CLAMP supports the following interfaces:
   

   1. Control Loop Life Cycle Management User interface (LCM UI) for:
      1. selecting the Control Loop flow.
      2. entering configuration policy parameter.
      3. entering operational policy parameter.
      4. manage lifecycle of DCAE blueprint (Control Loop flow).
   2. Control Loop dashboard User Interface based on "Kibana" (ELK stack, completely independent from LCM UI). 
    

8. Reference to the interfaces

   1. for the UI see readthedocs(obviously still under development for Dublin) : CLAMP latest user guide

   2. internal interface are available via swagger : clamp swagger pdf

9. What are the system limits

10. none so far, CLAMP is not a in the path of runtime call, so it is not heavily hit by massive amount of call. So auto scaling is not really required
    but could be added.

11. DB redundancy/HA relies on kubernetes and persistent volume. mariaDB cluster can be a future improvement

Application redundancy/HA relies on kubernetes.

Collectors

RESTConf collector            

Event Processors

VES/Universal Mapper 
3gpp PM-Mapper  
BBS Event processor
DL Handlers (POC)

Analytics/RCA


SON-Handler (former PCI-Handler)
Heartbeat (STRETCH GOAL) 
TCA-Gen2  (STRETCH GOAL)


 

12. New or modified interfaces

  <include arc diagram>

13. Interface naming

                 <refer m1>

14. Reference to the interfaces

    
    

15. What are the system limits

    Relies on k8s for loadbalancing and scaling. DCAE platform handles the control flow and do not carry the data/event; DCAE service components can be scaled and support state management.
    Cloudify is 3rd party product; HA feature on community version will be available later in 2019; will be incorporated for E release
    
    

16. Involved use cases, architectural capabilities or functional requirements

17. scaling use cases

model driven Control Loop: Model driven Control Loop Design

1. Usecases

   •5G Use Case (Dublin)
   •5G - Bulk PM (Casablanca carry-over items)
   •5G - OOF and PCI (Casablanca carry-over items)
   •BBS Broadband Service Use Case (Dublin)
   •CCVPN (E-LAN Service (EP-LAN, EVP-LAN) *, https://wiki.onap.org/pages/viewpage.action?pageId=45296665
   •Model Driven Control Loop Requirements

2. DL POC
   
   

Listing of new or impacted models used by the project (for information only)

1. None

   Support for new policy model as required by Model driven control loop requirement.