CLAMP Pair Wise Testing for Frankfurt Release

Health Check

PASSED

• Tested on Local microK8S with OOM

• Tested by the OOM Gating for PR https://gerrit.onap.org/r/c/oom/+/104402

The healthcheck done on the frontend is propagated to the backend, therefore it validates both at the same time.

CLAMP ↔ DCAE (SB-01)

PASSED

• Tested on local Clamp to Windriver DCAE (10.12.7.33:30471)

Deploy / Undeploy test DONE with TCA blueprint

• Tested on SB-01, issue detected CLAMP-804: DCAE deployment failed with error 422 UNprocessable entityClosed

• After the fixes new test with TCA, DCAE deploy operation has been started on DCAE as we can see here:

• Open

  

• Operation has been reported by DCAE as SUCCESSFUL as we can see here

  Open

  

• Undeploy has been tried as well and was successfully executed by DCAE

• Bug found for undeploy status CLAMP-807: Undeploy operation cannot be refreshed successfullyClosed but there is a workround

CLAMP ↔ Policy (SB-01)

PASSED

• Tested on local Clamp to Windriver Policy (10.12.6.1:30210) Submit / Deploy OK - Stop / Restart OK  - PDP group selection and update in the different policies OK - Policy model synchronization, so policies available for loop instance OK - UI generation from policy models OK

• Tested on SB-01,

• Policy synchro (Dynamic policies based on tosca model) OK

• Status of the policies (SENT AND DEPLOYED) after having added a frequency limiter policy (tested with Apex too)
  
  

  •                                                         Submit / Deploy OK - Stop / Restart OK  - PDP group selection and update in the different policies OK - Policy model synchronization, so policies available for loop instance OK - UI generation from policy models OK.               Bug found and Fixed CLAMP-801: Modify Loop instance crash when adding Apex policyClosed

  • Bug found when re-submitting the policiesCLAMP-808: Re-submit the policies failsClosed but there is a workaround

CLAMP ↔ SDC (SB-01)

PASSED

Tested on SB-01, Distribution done with the new DCAE blueprint TCA, the loop template was available, so it was possible to create a loop instance and submit to policy

Artifacts deployed 2 so it's well ok for CLAMP, the template is well in the CLAMP DB

It prooves the communication with DCAE at this point is also ok, artifact well deployed by SDC on DCAE

CLAMP  → AAF (SB-01)

PASSED

• Tested on Local microK8s with OOM

• Tested on SB-01, authentication successful with P12 certificate

• All permissions are well retrieved

CLAMP ↔ CDS (SB-01)

PASSED

• Tested Locally by Vidya

• Tested on SB-01

• Sdc distribution of the right artifact (triggering CDS), the one selected here:

• After creating a Loop instance from that template, we have added an APEX policy model (got from policy), the policy config UI well show the CDS info for the payload field:

• The remaining bug in that area is CLAMP-809: Each property in Payload of operational policy should have seperate text boxClosed