0

(given CLAMP is design time there is no point to adhere to L2 requirement) 

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

• 0 – none
• 1 – 72 hours component level soak w/random transactions
• 2 – 72 hours platform level soak w/random transactions
• 3 – 6 months track record of reduced defect rate

• 0 – none
• 1 – manual failure and recovery (< 30 minutes)
• 2 – automated detection and recovery (single site)
• 3 – automated detection and recovery (geo redundancy)

• 0 – none
• 1 – CII Passing badge + 50% Test Coverage, including no critical and high known vulnerabilities>60 days old
• 2 – CII Silver badge; internal/external communication encrypted; role-based access control and authorization for all calls based on CADI
• 3 – CII Gold

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

2

(1 if not enough resource1

(2, if CLAMP can get more resource from the community)

• 1 – single logging system across components; instantiation in < 1 hour

• 2 – ability to upgrade a single component; tracing across components; externalized configuration management
  ; All application logging to adhere to
  ONAP Application Logging Specification v1.2

• 3 - Transaction tracing across components

21

(1 if not enough resource)2, if CLAMP can get more resource from the community)

• 1 – user guide; deployment documentation; API documentation
• 2 – API documentation; usability testing; tutorial 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

• 3 - UI consistency; usability testing; API Documentation

  (changed and external APIs follow policy)

• 4 - API Documentation (all follow policy)