Performance

• Will work with integration team on gathering performance metrics related to SDNC

Stability

• SDNC will perform 72 hour soak at component level. We assume that integration team will also do a 72 hour ONAP soak which includes

Resiliency

• 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. SDNC will use that configuration to meet this requirement. See SDN-C Clustering on Kubernetes for further details

Security

• Current SDNC CII Badge status : 

  

  • Still need to reach 50% code coverage
  • Still need to address critical security vulnerabilities, where feasible
    • Most 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

• No specific SDNC development is planned for Beijing to address scalability.  However, SDNC can be scaled either by adding additional OpenDaylight containers and/or database containers, or by deploying multiple instances of SDNC cluster.

Manageability

• CCSDK includes a "filters" library which supports standard ONAP logging.  SDNC will use this library to provide standard logging.

Usability

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