Comment 5 for bug 1638428

Yeahp,

Just to clarify, if you need to reference templates from THT use the -e option and then use the --environment-directory for your custom env. files.

i.e.

openstack overcloud deploy \
--libvirt-type qemu \
--ntp-server pool.ntp.org \
--templates /home/stack/tripleo-heat-templates \
-e /home/stack/tripleo-heat-templates/environments/puppet-pacemaker.yaml \
-e /home/stack/tripleo-heat-templates/environments/network-isolation.yaml \
-e /home/stack/tripleo-heat-templates/environments/storage-environment.yaml \
-e /home/stack/tripleo-heat-templates/environments/ips-from-pool-all.yaml \
-e /home/stack/tripleo-heat-templates/environments/storage-environment.yaml \
-e /home/stack/tripleo-heat-templates/environments/enable-tls.yaml \
-e /home/stack/tripleo-heat-templates/environments/tls-endpoints-public-dns.yaml \
--environment-directory /home/stack/nuclab/ \
--debug

Then, in /home/stack/nuclab/ save:

  00-nuclab-host-definitions.yaml
  01-nuclab-storage-environment.yaml
  02-nuclab-network-environment.yaml
  03-nuclab-customisations.yaml
  04-nuclab-enable-ssl.yaml

This will keep THT structure getting relative paths correctly and you can reference your custom env files in another place.

In this case, you don't have to change or copy any file.

Does it sound as a good approach?

Cheers,
Carlos.