Project Name:
- Proposed name for the project:
CLAMP - Proposed name for the repository: (org.onap.)
clamp
...
Architecture Alignment
•CLAMP depends/interact interacts with SDC, DCAE and Policy.
•CLAMP is separated in 2 areas:
•Design
•Templates - 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
•Run
- , 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)
Resources
•Primary Contact Person:
NGUEKO Gervais-Martial (AT&T)
Other Contact/Contributor Person:
- SHACHAM Ron (AT&T)
- BHATNAGAR Aayush (Reliance Jio)
- NGUYEN Trung (Amdocs)
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 of course goes through Fossology , BlackDuck and other scan to ensure licensing issues are not present.
...