Page Comparison

...

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 Release table below
  • Companies per release: 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

...

• 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.