Description of problem:
Currently, to pass extra heat templates to the deployment, all of the templates need to be placed in a subdirectory of /etc/tripleo/extra_config.d/, and they must either be named *environment*.yaml or *registry*.yaml. This was done specifically so we could just drop the rhel-registration templates directory from tripleo-heat-templates in our extra config drop directory, and it would just work.
However, after trying to explain how this interface works to folks adding other extra configuration, it seems like this was not the best option. I would propose that instead of the drop directory approach, we just pass all extra configuration with individual -e options, exactly how it is done via heatclient.
Changing this interface post GA would potentially make upgrades painful. So, if we are going to change it, we should probably do it now.
(In reply to John Trowbridge from comment #0)
> Description of problem:
> Currently, to pass extra heat templates to the deployment, all of the
> templates need to be placed in a subdirectory of
> /etc/tripleo/extra_config.d/, and they must either be named
> *environment*.yaml or *registry*.yaml.
It's even worse, because the search is for <base_dir>/*/*environment*yaml (or *registry*). So the files actually need to be in /etc/tripleo/extra_config.d/<new_dir>/<files>. The documentation given when running "openstack help overcloud deploy" does not properly specify this.
Follow Trowbridge's suggestion, pass '-e extra-template1.yaml -e extra-template2.yaml' in a similar way to heat's client.
Patch submitted upstream: https://review.gerrithub.io/#/c/237408
Verified : python-rdomanager-oscplugin-0.0.8-13.el7ost.noarch
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.