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 50 Next »

This table summarizes each project's plan in regard to support of "Platform Maturity" in Guilin 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
1+ (75% toward silver)1+ (75% toward silver)
11

1


1
11
Application Authorization FrameworkR11
22
22
22
22

2

2
22
CLAMPD00
11
11
1+1+
11
11
11
Common Controller SDKR00
NANA
22
1+ (75% towards silver)1+ (75% towards silver)
NANA
22
22
DCAED & R1112222221+ (76% Silver)1+1+ (84% Sliver)1111+1+1+

1+

(see Note#13)

1+1+
DMaaPR11
22
22

1+

1+
11
1+1+
11
External API FrameworkR22
22
22
1+1+
11
11
22
HolmesR22
11
1+1+
1+1+
11
11
1+1+
Microservices BusR22
22
22
11+
22
22
22
ModelingD/R11
11
22
11
11
22
22
Multi VIM/CloudR11
22
22
22
11
11
22
ONAP CLID & R11
12
22
1.5 Note #281.5
11
11
2 Note #282
ONAP Optimization FrameworkR11
11
22

1+

(75% towards silver)

1+

(75% towards silver)


11
11
11
ONAP Usecase UI ProjectR11
11
22
11
11
11
22
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 & R

2

(Note #27)

2

(Note #27)


2

(Note #27

2

(Note #27


2

2



2

2



1

1


2

2


2+

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

(Note #10)

1

(Note #10)


11
Service OrchestratorR11
11
22

1

(89% towards Silver)

1
11
11
11
VFCR11
11
22
11
11
22
22
VIDR00

2

2
22
22
11

2

2
22
VNF SDKD00
11
11
1.5


1.5
11
11

2

(Note #19)

2


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

Note 11: Will work Logging Spec in Guilin

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 14: All level2 requirements will be addressed except logging complaince (for older component).

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, blocked http. oom updated.

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 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.

Note 27: Angular upgrade Completed, Security updates planned in Guilin release for Portal.

Note 28: 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



  • No labels