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

6 files changed, 14 insertions, 42 deletions

diff --git a/doc/source/install/configure-iscsi.rst b/doc/source/install/configure-iscsi.rst
deleted file mode 100644
index ce90376f5..000000000
--- a/doc/source/install/configure-iscsi.rst
+++ /dev/null
@@ -1,5 +0,0 @@
-Configuring iSCSI-based drivers
--------------------------------
-
-Ensure that the ``qemu-img`` and ``iscsiadm`` tools are installed on the
-**ironic-conductor** host(s).
diff --git a/doc/source/install/configure-tenant-networks.rst b/doc/source/install/configure-tenant-networks.rst
index 37656483b..6fca4cd50 100644
--- a/doc/source/install/configure-tenant-networks.rst
+++ b/doc/source/install/configure-tenant-networks.rst
@@ -93,10 +93,8 @@ provisioning will happen in a multi-tenant environment (which means using the
       * TFTP
       * egress port used for the Bare Metal service (6385 by default)
       * ingress port used for ironic-python-agent (9999 by default)
-      * if using :ref:`iscsi-deploy`, the ingress port used for iSCSI
-        (3260 by default)
       * if using :ref:`direct-deploy`, the egress port used for the Object
-        Storage service (typically 80 or 443)
+        Storage service or the local HTTP server (typically 80 or 443)
       * if using iPXE, the egress port used for the HTTP server running
         on the ironic-conductor nodes (typically 80).
 
diff --git a/doc/source/install/enabling-drivers.rst b/doc/source/install/enabling-drivers.rst
index 344b37131..81c1b9178 100644
--- a/doc/source/install/enabling-drivers.rst
+++ b/doc/source/install/enabling-drivers.rst
@@ -78,7 +78,7 @@ console
 deploy
     defines how the image gets transferred to the target disk. See
     :doc:`/admin/interfaces/deploy` for an explanation of the difference
-    between supported deploy interfaces ``direct`` and ``iscsi``.
+    between supported deploy interfaces.
 
     The deploy interfaces can be enabled as follows:
 
@@ -86,13 +86,10 @@ deploy
 
         [DEFAULT]
         enabled_hardware_types = ipmi,redfish
-        enabled_deploy_interfaces = iscsi,direct
+        enabled_deploy_interfaces = direct,ramdisk
 
-    Additionally,
-
-    * the ``iscsi`` deploy interface requires :doc:`configure-iscsi`
-
-    * the ``direct`` deploy interface requires the Object Storage service
+    .. note::
+      The ``direct`` deploy interface requires the Object Storage service
       or an HTTP service
 inspect
     implements fetching hardware information from nodes. Can be implemented
@@ -186,7 +183,7 @@ IPMI and Redfish, with a few additional features:
     enabled_hardware_types = ipmi,redfish
     enabled_boot_interfaces = pxe
     enabled_console_interfaces = ipmitool-socat,no-console
-    enabled_deploy_interfaces = iscsi,direct
+    enabled_deploy_interfaces = direct
     enabled_inspect_interfaces = inspector
     enabled_management_interfaces = ipmitool,redfish
     enabled_network_interfaces = flat,neutron
@@ -222,7 +219,7 @@ respectively:
 
     [DEFAULT]
     enabled_hardware_types = redfish
-    enabled_deploy_interfaces = iscsi
+    enabled_deploy_interfaces = ansible
     enabled_power_interfaces = redfish
     enabled_management_interfaces = redfish
 
@@ -241,13 +238,13 @@ respectively:
 
     [DEFAULT]
     enabled_hardware_types = redfish
-    enabled_deploy_interfaces = iscsi
+    enabled_deploy_interfaces = ansible
     enabled_power_interfaces = redfish
     enabled_management_interfaces = redfish
 
 This is because the ``redfish`` hardware type will have different enabled
 *deploy* interfaces on these conductors. It would have been fine, if the second
-conductor had ``enabled_deploy_interfaces = direct`` instead of ``iscsi``.
+conductor had ``enabled_deploy_interfaces = direct`` instead of ``ansible``.
 
 This situation is not detected by the Bare Metal service, but it can cause
 inconsistent behavior in the API, when node functionality will depend on
diff --git a/doc/source/install/enrollment.rst b/doc/source/install/enrollment.rst
index ce20f5aad..f52ca08ab 100644
--- a/doc/source/install/enrollment.rst
+++ b/doc/source/install/enrollment.rst
@@ -572,7 +572,7 @@ interfaces for a hardware type (for your deployment):
     +-------------------------------+----------------+
     | default_boot_interface        | pxe            |
     | default_console_interface     | no-console     |
-    | default_deploy_interface      | iscsi          |
+    | default_deploy_interface      | direct         |
     | default_inspect_interface     | no-inspect     |
     | default_management_interface  | ipmitool       |
     | default_network_interface     | flat           |
@@ -581,7 +581,7 @@ interfaces for a hardware type (for your deployment):
     | default_vendor_interface      | no-vendor      |
     | enabled_boot_interfaces       | pxe            |
     | enabled_console_interfaces    | no-console     |
-    | enabled_deploy_interfaces     | iscsi, direct  |
+    | enabled_deploy_interfaces     | direct         |
     | enabled_inspect_interfaces    | no-inspect     |
     | enabled_management_interfaces | ipmitool       |
     | enabled_network_interfaces    | flat, noop     |
@@ -627,10 +627,10 @@ Consider the following configuration (shortened for simplicity):
     [DEFAULT]
     enabled_hardware_types = ipmi,redfish
     enabled_console_interfaces = no-console,ipmitool-shellinabox
-    enabled_deploy_interfaces = iscsi,direct
+    enabled_deploy_interfaces = direct
     enabled_management_interfaces = ipmitool,redfish
     enabled_power_interfaces = ipmitool,redfish
-    default_deploy_interface = direct
+    default_deploy_interface = ansible
 
 A new node is created with the ``ipmi`` driver and no interfaces specified:
 
@@ -654,7 +654,7 @@ Then the defaults for the interfaces that will be used by the node in this
 example are calculated as follows:
 
 deploy
-    An explicit value of ``direct`` is provided for
+    An explicit value of ``ansible`` is provided for
     ``default_deploy_interface``, so it is used.
 power
     No default is configured. The ``ipmi`` hardware type supports only
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.
 
diff --git a/doc/source/install/setup-drivers.rst b/doc/source/install/setup-drivers.rst
index 41abd1f49..8e69b52d6 100644
--- a/doc/source/install/setup-drivers.rst
+++ b/doc/source/install/setup-drivers.rst
@@ -7,4 +7,3 @@ Set up the drivers for the Bare Metal service
    enabling-drivers
    configure-pxe
    configure-ipmi
-   configure-iscsi