The configuration input to director for overcloud operations is a variable list of yaml files and file trees of yamls. This makes for a challenging support and operational environment. There is no consistent practice of where to keep these files and trees. Because they do not have to be located in a specific location tooling such as updates will not necessarily find them. 
Support and customers spend much time looking for, reconstructing and diff’ing to  understanding exactly which files were used in a previous or the next director operation. 
Because there is no integrated history or change control of the files it can commonly occur that the past configuration simply can not be known or reconstructed
Upgrade is often unknowingly broken, The field and customers often copy the entire default tree to a new location which takes it out of the path of any upgrade utilities and is undetected 


a. Add a version ID and included it in each configuration yaml file
This will allow a yaml file from a previous OSP version can be identified regardless of where the user is referencing them from
b. Add a Checksum for every configuration yaml file
This will allow tooling to detect modification of the contents regardless of where the user is referencing them from
c. Automatically tar up and save for a successful director operation
The saved tarballs could be placed in the filesystem or stuffed in the undercloud or overcloud db?