While this doesn't have to be across the board, it would be nice if the user could choose a "Network Performance" profile, which this would be the default, and they choose the PCI Device(s) on each of the hosts with the "Network Performance" Profile.
Have the installer do the following for Network Performance Profile:
Enable iommu in grub line
Probe PCI devices
Give the user the ability to choose PCI devices (YAML?) to enable SRIOV. In the YAML have the user specify # of VFs.
Set max_vfs= for the driver.
Setup the Nova PCI White-list : use devname?
Intentionally leaving out the Neutron setup, as DanS has a lot of that figured out.
We added some capabilities to tuned that might work for c#0.
We wrote NFV tuned profiles for RHEL7.2 and KVM, which is being woven into an NFV SKU. I assume this is OSP-based but not sure (will find out).
Tuned in RHEL7.2 added support for a variables.conf file. "Something", whether it's the user or OSP-installer, could write the PCI address of the device to this variables.conf. Then, we could adjust the tuned profiles to implement whatever tuning you want (i.e. add VFs in sysfs).
Does this sound like it could work ?
Tuned doesn't handle module options yet, but here is an RFE for it:
I should note that tuned already supports cmdline options, so we could use that to enable the IOMMU as well.
cmdline = intel_iommu=on
power setting in the BIOS need to be set so RHEL can use tuned, each vendor will be different and power setting for different models cold also be different:
DELL POWEREDGE R620
System Profile Setting:
System Profile: Performance PerWatt (OS)
This bug did not make the OSP 8.0 release. It is being deferred to OSP 10.
*** Bug 1258844 has been marked as a duplicate of this bug. ***
Does latest OSPd contain relevant bits? If so, we can flip the bug to MODIFIED and fill in the 'fixed in version' field.
@Vijay, I flipped it to MODIFIED so that our Errata tooling will be able to pick it up and set it to ON_QA. That is our product flow.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.