Page History

...

• Upgrade of ODL to Fluorine SR2 (CCSDK dependency)
• Platform Maturity (i.e., S3P items)  https://wiki.onap.org/pages/viewpage.action?pageId=16003367, https://wiki.onap.org/display/DW/Dublin+Release+Platform+Maturity
  
  • Brown→ Jason's goal S3P page
  • Performance: Level 2
    • Level 1: baseline performance criteria identified and measured  (such as response time, transaction/message rate, latency, footprint, etc. to be defined on per component)
    • Level 2: performance improvement plan created 
    • unzip feature.zip during building docker.
    • Remove un-used bundles from CCSDK’s odlsli
  • Stability: Level 2
    
    • Level 2: 72 hour platform-level soak test (random test transactions with 80% code coverage; steady load)
    • Configuration Enhancement https://wiki.onap.org/display/DW/APPC+Configuration+Enhancement
  • Resiliency: Level 2
    
    • Level 2: support automated failure detection & rerouting 
      • within a single geographic site
      • stateless components: establish baseline measure of failed requests for a component failure within a site 
      • stateful components: establish baseline of data loss for a component failure within a site
    • OOM: move to variable for database’s user/password
    • CSIT OOM
  • Security:
    
    • Absolute Minimum expectation:
      • CII badging passing level
      • Continuously retaining no critical or high known vulnerabilities > 60 days old
      • All communication shall be able to be encrypted and have common role-based access control and authorization.
    • Desired expectation is full CII badging silver level, if not 75% towards that.
  • Scalability: Level 1
    
    • Level 1: supports single site horizontal scale out and scale in, independent of other component
    • APPC does not support dynamic cluster configuration in k8s only support static cluster configuration
    • Clustering env with downstream: netconf,  ansible
  • Manageability: Level 2
    
    • Level 2:
      • A component can be independently upgraded without impacting operation interacting components
      • Component configuration to be externalized in a common fashion across ONAP projects
      • All application logging to adhere to ONAP Application Logging Specification v1.2
      • Implement guidelines for a minimal container footprint - See this presentation and follow the Container Image Minimization Guidelines
  • Usability: Level 2
    
    • Level 2:
      • API Documentation
        • All new API’s must adhere to the ONAP API Common Versioning Strategy and Documentation Guidelines
        • All existing APIs must be documented in Swagger 2.0

...