Project Maturity Review for SDC
- ChrisC
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 D /2020
Project Description:
Provides a well-structured organization of visual design & testing tools, templates and catalogs to model and create resources, and services. The output of the SDC is a set of models which drives the orchestration
Project Landing Page: Service Design and Creation (SDC) Portal
Project Meeting Minutes: SDC Meetings
Leadership Resources :
Role | Name | Linux Foundation Login (LFID) | Email Address |
|---|---|---|---|
| PTL | os0695 | ofir.sonsino@intl.att.com | |
| Committers | Eli Levy | el489u | el489u@intl.att.com |
| Ilana Paktor | ilanap | ilanap@amdocs.com | |
| Ojas Dubey | Ojas Dubey | ojas.dubey@amdocs.com | |
| xuegao | xue.gao@intl.att.com | ||
| Yuli Shlosberg | ys9693 | ys9693@att.com | |
| Inna Manzon | im453s | im453s@intl.att.com | |
| ChrisC | christophe.closset@intl.att.com | ||
| JulienBe | julien.bertozzi@intl.att.com | ||
| sebdet | sebastien.determe@intl.att.com |
Project & Release History
- How long the project has been an active: At launch
- Release Participation: All ONAP releases
- Engagement levels for past releases (up to 3):
- Commits per Release:
- Contributors per Release:
- Companies per release:
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 ) | 754 | 54 | 8 |
| Beijing ( 11/17/2017 to 6/7/2018 ) | 1112 | 57 | 8 |
| Cassablanca ( 6/8/2018 to 11/30/2018 ) | 784 | 56 | 10 |
| Dublin ( 12/1/2018 to 7/9/2019 ) | 501 | 58 | 13 |
| El Alto ( 7/10/2019 to 10/24/2019 ) | 242 | 31 | 9 |
| Frankfurt ( 10/25/2019 to 6/18/2020 ) | 550 | 48 | 13 |
- Use Cases: SDC is pretty much involved in all use cases, since it's the entry point for models to be loaded into the system
Architecture Alignment:
- Latest review (Dublin) happened on : 3/6/2019 SDC Dublin Architecture Review
- Note that one is planned for Guilin. ( ARC SDC Component Description - Guilin (R7) Release)
- Latest Architecture documentation : ARC SDC Component Description - Frankfurt (Copy)
Artifact Information:
Codes:
sdc SDC Parent Project Catalog FE and BE sdc/dcae-d/ci DCAE Designer End To End Testing suite sdc/dcae-d/dt DCAE tab ui designer sdc/dcae-d/dt-be-main DCAE Designer Back End Logic sdc/dcae-d/dt-be-property DCAE Designer common datatypes and properties sdc/dcae-d/fe DCAE Designer Front End UI sdc/dcae-d/rule-engine DCAE Designer Rule Engine Front End UI sdc/dcae-d/tosca-lab DCAE Designer Tosca Lab tool to create Blueprint and Generate Tosca models sdc/jtosca A generic TOSCA parser based on the TOSCA 1.1 spec Marked read-only as per IT-18170 sdc/microservices SDC microservices placeholder sdc/onap-ui UI library containing different components, fonts and styles used by SDC and the different designers in order to create a single look and feel across SDC sdc/onap-ui-angular An Angular UI library containing different components, fonts and styles used by SDC and the different designers in order to create a single look and feel across SDC sdc/onap-ui-common A common UI library containing different components, fonts and styles used by SDC and the different designers in order to create a single look and feel across SDC sdc/onap-ui-react A React UI library containing different components, fonts and styles used by SDC and the different designers in order to create a single look and feel across SDC sdc/oom SDC OOM placeholder sdc/sdc-be-common SDC BE common tooling sdc/sdc-distribution-client SDC Distribution Client sdc/sdc-docker-base SDC base docker creation project sdc/sdc-pubsub Publish Subscribe library using post message for sdc plugins. sdc/sdc-titan-cassandra SDC Rebase Cassandra Marked read-only as per IT-18170 - documentations:
- SDC Overview :https://docs.onap.org/projects/onap-sdc/en/latest/index.html#master-index
- SDC interfaces: https://docs.onap.org/projects/onap-sdc/en/latest/offeredapis.html
- SDC User Guide (SDC is part of the design of VF, VNF, Worflows): https://docs.onap.org/en/latest/guides/onap-user/design/index.html
- SDC containers : https://docs.onap.org/projects/onap-sdc/en/latest/delivery.html#sdc-dockers-containers
- SDC tutorials : SDC Tutorials
- And much more :
Service Design and Creation (SDC) Portal
Tutorials, Guides, walkthrough recorded sessions, Test cases, Feature description, API doc and Subproject links
- SDC project team members, contributed, in all ONAP release, in the successfull completion of integration team testing
- To our knowledge, the following companies have used ONAP SDC and are actively involved in :
Amdocs – Workflow designer, onboarding
Ericsson – ETSI packages (SOL00x) support, CSIT
Yoppworks/Bell – refactoring, Java 11
Samsung – Python 3, unit tests
Nokia – CDS integration, 5G use cases such as PM dictionary
Also: Telstra, Fujitsu, Intel, Orange, CMCC, Huawei...
SDC is involved in use case testing as the main design tool, automated testing as part of integration runs and gating checks to verify healthy artifacts distribution is often seen as the green indicator for design time success.
SDC is being used in production deployement in several companies, has been used as a demo tool and is involved as the main model entrypoint successfully since ONAP launch.
Other Information:
- SDC codebase is quite huge, countening several hundred thousands of lines. Still SDC strives to adhere to ONAP code quality by improving its codebase with each release and still plans to improve.
Many different companies have already contributed to SDC, showing the interest of the community for the project. SDC is also a starting point to discuss standards and implement representations of xNFs (as we've seen over several releases)
- SDC is involved in many ONAP features and has a rich interaction with other projects as demonstrated by the following feature discussions that happened over the last few years
- Features Meetings