Performance

1

2

• 0 -- none

• 1 – baseline performance criteria identified and measured

• 2 & 3 – performance improvement plans created & implemented

Stability

1

2

• 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

Resiliency

2

2

Logging will leverage OOMs single site failure detection and recovery

• 0 – none

• 1 – manual failure and recovery (< 30 minutes)

• 2 – automated detection and recovery (single site)

• 3 – automated detection and recovery (geo redundancy)

Security

1

1

Logging will maintain 50+ test coverage

For javascript components (there are none), Logging will reach to attain +10% from the initial scan coverage value.

• 0 – none

• 1 – CII Passing badge + 50% Test Coverage

• 2 – CII Silver badge; internal communication encrypted; role-based access control and authorization for all calls

• 3 – CII Gold

Scalability

1

1

Logging will leverage OOM

• 0 – no ability to scale

• 1 – single site horizontal scaling

• 2 – geographic scaling

• 3 – scaling across multiple ONAP instances

Manageability

1

2

Logging needs to investigate the level of compliance we can reach with the ONAP logging specification 1.2

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

• 2 – ability to upgrade a single component; tracing across components; externalized configuration management

Usability

1

2

• 1 – user guide; deployment documentation; API documentation

• 2 – UI consistency; usability testing; tutorial documentation