diff options
| author | Dmitry Tantsur <dtantsur@protonmail.com> | 2021-05-03 17:03:29 +0200 |
|---|---|---|
| committer | Dmitry Tantsur <dtantsur@protonmail.com> | 2021-05-04 14:28:25 +0200 |
| commit | 929907d68473ae8a433ebb8c4dcb110473d42676 (patch) | |
| tree | 3b946e32ddbe3e7e91f1a8a88625b2e23af06add /doc/source/install/refarch | |
| parent | e79f163837dd2c27f84f693aba0f1575fa2353f7 (diff) | |
| download | ironic-929907d68473ae8a433ebb8c4dcb110473d42676.tar.gz | |
Bye-bye iSCSI deploy, you served us well
The iSCSI deploy was very easy to start with, but it has since become
apparently that it suffers from scalability and maintenance issues.
It was deprecated in the Victoria cycle and can now be removed.
Hide the guide to upgrade to hardware types since it's very outdated.
I had to remove the iBMC diagram since my SVG-fu is not enough to fix it.
Change-Id: I2cd6bf7b27fe0be2c08104b0cc37654b506b2e62
Diffstat (limited to 'doc/source/install/refarch')
| -rw-r--r-- | doc/source/install/refarch/common.rst | 17 |
1 files changed, 0 insertions, 17 deletions
diff --git a/doc/source/install/refarch/common.rst b/doc/source/install/refarch/common.rst index f4fdac2b8..ec2a0dbbb 100644 --- a/doc/source/install/refarch/common.rst +++ b/doc/source/install/refarch/common.rst @@ -99,18 +99,6 @@ implementation is available for the hardware, it is recommended using it for better scalability and security. Otherwise, it is recommended to use iPXE, when it is supported by target hardware. -Deploy interface -~~~~~~~~~~~~~~~~ - -There are two deploy interfaces in-tree, ``iscsi`` and ``direct``. See -:doc:`../../admin/interfaces/deploy` for explanation of the difference. -With the ``iscsi`` deploy method, most of the deployment operations happen on -the conductor. If the Object Storage service (swift) or RadosGW is present in -the environment, it is recommended to use the ``direct`` deploy method for -better scalability and reliability. - -.. TODO(dtantsur): say something about the ansible deploy, when it's in - Hardware specifications ~~~~~~~~~~~~~~~~~~~~~~~ @@ -328,11 +316,6 @@ the space requirements are different: ``image_download_source`` can also be provided in the node's ``driver_info`` or ``instance_info``. See :ref:`image_download_source`. -* 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 locally while the instance is active. |