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:
The SDN-C project provides a global network controller, built on the Common Controller Framework, which manages, assigns and provisions network resources. As a "global" controller, the SDN-C project is intended to run as one logical instance per enterprise, with potentially multiple geographically diverse virtual machines / docker containers in clusters to provide high availability. The project also supports the ability to invoke other local SDN controllers, including third party SDN controllers.
Project Landing Page: SDNC : Software Defined Network Controller Project Landing Page
Project Meeting Minutes: SDNC Weekly Meetings - ARCHIVE
Leadership Resources :
Role | Name | Linux Foundation Login (LFID) | Email Address |
|---|---|---|---|
| PTL | djtimoney | dtimoney@att.com | |
| Committers | David Stilwell | stilwelld | stilwelld@att.com |
| Prabhu Somasundaram | Prabhu_Ram | ps7551@att.com |
Project & Release History
SDNC 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 SDNC for the past 2 years:
71 authors representing 17 companies have contributed to SDNC over the past 2 years.
SDNC is used in the following use cases:
- vFW
- vDNS
- vCPE
- VoLTE
- CCVPN
- 5G
Architecture Alignment:
- SDNC was last reviewed with the Architecture subcommitee in January 2020 - see SDNC R6 Frankfurt Architecture Review
Artifact Information:
SDNC artifacts are listed in the SDNC release notes:
- SDNC Docker containers : https://docs.onap.org/projects/onap-sdnc-oam/en/latest/release-notes.html#docker-containers
SDNC has participated in every ONAP release as the ONAP network controller since inception.
.
| Release name and timeframe | commits | contributors | companies |
|---|---|---|---|
| Amsterdam ( 1/1/2017 to 11/16/2017 ) | 1137 | 34 | 11 |
| Beijing ( 11/17/2017 to 6/7/2018 ) | 121 | 20 | 7 |
| Casablanca ( 6/8/2018 to 11/30/2018 ) | 311 | 39 | 10 |
| Dublin ( 12/1/2018 to 7/9/2019 ) | 544 | 36 | 17 |
| El Alto ( 7/10/2019 to 10/24/2019 ) | 76 | 12 | 9 |
| Frankfurt ( 10/25/2019 to 6/18/2020 ) | 143 | 25 | 10 |
Note: ONAP bitergia appears to be missing commit data for SDNC prior to Frankfurt. The table above was derived from 'git log' for the sdnc/apps, sdnc/northbound and sdnc/oam repositories.
Other Information:
Code Coverage stats: https://sonarcloud.io/organizations/onap/projects?search=sdnc
Platform Maturity: Frankfurt Release Platform Maturity
CII badging status :
4 Comments
Eric Debeau
Can you provide some information about test coverage ?
Dan Timoney
Sure - sorry, forgot to add that. I added a link to our test coverage info in Sonar above under "Other Information"
Jason Hunt
Hi Dan Timoney- can you please include the chart of commits, contributors, and companies by release? Also, any information about deployment/use of SDNC by operators or others? Thanks!
Dan Timoney
I added a table similar to what we have for CCSDK for commits by release. However, for some reason, it appears that ONAP bitergia is missing a lot of SDNC data from before Frankfurt. I was able to derive that data from git log entries directly, but did want to call your attention to the fact that this data does not match bitergia.