doc: Update rbd-target-gw behavior info

The lio setup and teardown functionality was moved from rbd-target-gw to
rbd-target-api in ceph-iscsi.

Signed-off-by: Mike Christie <mchristi@redhat.com>

diff --git a/doc/rbd/iscsi-target-ansible.rst b/doc/rbd/iscsi-target-ansible.rst
index 0553bb1ed801522794c532a81191f0a90206d9e3..42e1c64e8af26d0ff6edf486b21c955933f85a1e 100644 (file)
--- a/doc/rbd/iscsi-target-ansible.rst
+++ b/doc/rbd/iscsi-target-ansible.rst
@@ -111,19 +111,19 @@ On the Ansible installer node, perform the following steps.
 **Service Management:**
 
 The ``ceph-iscsi`` package installs the configuration management
-logic and a Systemd service called ``rbd-target-gw``. When the Systemd
-service is enabled, the ``rbd-target-gw`` will start at boot time and
+logic and a Systemd service called ``rbd-target-api``. When the Systemd
+service is enabled, the ``rbd-target-api`` will start at boot time and
 will restore the Linux IO state. The Ansible playbook disables the
 target service during the deployment. Below are the outcomes of when
-interacting with the ``rbd-target-gw`` Systemd service.
+interacting with the ``rbd-target-api`` Systemd service.
 
 ::
 
-    # systemctl <start|stop|restart|reload> rbd-target-gw
+    # systemctl <start|stop|restart|reload> rbd-target-api
 
 -  ``reload``
 
-   A reload request will force ``rbd-target-gw`` to reread the
+   A reload request will force ``rbd-target-api`` to reread the
    configuration and apply it to the current running environment. This
    is normally not required, since changes are deployed in parallel from
    Ansible to all iSCSI gateway nodes