You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

This table summarizes each project's plan in regard to support of "Platform Maturity" in El-Alto 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

(min: Level 2 for closed-loop project; 0 for others)

Stability

(min: level 2 all projects)

Resiliency

(min: level 2 for runtime, level 1 others)

Security

(min: Project Level 2, 70% at silver)

Scalability

(min: level 1 for runtime projects)

Manageability

(min: level 2 all projects)

Usability

(min: level 2 all projects)

Min TSC Recommendations
M1 Actual

M1 Target

M4 resultM1 ActualM1 TargetM4 resultM1 ActualM1 TargetM4 resultM1 ActualM1 TargetM4 resultM1 ActualM1 TargetM4 resultM1 ActualM1 TargetM4 resultM1 ActualM1 TargetM4 result
Project Name





















A&AIR1

1

2

1

1

1

(see note #10)



1

Application Authorization FrameworkR11
22
22
22
22

1+ (see Note #11)

1+
1+1+
APPCR0

1

2

2

1

1

1

CLAMPD00
11
11
11
11
11
11
Common Controller SDKR0

NA

2

1

NA

1

1

DCAED & R11
22
22

1+

(see Note#14)

1+
11
11

1+

(see Note#13)

1+
DMaaPR1

1

(see note #15)



2

1+

(see note #16)



1

1+ (see note #17)

1

External API FrameworkR2

2

2

1

1

1

2

HolmesR2

1

1+

1+

1

1

1+

Integration

NANA

2

See note 22)



2

(See note 22)



NA

NA

NA

NA

Logging Enhancements ProjectR2* (unable to test/verify)

2

2

0

1

1 (see note #8)

1

POMBA (under but separate pod from Logging)R      2* (unable to test/verify)

     2

     2

       1

     1

     1

      1

Microservices BusR22
12
22
11
12
12
12
ModelingD/R0

1

1

1

1

0

1

Multi VIM/CloudR11
12
22
12
11
12
12
MUSICR1

1

2

2

2

1

1

ONAP CLI (N/C since Casablanca)D & R1

1

2

1

1

1

2

ONAP Optimization FrameworkR1

1

2

1+ (75% towards silver)

1

1

1

ONAP Usecase UI Project ProposalR1

1

2

1

1

1

1

Policy Framework Project ProposalD & R

D: 1

R: 2



2



D: 2

R: 2



2 (No silver)

1



1+



2

Portal Platform Project ProposalD & R11
11
22
11+
11
11
22+
SDN-CR0

1

2

1

1

1

1

Service Design & CreationD0

1

1

(Note #12)



1

0

1

1

Service OrchestratorR1

1

2

1

1

1

1

VFCR1

1

2

1

1

1

1

VIDR00

2

(Note #1)

2
22
12
11
1 (Note #8)2
12
VNF SDKD0

1

1

1+

(Note #18)



1

1

2

(Note #19)




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 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 10: logging spec very close to 1.2; completion slated for Dublin 

Note 11: Will work Logging Spec in Frankfurt

Note 12: As per risk #25, AAF integration and HTTPS support was postpone to El-Alto due to resources constraint.

Note 13:  Level2 - Swagger definition completed; new component API's standardized with ONAP API Common Versioning Strategy and some existing component (VESCollector) updated

Note 14: CII Passing badge level > 70%; all external ONAP communication interfaces support secure interface. RBAC/CADI integration deferred to next release.

Note 15: Assumption is that the platform level 72 hour testing will be executed by the Integration team.

Note 16: CII silver level > 70%. All external ONAP communication over secure interface. Not all internal communication secure and being deferred to El Alto.

Note 17: MDC and markers to be implemented. Project is already using EELF framework for logging.

Note 18: VNFSDK Already support to expose API via Https

Note 19: VNFSDK integrate OPNFV Dovetail and ONAP CLI to run the xNF Test cases and VNFSDK also have a portal to trigger the tests.

Note 22: Integration doesn't deliver code to ONAP platform. Integration team will run ONAP platform stability and resiliency test after RC2 when release candidate is available.  



  • No labels