Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 22 Next »

This table summarizes each project's plan in regard to support of "Platform Maturity" in Frankfurt 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
  • 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&AIR11
11
22
11
11

1

(see note #10)

1
11
Application Authorization FrameworkR11
22
22
22
22

1+ (see Note #11)

2 * (See Note # 26)
1+2 * (See Note # 26)
APPCR11
11
22
22
11
11
11
CLAMPD00
11
11
11+
11
11
11
Common Controller SDKR00
NANA
22
1+ (75% towards silver)1+ (75% towards silver)
NANA
22
22
DCAED & R11
22
22
1+ (76% Silver)1+ (76% Silver)
11
11+

1+

(see Note#13)

1+
DMaaPR1

2

2

1+

(see note #16)



1

1+ (see note #17)

1

External API FrameworkR22
22
22
11+
11
11
22
HolmesR2

1

1+

1+

1

1

1+

Integration

NANANANA

2

See note #22)

2+

2

(See note #22)

2+
NANANANANANANANANANANANA
Logging Enhancements ProjectR2* (unable to test/verify)

2

0

(See note #24)



1




1

1 (see note #8)

1

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

    2

     0

(See note #25)



1 




   1

     1

      1

Microservices BusR2

2

2

1

2

2

2

ModelingD/R11
11
22
11
11
11
11
Multi VIM/CloudR11
22
22
22
11
22
22
MUSICR11
11
22
21
22
11
11
ONAP CLID & R1

1

2

1

1

1

2

ONAP Optimization FrameworkR11
11
22
1+ (75% towards silver)1+
11
11
11
ONAP Usecase UI Project ProposalR1

1

2

1

1

1

1

Policy Framework Project ProposalD & R

D: 1

R: 2

D: 1

R: 2


2

2

D: 2

R: 2

D: 2

R: 2


2 (silver)2 (silver)

1

1

2

2
22
Portal Platform Project ProposalD & R1

1

2

1+

1

1

2+

SDN-CR00
11
22
1+ (75% towards silver)1+ (75% towards silver)
11
22
22
Service Design & CreationD00

2

(Note #2)

2

(Note #2)


1

1

1

(Note #12)

1

(Note #12)


11
1

1

(Note #10)


11
Service OrchestratorR11
11
22
11
11
11
11
VFCR11
11
22
11
11
11
11
VIDR0

2

(Note #1)



2

2

1

1

(Note #8)



2

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;

Note 2: Assumption is that platform 72 hour test is run by Integration team

Note 8: logging spec and implementation changes done with AT&T/TechMahindra to sync to Acumos

Note 10: logging spec very close to 1.2;

Note 11: Will work Logging Spec in Frankfurt

Note 12: plus AAF-generated certificate and HTTPS mode by default.

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

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.  2+ means that until frankfurt 72 hour stability was performed only on windriver lab. The goial would be to run it at least on 2 labs (windriver + E///, Orange, DT, ..)

Note 23: OOF lost passing badge as recommended by sec team late into Dublin release, due to hard coded credentials in OOM (please see PTL 2019-05-13 more details.)

Note 24: the logging project reads logs from other components and displays to Kibana.

Note 25: retrieve information from other components via API.

Note 26: Assuming AAF Resource needs are met.




  • No labels