...
- What kind of test cases can we actually design for?
- No white box testing - only black box testing
- how to define pass / fail criteria
- Node level ,
- Network resilience
- Switch level, port level?
- Availability of redundant fabric in OPNFV labs, Packet
- API for configuring switches
...
- Cedric
- RC-1/2 should be used in production environments and hence not execute destructive testing
- the Yardstick framework is hard to maintain → questionable if we want to re-active it
- key question: is resilience testing in the scope of RC-1/2
- CNTT specifies requirements on resilience → there is a need for validating such requirements via an automated test
- → we likely need such tests and then need to de-/select destructive tests depending on use case: workload onboarding (non-destructive) vs. OVP badging (destructive)
- Need to distinguish between HA and resiliency. A resilient system continues to function in case of a failure (we can limit to a single failure scenario)
- In a cloud environment one expects infrastructure failures and thus expect resiliency and HA from the software systems (OSTK, etc.) – # of deployments, etc.
- RA1 Chapters 3 and 4 specify the services, # of minimum deployments, etc. to meet the requirements specified in Chapter 2