Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

All testing performed on WindRiver Lab


S3P/Maturity AreaCommitted Beijing LevelTestResult
PerformanceLevel 0No performance test for Beijing ReleaseN/A
Stability

Level 1 -

72    hour    component    level    soak    w/random    

transactions

Implemented as part of Beijing as part of

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCLAMP-127


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)

Done

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCLAMP-163

Resiliency

Level 1   

manual    failure    and    recovery    (<    30    minutes)

Implemented, CLAMP is relying on OOM to recover from POD and container failure

Done

Resiliency test 1

Resiliency Test 2


Security

Level 1

 CII    Passing    badge    +    50%    test    coverage

Implemented as part of Beijing, criteria reviewed and approved at M4

See M4 results


CLAMP security threat analysis

Scalability

Level 1

1    – single    site    horizontal    scaling

CLAMP is integrated with OOM, HA setup is done with MariaDB/Gallera see

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyOOM-735

Done

Tested on WindRiver Lab, scaling CLAMP pod successfully (MariaDB is handled through Gallera cluster)

Image Modified

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

Verified proper log location and format in clamp container

Image Modified

Checking filebeat configuration to check logs in ELK log stack


Minor issue Remaining

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCLAMP-164


Useability

Level 1

1    – user    guide;    deployment documentation;    API    

documentation;    adherence    to    coding    guidelines

Implemented as part of Beijing

See CLAMP documentation