Background:

...

• 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(shared-1) with support for 3VFs2VFs
• 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

...

• 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 privateshared-1, count 12
• Generator part of policy asking for:
• Mandatory;
• SRIOV-NIC vendor 8086, 154C device ID on sharedprivate-1, count 31
• 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 flavor12 for firewallVM , flavor12 and flavor13 for generator and flavor13 for sink VMs.
• Why region 1: only cloud region one has support for 3 SRIOV-NIC vfsflavors that support the unique combinations perfectly

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

...

• 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:
      • Mandatory:
        • 2 vcpus
        • >1Gbytes of memory
        • < 30Gbytes of disk
        • Infrastructure Resource Isolation for VNF w/ Guaranteed QoS (Definition: Cloud Agnostic Intent and Mappings)
    • 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.

...