all: Actually honor public DNS set in IDF 63/69563/1
authorAlexandru Avadanii <Alexandru.Avadanii@enea.com>
Wed, 15 Jan 2020 17:05:55 +0000 (18:05 +0100)
committerAlexandru Avadanii <Alexandru.Avadanii@enea.com>
Fri, 17 Jan 2020 10:20:25 +0000 (10:20 +0000)
commit2dc42cd75a3fc5ee4147c4180ba78ad415b09381
treee152b7cbb530b8ac349130b6b2ef20a69e855b7e
parent238ed19eb4d7cd755bbc95c40e2399cc66eb6fc1
all: Actually honor public DNS set in IDF

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)
mcp/reclass/classes/cluster/all-mcp-arch-common/infra/maas.yml.j2
mcp/reclass/classes/cluster/all-mcp-arch-common/opnfv/init.yml.j2
mcp/scripts/docker-compose/docker-compose.yaml.j2