diskimage-builder/diskimage_builder/elements/simple-init
Ian Wienand 643415f366 simple-init: Use wrappers to call pip for glean install
Use the wrapper calls from Ia267a60eecfa8f4071dd477d86daebe07e9a7e38
to install glean.

Using this wrapper means we cover all cases without more and more
branches; it should work for python2, python3 and also the special
case of RHEL/CentOS where dib-python points to the special
/usr/libexec/platform-python (which is python3.6 with inbuilt pip)

Change-Id: If624e8bb66ce0761fc0d5f34c2bed8b93a7daeee
2019-10-07 10:47:09 +00:00
..
environment.d simple-init: default to NetworkManager for CentOS and Fedora 2019-10-07 10:46:57 +00:00
install.d simple-init: Use wrappers to call pip for glean install 2019-10-07 10:47:09 +00:00
post-install.d simple-init: default to NetworkManager for CentOS and Fedora 2019-10-07 10:46:57 +00:00
element-deps Have simple-init enable network.service 2017-03-28 19:28:51 +11:00
package-installs.yaml simple-init: allow for NetworkManager support 2018-11-30 10:02:47 +11:00
pkg-map Fedora 30 functional and boot tests 2019-08-28 11:21:46 +10:00
README.rst Replace git.openstack.org URLs with opendev.org URLs 2019-05-16 14:45:52 +08:00
source-repository-simple-init Replace git.openstack.org URLs with opendev.org URLs 2019-05-16 14:45:52 +08:00

===========
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.

Chosing glean installation source
---------------------------------

By default glean is installed using pip using the latest release on pypi.
It is also possible to install glean from a specified git repository
location. This is useful for debugging and testing new glean changes
for example. To do this you need to set these variables::

  DIB_INSTALLTYPE_simple_init=repo
  DIB_REPOLOCATION_glean=/path/to/glean/repo
  DIB_REPOREF_glean=name_of_git_ref

For example to test glean change 364516 do::

  git clone https://opendev.org/opendev/glean /tmp/glean
  cd /tmp/glean
  git review -d 364516
  git checkout -b my-test-ref

Then set your DIB env vars like this before running DIB::

  DIB_INSTALLTYPE_simple_init=repo
  DIB_REPOLOCATION_glean=/tmp/glean
  DIB_REPOREF_glean=my-test-ref

NetworkManager
--------------

By default, this uses the "legacy" scripts on each platform.  To use
NetworkManager instead, set ``DIB_SIMPLE_INIT_NETWORKMANAGER`` to
non-zero.  See the glean documentation for what the implications for
this are on each platform.

This is currently only implemented for CentOS and Fedora platforms.