d9dc8f1334
I recently built a ramdisk for IPA and was confused by the fact that the source-repositories name did not match the element name. (this is a convention, confusing when they don't match but certainly not required). This patch makes it so you can use DIB_REPOREF_ironic_agent to customize the IPA ramdisk sources when building ramdisks. For backwards compat if DIB_REPOREF_agent is set it automatically sets the new DIB_REPOREF_ironic_agent to that value as well. Change-Id: I082d989d0d85601f5984dc7c3767b8d66a3d5438 |
||
---|---|---|
.. | ||
cleanup.d | ||
environment.d | ||
finalise.d | ||
install.d | ||
post-install.d | ||
test-elements | ||
element-deps | ||
element-provides | ||
package-installs.yaml | ||
pkg-map | ||
README.rst | ||
source-repository-ironic-agent | ||
svc-map |
============ 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-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`` and ``gcc`` are also installed in order to support source based installation of ironic-python-agent and its dependencies. 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.kernel`` file; 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