933f1afefd
This patch drops use of the vip-hosts.yaml service which can cause issues during deployment because puppet 'hosts' resources overwrite the data in /etc/hosts. The only reason things seem to work at all at the moment is because our hosts element in t-i-e runs on each os-refresh-config iteration and re-adds the dropped hosts entries. To work around the issue we add a conditional which selectively adds the extra hosts entries only if the AddVipsToEtcHosts is set to true. Closes-bug: 1645123 Change-Id: Ic6aaeb249a127df83894f32a704219683a6382b2
28 lines
671 B
YAML
28 lines
671 B
YAML
heat_template_version: 2016-10-14
|
|
description: 'All Hosts Config'
|
|
|
|
parameters:
|
|
hosts:
|
|
type: string
|
|
|
|
resources:
|
|
|
|
hostsConfigImpl:
|
|
type: OS::Heat::StructuredConfig
|
|
properties:
|
|
group: os-apply-config
|
|
config:
|
|
hosts: {get_param: hosts}
|
|
|
|
outputs:
|
|
config_id:
|
|
description: The ID of the hostsConfigImpl resource.
|
|
value:
|
|
{get_resource: hostsConfigImpl}
|
|
hosts_entries:
|
|
description: |
|
|
The content that should be appended to your /etc/hosts if you want to get
|
|
hostname-based access to the deployed nodes (useful for testing without
|
|
setting up a DNS).
|
|
value: {get_attr: [hostsConfigImpl, config, hosts]}
|