I'm uncertain as to why this is using the "fedora" element for testing ... but it requires downloading the fedora .qcow on every test which has shown to be unreliable. An easy thing to do is to switch it to fedora-minimal; that will only involve downloads from local mirrors in the gate. Add redhat-rpm-config for minimal. I admit I have not fully gone through why this is not pulled in. It's been an issue since I459f2203fa145049dda185da952813118193d573 and there's all sorts of bugs. Change-Id: I37458e3926dae32a259bd5aa9efc645561b029a0
ironic-agent
- Builds a ramdisk with ironic-python-agent. More information can be found at:
-
https://git.openstack.org/cgit/openstack/ironic-python-agent/
Beyond installing the ironic-python-agent, this element does the following:
- Installs the
dhcp-all-interfacesso the node, upon booting, attempts to obtain an IP address on all available network interfaces. - Disables the
iptablesservice on SysV and systemd based systems. - Disables the
ufwservice on Upstart based systems. - Installs packages required for the operation of the ironic-python-agent::
-
qemu-utilspartedhdparmutil-linuxgenisoimage
- When installing from source,
python-devandgccare 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_CERTfor 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.
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.$IMAGE-NAME.vmlinuz: A hard link pointing to the$IMAGE-NAME.kernelfile; this is just a backward compatibility layer, please do not rely on this 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