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: 07/XX/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 | |
Einav Keidar | einavk | einavw@amdocs.com | |
Yuli Shlosberg | ys9693 | ys9693@att.com | |
Inna Manzon | im453s | im453s@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. (
- Latest Architecture documentation : ARC SDC Component Description - Frankfurt (Copy)
Artifact Information:
SDC project portal includes a lot of artifact, information and documentation :
Service Design and Creation (SDC) Portal
Tutorials, Guides, walkthrough, Test cases, Feature description, API doc and Subproject links
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 stives to adhere to ONAP code quality by improving its codebase with each release.
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)