...
| S3P/Maturity Area | Committed Beijing Level | Test | Result | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Performance | Level 0 | No performance test for Beijing Release | N/A | ||||||||||
| Stability | Level 1 - 72 hour component level soak w/random transactions | Implemented as part of Beijing as part of
72h stability test - including create-deploy actions every 20sec, collection of RAM,CPU and stats Re run on WindRiver lab in CLAMP sub project | RUNNING on clamp-test host (windriver lab) | ||||||||||
| Resiliency | Level 1 manual failure and recovery (< 30 minutes) | Implemented, CLAMP is relying on OOM to recover from POD and container failure | Done | ||||||||||
| Security | Level 1 CII Passing badge + 50% test coverage | Implemented as part of Beijing, criteria reviewed and approved at M4 | See M4 results | ||||||||||
| Scalability | Level 1 1 – single site horizontal scaling | CLAMP is integrated with OOM, HA setup is done with MariaDB/Gallera see
| Done Tested on WindRiver Lab, scaling CLAMP pod successfully (MariaDB is handled through Gallera cluster)
| ||||||||||
| Manageability | Level 1 1 – single logging system across components; instantiation in < 1 hour | Implemented as Part of Beijing, CLAMP is integrated with OOM and logging is consistently collected acorss all components | SETUP in Progress CLAMP k8s lab being setup to perform OOM testsVerified proper log location and format in clamp container
Checking filebeat configuration to check logs in ELK log stack | ||||||||||
| Useability | Level 1 1 – user guide; deployment documentation; API documentation; adherence to coding guidelines | Implemented as part of Beijing |
...