
* Move remove-extra-packages to post-install since finalise.d is running on the final image and the DIB documentation recommends avoiding unnecessary actions there. * Remove a few packages that used to be removed only for Fedora; do not try to remove those that aren't on the cloud image. * Do all uninstallations in pre-install phase, so that it doesn't try to remove dependencies of already installed packages. * Exclude more locale files from the image. * Exclude the content of /var/log. Change-Id: Idb7819b1d783f4f5f390cc7621019d3be2fa576f
ironic-python-agent-ramdisk
Builds a ramdisk with ironic-python-agent.
More information can be found at: https://docs.openstack.org/ironic-python-agent/latest/
Beyond installing the ironic-python-agent, this element does the following:
- Installs the
dhcp-all-interfaces
so the node, upon booting, attempts to obtain an IP address on all available network interfaces. - Disables the
iptables
service on SysV and systemd based systems. - Disables the
ufw
service on Upstart based systems. - Installs packages required for the operation of the ironic-python-agent::
-
qemu-utils
parted
hdparm
util-linux
genisoimage
- When installing from source,
python-dev
andgcc
are also installed in order to support source based installation of ironic-python-agent and its dependencies. - Install the certificate if any, which is set to the environment
variable
DIB_IPA_CERT
for validating the authenticity by ironic-python-agent. The certificate can be self-signed certificate or CA certificate. - Compresses initramfs with command specified in environment variable
DIB_IPA_COMPRESS_CMD
, which is 'gzip' by default. This command should listen for raw data from stdin and write compressed data to stdout. Command can be with arguments. - Configures rescue mode if
DIB_IPA_ENABLE_RESCUE
is not set tofalse
.
This element outputs three files:
$IMAGE-NAME.initramfs
: The deploy ramdisk file containing the ironic-python-agent (IPA) service.$IMAGE-NAME.kernel
: The kernel binary file.
Note
The package based install currently only enables the service when using the systemd init system. This can easily be changed if there is an agent package which includes upstart or sysv packaging.
Note
Using the ramdisk will require at least 1.5GB of ram