Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 3 Next »


V0001: ONAP WindRiver OpenStack VIM Resource Onboarding

Test Case IdV00001
Test Case NameONAP WindRiver OpenStack VIM Resource Onboarding
DescriptionONAP WindRiver OpenStack VIM Resource Onboarding
Preconditions
  1. The WindRiver OpenStack VIM is configured with tenant information and provider networks
  2. The WindRiver OpenStack VIM services (console, auth, neutron, image, glance, etc) are accessible from ONAP by IP
Testing Steps
  1. Add VIM from ONAP GUI with VIM location information, tenant authentication information
  2. VIM default service url can be configured based on real VIM settings
Expected Results
  1. VIM resource is onboarded successfully
  2. Tenant authentication information is stored successfully
Actual Results
Conclusion (Pass/Fail)
Tester Name


V0002: ONAP WindRiver OpenStack 2nd VIM Resource Onboarding

Test Case IdV00002
Test Case NameONAP WindRiver OpenStack 2nd VIM Resource Onboarding
DescriptionThis is to test multi VIM support
Preconditions
  1. V0001 is successful
  2. The new WindRiver OpenStack VIM is configured with tenant information and provider networks
  3. The new WindRiver OpenStack VIM services (console, auth, neutron, image, glance, etc) are accessible from ONAP by IP
Testing Steps
  1. Add the new VIM from ONAP GUI with VIM location information, tenant authentication information
  2. The new VIM default service url can be configured based on the new VIM settings
Expected Results
  1. The new VIM resource is onboarded successfully
  2. The new VIM Tenant authentication information is stored successfully
Actual Results
Conclusion (Pass/Fail)
Tester Name


- VoLTE VNF onboarding: vendors vEPC and vIMS VNFs are onboarded successfully.

- VoLTE e2e service creation: Network, workflow, alarms, DGs are designed or uploaded. VoLTE e2e network service, including intra data center and inter data center connectivity, are  designed successfully.

- Close loop design: DCAE template, Holmes correlation rules and operational policy are designed or uploaded, and distributed by CLAMP successfully

- Instantiation: VNFs are deployed in edge and core data centers successfully. Intra data center network, underlay and overlay WAN network cross the two data centers are setup correctly

- Auto-healing for VIM event: DCAE VES collector receives the VNF event from VIM, and forwards it to Holmes. Holmes does the correlation and generates signature event and sends to  Policy. Then auto-healing policy is triggered and proper actions are taken to mitigate the situation

- Auto-healing for VNF event: When alarm is generated by VNF, VFC will receive the alarm via vendor’s EMS and forwards to DCAE VES collector. The DCAE collector will then forward  alarm to Holmes via DMaaP. Holmes does the alarm correlation and sends signature event to Policy. Finally the auto-healing policy is triggered and proper actions are taken to mitigate the situation

- Service termination: When user terminates the VoLTE service, VNFs and related resource for the service are properly removed, and WAN connectivity between the two data center is  also removed successfully.




  • No labels