From 5a92ce53df5d8c6c047c8e648559f012d51054e6 Mon Sep 17 00:00:00 2001 From: Shuhei Matsumoto Date: Fri, 14 Aug 2020 12:29:36 +0900 Subject: [PATCH] doc/iscsi: Fix description about iSCSI login redirection By the previous patches, updating redirect portal and requesting logout are done using different RPCs. Update description to reflect this change. Signed-off-by: Shuhei Matsumoto Change-Id: Id1f00bde39446bc2a8de9635135136b8f0194faf Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/3781 Reviewed-by: Changpeng Liu Reviewed-by: Jim Harris Tested-by: SPDK CI Jenkins --- doc/iscsi.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/doc/iscsi.md b/doc/iscsi.md index ed1e30ff38..7ba30cd9d8 100644 --- a/doc/iscsi.md +++ b/doc/iscsi.md @@ -353,9 +353,10 @@ initiator logs in to the target again through the redirect portal. Users set a portal group to public or private at creation using the `iscsi_create_portal_group` RPC, associate portal groups with a target using the -`iscsi_create_target_node` RPC or the `iscsi_target_node_add_pg_ig_maps` RPC, and +`iscsi_create_target_node` RPC or the `iscsi_target_node_add_pg_ig_maps` RPC, specify a up-to-date redirect portal in a public portal group for a target using -`iscsi_target_node_set_redirect` RPC. +the `iscsi_target_node_set_redirect` RPC, and terminate the corresponding connections +by asynchronous logout request using the `iscsi_target_node_request_logout` RPC. Typically users will use the login redirection feature in scale out iSCSI target system, which runs multiple SPDK iSCSI target applications.