Page Comparison

...

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:

...

›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

...

meetings and minutes

Leadership Resources :

...

Role	Name (must use @ macro )	Linux Foundation Login (LFID)	Email Address  (if different from @ macro)
PTL	Gervais-Martial Ngueko	osgn422w
Committers	Sebastien Determe	sebdet
	Xue Gao	xuegao
	ChrisC	ChrisC
	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:  see Release table below
  • Contributors per Release: see  see Release table below
  • Companies per release: see  see Release table below

    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: 
  • Scale Out Use Case 
  • Self Serve Control Loop

...

• last architecture review done on 7th of October 2019: ARC CLAMP Component Description - Frankfurt

Artifact Information:

• codes:
  • https://gerrit.onap.org/r/admin/repos/clamp
  • https://gerrit.onap.org/r/admin/repos/clamp/dashboard
• documentations:
  • CLAMP Overview : https://docs.onap.org/projects/onap-clamp/en/latest/index.html#master-index
  • CLAMP internal interfaces:  https://docs.onap.org/projects/onap-clamp/en/latest/_downloads/d25f20712a4cf2524a1cf13242349743/swagger.pdf 
  • CLAMP User Guide: https://docs.onap.org/projects/onap-clamp/en/latest/user-guide.html#
• CLAMP project team members, contributed, in all ONAP release, in the successfull completion of  integration team testing (for Scale out Use case)
• To our knowledge, the following companies have used ONAP CLAMP internally: AT&T, Ericsson, Orange, Tech Mahindra, Nokia, Samsung

Other Information:

• CLAMP hosted a booth and made a demo during 2018 Amsterdam ONS: https://events19.linuxfoundation.org/events/open-networking-summit-europe-2018/program/schedule/
• CLAMP had topic (unconference topic) during the 2019 Antwerpen DDF: https://events19.linuxfoundation.org/events/onap-ddf-opnfv-plugfest/
• CLAMP team has received kudos from the security subcommittee(Paweł Pawlak ), for the El Alto and Frankfurt releases, for the Effort put in reaching compliance with S3P recommendations in both of those releases.
• Current, as of today, ccode coverage is 73% see screenshot:
  Image Added

• Control Loop Sub Committee:

  The CLAMP Project has been active in the Control Loop subcommittee from its inception. Working very closely with Policy Framework and DCAE to support the automation and enhancement of Control Loops in ONAP.

  The project shares weekly meetings with the Policy Framework Project.