...
- 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)(future not in R1)
- Trial mode, production mode, ….(future not in R1)
- Activation (manually and/or triggered by a policy(future not in R1) and/or tied to the vnf startup(future not in R1))
Architecture Alignment
•CLAMP depends/interacts •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 •CLAMP is separated in 2 areas:
- Design Time(Cockpit/UI to define the templates)
- Templates are pushed to SDC. The template format is TOSCA blueprint, those blueprints will be pushed/provisioned, by SDC, to DCAE orchestration engine.
- policies(operational policies) are pushed/provisioned towards the Policy Component of ONAP. (those policies will be triggered by DCAE during Closed Loop operations).
- Run time(DCAE-Policy, grabbing events and triggering policies based actions)
- 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. - The CLAMP cockpit will support the following action at runtime:
- start (start the provisioned Closed Loop on DCAE)
- stop (stop a provisioned Closed loop on DCAE)
- 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)
...
There is a plan to move the design part of CLAMP towards the "DCAE design Studio" inside SDC, but this won't be in R1, see below:
CLAMP depends upon the following open source projects:
- AJSC 6.0 (container framework based on Spring and developed by "AT&T Common platform" Team)
- AJSC-Camunda 6.0 (Camunda Workflow integration to AJSC container developed by "AT&T Common platform" Team)
Resources
•Primary Contact Person:
NGUEKO Gervais-Martial (AT&T - gn422w@intl.att.com)
Other Contact/Contributor Person:
- SHACHAM Ron (AT&T - rshacham@research.att.com)
- BHATNAGAR Aayush (Reliance Jio - aayush.bhatnagar@ril.com)
- NGUYEN Trung (Amdocs)
- MIAO Xin (Futurewei - xin.miao@huawei.com)
Committers/Maintainers:
- Christophe Closset (AT&T - cc697w@intl.att.com)
- Sebastien Determe (AT&T - sd378r@intl.att.com)
- Pierre Close (AT&T - pc457b@intl.att.com)
- Eddy Hautot (AT&T - eh552t@intl.att.com)
- Xue Gao (AT&T - xg353y@intl.att.com)
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 goes through Fossology , BlackDuck and other scan to ensure licensing issues are not present.
...