ba808fa6ec
The ironic-agent element is created using the disk-image-create utility (even being a ramdisk) and outputs a .vmlinuz file for the kernel (different than the ramdisk-image-create which outputs a .kernel file for the kernel). This is inconsistent and make scripting against the diskimage-builder more complicated if one wants to support different types of ramdisk. This patch creates a hard link for the .vmlinuz file to a .kernel file at the end of the process (to keep backward compatibility) and print a deprecation message. Depends-On: I81400305f166d62aa4612aab54602abb8178b64c Change-Id: I476f9ec9ec4206ece0261eaaf2b4182c6bcbd802 Closes-Bug: #1482606
35 lines
1.5 KiB
ReStructuredText
35 lines
1.5 KiB
ReStructuredText
============
|
|
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
|