Versions Compared

Key

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

...

  1. Designing the Control Loop:
    1. Model based (based on templates)
    2. Re-usable designs
  2. Configuring the Control Loop:
    1. VNF driven, future should be SERVICE driven
    2. Defining threshold values…
  3. Deploying the Control Loop:
    1. Sending template towards DCAE, Policy, …
  4. Lifecycle Management of the Control Loop:
    1. Stopping/re-starting/updating
    2. Monitoring (visualization of the Loop)
    3. Trial mode, production mode, ….(future)
    4. Activation (manually, triggered by policy, tied to the vnf startup, ….still to be defined)


 Architecture Alignment


•CLAMP depends/interact with SDC, DCAE and Policy.
•CLAMP is separated in 2 areas:
•Design Time(Cockpit/UI to define the templates)
•Templates are pushed to SDC
•Run time(DCAE-Policy, grabbing events and triggering policies based actions)

...

•Primary Contact Person:

  NGUEKO Gervais-Martial (AT&T) (gerrit id’s ????)


Other Contact/Contributor Person:

  • SHACHAM Ron (AT&T)
  • BHATNAGAR Aayush (Reliance Jio)
  • NGUYEN Trung (Amdocs)


Other Information's


•The proposal is coming from the AT&T CLAMP project. Before publishing the codebase as part of release 1, AT&T will make sure that all proprietary trademarks, logo’s, etc… are removed.
•The code will also of course goes through Fossology , BlackDuck and other scan to ensure licensing issues are not present.




...