Versions Compared

Old Version 31

changes.mady.by.user Gervais-Martial Ngueko

Saved on

compared with

New Version 32

changes.mady.by.user Gervais-Martial Ngueko

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

  1. Project Name:

  • Proposed name for the project: CLAMP
  • Proposed name for the repository: (org.onap.)clamp

...

      vFW Control Loop design will consist of:

    1. create the blueprint for DCAE to capture traffic level .
    2. create the policy that will define theshold signature that DCAE will use.
      1. DCAE team provides model to Policy team to built the Configuration policy
    3. create the policy that will trigger traffic gen to lower traffic.

      vDNS Control Loop design will consist of:

    1. create the blueprint for DCAE to capture traffic level.
    2. create the policy that will define theshold signature that DCAE will use.
      1. DCAE team provides model to Policy team to built the Configuration policy
    3. create the policy that will trigger SO to spun up a new vDNS vm.


Interfaces:

The following interfaces will be implemented by other components but used for CLAMP.  Therefore, CLAMP has these as dependencies:

...

•CLAMP interfaces with the following ONAP Components: SDC, DCAE and Policy.
  • SDC : Rest based interface exposed by the SDC
  • DCAE: Rest based interface exposed by DCAE
  • Policy: Rest based interface (the Policy team provide a "jar" to handle the communication). 
•CLAMP is separated in 2 areas:
  1. Design Time(Cockpit/UI to define the templates)
    1. Templates are pushed to SDC. The template format is TOSCA blueprint, those blueprints will be pushed/provisioned, by SDC, to DCAE orchestration engine.
    2. policies (configuration and operational policies) are pushed/provisioned towards the Policy Component of ONAP. (those policies will be triggered by DCAE during Closed Loop operations).
      1. The DCAE team needs to provide models to Policy team in order for the Configuration policy to be built. 
  2. Run time(DCAE-Policy, grabbing events and triggering policies based actions)
    1. In the first release of CLAMP, the triggering to deploy(and then effectively start the closed loop)  a blueprint will be manual (via CLAMP cockpit)
      an automatic deployment based on an event will come in future release.
    2. The CLAMP cockpit will support the following action at runtime:
      1. start (start the provisioned Closed Loop on DCAE)
      2. stop (stop a provisioned Closed loop on DCAE)


...