openstack-ansible-lxc_hosts/container-resolv-host-match-c6e3760cf4a8e5cd.yaml at c1cff6dfdcbd21f71679f880cdeafb2bc336f6d9 - openstack-ansible-lxc_hosts - OpenDev: Free Software Needs Free Tools

openstack/openstack-ansible-lxc_hosts

Jesse Pretorius f11bbc4f34 Make the LXC cache prep use the host resolver config

Currently the container cache preparation process uses a list of
resolver addresses in order to prepare the container DNS resolution
configuration.

This presents a few problems:
- The default value is set to Google's DNS addresses, which may not
  be accessible from a deployer's environment. This will cause an
  installation to fail and the deployer will have to dig around to
  find out why. This is counterintuitive - it would be better if the
  default process was to discover the host's configuration and to use
  that instead.
- Nothing other than a very simple resolv.conf can be implemented.
  Deployers may wish to implement more advanced settings such as
  timeouts and round-robin queries.

This patch changes the image cache preparation process to ensure that
the container resolver configuration matches that of the host. This is
simpler and more intuitive.

Change-Id: I66b448dee361e231d172eb278b290ec4dccfdf97

2016-05-27 16:21:07 +00:00

7 lines

258 B

YAML

Raw Blame History

 ---
 upgrade:
   - The LXC container cache preparation process now copies DNS
     resolution configuration from the host instead of implementing
     its own configuration. The ``lxc_cache_resolvers`` variable
     is therefore unnecessary and has been removed.