DOCTEAM-2086: post merge-feedback#746
Open
Amrita42 wants to merge 1 commit into
Open
Conversation
Contributor
Author
|
@dariavladykina please review the entire DC-SLES-ISCSI article. I have tried to implement some of the gem(geo/metadata) suggestions thanks |
dariavladykina
left a comment
dariavladykina
left a comment
Contributor
There was a problem hiding this comment.
Hi Amrita, please see some sugestions for the parts of htis PR. Please let me see the entire article again once this is merged. Thank you!
| <abstract> | ||
| <variablelist> | ||
| <varlistentry> | ||
| <term>WHAT?</term> |
Contributor
There was a problem hiding this comment.
We plan to use the updated abstract from now on, which does not have the What? Why? etc. structure anymore. So we can replace this with sth like: iSCSI (Internet Small Computer Systems Interface) is a networking protocol that transmits SCSI commands over IP networks, allowing a system to access remote storage as locally attached block drives. By using existing Ethernet infrastructure rather than costly dedicated hardware, it enables cost-effective storage consolidation while delivering high-performance, low-latency block access with flexible formatting options for virtualized environments and enterprise databases.
I like the Requirements here, so we can keep them as is.
| </listitem> | ||
| <listitem> | ||
| <para> | ||
| <emphasis>Storage fundamentals:</emphasis> Understanding the difference between file level storage (like a folder on Google Drive) and block level storage (like a raw, unformatted hard drive), as iSCSI is strictly block-level. |
Contributor
There was a problem hiding this comment.
Suggested change
| <emphasis>Storage fundamentals:</emphasis> Understanding the difference between file-level storage (like a folder on Google Drive) and block-level storage (like a raw, unformatted hard drive), as iSCSI is strictly block-level. |
| <title>What is iSCSI and how does it work?</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> |
Contributor
There was a problem hiding this comment.
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> |
| <listitem><para><emphasis role="bold">Physical Ports:</emphasis> These are the dedicated connection points on the server used exclusively for storage traffic to ensure low latency and high throughput.</para></listitem> | ||
| </itemizedlist> | ||
| </listitem> | ||
| <listitem><para><emphasis role="bold">The iSCSI LIO Target:</emphasis>The target is the physical hardware device that houses the data. LIO (Linux-IO) is the standard, open-source storage enterprise-grade target for the Linux kernel.</para> |
Contributor
There was a problem hiding this comment.
Suggested change
| <listitem><para><emphasis role="bold">The iSCSI LIO Target:</emphasis> The target is the physical hardware device that houses the data. LIO (Linux-IO) is the standard, open source storage enterprise-grade target for the Linux kernel.</para> |
| </section> | ||
| <section xml:id="features-iscsi"> | ||
| <title>Key characteristics of remote iSCSI storage</title> | ||
| <para>Following are some the common characteristics of iSCSI:</para> |
Contributor
There was a problem hiding this comment.
Suggested change
| <para>Following are some the common characteristics of iSCSI:</para> | |
| < para>The following are some of the common characteristics of iSCSI:</para> |
| <listitem><para><emphasis role="bold">Block-Level Access:</emphasis> Unlike a network share where you see files, with iSCSI, your system sees raw sectors. This allows you to format the remote drive with any file system such as NTFS, ReFS, or ext4.</para></listitem> | ||
| <listitem><para><emphasis role="bold">Distance and Flexibility:</emphasis> The storage can be in a server rack across the room or in a data center across the city. Because iSCSI uses block-level storage, the system treats this network-attached storage exactly like a local hard drive. | ||
| When traversing these distances, security is maintained by enforcing CHAP for secure authentication between the system and the storage target, alongside IPsec to encrypt the data packets in transit.</para></listitem> | ||
| <listitem><para><emphasis role="bold">Low Latency Requirement:</emphasis> Because the OS thinks the drive is local, it expects fast responses. This is why remote iSCSI usually requires a high-speed network ( preferably 10Gbps or higher).</para></listitem> |
Contributor
There was a problem hiding this comment.
Suggested change
| <listitem><para><emphasis role="bold">Low Latency Requirement:</emphasis> Because the OS thinks the drive is local, it expects fast responses. This is why remote iSCSI usually requires a high-speed network (preferably 10Gbps or higher).</para></listitem> |
| <screen>&prompt.sudo; systemctl restart iscsid </screen> | ||
| </step> | ||
| <step> | ||
| <para>The following steps are optional as the Initiator name is set by default.</para> |
Contributor
There was a problem hiding this comment.
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> |
| 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> |
Contributor
There was a problem hiding this comment.
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> |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR creator: Description
Describe the overall goals of this pull request.
PR creator: Are there any relevant issues/feature requests?
PR reviewer: Checklist for editorial review
Apart from the usual checks, please double-check also the following: