Performance

• Will work with integration team on gathering performance metrics related to CCSDK, if applicable

Stability

• Not applicable - as a project that provides a library framework, CCSDK has no standalone component that can be soaked.

Resiliency

• While CCSDK itself has no standalone component, it does provide an OpenDaylight docker container used by SDNC and APPC. In Beijing, CCSDK will support a clustered OpenDaylight configuration in Kubernetes, as well as a clustered database, to allow for automated detection and recovery within a site.

Security

• Current CCSDK CII Badge status : 

  

  • Still need to reach 50% code coverage
  • Adding integration with AAF (same as APPC)
  • Still need to address critical security vulnerabilities, where feasible
    • Several vulnerabilities reported are actually related to jar files that are part of base OpenDaylight platform.
    • Will report these back to OpenDaylight Nitrogen project team to ask for direction

Scalability

• Scaling does not apply to CCSDK itself, since it is simply a set of libraries.

Manageability

• CCSDK includes a "filters" library which supports standard ONAP logging.

Usability

• Documentation updates will be made to existing readthedocs and wiki documentation.