Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1687947 - Need a procedure for Configuring the Compute pci_passthrough_whitelist parameter: ( 3.1.2 - 5.ii ) [NEEDINFO]
Summary: Need a procedure for Configuring the Compute pci_passthrough_whitelist parame...
Status: NEW
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: RHOS Documentation Team
QA Contact: RHOS Documentation Team
Depends On:
TreeView+ depends on / blocked
Reported: 2019-03-12 17:55 UTC by Derek
Modified: 2019-04-11 14:16 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed:
Target Upstream Version:
dcadzow: needinfo? (kiyyappa)

Attachments (Terms of Use)

Description Derek 2019-03-12 17:55:07 UTC
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 or on 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 )

Note You need to log in before you can comment on or make changes to this bug.