Page Comparison

Level 1 - Design

• Policy GUI
• PAP

Level 1+ - Runtime

• PAP (level 1)
• Drools
• XACML
• Apex (level 1)
• Distribution (level 1)

Level 1 - Design

• Policy GUI
• PAP (to be deprecated)

Level 2 (Runtime components)

• 0 -- none
• 1 – baseline performance criteria identified and measured
• 2 & 3 – performance improvement plans created & implemented

- Runtime

• PAP
• API
• Drools
• XACML
• Apex
• Distribution

Performance

• • Level 0: no performance testing done
  • 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 
  • Level 3: performance improvement plan implemented for 1 release (improvement measured for equivalent functionality & equivalent hardware)

Stability

• • Level 0: none beyond release requirements
  • Level 1: 72 hour component-level soak test (random test transactions with 80% code coverage exercising major code branches; steady load)
  • Level 2: 72 hour platform-level soak test (random test transactions with 80% code coverage exercising major code branches; steady load)
  • Level 3: track record over 6 months of reduced defect rate

Level 2

Level 2

Resiliency Levels

• • Level 0: no redundancy
  • Level 1: support manual failure detection & rerouting or recovery within a single site; tested to complete in 30 minutes
  • 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

  • Level 3: support automated failover detection & rerouting 

    • across multiple sites 

    • stateless components 

      • improve on # of failed requests for component failure within a site 

      • establish baseline for failed requests for site failure 

    • stateful components 

      • improve on data loss metrics for component failure within a site 

      • establish baseline for data loss for site failure

• 0 – none
• 1 – CII Passing badge
  • Including no critical and high known vulnerabilities > 60 days old
• 2 – CII Silver badge;

• • All internal/external system communications shall be able to be encrypted.

• • All internal/external service calls shall have common role-based access control and authorization using CADI framework

• 3 – CII Gold

Level 1

• 0 – no ability to scale
• 1 – single site horizontal scaling
• 2 – geographic scaling
• 3 – scaling across multiple ONAP instances

• 1 – single logging system across components; instantiation in < 1 hour
• 2 – ability to upgrade a single component; tracing across components; externalized configuration management

• 1 – user guide; deployment documentation; API documentation
• 2 – UI consistency; usability testing; tutorial documentation