Description of problem:

There is a need for customers to build in additional tools to help support their environments from an IPA perspective and an overcloud image perspective.  An example of this is the HP Proliant tools which are proprietary so they would not be shipped in the image by default. 

The concern about supportability comes into play as well when rebuilding these images.

If we could document the process of how we build the overcloud/IPA images, that would ensure when customers rebuild them, they still contain the elements we used to build them and they would still be supportable but then also contain the additional software the customer needs but we could not ship. 

Note there are options to use virt-customize and documentation to push in packages into a IPA image, however it might be a bit cleaner/elegant to provide the rebuild of the images option as described above.


Version-Release number of selected component (if applicable):
OSP9

How reproducible:
100%

Steps to Reproduce:
1.
2.
3.

Actual results:
No documentation on how to rebuild the overcloud/IPA images

Expected results:
Documentation on how to rebuild the overcloud/IPA images

Additional info: