...

This test plan covers the tests related to testing

• Support for vFW/vDNS 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,

...

• 512 Mbytes of memory, 20Gb disk
• Numa page size: 2Mbytes

...

• Flavor 12:
• 2 vcpus,

...

• 2048 Mbytes of memory, 20Gb disk
• Numa page size: 2Mbytes

...

• SRIOV-NIC with PCI Vendor:

...

• 8086 and PCI device :

...

• 154C on physical network 1(

...

• private-1) with support for 2VFs
• Flavor 13:
• 2 vcpus,

...

• 2048 Mbytes of memory, 20Gb disk
• Numa page size: 2Mbytes

...

• SRIOV-NIC with PCI Vendor:

...

• 8086 and PCI device :

...

• 154C on physical network 2(private-1

...

• ) with support for 1VFs

...

• Cloud-region2 :
• Flavor 21:
• 2 vcpus, 512

...

• Mbytes of memory, 20Gb disk
• Numa page size: 2Mbytes and number pages 4

...

• Cpu thread policy=isolate and cpu pinning policy is dedicated
• Flavor 22:
• 2 vcpus,

...

• 2048 Mbytes of memory, 20Gb disk
• Numa page size: 2Mbytes

...

• SRIOV-NIC with PCI Vendor:

...

• 8086 and PCI device :

...

• 154C on physical network 2 (private-1

...

• ) with support for 2VFs
• Flavor 23:
• 2 vcpus,

...

• 2048 Mbytes of memory, 20Gb disk
• Numa page size: 2Mbytes

...

• SRIOV-NIC with PCI Vendor:

...

• 8086 and PCI device :

...

• 154C on physical network

...

• 2(shared-1) with support for

...

• 2VFs

• Cloud-region3:
• Flavor 31:
• 2 vcpus,

...

• 512 Mbytes of memory, 20Gb disk
• Numa page size: 2Mbytes

...

• Cpu thread policy=isolate and cpu pinning policy is dedicated
• Flavor 32:
• 2 vcpus, 8 Gbytes of memory, 20Gb disk
• Numa page size: 1Gbytes

...

• Flavor 33:
• 2 vcpus,

...

• 4 Gbytes of memory, 20Gb disk
• Numa page size: 2Mbytes

...

• SRIOV-NIC with PCI Vendor:

...

• 8086 and PCI device :

...

• 154C on physical network 2(shared-1

...

• ) with support for

...

• 1VF

  vFW TEST CASES

...

• Test 1 (Basic)
• Scenario:
• Use vFW VNF (firewall, generator and sink)
• firewall part of  policy asking for:
• Mandatory:
• 2 vcpus

...

• 512Mbytes of memory

...

• >=10Gbytes of disk
• Numa page size : 2Mbytes

...

• Optional:

...

• dedicated cpu pinning and policy and isolated cpu thread policy with score of 100
• Generator part of policy asking for:
• Mandatory;
• 1 vcpu
• 7Gbytes of memory

...

• >=10Gbytes of disk
• No Numa
• No optional
• 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

...

• and only flavor31 has cpu thread policy of isolated and cpu pinning policy of dedicated 

• 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

...

• vFW and sink are connected

...

• together on private-1
• firewall part of  policy asking for:
• Mandatory:
• SRIOV-NIC vendor

...

• 8086,

...

• 154C device ID on

...

• private-1, count 2
• Generator part of policy asking for:
• Mandatory;
• SRIOV-NIC vendor 8086, 154C device ID on private-1, count 1
• Sink part of policy asking for:
• Mandatory
• SRIOV-NIC vendor

...

• 8086,

...

• 154C device ID on

...

• private-1, count 1
• 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-region1 with flavor12 for firewallVM and flavor13 for generator and sink VMs.
• Why region 1: only cloud region one has flavors that support the unique combinations perfectly

• 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
• 4Gbytes of memory
• 10Gbytes of disk
• Numa page size : 2Mbytes and pages 6
• Optional:
• SRIOV-NIC vendor 8086, 154C device ID on shared-1, count 1 - score 100
• Generator part of policy asking for:
• Mandatory;
• 1 vcpu
• >=10Gbytes of disk
• 2Gbytes of memory
• optional
• >=1Gbytes of Numa page size with Numa count 2 -  score 200
• 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 flavor33 for firewallVM, flavor32 for generator and any flavor for sink.
• Why region 3:  Since only Flavor32 has 1Gbyte of NUMA pages and the total score is 300

  vDNS TEST CASES

• Test 1 (Basic)
• Scenario:
• Use vLB VNF (loadbalancer, generator and vDNS)
• vLB part of  policy asking for:
• Mandatory:
• 2 vcpus
• 512Mbytes of memory
• 10Gbytes of disk
• Numa page size : 2Mbytes
• Optional:
• dedicated cpu pinning and policy and isolated cpu thread policy with score of 100
• Generator part of policy asking for:
• Mandatory;
• 1 vcpu
• 7Gbytes of memory
• 10Gbytes of disk
• No Numa
• No optional
• Sink part of policy asking for:
• No mandatory
• No optional
• Modify vLB 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 vLB VM, flavor32 for for generator and any flavor for vDNS.
• Why region 3:  Since only Flavor32 has 8Gbytes of memory that can match Generator policy requirements.

• Test 2:  (to test SRIOV-NIC feature) (to ensure that right cloud-region is selected based on score)
• Scenario:
• Use vLB VNF (vlb, vpg and vdns)
• vlb part of  policy asking for:
• Mandatory:
• SRIOV-NIC vendor 8086, 154C device ID on private-1, count 2
• vpg part of policy asking for:
• Mandatory;
• SRIOV-NIC vendor

...

• 8086,

...

• 154C device ID on

...

• private-1, count

...

• 1

...

• vdns part of policy asking for:

...

• Mandatory
• SRIOV-NIC vendor

...

• 8086,

...

• 154C device ID on

...

• private-1, count 1
• No optional
• Modify

...

• vLB 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

...

• flavor12 for

...

• vlb and flavor13 for

...

• vpg and vdns.
• Why region 1: This best meets its vf requirements

• Test 3 (to ensure that right cloud-region is selected based on score)

• Scenario:
• Use

...

• vLB VNF (

...

• vlb,

...

• vpg and

...

• vdns)

...

• vLB part of  policy asking for:
• Mandatory:
• 2 vcpus

...

• 4Gbytes of memory

...

• 10Gbytes of disk
• Numa page size : 2Mbytes

...

• Optional:
• SRIOV

...

• -NIC vendor 8086, 154C device ID on shared-1, count 1 - score 100
• Generator part of policy asking for:
• Mandatory;
• 1 vcpu

...

• 10Gbytes of disk
• 2Gbytes of memory
• optional
• >=1Gbytes of Numa page size with Numa count 2 -  score 200

...

• vdns part of policy asking for:
• No mandatory
• No optional
• Modify

...

• vLB 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

...

• flavor33 for

...

• vLB, flavor32 for

...

• generator and any flavor for

...

• vdns.
• Why region 3:  Since only Flavor32 has

...

• 1Gbyte of NUMA pages and the total score is 300

...

Test Plan 2 

This test plan covers the tests related to testing

...