Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The Platform Maturity recommendations are documented in "Platform Maturity Status" from djhunt

Tip
titleLegend

Color code:

Yellow: same maturity.

Green: improved maturity level.

Red: below 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.

WIP


AREA

Design / Run-Time

Performance

Stability

Resiliency

Security

Scalability

Manageability

Usability

Min TSC Recommendations

Min Runtime: 1

Min Remaining: 0

Min all projects: 1

Min Runtime: 2

Min Remaining: 1

Min all projects: 1

Min Runtime: 1

Min Remaining: 0

Min all projects: 1
Min all projects: 1
Project Name
M1 Actual

M1 Target

M4 resultM1 ActualM1 TargetM4 resultM1 ActualM1 TargetM4 resultM1 ActualM1 TargetM4 resultM1 ActualM1 TargetM4 resultM1 ActualM1 TargetM4 resultM1 ActualM1 TargetM4 result
A&AIR01

WIP

Note 11

01

WIP

Note 11

12201

 WIP

Note 10

011111111
Application Authorization FrameworkR01

WIP

Note 11

01

WIP

Note 11

12

WIP

Note 11

01

0

Note 16

01

0

Note 11

111111
APPCR00001

1Note 12

11

2


201

WIP1

Note 13

11

1

Note 14

111111
CLAMPD00001

1

Note 27

11101111

1

Note 28

111111
Common Controller SDKR0000

NA

Note 2

NA

Note

2

12

2

01

WIP

Note 18

0

NA

Note 3

NA

Note 3

111111
DCAER11112WIP1

2

Note 1

201WIP01101111WIP
DMaaPR0

1


WIP

Note7

11

WIP

Note7

22201

WIP

Note8


11111112

WIP

Note9

DocumentationNAOversee documentation from all other projects that support their maturity commitments12
External API FrameworkR0110011001101101

1

Note 30

00110110
HolmesR01WIP01WIP02101

WIP

Note 19

01

1

Note 20

01

1

Note 20

111

Integration

NAIntegration Team will perform overall E2E  testing with the 4 use cases.
Logging Enhancements Project R00
11
2

2

Note 4


00
11
11
01

WIP

Note 17

Microservices BusR01
01
12
01Note1511
11
11
ModelingD01
11
12
01
01
01
11
Multi VIM/CloudR01
01
12
01
11
01
22
MUSICR11
11
22
22
11
11
11
ONAP CLID & R01101112201

1

111111122
ONAP Operations ManagerR11
01
12
11
01
01
11
ONAP Optimization FrameworkR01

WIP

Note 111

01

WIP

Note 111

12WIP201101

1

WIP

Note 30

01WIP111WIP1
ONAP Usecase UI Project ProposalD01
01
12
01
00
01
11
Policy Framework Project ProposalD & R11No work done11

No work done

12WIP11101WIP11WIP11WIP
Portal Platform Project ProposalD & R01111112

2

011011111122
SDN-CR00001

WIP

12201WIP Note 21011111111
Service Design & CreationD00No work done01WIP11No work done01WIP00No work done0

0

Note 5

WIP01WIP
Service OrchestratorR01

WIP

Note 29

01

WIP

Note 29

12

WIP

Intertaring with OOM

01

WIP

01

WIP

Intertaring with OOM

01

WIP

Intertaring with OOM

01WIP
VFCR01

WIP

Note 11


01

WIP

Note 11


12201

Note22

0

1(*)

Note 6

001

WIP

Note231

111
VIDR01

WIP

Note 32

01

WIP

Note 32

12

WIP

Note 31

01

WIP1

Note26

01

WIP

Note 31

0

0

Note 5

WIP011WIP1
VNF SDKD000111111011000111111
VNF RequirementsNANA. VNFRQTS is primarily a documentation project and does not deliver ONAP platform code1

VNF Validation (VVP)D




















...

Note 11: Performance and scalability tests will be performed during integration testingNote 12: 72 hour soak test completed on Amsterdam code base due to defect APPC-658 which prevents DMaaP messages from being received or sent.  Test results and notes can be found at:  ONAP APPC 72 Hour Stability Test Results. Once DMaaP issue is resolved on Beijing, we will re-run 72 hour soak test.

Note 13: CII Passing is 95%; Code Coverage is at 48.2% and progressing; however, not likely to meet 50% by 3/29over 50% .

Note 14: APPC component is fully scalable via approach of using Kubernetes, APPC instances (N+) can be added to the cluster; however, due to constraints encountered with MySQL DB, the DB is not scalable until we migrate to MariaDB plus Galera (planned for Casablanca per feedback from CCSDK), which would provide the active-active architecture. Further details are tracked under OOM project (OOM-733), who we've been working with. 

...

Note 22: CII Passing is 97% ; code coverage is already above 50%; there are still unresolved critial issues, we‘re stilling working on that.

Note 23: VF-C updated log configuration and added filebeat container to VF-C existing components in OOM. OOM and Logging team are helping us review’ these updates.

...

Note 26: VID coverage is 50%, CII Passing is 94%, still working on fixing CLM issues97%

Note 27: CLAMP 72h stability test was performed just after completing work for M4 - see report in subtasks of CLAMP-127

...

Note 29: Working with the intergration (and benchmarkin) team to define the criteria.Will be done by final release.

Note30: Scalability provided by Kubernetes

Note 31: Tested locally, and submitted to OOM to review

Note 32: As performed by integration team