openstack
/
ironic
Code Issues Proposed changes

Add note regarding configuration drives to tuning docs 

Configuraiton drives get stored in the instance_info field which
is of a text type, which in theory is not a big deal, however large
configuration drives are returned over the database client
and when entire node objects are generated by the client, which
has an obvious bandwidth and record transfer latency overhead.

Change-Id: I7f2b6ab9c3adf88202f213a42af7553cf9e8276d
This commit is contained in:
Julia Kreger 2021-05-04 12:18:59 -07:00
parent 416a0951c8
commit 85212fead4
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/source/admin/tuning.rst
View File

@ -215,3 +215,9 @@ use.
wish to explore a mix of the ``direct`` deploy interface and caching
proxies. Such a configuration can be highly beneficial in wide area
deployments. See :ref:`Using proxies for image download <ipa-proxies>`.
* If you're making use of large configuration drives, you may wish to ensure
you're using Swift to store them as opposed to housing them inside of the
database. The entire object and contents are returned whenever Ironic
needs to evaluate the entire node, which can become a performance impact.
For more information on configuration drives, please see
:ref:`Enabling the configuration drive <configdrive>`.