Page Comparison

...

• 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

...

Area	Actual Level	Targeted Level for current Release	How, Evidences	Comments
Performance	0	1 or 2	Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key APPC-1310
Stability	1 - project team 2 - Integration team	1 - project team 2 - Integration team Assume Integration team will address Level 2 -  72 hour test in Dublin		*current (1/11/19) code coverage is 67.5% Level 0: none beyond release requirements Level 1: 72 hour component-level soak test (random test transactions with 80% code coverage; steady load)
Resiliency	2	2
Security	1	Minimum Expectation		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.
Scalability	1	1
Manageability	1	1, 2(partial)		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
Usability	1	1		Recommendation for Casablanca is Level 2; however, we cannot meeting Level 2 All new API’s must adhere to the ONAP API Common Versioning Strategy and Documentation Guidelines;   - There was an issue with ODL & API version - need to investigate further TBD - Swagger 2.0 - We dependent on what ODL Fluroine for API documentation and they dictate version of Swagger used, currently looked like

...