...
Intention is to keep number of test cases to minimum. We believe that three test plans are needed.
Test Plan 1: Covering enhancements 1 to 5 in above list.
Test Plan 2: Covers enhancement 6.
Test Plan 3: Covers enhancement 7
Test Plan 1
This test plan covers the tests related to testing
- Support for vFW use case
- Multi-Cloud API changes with oof_directives and sdnc_directives.
- Multi-Cloud preparing HEAT parameters from oof_directives and sdnc_directives
- SRIOV-NIC feature
- Region selection based on score
Scenario:
- ONAP managing 3 cloud-regions.
- Cloud-region1, Cloud-region2 and Cloud-region3
- All cloud regions are controlled by Openstack (with HEAT service)
- Each cloud-region has three flavors
- Cloud-region1:
- Flavor 11:
- 2 vcpus, 2 Gbytes of memory, 20Gb disk
- Numa page size: 2Mbytes and number pages 4
- Flavor 12:
- 2 vcpus, 2 Gbytes of memory, 20Gb disk
- Numa page size: 2Mbytes and number pages 6
- SRIOV-NIC with PCI Vendor: 1234 and PCI device :3456 on physical network 1 (physnet1) with support for 2VFs
- Flavor 13:
- 2 vcpus, 2 Gbytes of memory, 20Gb disk
- Numa page size: 2Mbytes and number pages 6
- SRIOV-NIC with PCI Vendor: 1234 and PCI device :3456 on physical network 1 (physnet1) with support for 1VFs
- SRIOV-NIC with PCI Vendor: 1234 and PCI device :3456 on physical network 1 (physnet2) with support for 1VFs
- Flavor 11:
- Cloud-region2:
- Flavor 21:
- 2 vcpus, 4 Gbytes of memory, 20Gb disk
- Numa page size: 2Mbytes and number pages 4
- SRIOV (non-NIC) with PCI vendor: 1234 Device ID: 7890 Count as 2.
- Flavor 22:
- 2 vcpus, 6 Gbytes of memory, 20Gb disk
- Numa page size: 2Mbytes and number pages 6
- SRIOV-NIC with PCI Vendor: 1234 and PCI device :3456 on physical network 1 (physnet1) with support for 2VFs
- Flavor 23:
- 2 vcpus, 2 Gbytes of memory, 20Gb disk
- Numa page size: 2Mbytes and number pages 6
- SRIOV-NIC with PCI Vendor: 1234 and PCI device :7654 on physical network 1 (physnet1) with support for 1VFs
- SRIOV-NIC with PCI Vendor: 1234 and PCI device :3456 on physical network 1 (physnet2) with support for 1VFs
- Flavor 21:
- Cloud-region3:
- Flavor 31:
- 2 vcpus, 4 Gbytes of memory, 20Gb disk
- Numa page size: 2Mbytes and number pages 4
- SRIOV (non-NIC) with PCI vendor: 1234 Device ID: 7890 Count as 2.
- 2 vcpus, 8 Gbytes of memory, 20Gb disk
- Numa page size: 8Mbytes and number pages 6
- 2 vcpus, 2 Gbytes of memory, 20Gb disk
- Numa page size: 2Mbytes and number pages 6
- SRIOV-NIC with PCI Vendor: 1234 and PCI device :3456 on physical network 1 (physnet3) with support for 1VFs
- SRIOV-NIC with PCI Vendor: 1234 and PCI device :3456 on physical network 1 (physnet4) with support for 1VFs
- Cloud-region1:
- Test 1 (Basic)
- Scenario:
- Use vFW VNF (firewall, generator and sink)
- firewall part of policy asking for:
- Mandatory:
- 2 vcpus
- >4Gbytes of memory
- <10Gbytes of disk
- Numa page size : 2Mbytes and pages 4
- Optional:
- SRIOV PCI vendor 1234 and device ID 7890 with PCI count 1 with score 100
- Mandatory:
- Generator part of policy asking for:
- Mandatory;
- 1 vcpu
- 7Gbytes of memory
- <10Gbytes of disk
- No Numa
- No optional
- Mandatory;
- Sink part of policy asking for:
- No mandatory
- No optional
- Modify vFW HOT templates with right label and ensure that those labels are referred in the policy properly.
- Instantiate the VNF
- Check for results:
- It would have selected Cloud-region3 with flavor31 for firewallVM, flavor32 for for generator and any flavor for sink.
- Why region 3: Since only Flavor32 has 8Gbytes of memory that can match Generator policy requirements.
- Scenario:
- Test 2: (to test SRIOV-NIC feature) (to ensure that right cloud-region is selected based on score)
- Scenario:
- Use vFW VNF (firewall, generator and sink)
- Say generator and one side of firewall are connected over physnet1
- And other side of firewall and sink are connected on physical network2 (physnet2)
- firewall part of policy asking for:
- Mandatory:
- SRIOV-NIC vendor 1234, 3456 device ID on physnet1, count 1
- SRIOV-NIC vendor 1234, 3456 device ID on physnet2, count 1
- Mandatory:
- Generator part of policy asking for:
- Mandatory;
- SRIOV-NIC vendor 1234, 3456 device ID on physnet1, count 2
- Mandatory;
- Sink part of policy asking for:
- mandatory
- SRIOV-NIC vendor 1234, 3456 device ID on physnet2, count 1
- No optional
- mandatory
- Modify vFW HOT templates with right label and ensure that those labels are referred in the policy properly.
- Instantiate the VNF
- Check for results:
- It would have selected Cloud-region1 with flavor13 for firewallVM, flavor12 for for generator and flavor13 for sink.
- It would have selected Cloud-region1 with flavor13 for firewallVM, flavor12 for for generator and flavor13 for sink.
- Scenario:
- Test 3 (to ensure that right cloud-region is selected based on score)
- Scenario:
- Use vFW VNF (firewall, generator and sink)
- firewall part of policy asking for:
- Mandatory:
- 2 vcpus
- 2Gbytes of memory
- <10Gbytes of disk
- Numa page size : 4Mbytes and pages 4
- Optional:
- SRIOV PCI vendor 1234 and device ID 7890 with PCI count 1 with score 100
- Generator part of policy asking for:
- Mandatory;
- 1 vcpu
- <10Gbytes of disk
- 2Gbytes of memory
- optional
- >=4Gbytes of Numa page size with Numa count 2 - score 200
- Mandatory;
- Sink part of policy asking for:
- No mandatory
- No optional
- Modify vFW HOT templates with right label and ensure that those labels are referred in the policy properly.
- Instantiate the VNF
- Check for results:
- It would have selected Cloud-region3 with flavor31 for firewallVM, flavor32 for for generator and any flavor for sink.
- Why region 3: Since only Flavor32 has 8Mbyte of NUMA pages and the total score is 300 and in case of region 2, the score is only 100.
- Scenario: