Versions Compared

Old Version 8

changes.mady.by.user ramki krishnan

Saved on

compared with

New Version 9

changes.mady.by.user ramki krishnan

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Background:

Multiple enhancements are happening in R3 with respect to HPA.  This test plan is to ensure that changes and new enhancements being added to R3 are tested (Preferably testing by developers as well as part of integration testing).

...

Test Plan 3:  Covers enhancement 7

Test Plan 1

This test plan covers the tests related to testing

...

  • 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
    • 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
    • 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.
        Flavor 32:
        • 2 vcpus, 8 Gbytes of memory, 20Gb disk
        • Numa page size: 8Mbytes and number pages 6
        Flavor 33:
        • 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
  • 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
      • 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.
  • 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
      • Generator part of policy asking for:
        • Mandatory;
          • SRIOV-NIC vendor 1234, 3456 device ID on physnet1, count 2
      • Sink part of policy asking for:
        • mandatory
          • SRIOV-NIC vendor 1234, 3456 device ID on physnet2, 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 flavor13 for firewallVM, flavor12 for for generator and flavor13 for sink.

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

Test Plan 2 

This test plan covers the tests related to testing

...

  • ONAP managing 1 cloud-region 3.
    • Cloud-region 3
    • All cloud regions are controlled by VMware Integrated Openstack (with HEAT service)
  • Each cloud-region has three flavors
    • Cloud-region 1:
      • Flavor 31:
      • Flavor 32:
        • 2 vcpus, 8 Gbytes of memory, 20Gb disk 
        • Infrastructure Resource Isolation for VNF w/ Burstable QoS, Oversubscription Percentage (Definition: Cloud Agnostic Intent and Mappings) 
        Flavor 33:
        • 2 vcpus, 2 Gbytes of memory, 20Gb disk 
  • Test 1 (Basic)
    • Scenario:
      • Use vFW VNF (firewall, generator and sink)
      • firewall part of  policy asking for:
      • Generator part of policy asking for:
        • Mandatory;
          • 1 vcpu
          • 7Gbytes of memory
          • <10Gbytes of disk
          • Infrastructure Resource Isolation for VNF w/ Burstable QoS, Oversubscription Percentage (Definition: Cloud Agnostic Intent and Mappings) 
      • 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.

Test Plan 3 : VF-C HPA testing (Huang Haibin to fill up)