Update refarch with information about image_download_source
Change-Id: Ia06b01e89d79bf0f65d95dd0c20e91b456b8acae
This commit is contained in:
parent
bad281cf16
commit
e79f163837
|
@ -27,6 +27,8 @@ You can specify this deploy interface when creating or updating a node::
|
||||||
``agent``. This is because before the Kilo release **ironic-python-agent**
|
``agent``. This is because before the Kilo release **ironic-python-agent**
|
||||||
used to only support this deploy interface.
|
used to only support this deploy interface.
|
||||||
|
|
||||||
|
.. _image_download_source:
|
||||||
|
|
||||||
Deploy with custom HTTP servers
|
Deploy with custom HTTP servers
|
||||||
-------------------------------
|
-------------------------------
|
||||||
|
|
||||||
|
|
|
@ -312,15 +312,26 @@ the space requirements are different:
|
||||||
|
|
||||||
* The deployment kernel and ramdisk are always cached during the deployment.
|
* The deployment kernel and ramdisk are always cached during the deployment.
|
||||||
|
|
||||||
* The ``iscsi`` deploy method requires caching of the whole instance image
|
* When ``[agent]image_download_source`` is set to ``http`` and Glance is used,
|
||||||
locally during the deployment. The image has to be converted to the raw
|
the conductor will download instances images locally to serve them from its
|
||||||
format, which may increase the required amount of disk space, as well as
|
HTTP server. Use ``swift`` to publish images using temporary URLs and convert
|
||||||
the CPU load.
|
them on the node's side.
|
||||||
|
|
||||||
|
When ``[agent]image_download_source`` is set to ``local``, it will happen
|
||||||
|
even for HTTP(s) URLs. For standalone case use ``http`` to avoid unnecessary
|
||||||
|
caching of images.
|
||||||
|
|
||||||
|
In both cases a cached image is converted to raw if ``force_raw_images``
|
||||||
|
is ``True`` (the default).
|
||||||
|
|
||||||
.. note::
|
.. note::
|
||||||
This is not a concern for the ``direct`` deploy interface, as in this case
|
``image_download_source`` can also be provided in the node's
|
||||||
the deployment ramdisk downloads the image and either streams it to the
|
``driver_info`` or ``instance_info``. See :ref:`image_download_source`.
|
||||||
disk or caches it in memory.
|
|
||||||
|
* The ``iscsi`` deploy method always requires caching of the whole instance
|
||||||
|
image locally during the deployment. The image has to be converted to the raw
|
||||||
|
format, which may increase the required amount of disk space, as well as the
|
||||||
|
CPU load.
|
||||||
|
|
||||||
* When network boot is used, the instance image kernel and ramdisk are cached
|
* When network boot is used, the instance image kernel and ramdisk are cached
|
||||||
locally while the instance is active.
|
locally while the instance is active.
|
||||||
|
|
Loading…
Reference in New Issue