67cbecdfb4
I was a little too hasty in I76acbd08acda20c88ff9fd9148e3918b78d6c6c6 removing the scripts/ directory. It has broken the puppeting of old hosts. Restore the directory with a blank file explaining the situation. Also, we don't need to copy this in the nodepool elements; remove that. Change-Id: I8b82950237ef69c4941866900cac9bda42f58ca2 |
||
---|---|---|
.. | ||
cleanup.d | ||
environment.d | ||
finalise.d | ||
glean@.service.d | ||
install.d | ||
post-install.d | ||
pre-install.d | ||
root.d | ||
README.rst | ||
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