This table summarizes each project's plan in regard to support of "Platform Maturity" in Honolulu Release. The data below are extracted from each project plan.
The Platform Maturity recommendations are documented in Platform Maturity Requirements (and sub-pages) from djhunt
Legend
Color code:
- Red: below maturity level from previous release
- Yellow: same maturity level than previous release.
- Green: improved maturity level from previous release
M2 Actual represents the assessment before M2 (from previous release or the starting point for a new project).
M2 Target represents, at M2 date (spec freeze) what the team plans to implement.
M3 result (code freeze) represents what has been really implemented at M4 date . All these fields are self-assessed by the team.
CII Badging Tracking: http://tlhansen.us/onap/cii.html
| AREA | ||||||||||||||||||||||
| Design / Run-Time | (min: Level 2 for closed-loop project; 0 for others) | (min: level 2 all projects) | (min: level 2 for runtime, level 1 others) | (min: Project Level 2, 70% at silver) | (min: level 1 for runtime projects) | (min: level 2 all projects) | (min: level 2 all projects) | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Min TSC Recommendations | M2 Actual | M2 Target | M3 result (code freeze) | M2 Actual | M2 Target | M3 result | M2 Actual | M2 Target | M3 result | M2 Actual | M2 Target | M3 result | M2 Actual | M2 Target | M3 result | M2 Actual | M2 Target | M3 result | M2 Actual | M2 Target | M3 result | |
| Project Name | ||||||||||||||||||||||
| A&AI | R | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | 2 | 1+ (75% toward silver) | 1+ (75% toward silver) | 1+ (75% toward silver) | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
| Common Controller SDK | R | 0 | 0 | 0 | NA | NA | 1 | 2 | 2 | 2 | 1+ (75% towards silver) | 1+ (75% towards silver) | 1+ (75% towards silver) | NA | NA | NA | 2 | 2 | 2 | 2 | 2 | 1 |
| CPS | R | 0 | 0 | 0 | 1 (Note #4) | update after RC0 because CSP is New | 0 | 1 (Stretch 2) | update after RC0 because CSP is New | 1+ (90% towards silver) | 2 | 2 (90% towards silver) | 0 | 0 | 0 | 2 | 2 | 2 | 0 | 1 (Stretch 2) | 1 | |
| DCAE | D & R | 1 | 1 | 1 | 2 | 2 | 2 | 2 | 2 | 2 | 1+ (84% Silver) | 1+ (84% Silver) | 1+ (95% Silver) | 1 | 1 | 1 | 1+ | 1+ | 1+ | 1+ (Note#1) | 1+ | 1+ |
| DMaaP | R | 1 | 1 | 1 | 2 | 2 | 2 | 2 | 2 | 2 | 1+ | 1+ | 1+ | 1 | 1 | 1 | 1+ | 1+ | 1+ | 1 | 1 | 1 |
| External API Framework | R | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 1+ | 1+ | 1+ | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | 2 |
| Holmes | R | 2 | 2 | 2 | 1 | 1 | 1 | 1+ | 1+ | 1+ | 1+ | 1+ | 1+ | 1 | 1 | 1 | 1 | 1 | 1 | 1+ | 1+ | 1+ |
| Microservices Bus | R | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 1 | 1 | 1 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 |
| Modeling | D/R | 1 | 1 | 1 | 2 | 2 | 2 | 2 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | 2 | 2 | 2 | 2 |
| Multi VIM/Cloud | R | 1 | 1 | 1 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | 2 |
| ONAP CLI | D & R | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | 2 | 1.5 Note #2 | 1.5 Note #2 | 1.5 Note #2 | 1 | 1 | 1 | 1 | 1 | 1 | 2 (Note #2) | 2 (Note #2) | 2 |
| ONAP Optimization Framework | R | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | 2 | 1+ (84% towards silver) | 1+ (84% towards silver) | 1+ (85% towards silver) | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
| ONAP Usecase UI Project | R | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | 2 |
| Policy Framework Project Proposal | D & R | D: 1 R: 2 | D: 1 R: 2 | D: 1 R: 2 | 2 | 2 | 2 | D: 2 R: 2 | D: 2 R: 2 | D: 2 R: 2 | 2 (silver) | 2 | 2 (57% towards gold) | 1 | 1 | 1 | 2 | 2 | 1 | 2 | 2 | 2 |
| SDN-C | R | 0 | 0 | 0 | 1 | 1 | 1 | 2 | 2 | 2 | 1+ (75% towards silver) | 1+ (75% towards silver) | 1+ (75% towards silver) | 1 | 1 | 1 | 2 | 2 | 2 | 2 | 2 | 2 |
| Service Design & Creation | D | 0 | 0 | 0 | 2 | 2 (Note #4) | 2 (Note #4) | 1 | 1 | 1 | 1 (Note #5) | 1 | 1 (Note #5) | 1 | 1 | 1 | 1 (Note #6) | 1 | 1 (Note #6) | 1 | 1 | 1 |
| Service Orchestrator | R | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | 2 | 1+ (89% towards Silver) | 1+ | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
| VFC | R | 1 | 1 | 1 | 2 | 2 | 2 | 2 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | 2 | 2 | 2 | 2 |
| VID | R | 0 | 0 | 0 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 1 | 1 | 1 | 2 | 2 | 2 | 2 | 2 | 2 |
| VNF SDK | D | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 1.5 | 1.5 | 1.5 | 1 | 1 | 1 | 1 | 1 | 1 | 2 (Note #7) | 2 | 2 |
Note 1: Level2 - Swagger definition completed; new component API's standardized with ONAP API Common Versioning Strategy and some existing component (VESCollector) updated
Note 2: CLI https enabled, direct vaulnerability cleared with avaiable new 3rd party versions, but silver badge is not applied yet. so given with 1.5. increased manageability by providing additional commands already. usability increased with provided web console, linux console and direct mode
Note 3: Angular upgrade Completed, Security updates planned in Guilin release for Portal.
Note 4: Assumption is that platform 72 hour test is run by Integration team
Note 5: plus AAF-generated certificate and HTTPS mode by default.
Note 6: logging spec very close to 1.2;
Note 7: VNFSDK integrate OPNFV Dovetail and ONAP CLI to run the xNF Test cases and VNFSDK also have a portal to trigger the tests.