Description of problem:
VLAN Tagging Provisioning network for overcloud

Version-Release number of selected component (if applicable):
Below paragraph is creating Big confusion for customer .

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/7/html-single/Director_Installation_and_Usage/

..focussing on the following paragraph in section 2.3:

"The Provisioning network provides DHCP and PXE boot functions to help discover bare metal systems for use in the Overcloud. This network should ideally use a native VLAN on a trunked interface so that the director serves PXE boot and DHCP requests. "

...specifically, the word "ideally".

Our documentation doesn't say we *must* use a native VLAN - merely that it's a preference - but it doesn't provide any other guidance
How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
 should say that *ideally* tagging should not be used, or how to proceed if tagging *must* be used

Expected results:

clarify our documentation to make untagged provisioning a requirement rather than a recommendation, or provide details on how to proceed when tagging is being used.
Additional info: