We currently do not configure linux:network:resolv:dns via reclass
pillar data, so we don't actually enforce the public DNS set in
the IDF file, but instead leave it to the OS to figure it out, which
most of the time works fine, but it's not completely reliable.
Change that behavior to instead enforce it via linux.network.resolv
state across all cluster nodes.
Change-Id: I4f82315a473fcbdc8573380cfcac1e30b44c3dd4
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
(cherry picked from commit
4deaa15d1e8a9e0e7e0bfb26d4cf3c1b2450c1a1)
~kernel:
sysctl:
net.ipv4.ip_forward: 1
- network:
- resolv:
- dns:
-{%- for server in nm.dns_public %}
- - {{ server }}
-{%- endfor %}
iptables:
schema:
epoch: 1
minion:
tcp_keepalive: True
tcp_keepalive_idle: 60
+ linux:
+ network:
+ resolv:
+ dns:
+{%- for server in nm.dns_public %}
+ - {{ server }}
+{%- endfor %}
hostname: cfg01
domainname: {{ conf.cluster.domain }}
privileged: true
+ dns:
+{%- for server in nm.dns_public %}
+ - {{ server }}
+{%- endfor %}
{%- if nm.cluster.has_baremetal_nodes %}
opnfv-fuel-maas:
container_name: "maas"
hostname: mas01
domainname: {{ conf.cluster.domain }}
privileged: true
+ dns:
+{%- for server in nm.dns_public %}
+ - {{ server }}
+{%- endfor %}
ports:
- 5240:5240
{%- endif %}