openstack/ironic
Code Issues Proposed changes

[doc] Add instructions on making big fake-BM nodes

Browse Source 
Many testing scenarios, including testing "full size" DIB ramdisks
instead of using tinyipa, require adjustment of our proscribed values
for Ironic VM size. Document this in the devstack guide.

Change-Id: I58823fa19d65c12ea2f9229394080f83d1d397f4
This commit is contained in:
Jay Faulkner 2024-08-30 12:36:56 -07:00
parent 3f22f8c5f0
commit 9810fa996a
1 changed files with 20 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
doc/source/contributor/devstack-guide.rst
View File

@ -270,6 +270,20 @@ services to run in that version, too. Just add this config:
``TARGET_BRANCH=stable/2024.1``
.. _ir-vm-size:
VM Sizing and Config
--------------------
Ironic devstack uses VMs to masquerade as baremetal for testing.
You can change the size and number of fake baremetal VMs spun up via
``IRONIC_VM_COUNT``, ``IRONIC_VM_SPECS_RAM`` and, ``IRONIC_VM_SPECS_DISK`` in
your devstack ``local.conf``.
If you want to test fully-featured DIB ramdisks in one of these configs,
increase the value of ``IRONIC_VM_SPECS_RAM``. A value of
``IRONIC_VM_SPECS_RAM=4096`` should be sufficient. If necessary, you can
reduce the ``IRONIC_VM_COUNT`` to free up additional ram for fewer, larger VMs.
Other Devstack Configurations
-----------------------------
@ -497,3 +511,9 @@ a branch or tag::
For more details, see the
`devstack plugin interface documentation
<https://docs.openstack.org/devstack/latest/plugins.html#plugin-interface>`_.
Custom Ironic-Python-Agent ramdisk raising kernel panic
-------------------------------------------------------
The above devstack configurations configure VMs for 2GB ram, which is
insufficient to run anything but the TinyIPA CI ramdisk. See :ref:`ir-vm-size`
for instructions on raising this value.