Project Maturity Review for CCSDK
- Dan Timoney
- cl664y@att.com
- 1 Information for PTL
- 2 Review Submission Date:
- 3 Project Description:
- 4 Project Landing Page: CCSDK : Common Controller SDK Project Landing Page
- 5 Project Meeting Minutes: CCSDK/SDNC Weekly Meeting Agenda/Minutes
- 6 Leadership Resources :
- 7 Project & Release History
- 8 Architecture Alignment:
- 9 Artifact Information:
- 10 Other Information:
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:
This project provides a common set of reusable code that can be used across multiple controllers. The code could be used in other components but would not be an end solution for use cases by itself and would not be deployed on its own.
For example, the SDN-C , APP-C, DCAE, ONAP Operations Manager and ONAP controller can reuse common pieces from this framework.
While controllers are encouraged to use the common controller SDK libraries, usage of this common code is optional.
Our goal is to provide code that is sufficiently flexible that there is no need for controllers to implement their own custom solutions, but we recognize that there are valid reasons why specific controllers might need to implement their own solutions and would not prevent them from doing so.
Project Landing Page: CCSDK : Common Controller SDK Project Landing Page
Project Meeting Minutes: CCSDK/SDNC Weekly Meeting Agenda/Minutes
Leadership Resources :
Role | Name | Linux Foundation Login (LFID) | Email Address |
|---|---|---|---|
PTL | @Dan Timoney | djtimoney | dtimoney@att.com |
Committers | @Jack Lucas | jackl | |
@jh245g@att.com | jh245g | ||
@gaurav.agrawal | agrawalgaurav | ||
@brindasanth | brindasanthm | ||
@nullop | nullop | ||
@Kapil Singal (Deactivated) | kasingal |
Project & Release History
CCSDK has been active since ONAP launch, and remains active in the current ONAP release (Guilin).
Release name and timeframe | commits | contributors | companies |
|---|---|---|---|
Amsterdam ( 1/1/2017 to 11/16/2017 ) | 439 | 28 | 8 |
Beijing ( 11/17/2017 to 6/7/2018 ) | 317 | 22 | 6 |
Casablanca ( 6/8/2018 to 11/30/2018 ) | 735 | 37 | 10 |
Dublin ( 12/1/2018 to 7/9/2019 ) | 1512 | 57 | 15 |
El Alto ( 7/10/2019 to 10/24/2019 ) | 642 | 41 | 13 |
Frankfurt ( 10/25/2019 to 6/18/2020 ) | 872 | 60 | 14 |
The following diagram from the ONAP bitergia shows the activity in CCSDK for the past 2 years:
112 authors representing 17 companies have contributed to CCSDK over the past 2 years.
The most active area in the CCSDK project has ben the Controller Design Studio (CDS). The following diagram shows the level of community engagement in CDS:
CCSDK is used in the following use cases:
vFW
vDNS
vCPE
VoLTE
CCVPN
5G
Architecture Alignment:
CCSDK was last reviewed with the Architecture subcommitee in January 2020 - see CCSDK R6 Frankfurt Architecture Review
Artifact Information:
The list of CCSDK artifacts and their current release versions are contained in the CCSDK release notes (https://docs.onap.org/projects/onap-ccsdk-distribution/en/latest/release-notes.html)
CCSDK docker containers : https://docs.onap.org/projects/onap-ccsdk-distribution/en/latest/release-notes.html#docker-containers
CCSDK maven artifacts : https://docs.onap.org/projects/onap-ccsdk-distribution/en/latest/release-notes.html#maven-artifacts
CCSDK has provided the base platform used by the SDNC and APPC projects since ONAP inception.
Other Information:
Code Coverage stats: https://sonarcloud.io/organizations/onap/projects?search=ccsdk
Platform Maturity: Frankfurt Release Platform Maturity
CII badging status :
The Controller Design Studio (CDS) - which is part of CCSDK - came in first in the Dublin demo poll. For more information about CDS, please see Read The Docs : CDS