This table summarizes each project's plan in regard to support of "Platform Maturity" in Dublin Release. The data below are extracted from each project plan.
The Platform Maturity recommendations are documented in Platform Maturity Requirements (and sub-pages) from Jason Hunt
Legend
Color code:
- Red: below maturity level
- Yellow: same maturity.
- Green: improved 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 | 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 | |
| Project Name | ||||||||||||||||||||||
| A&AI | R | 1 | 1 | 1 | 1 | 2 | 2 | 1 | 2 (Stretch goal) | 1 | 1 | 1+ (see note #10) | 1+ (see note #10) | 1 | 1 | |||||||
| Application Authorization Framework | R | 1 | 2 (Stretch Target may not reach) | 2 | 3 excluding test coverage @80% | 2 | 3 | 2 | 2 | 2 | 3 | 1 | 1 | 1 | 2 | |||||||
| APPC | R | 1 | 2 (Stretch Target) | 1 | 1 | 2 | 2 | 1 | 2 (Stretch goal) | 1 | 1 | 1 | 2 (Stretch goal) | 1 | 1 | |||||||
| CLAMP | D | 0 | 0 | 1 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||
| Common Controller SDK | R | 0 | 0 | NA | NA | 2 | 2 | 1 | 1 | NA | NA | 1 | 1 | 1 | 1 | |||||||
| DCAE | D & R | 1 | 1 | 2 | 1 Note#2 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 (STRETCH GOAL) | |||||||
| DMaaP | R | 1 | 1 | 1 | 2 | 2 | 2 | WIP Note #9 | 2 (Stretch goal) | 1 | 1 | 1 | 2 | 1 | 1 | |||||||
| Documentation | NA | |||||||||||||||||||||
| External API Framework | R | 1 | 2 | 1 | 2 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | |||||||
| Holmes | R | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 1 | 1 | 1 | 1 | 2 | |||||||
| NA | ||||||||||||||||||||||
| Logging Enhancements Project | R | 2 | 2 | 2 | 3 | 2 | 2 | 0 | 0 (M4 stretch 1) | 1 | 1 | 1 (see note #8) | 1 | 1 | 1 | |||||||
| POMBA (under but separate pod from Logging) | R | 2 | 2 | 2 | 3 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||
| Microservices Bus | R | 1 | 2 | 1 | 2 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | |||||||
| Modeling | D/R | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 0 | 0 | 1 | 1 | |||||||
| Multi VIM/Cloud | R | 1 | 1 | 1 | 1 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||
| MUSIC | R | 1 | 1 | 1 | 1 | 2 | 2 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||
| ONAP CLI | D & R | 1 | 1 | 1 | 1 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | |||||||
| ONAP Operations Manager | NA | |||||||||||||||||||||
| ONAP Optimization Framework | R | 1 | 1 | 1 | 1 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||
| ONAP Usecase UI Project Proposal | D | 1 | 1 | 1 | 2 | 2 | 2 | 1 | 1+ | 1 | 1 | 1 | 1+ | 1 | 1+ | |||||||
| Policy Framework Project Proposal | D & R | 1+ See Note #5 | 1 | 1 See Note #4 | 1 | 1 See Note #4 | 1 | 1 | 2 (Stretch goal) | 1 See Note #4 | 1 | 1 See Note #6 | 1 | 1 | 1 | |||||||
| Portal Platform Project Proposal | D & R | 1 | 1 See Note #11 | 1 | 1 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | |||||||
| SDN-C | R | 0 | 0 | 1 | 1 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||
| Service Design & Creation | D | 0 | 1 | 1 | 1 | 0 | 0 | 1 | 1 | |||||||||||||
| Service Orchestrator | R | 1 | 1 | 1 | 1 | 2 | 2 | 1 | 2 (Stretch goal) | 1 | 1 | 1 | 1 | 1 | 1 | |||||||
| VFC | R | 1 | 1 | 1 | 1 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||
| VID | R | 0 | 0 | 2 (Note #1) | 2 | 2 | 2 | 1 | 1 | 1 | 1 | 1 (Note #8) | 1 | 1 | 1 | |||||||
| VNF SDK | D | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 0 | 1 | 1 | 1 | 1 | 2 | |||||||
| VNF Requirements | NA | |||||||||||||||||||||
| VNF Validation (VVP) | D | NA | NA | NA | 1 | NA | NA | NA | ||||||||||||||
Note 1: Assumption is that platform 72 hour test is run by Integration team; Component team will run regression (Level 1) on Casablanca release
Note 2: Drop in Stability level due to new requirement for 80% coverage; project team cannot commit due to resource constraint. Level 2 (platform) test will be under Integration team scope
Note 3: SO for security improvement based on the resource availability
Note 4: The policy project added a new application component to support SDC Service Distribution for the HPA Use Case. However, promised resources did not fulfill any of the S3P work for this runtime component.
Note 5: Only the drools PDP had a performance plan improvement. We ran out of time to build a performance plan for XACML PDP. (NOTE: No requirements for brand new Apex PDP, that is targeted for 'E' release).
Note 6: The resources for doing logging v1.2 went away as part of the contract/restructuring between the two corporations early 2018.
Note 8: logging spec and implementation changes done with AT&T/TechMahindra to sync to Acumos - logging resources are absolute minimal during casablanca - 1.2 spec completion is pushed to Dublin
Note 9: AAF CADI integration is pending
Note 10: logging spec very close to 1.2; completion slated for Dublin
Note 11: As per risk# 3 and 4, all the target maturity levels for Portal will remain same as actuals due to resource constraint.