Test Case Id | Description | Pre-conditions | Test Steps | Expected Results |
---|---|---|---|---|
1 | Perform healthcheck for the Policy components using Healthcheck API
|
| API – healthcheck Method - GET Endpoint: http://<host>:8081/healthcheck | All the policy components should return health status as “true” |
2 | Create config Policy for the following use cases
| Policy components up and running | API – CreateConfig Method – PUT Endpoint: https://<host>:8081/Pdp/createPolicy | Config Policy should be created in Policy Engine (PAP) |
3 | Push Config policy to the PDP Engines for the following use cases
| Policy components up and running | API - pushPolicy Method - PUT Endpoint: https:// <host>:8081/Pdp/pushPolicy | Config Policy should be pushed to the PDP group |
4 | Load the Drools Controller Configurations | |||
5 | Import/Load Use case template for the following use cases (VoLTE, vCPE, vFW, vDNS) | Policy components should be up and running | API – policyEngineImport Method – POST Endpoint: https://<host>:8081/pdp/policyEngineImport | Policy service models should be imported for the specified use cases. We should be able to create policy from here. |
6 | Create Operational policy for the following use cases
| Policy components up and running | API - createPolicy Method – PUT Endpoint: https://<host>:8081/Pdp/createPolicy | Operational Policy should be created in Policy Engine (PAP) |
7 | Push operational Policy to the PDP Engines for each use case
| Policy components up and running | API - pushPolicy Method - PUT Endpoint: https:// <host>:8081/Pdp/pushPolicy | Operational Policy should be pushed to the PDP group |
8 | Retrieve the configs for the following use cases
| Policy components up and running | API – getConfig Method – POST Endpoint: https://<host>:8081/Pdp/getConfig | Both Config and Operational Policies configured for each use case should be retrieved successfully |
9 | Simulate DCAE Control loop event for each use case with higher or lower threshold values
|
| Invoke the Simulator API to trigger a DCAE control loop event | DCAE event should be triggered to Policy for each use case depending on the threshold configured |
10 | Simulate A&AI Response for Use Case vFW | |||
11 | Simulate APPC Response for Use Case vFW |
| Invoke APPC simulator API with Policy data or Trigger a DCAE control loop event for vFW/vCPE | Valid Response from AppC Simulator API |
12 | Simulate A&AI Response for Use Case vCPE | |||
13 | Simulate APPC Response for Use Case vCPE | |||
14 | Simulate A&AI Response for Use Case VOLTE | |||
15 | Simulate VF-C Response for Use Case VOLTE |
| Invoke VF-C simulator API with Policy data or Trigger a DCAE control loop event for VOLTE | Valid Response from VF-C Simulator API |
16 | Simulate SO Response for VDNS |
| Invoke SO simulator API with Policy data or Trigger a DCAE control loop event for vDNS | Valid Response from SO Simulator API |
17 | Simulate A&AI Response for VDNS |
| Invoke A&AI simulator API with Policy data or Trigger a DCAE control loop event for vDNS | Valid Response from A&AI Simulator API |
vFirewall Use Case
*TODO Show the API call to A&AI Policy is getting the event from the Load Balancer. but the API call MUST go to the vpg VNF. In R0 previously Policy pattern/match replaced the name. But that will not work with the introduction of CLAMP and the use of Policy YAML to specify the policy. Policy needs to look up the service and then the VNF ID in order to make the call to APPC.
*TODO show the returned response from A&AI
*TODO show the ModifyConfig API call to APPC
*TODO show the APPC response messages
vDNS Use Case
*TODO Show the API call to A&AI This is the NAMED QUERY used in R0
*TODO show the returned response from A&AI
*TODO show the API call to SO This format should not have changed from R0
*TODO show the SO API response message
VOLTE Use Case
* TODO Sample A&AI call to retrieve these values: "service-instance.service-instance-id" : "TBD - Can Holmes provide this?", "generic-vnf.vnf-id" : "TBD", "vserver.vserver-id" : "TBD" May require 2 calls. We are also hoping Holmes could prepopulate this if that team is going to retrieve topology details from A&AI anyway.
* TODO - A&AI response(s)
*TODO Call to VFC details
*TODO response from VFC
vCPE Use Case
*TODO Call to A&AI to retrieve values for APPC Restart
*TODO response from A&AI
*TODO request to APPC
*TODO responses from APPC