History

Ian Wienand f7a8f02462 nodepool elements: create suse boot rc directory As noted inline, the /etc/init.d directory appears to have been somehow remove/no longer created with a recent update. I've added this manually and the image builds, and the rc-local.service still runs. Do this for now to unblock other builds. Change-Id: I0b0b2e38951bad656bcfdb47b6470e033564db59		2021-03-17 13:37:12 +11:00
..
cleanup.d	Remove root user .cache folder	2017-04-20 15:22:28 -04:00
environment.d	Switch from 1.1.1.1 to 1.0.0.1	2019-04-25 13:14:53 +00:00
finalise.d	nodepool elements: create suse boot rc directory	2021-03-17 13:37:12 +11:00
glean@.service.d	Create glean@.service.d/override.conf	2017-08-18 16:28:54 -04:00
install.d	Revert "Pin setuptools<50 in our image venvs"	2020-09-03 09:19:52 -07:00
post-install.d	Bye, Bye, Trusty	2020-01-19 16:00:55 +01:00
pre-install.d	Stop installing and running puppet in node builds	2017-04-27 23:23:32 +02:00
root.d	Use AFS mirrors to build ubuntu-bionic DIB	2018-04-02 12:45:24 -04:00
element-deps	nodepool-elements: Use venv for utilities	2020-03-11 10:12:00 +11:00
package-installs.yaml	Manage unbound on zuul workers in DIB	2017-04-04 09:32:36 +02:00
README.rst	Restore blank nodepool/scripts	2020-03-03 15:01:23 +11:00

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