...
- Designing the Control Loop:
- Model based (based on templates)
- Re-usable designs
- Configuring the Control Loop:
- VNF driven, future should be SERVICE driven
- Defining threshold values…
- Deploying the Control Loop:
- Sending template towards DCAE, Policy, …
- Lifecycle Management of the Control Loop:
- Stopping/re-starting/updating
- Monitoring (visualization of the Loop)
- Trial mode, production mode, ….(future)
- 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.
...