all: Actually honor public DNS set in IDF 61/69561/1
authorAlexandru Avadanii <Alexandru.Avadanii@enea.com>
Wed, 15 Jan 2020 17:05:55 +0000 (18:05 +0100)
committerAlexandru Avadanii <Alexandru.Avadanii@enea.com>
Thu, 16 Jan 2020 15:34:16 +0000 (16:34 +0100)
commit4deaa15d1e8a9e0e7e0bfb26d4cf3c1b2450c1a1
tree89fca984e19531021328ec5fd37d4895f2f537d9
parent29f7bab413201b24fa09c70eb08a569c78d56f9f
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>
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