en-US/Contributors_and_production_methods.xml en-US/Disk_Partitioning_Advanced_Storage_common-para-1.xml en-US/Installation_Guide.xml en-US/iSCSI.xml en-US/X86_Uninstall.xml
Rüdiger Landmann
rlandmann at fedoraproject.org
Tue Mar 31 04:09:16 UTC 2009
en-US/Contributors_and_production_methods.xml | 5 +
en-US/Disk_Partitioning_Advanced_Storage_common-para-1.xml | 2
en-US/Installation_Guide.xml | 1
en-US/X86_Uninstall.xml | 4
en-US/iSCSI.xml | 60 +++++++++++++
5 files changed, 69 insertions(+), 3 deletions(-)
New commits:
commit 45a20353fd382c8364d8d670fd34125e56c832cd
Author: Ruediger Landmann <r.landmann at redhat.com>
Date: Tue Mar 31 14:08:50 2009 +1000
Add section on iSCSI contributed by BaseOS team
diff --git a/en-US/Contributors_and_production_methods.xml b/en-US/Contributors_and_production_methods.xml
index 9b40cc8..1302de4 100644
--- a/en-US/Contributors_and_production_methods.xml
+++ b/en-US/Contributors_and_production_methods.xml
@@ -61,6 +61,11 @@
</listitem>
<listitem>
<para>
+ <ulink url="https://fedoraproject.org/wiki/HansdeGoede">Hans De Goede</ulink> (writer)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
<ulink url="http://fedoraproject.org/wiki/PiotrDr%C4%85g">Piotr DrÄ…g</ulink> (translator - Polish)
</para>
</listitem>
diff --git a/en-US/Disk_Partitioning_Advanced_Storage_common-para-1.xml b/en-US/Disk_Partitioning_Advanced_Storage_common-para-1.xml
index f967d0e..71855c5 100644
--- a/en-US/Disk_Partitioning_Advanced_Storage_common-para-1.xml
+++ b/en-US/Disk_Partitioning_Advanced_Storage_common-para-1.xml
@@ -3,5 +3,5 @@
]>
<para>
- From this screen you can choose to disable a dmraid device, in which case the individual elements of the dmraid device will appear as separate hard drives. You can also choose to configure an iSCSI (SCSI over TCP/IP) target.
+ From this screen you can choose to disable a dmraid device, in which case the individual elements of the dmraid device will appear as separate hard drives. You can also choose to configure an iSCSI (SCSI over TCP/IP) target. See <xref linkend="ISCSI_disks" /> for an introduction to iSCSI.
</para>
\ No newline at end of file
diff --git a/en-US/Installation_Guide.xml b/en-US/Installation_Guide.xml
index 19aaa66..a652e1c 100644
--- a/en-US/Installation_Guide.xml
+++ b/en-US/Installation_Guide.xml
@@ -127,6 +127,7 @@
</para>
</partintro>
<xi:include href="Partitions-x86.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="iSCSI.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
<xi:include href="DiskEncryptionUserGuide.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
<xi:include href="Understanding_LVM.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
<xi:include href="Grub.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
diff --git a/en-US/X86_Uninstall.xml b/en-US/X86_Uninstall.xml
index d5b93fe..c558667 100644
--- a/en-US/X86_Uninstall.xml
+++ b/en-US/X86_Uninstall.xml
@@ -15,7 +15,7 @@
<!-- End Index terms -->
<para>
- Because we respect your freedom to choose an operating system for your computer, this section explains how to uninstall Fedora.
+ We respect your freedom to choose an operating system for your computer. This section explains how to uninstall Fedora.
</para>
<warning>
@@ -38,7 +38,7 @@
</para>
<para>
- These instructions cannot cover every possible computer configuration. If your computer is configured to boot three or more operating systems, or has a highly-customized partition scheme, use the following sections as a general guide to partition removal with the various tools described. In these situations, you will also need to learn to configure your chosen bootloader. See the appendix on bootloaders for a general introduction to the subject, but detailed instructions are beyond the scope of this document.
+ These instructions cannot cover every possible computer configuration. If your computer is configured to boot three or more operating systems, or has a highly-customized partition scheme, use the following sections as a general guide to partition removal with the various tools described. In these situations, you will also need to learn to configure your chosen bootloader. See <xref linkend="ch-grub"/> for a general introduction to the subject, but detailed instructions are beyond the scope of this document.
</para>
<important>
diff --git a/en-US/iSCSI.xml b/en-US/iSCSI.xml
new file mode 100644
index 0000000..2d6dfa3
--- /dev/null
+++ b/en-US/iSCSI.xml
@@ -0,0 +1,60 @@
+<?xml version="1.0" encoding="utf-8"?>
+
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
+
+<appendix id="ISCSI_disks">
+<title>ISCSI disks</title>
+ <para><firstterm>Internet Small Computer System Interface</firstterm> (iSCSI) is a protocol that allows computers to communicate with storage devices by SCSI requests and responses carried over TCP/IP. Because iSCSI is based on the standard SCSI protocols, it uses some terminology from SCSI. The device on the SCSI bus to which requests get sent (and which answers these requests) is known as the <firstterm>target</firstterm> and the device issuing requests is known as the <firstterm>initiator</firstterm>. In other words, an iSCSI disk is a target and the iSCSI software equivalent of a SCSI controller or SCSI Host Bus Adapter (HBA) is called an initiator. This appendix only covers Linux as an iSCSI initiator: how Linux uses iSCSI disks, but not how Linux hosts iSCSI disks.</para>
+
+ <para>Linux has a software iSCSI initiator in the kernel that takes the place and form of a SCSI HBA driver and therefore allows Linux to use iSCSI disks. However, as iSCSI is a fully network-based protocol, iSCSI initiator support needs more than just the ability to send SCSI packets over the network. Before Linux can use an iSCSI target, Linux must find the target on the network and make a connection to it. In some cases, Linux must send authentication information to gain access to the target. Linux must also detect any failure of the network connection and must establish a new connection, including logging in again if necessary.</para>
+
+ <para>The discovery, connection, and logging in is handled in userspace by the <application>iscsiadm</application> utility, and the error handling is also handled in userspace by <application>iscsid</application>.</para>
+
+ <para>Both <application>iscsiadm</application> and <application>iscsid</application> are part of the <application>iscsi-initiator-utils</application> package under Fedora.</para>
+
+
+ <section id="sn-iSCSI_in_Fedora-iSCSI_disks_in_anaconda">
+ <title>iSCSI disks in <application>anaconda</application></title>
+ <para><application>Anaconda</application> can discover (and then log in to) iSCSI disks in two ways:</para>
+
+ <orderedlist>
+ <listitem>
+ <para>When anaconda starts, it checks if the BIOS or add-on boot ROMs of the system support <firstterm>iSCSI Boot Firmware Table</firstterm> (iBFT), a BIOS extension for systems which can boot from iSCSI. If the BIOS supports iBFT, <application>anaconda</application> will read the iSCSI target information for the configured boot disk from the BIOS and log in to this target, making it available as an installation target.</para>
+ </listitem>
+ <listitem>
+ <para>The initial partitioning screen presents you with an <guilabel>Advanced storage configuration</guilabel> button that allows you to add iSCSI target information like the discovery IP-address. <application>Anaconda</application> will probe the given IP-address and log in to any targets that it finds. See <xref linkend="s1-advanced-storage-x86"/> for the details that you can specify for iSCSI targets.</para>
+ </listitem>
+ </orderedlist>
+
+ <para>While <application>anaconda</application> uses <application>iscsiadm</application> to find and log into iSCSI targets, <application>iscsiadm</application> automatically stores any information about these targets iscsiadm iSCSI database. <application>Anaconda</application> then copies this database to the installed system and marks any iSCSI targets not used for <filename>/</filename> so that the system will automatically log in to them when it starts. If <filename>/</filename> is placed on an iSCSI target, <application>initrd</application> will log into this target and <application>anaconda</application> does not include this target in start up scripts to avoid multiple attempts to log into the same target.</para>
+
+ <para>If <filename>/</filename> is placed on an iSCSI target, <application>anaconda</application> sets <application>NetworkManager</application> to ignore any network interfaces that were active during the installation process. These interfaces will also be configured by <application>initrd</application> when the system starts. If <application>NetworkManager</application> were to reconfigure these interfaces, the system would lose its connection to <filename>/</filename>.</para>
+ </section>
+
+
+ <section id="sn-iSCSI_disks_during_start_up">
+ <title>iSCSI disks during start up</title>
+ <para>ISCSI-related events might occur at a number of points while the system starts:</para>
+
+ <orderedlist>
+ <listitem>
+ <para>The init script in the <application>initrd</application> will log in to iSCSI targets used for <filename>/</filename> (if any). This is done using the <application>iscsistart</application> utility (which can do this without requiring <application>iscsid</application> to run).</para>
+ </listitem>
+ <listitem>
+ <para>When the root filesystem has been mounted and the various service initscripts get run, the <application>iscsid</application> initscript will get called. This script will then start <application>iscsid</application> if any iSCSI targets are used for <filename>/</filename>, or if any targets in the iSCSI database are marked to be logged in to automatically.</para>
+ </listitem>
+ <listitem>
+ <para>After the classic network service script has been run (or would have been run if enabled) the iscsi initscript will run. If the network is accessible, this will log in to any targets in the iSCSI database which are marked to be logged in to automatically. If the network is not accessible, this script will exit quietly.</para>
+ </listitem>
+ <listitem>
+ <para>When using <application>NetworkManager</application> to access the network (instead of the classic network service script), <application>NetworkManager</application> will call the iscsi initscript. See: <filename>/etc/NetworkManager/dispatcher.d/04-iscsi</filename></para>
+ <important>
+ <para>Because <application>NetworkManager</application> is installed in <filename>/usr</filename>, you cannot use it to configure network access if <filename>/usr</filename> is on network-attached storage such as an iSCSI target.</para>
+ </important>
+ </listitem>
+ </orderedlist>
+
+ <para>If <application>iscsid</application> is not needed as the system starts, it will not start automatically. If you start <application>iscsiadm</application>, <application>iscsiadm</application> will start <application>iscsid</application> in turn.</para>
+ </section>
+</appendix>
\ No newline at end of file
More information about the Fedora-docs-commits
mailing list