This table summarizes the plan in regard to support of "Platform Maturity" for each project in Beijing Release. The data below are extracted from each project plan.
The Platform Maturity recommendations are documented in "Platform Maturity Status" from Jason Hunt
Legend
Color code:
Yellow: same maturity.
Green: improved maturity level.
Red: below maturity level
| AREA | ||||||||||||||||||||||
| Design / Run-Time | Performance | Stability | Resiliency | Security | Scalability | Manageability | Usability | |||||||||||||||
| Min TSC Recommendations | Min Runtime: 1 Min Remaining: 0 | Min all projects: 1 | Min Runtime: 2 Min Remaining: 1 | Min all projects: 1 | Min Runtime: 1 Min Remaining: 0 | Min all projects: 1 | Min all projects: 1 | |||||||||||||||
| Project Name | Actual | Target | M4 result | Actual | Target | M4 result | Actual | Target | M4 result | Actual | Target | M4 result | Actual | Target | M4 result | Actual | Target | M4 result | Actual | Target | M4 result | |
| A&AI | R | 0 | 1 | 0 | 1 | 1 | 2 | 0 | 1 | 0 | 1 | 1 | 1 | 1 | 1 | |||||||
| Application Authorization Framework | R | 0 | 1 | 0 | 1 | 1 | 2 | 0 | 1 | 0 | 1 | 1 | 1 | 1 | 1 | |||||||
| APPC | R | 0 | 0 | 0 | 1 | 1 | 2 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||
| CLAMP | D | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
| Common Controller SDK | R | 0 | 0 | 0 | NA Note 2 | 1 | 2 | 0 | 1 | 0 | NA Note 3 | 1 | 1 | 1 | 1 | |||||||
| DCAE | R | 1 | 1 | 1 | 2 | 1 | 2 Note 1 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | |||||||
| DMaaP | R | 0 | 1 | 1 | 1 | 2 | 2 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | |||||||
| Documentation | NA | Oversee documentation from all other projects that support their maturity commitments | 1 | 2 | ||||||||||||||||||
| External API Framework | R | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | |||||||
| Holmes | R | 0 | 1 | 0 | 1 | 0 | 2 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | |||||||
| NA | Integration Team will perform overall E2E testing with the 4 use cases. | |||||||||||||||||||||
| Logging Enhancements Project | R | 0 | 0 | 1 | 1 | 2 | 2 Note 4 | 0 | 0 | 1 | 1 | 1 | 1 | 0 | 1 | |||||||
| Microservices Bus | R | 0 | 1 | 0 | 1 | 1 | 2 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||
| Modeling | D | 0 | 1 | 1 | 1 | 1 | 2 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | |||||||
| Multi VIM/Cloud | R | 0 | 1 | 0 | 1 | 1 | 2 | 0 | 1 | 1 | 1 | 0 | 1 | 2 | 2 | |||||||
| MUSIC | R | 1 | 1 | 1 | 1 | 1 | 2 | 2 | 2 | 0 | 1 | 1 | 1 | 1 | 1 | |||||||
| ONAP CLI | D & R | 0 | 1 | 0 | 1 | 1 | 2 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | |||||||
| ONAP Operations Manager | R | 1 | 1 | 0 | 1 | 1 | 2 | 1 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | |||||||
| ONAP Optimization Framework | R | 0 | 1 | 0 | 1 | 1 | 2 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | |||||||
| ONAP Usecase UI Project Proposal | D | 0 | 1 | 0 | 1 | 1 | 2 | 0 | 1 | 0 | 0 | 0 | 1 | 1 | 1 | |||||||
| Policy Framework Project Proposal | D & R | 1 | 1 | No work done | 1 | 1 | No work done | 1 | 2 | WIP | 1 | 1 | 1 | 0 | 1 | WIP | 1 | 1 | WIP | 1 | 1 | WIP |
| Portal Platform Project Proposal | D & R | 0 | 1 | 1 | 1 | 1 | 2 | 0 | 1 | 0 | 1 | 1 | 1 | 1 | 2 | |||||||
| SDN-C | R | 0 | 0 | 0 | 1 | 1 | 2 | 0 | 1 | 0 | 1 | 1 | 1 | 1 | 1 | |||||||
| Service Design & Creation | D | 0 | 0 | 0 | 1 | 1 | 1 | 0 | 1 | 0 | 0 | 0 | 0 Note 5 | 0 | 1 | |||||||
| Service Orchestrator | R | 0 | 1 | 0 | 1 | 1 | 2 | 0 | 1 | 0 | 1 | 0 | 1 | 0 | 1 | |||||||
| VFC | R | 0 | 1 | 0 | 1 | 1 | 2 | 0 | 1 | 0 | 1(*) Note 6 | 0 | 1 | 1 | 1 | |||||||
| VID | R | 0 | 1 | 0 | 1 | 1 | 2 | 0 | 1 | 0 | 1 | 0 | 0 Note 5 | 1 | 1 | |||||||
| VNF SDK | D | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 0 | 1 | 1 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 1 |
| VNF Requirements | NA | NA. VNFRQTS is primarily a documentation project and does not deliver ONAP platform code | 1 | |||||||||||||||||||
| VNF Validation (VVP) | D | |||||||||||||||||||||
Note 1: For DCAE the plan is to meet level 2 for DCAE components that can be made into docker containers, but for those components that cannot, it will depend on upstream providers (i.e. Cloudify Manager and CDAP). During M1 review, TSC agree with level 2 ok with exception granted for cloudify
Note 2: For CCSDK, as a project that provides a library framework, CCSDK has no standalone component that can be soaked
Note 3: Scaling does not apply to CCSDK itself, as a set of libraries.
Note 4: LOG: standard OOB OOM Kubernetes resilience/stability
Note 5: SDC and VID. For Manageability, instantiation in < 1 hour is already supported. No plan to support single loging in Beijing.
Note 6: Due to lack of resources, VF-C may not achieve scalability level 1 for all components in this release and plans to support scalability level 1 for part of components first.