11128b0673
Every platform has a different name for their DHCP client, so use a generic name "dhcp-client" in the package name and let everyone choose their sub-name. This also brings some consistency across simple-init & dhcp-all-interfaces Change-Id: I797aa7aacb13dfb7f35700463dc11d55552eb108 |
||
|---|---|---|
| .. | ||
| cleanup.d | ||
| environment.d | ||
| install.d | ||
| README.rst | ||
| element-deps | ||
| package-installs.yaml | ||
| pkg-map | ||
| source-repository-simple-init | ||
README.rst
simple-init
Basic network and system configuration that can't be done until boot
Unfortunately, as much as we'd like to bake it in to an image, we can't know in advance how many network devices will be present, nor if DHCP is present in the host cloud. Additionally, in environments where cloud-init is not used, there are a couple of small things, like mounting config-drive and pulling ssh keys from it, that need to be done at boot time.
Autodetect network interfaces during boot and configure them
The rationale for this is that we are likely to require multiple network interfaces for use cases such as baremetal and there is no way to know ahead of time which one is which, so we will simply run a DHCP client on all interfaces with real MAC addresses (except lo) that are visible on the first boot.
The script /usr/local/sbin/simple-init.sh will be called early in each boot and will scan available network interfaces and ensure they are configured properly before networking services are started.
Processing startup information from config-drive
On most systems, the DHCP approach desribed above is fine. But in some clouds, such as Rackspace Public cloud, there is no DHCP. Instead, there is static network config via config-drive. simple-init will happily call glean which will do nothing if static network information is not there.
Finally, glean will handle ssh-keypair-injection from config drive if cloud-init is not installed.