Skip to end of metadata
Go to start of metadata

This table summarizes the plan in regard to support of "Platform Maturity" for each project in Beijing Release. The data below are extracted from each project plan.

The Platform Maturity recommendations are documented in "Platform Maturity Status" from Jason Hunt

Legend

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.



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

1

1

2


201

1

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 FrameworkR01101101101101

1

Note 30

011011
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

1

01

1

12201101

1

Note 30

011111
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


01

WIP


12201

Note22

0

1(*)

Note 6

001

1

111
VIDR01

WIP

Note 32

01

WIP

Note 32

12

WIP

Note 31

01

1

Note26

01

WIP

Note 31

0

0

Note 5

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

VNF Validation (VVP)D




















Note 1: For DCAE the plan is to meet level 2 for DCAE components that can be made into docker containers, but for those components that cannot, it will depend on upstream providers (i.e. Cloudify Manager and CDAP). During M1 review, TSC agree with level 2 ok with exception granted for cloudify

Note 2: For CCSDK, as a project that provides a library framework, CCSDK has no standalone component that can be soaked

Note 3: Scaling does not apply to CCSDK itself, as a set of libraries.

Note 4: LOG: standard OOB OOM Kubernetes resilience/stability

Note 5: SDC and VID. For Manageability, instantiation in < 1 hour is already supported. No plan to support single loging in Beijing.

Note 6: Due to lack of resources, VF-C may not achieve scalability level 1 for all components in this release and plans to support scalability level 1 for part of  components first.

Note 7: 72 hrs. Soak test completed for Message router and in progress for Bus controller.

Note 8: We reached 50% code coverage for Message Router. Code coverage for Bus controller is in progress.

Note 9: Documentation is completed for Message router, in progress for Bus controller.

Note 10: AAI hasn't cleared vulnerable dependencies and won't be clear before M4 but we have a plan to have them clear by release

Note 11: Performance and scalability tests will be performed during integration testing.

Note 13: CII Passing is 95%; Code Coverage is over 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 15: MSB CII Badge progress is 98% ; the main challenge for us is to fix all the security issues above level 4, we're still working on that. The coverage is already above 50%.

Note 16: AAF latest code set supports certificate manager and  OAuth. Need to test the security during integration testing

Note 17: logging spec page being finalized with mostly AT&T - spawned a Casablanca spec moving forward

Note 18: Remaining security vulnerabilities in CCSDK are due to library versions delivered in OpenDaylight Nitrogen release.  These cannot be cleared without breaking OpenDaylight platform.

Note 19: The current status of  Holmes CII Badge progress is 98%. There's still one severe problem unsolved. But it seem to be a false positive. Details could be found at Holmes Security/Vulnerability Threat Impact Analysis. Now we are still working on the issues ranked above L4.

Note 20: Holmes itself has implemented all the functionalities regarding scaling and logging. Now we are still working with the DCAE team for integration.

Note 21: Remaining security vulnerabilities in SDNC are due to versions delivered in base platforms (OpenDaylight Nitrogen and NodeRed).  These need to be cleared in these dependent projects and then SDNC will use updated version of base platforms.

Note 22: CII Passing is 97% ; code coverage is already above 50%; there are still unresolved critial issues.

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 24: CLI https enablment is pending and will be enabled as part of RC0. (once we confirm on the CA cerificate use)

Note 25: PORTAL working on nexus-IQ issues to improve the security; also working with MUSIC integration to improve the scalability and resiliency. The PORTAL's security issues are resolved and MUSIC integration completed.

Note 26: VID coverage is 50%, CII Passing is 97%

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

Note 28: CLAMP is integrated with OOM, HA setup is done with MariaDB/Gallera see OOM-735

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


2 Comments

  1. Michael O'Brien (Amdocs 1705-1905) filling in today for logging and oom (by proxy) - sorry missed the TSC mail

  2. Gildas Lanilis - should we add a column for RC2 status update?