916b043710
Until now, whenever NetworkManager gets reloaded/restarted/lease refresh, it would override the /etc/resolv.conf file with the nameservers and related it gets from the network. This patch ensures this won't happen ever again. Note: this is a corrected version of I92bc12b8f712e28962d24dd6474cfce22b81222c that was reverted due to indentation + use of ConfigParser issues. Change-Id: I48560641238911154cc9f353f707a9374613e51a |
||
---|---|---|
.. | ||
cleanup.d | ||
environment.d | ||
finalise.d | ||
glean@.service.d | ||
install.d | ||
post-install.d | ||
pre-install.d | ||
root.d | ||
element-deps | ||
package-installs.yaml | ||
README.rst |
nodepool-base
Tasks to deal with image metadata and other Nodepool cloud specific tweaks.
Name resolution
The image should have the unbound DNS resolver package installed, the
nodepool-base
element then configures it to forward DNS
queries to:
NODEPOOL_STATIC_NAMESERVER_V4
, default:1.0.0.1
NODEPOOL_STATIC_NAMESERVER_V4_FALLBACK
, default:8.8.8.8
.
If NODEPOOL_STATIC_NAMESERVER_POPULATE_IPV6
is set to
1
then the following two servers will be configured as
forwarders too
NODEPOOL_STATIC_NAMESERVER_V6
, default:2606:4700:4700::1111
NODEPOOL_STATIC_NAMESERVER_V6_FALLBACK
, default:2001:4860:4860::8888
Note externally setting either of these values implies
NODEPOOL_STATIC_NAMESERVER_POPULATE_IPV6=1