...
| Time (EDT) | Categories | Sub-Categories (In Error Mode Component) | Time to Detect Failure and Repair | Pass? | Notes |
|---|---|---|---|---|---|
| VNF Onboarding and Distribution | 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 |
| ||
| SDNC | < 8 minutes | Pass |
Delete SDNC pod, it took very very long time to get back, it might because of the network issues. And we got a very "weird" system, SDC gives us the following error:
| ||
| < 5 minutes | Pass |
2. Run health and preload | |||
| VNF Instantiation | SDC | < 2 seconds | Pass | Tested with manually kill the docker container | |
| VID | < 1 minute | Pass |
| ||
| SO | 5 minutes | Pass | so pod restarted as part of hard rebooting 2 k8s VMs out of 9 | ||
| A&AI | restarted aai-model-loader, aai-hbase, and aai-sparky-be due to hard rebotting k8s VMs | ||||
| SDNC | 5 minutes | Pass | sdnc pods restarted as part of hard rebooting 2 k8s VMs out of 9 | ||
| MultiVIM | |||||
| Closed Loop | DCAE | Pre define manually this closed loop | |||
| DMaaP | |||||
| Policy | Policy documentation: Policy on OOM | ||||
| A&AI | |||||
| APPC |
...