...
The Platform Maturity recommendations are documented in "Platform Maturity Status" from djhunt
Tip | ||
---|---|---|
| ||
Color code: Yellow: same maturity. Green: improved maturity level. Red: below maturity level M1 Actual represents the assessment before M1. M1 Target represents, at M1 date, what the team plans to implement. M4 result represents what has been really implemented at M4 date . All these fields are self-assessed by the team. |
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 | M1 Actual | M1 Target | M4 result | M1 Actual | M1 Target | M4 result | M1 Actual | M1 Target | M4 result | M1 Actual | M1 Target | M4 result | M1 Actual | M1 Target | M4 result | M1 Actual | M1 Target | M4 result | M1 Actual | M1 Target | M4 result | |
A&AI | R | 0 | 1 | WIP Note 11 | 0 | 1 | WIP Note 11 | 1 | 2 | 2 | 0 | 1 | WIP Note 10 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
Application Authorization Framework | R | 0 | 1 | WIP Note 11 | 0 | 1 | WIP Note 11 | 1 | 2 | WIP Note 11 | 0 | 1 | 0 Note 16 | 0 | 1 | 0 Note 11 | 1 | 1 | 1 | 1 | 1 | 1 |
APPC | R | 0 | 0 | 0 | 0 | 1 | 1Note 12 | 11 | 2 | 2 | 0 | 1 | WIP1 Note 13 | 1 | 1 | 1 Note 14 | 1 | 1 | 1 | 1 | 1 | 1 |
CLAMP | D | 0 | 0 | 0 | 0 | 1 | 1 Note 27 | 1 | 1 | 1 | 0 | 1 | 1 | 1 | 1 | 1 Note 28 | 1 | 1 | 1 | 1 | 1 | 1 |
Common Controller SDK | R | 0 | 0 | 0 | 0 | NA Note 2 | NA Note 2 | 1 | 2 | 2 | 0 | 1 | WIP Note 18 | 0 | NA Note 3 | NA Note 3 | 1 | 1 | 1 | 1 | 1 | 1 |
DCAE | R | 1 | 1 | 1 | 1 | 2 | WIP | 1 | 2 Note 1 | 2 | 0 | 1 | WIP | 0 | 1 | 1 | 0 | 1 | 1 | 1 | 1 | WIP |
DMaaP | R | 0 | 1 | WIP Note7 | 1 | 1 | WIP Note7 | 2 | 2 | 2 | 0 | 1 | WIP Note8 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | WIP Note9 |
Documentation | NA | Oversee documentation from all other projects that support their maturity commitments | 1 | 2 | ||||||||||||||||||
External API Framework | R | 0 | 1 | 1 | 0 | 1 | 1 | 0 | 1 | 1 | 0 | 1 | 1 | 0 | 1 | 1 Note 30 | 0 | 1 | 1 | 0 | 1 | 1 |
Holmes | R | 0 | 1 | WIP | 0 | 1 | WIP | 0 | 2 | 1 | 0 | 1 | WIP Note 19 | 0 | 1 | 1 Note 20 | 0 | 1 | 1 Note 20 | 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 | WIP Note 17 | ||||||
Microservices Bus | R | 0 | 1 | 0 | 1 | 1 | 2 | 0 | 1 | Note15 | 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 | 2 | 2 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||
ONAP CLI | D & R | 0 | 1 | 1 | 0 | 1 | 1 | 1 | 2 | 2 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 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 | WIP Note 111 | 0 | 1 | WIP Note 111 | 1 | 2 | WIP2 | 0 | 1 | 1 | 0 | 1 | 1 WIPNote 30 | 0 | 1 | WIP1 | 1 | 1 | WIP1 |
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 | 1 | 1 | 2 | 2 | 0 | 1 | 1 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 2 |
SDN-C | R | 0 | 0 | 0 | 0 | 1 | WIP | 1 | 2 | 2 | 0 | 1 | WIP Note 21 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
Service Design & Creation | D | 0 | 0 | No work done | 0 | 1 | WIP | 1 | 1 | No work done | 0 | 1 | WIP | 0 | 0 | No work done | 0 | 0 Note 5 | WIP | 0 | 1 | WIP |
Service Orchestrator | R | 0 | 1 | WIP Note 29 | 0 | 1 | WIP Note 29 | 1 | 2 | WIP Intertaring with OOM | 0 | 1 | WIP | 0 | 1 | WIP Intertaring with OOM | 0 | 1 | WIP Intertaring with OOM | 0 | 1 | WIP |
VFC | R | 0 | 1 | WIP | 0 | 1 | WIP | 1 | 2 | 2 | 0 | 1 | Note22 | 0 | 1(*) Note 6 | 0 | 0 | 1 | 1 | 1 | 1 | 1 |
VID | R | 0 | 1 | WIP Note 32 | 0 | 1 | WIP Note 32 | 1 | 2 | WIP Note 31 | 0 | 1 | WIP1 Note26 | 0 | 1 | WIP Note 31 | 0 | 0 Note 5 | WIP0 | 1 | 1 | WIP1 |
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 11: Performance and scalability tests will be performed during integration testingNote 12: 72 hour soak test completed on Amsterdam code base due to defect APPC-658 which prevents DMaaP messages from being received or sent. Test results and notes can be found at: ONAP APPC 72 Hour Stability Test Results. Once DMaaP issue is resolved on Beijing, we will re-run 72 hour soak test.
Note 13: CII Passing is 95%; Code Coverage is at 48.2% and progressing; however, not likely to meet 50% by 3/29over 50% .
Note 14: APPC component is fully scalable via approach of using Kubernetes, APPC instances (N+) can be added to the cluster; however, due to constraints encountered with MySQL DB, the DB is not scalable until we migrate to MariaDB plus Galera (planned for Casablanca per feedback from CCSDK), which would provide the active-active architecture. Further details are tracked under OOM project (OOM-733), who we've been working with.
...
Note 26: VID coverage is 50%, CII Passing is 94%, still working on fixing CLM issues97%
Note 27: CLAMP 72h stability test was performed just after completing work for M4 - see report in subtasks of CLAMP-127
...
Note30: Scalability provided by Kubernetes
Note 31: Tested locally, and submitted to OOM to review
Note 32: As performed by integration team