Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »


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 Meeting Minutes

Leadership Resources :


Role

Name
(must use @ macro )

Linux Foundation Login (LFID)

Email Address 
(if different from @ macro)

PTL

Dan Timoney

djtimoneydtimoney@att.com
Committers

Jack Lucas

jackljflucas@research.att.com

jh245g@att.comjh245gjh245g@att.com

gaurav.agrawalagrawalgauravgaurav.agrawal@huawei.com

brindasanthbrindasanthmbrindasanth@in.ibm.com

nullopnullopks6305@att.com

Kapil Singal (Deactivated)kasingalkaggarwal@in.ibm.com

Project & Release History

CCSDK has been active since ONAP launch, and remains active in the current ONAP release (Guilin).

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.

CCSDK is used in the following use cases:

  • vFW
  • vDNS
  • vCPE
  • VoLTE
  • CCVPN
  • 5G

Architecture Alignment:

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 has provided the base platform used by the SDNC and APPC projects since ONAP inception.

Other Information:

The Controller Design Studio (CDS) - which is part of CCSDK - came in first in the Dublin demo poll.



  • No labels