Information for PTL
This template is to be filled out for any project wishing to move to the "Mature" phase of the ONAP project lifecycle.
Once completed, remove this info box and the send the link for this page to onap-tsc@lists.onap.org to initiate the maturity review.
Per the ONAP Technical Community Document, the metrics for maturity review are:
›Successful participation in releases: The project demonstrates stable output (code base, documents) within its history of releases in accordance with the release policy.
›Architecture has been reviewed by the Architecture Committee
›Project is active and contributes to ONAP: The project demonstrates a stable or increasing number of contributions across recent releases. Contributions are commits which got merged to a repository of an ONAP project or a related upstream project. Commits can for example be patches to update the requirements document of a project, code addition to an ONAP or upstream project repository, new test cases and so forth.
›Mature artifacts produced: The project demonstrates that the artifacts produced by the project are deployable (where applicable) and have been successfully deployed, configured and used by end users (typically, service providers).
Review Submission Date:
Project Description:
CLAMP is a platform for designing and managing control loops. It is used to design a closed loop, configure it with specific parameters for a particular network service, then deploying and undeploying it. Once deployed, the user can also update the loop with new parameters during runtime, as well as suspending and restarting it.
Project Landing Page: CLAMP Project
Project Meeting Minutes: [clamp] Team ONAP9, Wed UTC 13:00 / China 21:00 / Eastern 09:00 / Pacific 06:00
Leadership Resources :
add lines if necessarry
Role | Name | Linux Foundation Login (LFID) | Email Address |
|---|---|---|---|
| PTL | |||
| Committers | Sebastien Determe | ||
| Xue Gao | |||
| Eddy HAUTOT | ehautot | eddy.hautot@intl.att.com |
Project & Release History
- How long the project has been an active: At launch of ONAP the date is 5th of November 22017
- Release Participation: All ONAP Releases (Amsterdam Release through Frankfurt Release)
- Engagement levels for past releases (up to 3):
- Commits per Release:
- Contributors per Release:
- Companies per release:
Statistics taken from Bitergia : https://onap.biterg.io/app/kibana#/dashboard/Overview
Release name and timeframe commits contributors companies Amsterdam ( 1/1/2017 to 11/16/2017 ) 191 13 4 Beijing ( 11/17/2017 to 6/7/2018 ) 275 11 5 Cassablanca ( 6/8/2018 to 11/30/2018 ) 118 9 4 Dublin ( 12/1/2018 to 7/9/2019 ) 263 18 6 El Alto ( 7/10/2019 to 10/24/2019 ) 130 5 2 Frankfurt ( 10/25/2019 to 6/18/2020 ) 273 14 2 - Use Cases:
- ScaleOut Use Case