aboutsummaryrefslogtreecommitdiffstats
path: root/overcloud-resource-registry-puppet.j2.yaml
diff options
context:
space:
mode:
authorJuan Antonio Osorio Robles <jaosorior@redhat.com>2016-11-28 12:58:25 +0200
committerJuan Antonio Osorio Robles <jaosorior@redhat.com>2016-12-01 11:08:41 +0200
commit7a2c2b0f938716f6fc584f1c53ac3fa2896d70f3 (patch)
tree058f9aae39e672197aee704eb258dc99516c4b1f /overcloud-resource-registry-puppet.j2.yaml
parent787685101179f13f6074901070cf307bd9bb0731 (diff)
Introduce network-based FQDNs via hiera
Currently, one can get the network-based FQDNs via a custom puppet fact. This is currently unreliable, as it's based on the ::hostname fact which we assume it's set correctly by nova. However, this is not necessarily the case (for instance, if you use pre-deployed services such as we do with the multinode-jobs). In these cases, the ::hostname fact will return something other than what we specified in nova, and effectively breaks the configurations in we relly too much on the network-based FQDN facts. By using hiera instead, we avoid this issue as we set those values to be exactly what we expect (as we set them in the OS::TripleO::Server resource. Change-Id: I6ce31237098f57bdc0adfd3c42feef0073c224fb
Diffstat (limited to 'overcloud-resource-registry-puppet.j2.yaml')
0 files changed, 0 insertions, 0 deletions