"Fossies" - the Fresh Open Source Software Archive 
Source code changes of the file "doc/source/install/refarch/common.rst" between
ironic-17.0.2.tar.gz and ironic-17.0.3.tar.gz
About: OpenStack Ironic (Optional Service: Bare-Metal Provisioning) aims to provision bare metal machines instead of virtual machines, forked from the Nova baremetal driver. The "Wallaby" series (latest release).
| common.rst (ironic-17.0.2) | : | common.rst (ironic-17.0.3) | ||
|---|---|---|---|---|
| skipping to change at line 315 | skipping to change at line 315 | |||
| Disk space | Disk space | |||
| ^^^^^^^^^^ | ^^^^^^^^^^ | |||
| Each conductor needs enough free disk space to cache images it uses. | Each conductor needs enough free disk space to cache images it uses. | |||
| Depending on the combination of the deploy interface and the boot option, | Depending on the combination of the deploy interface and the boot option, | |||
| the space requirements are different: | 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. | |||
| .. note:: | .. note:: | |||
| All images may be stored for some time after they are no longer needed. | All images may be stored for some time after they are no longer needed. | |||
| This is done to speed up simultaneous deployments of many similar images. | This is done to speed up simultaneous deployments of many similar images. | |||
| The caching can be configured via the ``image_cache_size`` and | The caching can be configured via the ``image_cache_size`` and | |||
| ``image_cache_ttl`` configuration options in the ``pxe`` group. | ``image_cache_ttl`` configuration options in the ``pxe`` group. | |||
| End of changes. 2 change blocks. | ||||
| 7 lines changed or deleted | 18 lines changed or added | |||