Beijing Release Resiliency Testing Status

We will use vFW use case as the baseline to test this:

Pre-requirement: Instantiate a vFW with closed loop running.

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	Killed aai-modelloader; it finished the task in 3:04 minutes Killed two aai-cassandra pods; it finished the task in ~1 minutes.
	SDNC			Run preload using scripts
VNF Instantiation	SDC			ete-k8s.sh onap instantiate (could we de-couple with onboarding part??)
	VID	< 1 minute	Pass	kubectl delete pod dev-vid-6d66f9b8c-9vdlt -n onap //back in 1 minute kubectl delete pod dev-vid-mariadb-fc95657d9-wqn9s -n onap // back in 1 minute
	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 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)

Space shortcuts