We will use vFW use case as the baseline to test this:
Pre-requirement: Instantiate a vFW with closed loop running.
| Time (EDT) | Categories | Sub-Categories (In Error Mode Component) | Time to Detect Failure and Repair | Pass? | Notes |
|---|---|---|---|---|---|
| VNF Crash | vFW-VNF | Maybe leave the first three to project team? | |||
| vSink | |||||
| Openstack error (Out of memory??) | |||||
ONAP Component Check:
| A&AI | ||||
| APPC | |||||
| DCAE | |||||
| DMaaP | |||||
| MultiVIM | |||||
| Portal | |||||
| Policy | Policy documentation: Policy on OOM | ||||
| SDNC | |||||
| SO | |||||
| VFC | |||||
| VID | |||||
| VNF Onboarding | SDC | < 5 minutes | Pass | Timing?? 30 minutes. Using a script kills those components randomly, and continue onboarding VNFs. ete-k8s.sh onap healthdist After kicking off the command; waiting for 1 minutes; killed SDC; The first one was failed; then we did redistribute, it was success. | |
| SO | < 5 minutes | Pass | After kicking off the command; waiting for 1 minutes; killed SO; The first one was failed; then we did redistribute, it was success. | ||
| A&AI | < 5 minutes | Pass |
| ||
| APPC | |||||
| SDNC | |||||
| DCAE | |||||
| Policy | Policy documentation: Policy on OOM | ||||
| VNF Instantiation | SDC | ete-k8s.sh onap instantiate (could we de-couple with onboarding part??) | |||
| VID | |||||
| SO | |||||
| A&AI | |||||
| SDNC | |||||
| MultiVIM | |||||
| Closed Loop | DCAE | Pre define manually this closed loop | |||
| DMaaP | |||||
| Policy | Policy documentation: Policy on OOM | ||||
| A&AI | |||||
| APPC |
Requirement
Area | Priority | Min. Level | Stretch Goal | Level Descriptions (Abbreviated) |
Resiliency | High | Level 2 – run-time projects | Level 3 – run-time projects | •1 – manual failure and recovery (< 30 minutes) |