Bug 1687947

Description of problem:
CES from Ribbon Communications Inc: "Documentation could use some work".  Direct communication with the customer (Jamir Ivy) yielded that the issue is: 

If you look at case 02238281, the engineer gives me a solution but provides no documentation for inputs(puppet input parameters for nova) to that solution. This is not a knock on the engineer because I couldn’t find any documentation on openstack.org or on redhat.com. The engineer had to finally test different variations of the inputs in his test environment before he provided me with a working solution to the issue I had. There was no suggestion to me that any documentation would be created around these  puppet parameter inputs usage which is a recommendation to a common issue any cloud designer would have.  

The engineer involved was Kosal Raj.  He said: 

The solution is shared by Anil Dhingra from one the test environment. I don't see it in our documentation also.

After comparing the templates with our test environment:

Parameter in customer environment,
~~~
nova::compute::pci_passthrough: “[ { ‘devname’:’ens1f0′,’physical_network’:’sriova’ },{ ‘devname’:’ens1f1′,’physical_network’:’sriovb’ }, { ‘devname’:’ens2f0′,’physical_network’:’sriova’ }, { ‘devname’:’ens2f1′,’physical_network’:’sriovb’ } ]”
~~~

Working parameter in our test environment with multiple role,
~~~~
# List of PCI Passthrough whitelist parameters.
    nova::compute::pci_passthrough: "'[{\"devname\": \"ens1f0\", \"physical_network\": \"providernetsriov1\"},{\"devname\": \"ens1f1\", \"physical_network\": \"providernetsriov2\"}]'"
~~~~

This need to be verified from RHOSP engineering team to add or improvise the document.

The provided steps comes under Installation and Configuration section.

The steps I shared is the alternative way to specify to configure the Compute pci_passthrough_whitelist parameter: ( 3.1.2 - 5.ii )

https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/10/html-single/network_functions_virtualization_configuration_guide/#modify_link_linkend_ap_sriov_network_environment_literal_network_environment_yaml_literal_link