Skip to content

DOCTEAM-2086: post merge-feedback #746

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Amrita42 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

DOCTEAM-2086: post merge-feedback #746

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions articles/iscsi.asm.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -76,11 +76,11 @@
</meta>

<!-- Social Media -->
<meta name="title" its:translate="yes">Introduction to iSCSI</meta>
<meta name="social-descr" its:translate="yes">Understanding iSCSI allows you to treat remote network storage as a locally attached hard drive, giving you the power to run high-performance applications like databases and virtual machines</meta>
<meta name="title" its:translate="yes">Understanding iSCSI Target and Initiator on Linux</meta>
<meta name="social-descr" its:translate="yes">Configure iSCSI target and initiator storage on Linux</meta>

<!-- Search -->
<meta name="description" its:translate="yes">Use iSCSI to manage your storage</meta>
<meta name="description" its:translate="yes">Learn how iSCSI transmits SCSI commands over IP networks to provide systems with block-level access to remote storage configured as local drives</meta>

<abstract>
<variablelist>
Expand Down
7 changes: 5 additions & 2 deletions concepts/intro-iscsi.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@
xmlns:xlink="http://www.w3.org/1999/xlink"
xmlns:trans="http://docbook.org/ns/transclusion">
<info>
<title>About iSCSI</title>
<title>What is iSCSI?</title>
<meta name="maintainer" content="amrita.sakthivel@suse.com" its:translate="no"/>
<abstract>
<para>
Expand All @@ -29,6 +29,8 @@
Note that LU (Logical Unit) is the data container or virtual disk and LUN (Logical Unit Number) is the numerical address of the container.
Linux iSCSI provides iSCSI initiator and iSCSI LIO (Linux-IO) target software for connecting Linux servers to central storage systems.
</para>
<section xml:id="what-is">
<title>What is iSCSI and how does it work?</title>

@dariavladykina dariavladykina Jul 24, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So that it's not repetitive of the chapter title:

Suggested change
<title>What is iSCSI and how does it work?</title>
<title>iSCSI architecture and components</title>

<para>In a physical iSCSI environment, the initiator is the server’s software that requests data, the LIO target is the physical storage appliance that hosts the data and the LUN (Logical Unit Number) represents the specific physical disk capacity assigned to the server.</para>
<itemizedlist>
<listitem><para><emphasis role="bold">The iSCSI Initiator:</emphasis>The initiator is the physical server that needs to consume the storage. It initiates the conversation with the target.</para>

@dariavladykina dariavladykina Jul 24, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<listitem><para><emphasis role="bold">The iSCSI Initiator:</emphasis>The initiator is the physical server that needs to consume the storage. It initiates the conversation with the target.</para>
<listitem><para><emphasis role="bold">The iSCSI Initiator:</emphasis> The initiator is the physical server that needs to consume the storage. It initiates the conversation with the target.</para>

Expand All @@ -47,6 +49,7 @@
</itemizedlist>
</listitem>
</itemizedlist>
</section>
<section xml:id="features-iscsi">
<title>Key characteristics of remote iSCSI storage</title>
<para>Following are some the common characteristics of iSCSI:</para>

@dariavladykina dariavladykina Jul 24, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<para>Following are some the common characteristics of iSCSI:</para>
< para>The following are some of the common characteristics of iSCSI:</para>

Expand All @@ -58,7 +61,7 @@
</itemizedlist>
</section>
<section xml:id="usecase-iscsi">
<title>Use cases for remote iSCSI storage</title>
<title>What are the main use cases for iSCSI storage?</title>
<para>The common use cases for iSCSI include:</para>
<itemizedlist>
<listitem><para><emphasis role="bold">Virtualization:</emphasis> Servers running VMware or Hyper-V store virtual machines on remote iSCSI targets so that if one physical server dies, another can immediately take over the disk over the network.</para></listitem>
Expand Down
26 changes: 18 additions & 8 deletions tasks/install-configure-iscsi-initiator.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,14 +29,24 @@ An iSCSI Initiator is the client component in a SAN that initiates communication
<step><para>Install the iSCSI Initiator if needed:</para>
<screen>&prompt.sudo; zypper install install open-iscsi</screen>
</step>
<step><para>This step is optional as the Initiator name is set by default. Configure the Initiator name. The name must match the ACL created on the Target.
Open the configuration file: </para>
<screen>vi /etc/iscsi/initiatorname.iscsi</screen>
<para>Edit the line to match:</para>
<screen>InitiatorName=iqn.2026-04.com.example:sles.initiator</screen>
<para>Restart the service:</para>
<screen>&prompt.sudo; systemctl restart iscsid </screen>
</step>
<step>
<para>The following steps are optional as the Initiator name is set by default.</para>

@dariavladykina dariavladykina Jul 24, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<para>The following steps are optional as the Initiator name is set by default.</para>
<para>The following steps are optional, as the Initiator name is set by default.</para>

<substeps>
<step>
<para>Configure the Initiator name. The name must match the ACL created on the Target.
Open the configuration file:</para>
<screen>vi /etc/iscsi/initiatorname.iscsi</screen>
</step>
<step>
<para>Edit the line to match:</para>
<screen>InitiatorName=iqn.2026-04.com.example:sles.initiator</screen>
</step>
<step>
<para>Restart the service:</para>
<screen>&prompt.sudo; systemctl restart iscsid</screen>
</step>
</substeps>
</step>

</procedure>

Expand Down
6 changes: 2 additions & 4 deletions tasks/troubleshooting-iscsi.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,10 +72,8 @@ iscsi_target_mod 491520 7
</para></listitem></varlistentry>
<varlistentry><term>Using iSCSI volumes with LVM</term>
<listitem><para>Use the troubleshooting tips in this section when using LVM on iSCSI
targets.</para></listitem></varlistentry>
<varlistentry><term>Check if iSCSI targets connect automatically at boot</term>
<listitem><para>When configuring the iSCSI initiator, ensure that the iSCSI service and target nodes are set to start automatically at boot. This ensures that iSCSI sessions are established during startup, allowing <literal>udev</literal> to initialize the block devices so that LVM can detect and activate the volume groups.</para></listitem></varlistentry>
<varlistentry><term>Check that the iSCSI service automatically establishes target sessions during boot</term>
targets. When configuring the iSCSI initiator, ensure that the iSCSI service and target nodes are set to start automatically at boot. This ensures that iSCSI sessions are established during startup, allowing <literal>udev</literal> to initialize the block devices so that LVM can detect and activate the volume groups.</para></listitem></varlistentry>
<varlistentry><term>Check that the iSCSI service automatically establishes target sessions during boot</term>
<listitem><para>Remember that <filename>udev</filename> provides the default setup for
devices. Ensure that all of the applications that create devices are
started at boot time so that <command>udev</command> can recognize and
Expand Down
10 changes: 6 additions & 4 deletions tasks/workflow-iscsi.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,13 +31,15 @@ Additionally, as an example the iSCSI LIO target server has an IP address <liter
LISTEN 0 256 *:3260 *:* </screen>
<para>You must see <literal>0.0.0.0:3260</literal> or your specific target IP.</para>
</step>
<step><para>Enter the <literal>targetcli</literal> shell and verify the initiator's IQN is listed under the ACLs for your specific TPG (Target Portal Group):
</para>
<step><para>Enter the <literal>targetcli</literal> shell.</para>
<screen>&prompt.sudo; targetcli
targetcli shell version 3.0.1
Copyright 2011-2013 by Datera, Inc and others.
For help on commands, type 'help'.

For help on commands, type 'help'.</screen>
</step>
<step>
<para>Verify the initiator's IQN is listed under the ACLs for your specific TPG (Target Portal Group):</para>
<screen>
/&gt; ls /iscsi
o- iscsi ........................................................[Targets: 1]
o- iqn.2026-04.com.example:sles.target ...........................[TPGs: 1]
Expand Down