You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »


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 FailureTime to RepairPass?Notes

VNF CrashvFW-VNF


Maybe leave the first three to project team?

vSink




Openstack error (Out of memory??)





ONAP Component

Check:

  1. Is Memory Data Kept?
  2. Is File System/db Data Kept?
A&AI




APPC




DCAE




DMaaP




MultiVIM




Portal




Policy




SDNC




SDC




SO




VFC




VID




VNF OnboardingSDC


Timing?? 30 minutes.  Using  a script kills those components randomly, and continue onboarding VNFs.

ete-k8s.sh onap distribute


SO




A&AI




APPC




SDNC




DCAE




Policy




VNF InstantiationSDC


ete-k8s.sh onap instantiate  (could we de-couple with onboarding part??)

VID




SO




A&AI




SDNC




MultiVIM




Closed LoopDCAE


Pre define manually this closed loop

DMaaP




Policy




A&AI




APPC



Requirement

Area

Priority

Min. Level

Stretch Goal

Level Descriptions (Abbreviated)

Resiliency

High

Level 2 – run-time projects
Level 1 – remaining projects

Level 3 – run-time projects
Level 2 – remaining projects

•1 – manual failure and recovery (< 30 minutes)
•2 – automated detection and recovery (single site) (<30 miutes)
•3 – automated detection and recovery (geo redundancy)

  • No labels