Versions Compared

Old Version 24

changes.mady.by.user Itohan Ukponmwan (Deactivated)

Saved on

compared with

New Version 25

changes.mady.by.user Itohan Ukponmwan (Deactivated)

Saved on

Key

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

Background:

...

  • Each cloud-region has three flavors
    • Cloud-region1:
      • Flavor 11:
        • 2 vcpus, 8 Mbytes of memory, 20Gb disk
        • Numa page size: 2Mbytes and number pages 4
      • Flavor 12:
        • 2 vcpus, 12 Mbytes of memory, 20Gb disk
        • Numa page size: 2Mbytes and number pages 6
        • SRIOV-NIC with PCI Vendor: 8086 and PCI device :154C on physical network 1(shared-1) with support for 3VFs
      • Flavor 13:
        • 2 vcpus, 12 Mbytes of memory, 20Gb disk
        • Numa page size: 2Mbytes and number pages 6
        • 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, 8 Mbytes of memory, 20Gb disk
      • Numa page size: 2Mbytes and number pages 4
      • SRIOV (non-NIC)  ( with PCI vendor: 8086 Device ID: 0443 Count as 2. (alias={"name":"qat-dh895xcc-vf","product_id":"0443","vendor_id":"8086"})
    • Flavor 22:
      • 2 vcpus, 12 Mbytes of memory, 20Gb disk
      • Numa page size: 2Mbytes and number pages 6
      • SRIOV-NIC with PCI Vendor: 8086 and PCI device :154C on physical network 1 (shared-1) with support for 2VFs
    • Flavor 23:
      • 2 vcpus, 12 Mbytes of memory, 20Gb disk
      • Numa page size: 2Mbytes and number pages 6
      • SRIOV-NIC with PCI Vendor: 8086 and PCI device :154C on physical network 2(private-1) with support for 2VFs

...


  • Cloud-region3:
    • Flavor 31:
      • 2 vcpus, 8 Mbytes of memory, 20Gb disk
      • Numa page size: 2Mbytes and number pages 4
      • SRIOV (non-NIC) with PCI vendor: 8086 Device ID: 37c9 Count as 2. (alias={"name":"qat-c62x-vf","product_id":"37c9","vendor_id":"8086"})
    • Flavor 32:
      • 2 vcpus, 8 Gbytes of memory, 20Gb disk
      • Numa page size: 1Gbytes and number pages 8
    • Flavor 33:
      • 2 vcpus, 12 Mbytes of memory, 20Gb disk
      • Numa page size: 2Mbytes and number pages 6
      • SRIOV-NIC with PCI Vendor: 8086 and PCI device :154C on physical network 1(shared-1) with support for 1VFs

...

 



  • Test 1 (Basic)
    • Scenario:
      • Use vFW VNF (firewall, generator and sink)
      • firewall part of  policy asking for:
        • Mandatory:
          • 2 vcpus
          • 8Mbytes of memory
          • >=10Gbytes of disk
          • Numa page size : 2Mbytes and pages 4
        • Optional:
          • SRIOV PCI vendor 8086 and device ID 37c9 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 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 1
      • Generator part of policy asking for:
        • Mandatory;
          • SRIOV-NIC vendor 8086, 154C device ID on shared-1, count 3
      • 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 flavor13 for firewallVM, flavor12 for generator and flavor13 for sink.
      • Why region 1: only cloud region one has support for 3 SRIOV-NIC vfs

 

...



• 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
        • 8Mbytes of memory
        • >=10Gbytes of disk
        • Numa page size : 2Mbytes and pages 4
      • 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

...

  • ONAP managing 1 cloud-region.
    • Cloud-region1
    • All cloud regions are controlled by VMware Integrated Openstack (with HEAT service)
  • Each cloud-region has three flavors
    • Cloud-region 1:
      • onap.flavor1:
        • name: onap.flavor1
        • 2 vcpus, 4 Gbytes of memory, 20Gb disk
        • Add following metadata:
          • quota:memory_reservation_percent: 100
          • quota:cpu_reservation_percent: 100
        • Infrastructure Resource Isolation for VNF w/ Guaranteed QoS (Definition: Cloud Agnostic Intent and Mappings)
        onap.flavor2:
        • name: onap.flavor2
        • 2 vcpus, 8 Gbytes of memory, 20Gb disk 
        • Add following metadata:
          • quota:memory_reservation_percent: 25
          • quota:cpu_reservation_percent: 25
        • Infrastructure Resource Isolation for VNF w/ Burstable QoS, Oversubscription Percentage (Definition: Cloud Agnostic Intent and Mappings) 
        flavor3:
        • name: flavor3
        • 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 > 20% (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-region1 with onap.flavor1 for firewallVM, onap.flavor2 for for generator and any flavor for sink.

...