[virtualization-guide: 1/2] more edits
Chris Curran
tsagadai at fedoraproject.org
Fri Jun 11 06:31:55 UTC 2010
commit 0bd3b196229517f1d4fe72d681d0d5f74943fe6d
Author: Chris Curran <ccurran at redhat.com>
Date: Fri Jun 11 16:28:32 2010 +1000
more edits
en-US/Storage_Pools.xml | 2 +-
en-US/Storage_Pools_Directory.xml | 2 +-
en-US/Storage_Pools_FC.xml | 4 +-
...ls_File_System.xml => Storage_Pools_Partitions} | 265 ++++++++++++--------
en-US/Storage_Pools_iSCSI.xml | 4 +-
5 files changed, 161 insertions(+), 116 deletions(-)
---
diff --git a/en-US/Storage_Pools.xml b/en-US/Storage_Pools.xml
index 14fbab9..00fcc8c 100644
--- a/en-US/Storage_Pools.xml
+++ b/en-US/Storage_Pools.xml
@@ -15,7 +15,7 @@
Creating storage pools
</title>
<xi:include href="Storage_Pools_Dedicated_Disk.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Storage_Pools_File_System.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Storage_Pools_Partitions.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Storage_Pools_Directory.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Storage_Pools_LVM.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Storage_Pools_iSCSI.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
diff --git a/en-US/Storage_Pools_Directory.xml b/en-US/Storage_Pools_Directory.xml
index 8d319f8..93d8c6b 100644
--- a/en-US/Storage_Pools_Directory.xml
+++ b/en-US/Storage_Pools_Directory.xml
@@ -200,7 +200,7 @@ default active yes
guest_images_dir inactive no</screen> </step>
- step>
+ <step>
<title>Start the storage pool</title>
<para>
Use the virsh command <command>pool-start</command> for this. <command>pool-start</command> enables a directory storage pool, allowing it to be used for volumes and guests.
diff --git a/en-US/Storage_Pools_FC.xml b/en-US/Storage_Pools_FC.xml
index 9f45202..12d8290 100644
--- a/en-US/Storage_Pools_FC.xml
+++ b/en-US/Storage_Pools_FC.xml
@@ -2,9 +2,9 @@
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]>
<section id="sect-Virtualization-Storage_Pools-Creating-FC">
- <title>Using Fibre Channel for storing virtual disk images</title>
+ <title>Fibre Channel-based storage pools</title>
<para>
- This chapter covers using <firstterm>Fibre Channel</firstterm> (FC) to store virtualized guests.
+ This chapter covers using <firstterm>Fibre Channel</firstterm> to store virtualized guests.
</para>
</section>
diff --git a/en-US/Storage_Pools_File_System.xml b/en-US/Storage_Pools_Partitions
similarity index 54%
rename from en-US/Storage_Pools_File_System.xml
rename to en-US/Storage_Pools_Partitions
index 520a089..2cfa17e 100644
--- a/en-US/Storage_Pools_File_System.xml
+++ b/en-US/Storage_Pools_Partitions
@@ -2,24 +2,28 @@
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]>
<section id="sect-Virtualization-Storage_Pools-Creating-File_Systems">
- <title>File systems</title>
+ <title>Partition-based storage pools</title>
<para>
- This section covers using pre-formatted block devices to store virtualized guests.
+ This section covers using a pre-formatted block device, a partition, as a storage pool.
</para>
<para>
- For example, a host has a 500GB hard drive (<systemitem>/dev/sdc</systemitem>) partitioned into one 500GB, ext4 formatted partition (<systemitem>/dev/sdc1</systemitem>). We set up a storage pool for it using the procedure below.
+ For the following examples, a host has a 500GB hard drive (<systemitem>/dev/sdc</systemitem>) partitioned into one 500GB, ext4 formatted partition (<systemitem>/dev/sdc1</systemitem>). We set up a storage pool for it using the procedure below.
</para>
- <procedure>
- <title>Creating pre-formatted block device storage pools using the Virtual Machine Manager GUI</title>
- <step>
- <title>Edit the storage pools definition</title>
+ <section>
+ <title>Creating a partition-based storage pool using virt-manager</title>
+ <para>This procedure creates a new storage pool using a partition of a storage device with the <command>virsh</command> command. </para>
+
+ <procedure>
+ <title>Creating a partition-based storage pool with virt-manager</title>
+ <step>
+ <title>Open the storage pool settings</title>
<substeps>
<step>
<para>
- With <command>Virtual Machine Manager</command> running, select the host from the main window.
+ In the <command>virt-manager</command> graphical interface, select the host from the main window.
</para>
<para>
- Open the <guilabel>Edit</guilabel> menu and select Host Details
+ Open the <guilabel>Edit</guilabel> menu and select <guilabel>Host Details</guilabel>
</para>
<mediaobject>
<imageobject>
@@ -30,7 +34,7 @@
<step>
<para>
- Click on the <guilabel>Storage</guilabel> tab of the <guilabel>Host</guilabel> Details window.
+ Click on the <guilabel>Storage</guilabel> tab of the <guilabel>Host Details</guilabel> window.
</para>
<mediaobject>
<imageobject>
@@ -39,144 +43,184 @@
</mediaobject>
</step>
</substeps>
- </step>
+ </step>
<step>
<title>Create the new storage pool</title>
<substeps>
<step>
- <title>Start the Wizard</title>
- <para>
+ <title>Add a new pool (part 1)</title>
+ <para>
Press the <guilabel>+</guilabel> button (the add pool button). The <guilabel>Add a New Storage Pool</guilabel> wizard appears.
</para>
- <para>
- Choose a <guibutton>Name</guibutton> for the storage pool. We use <replaceable>guest_images_fs</replaceable> for this example. Then change the <guibutton>Type</guibutton> to <command>fs: Pre-Formatted Block Device</command>, and click the <guibutton>Forward</guibutton> button to continue.
+ <para>
+ Choose a <guibutton>Name</guibutton> for the storage pool. This example uses the name <replaceable>guest_images_fs</replaceable>. Change the <guibutton>Type</guibutton> to <command>fs: Pre-Formatted Block Device</command>.
</para>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/virt-manager_storage_pools_add_fs_step_1_name_and_type.png" format="PNG" scalefit="1" />
- </imageobject>
- </mediaobject>
- </step>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/virt-manager_storage_pools_add_fs_step_1_name_and_type.png" format="PNG" scalefit="1" />
+ </imageobject>
+ </mediaobject>
+ <para>Press the <guibutton>Forward</guibutton> button to continue.</para>
- <step>
- <title>Complete the Wizard</title>
- <para>
- Now fill in the <guibutton>Target Path</guibutton>, <guibutton>Format</guibutton>, and <guibutton>Source Path</guibutton> fields.
+ </step>
+
+ <step>
+ <title>Add a new pool (part 2)</title>
+ <para>
+ Change the <guibutton>Target Path</guibutton>, <guibutton>Format</guibutton>, and <guibutton>Source Path</guibutton> fields.
</para>
- <itemizedlist>
- <listitem>
- <para>
+ <varlistentry><term><name>guest_images_disk</name></term><listitem>
+ <para>
+ The <parameter>name</parameter> parameter determines the name of the storage pool. This example uses the name <replaceable>guest_images_disk</replaceable> in the example below.
+ </para>
+ </listitem></varlistentry>
+ <varlistentry><term> <device path='<replaceable>/dev/sdb</replaceable>'/></term>
+ <listitem>
+ <para>
+ The <parameter>device</parameter> parameter with the <parameter>path</parameter> attribute
+ specifies the device path of the storage device. This example uses the device <replaceable>/dev/sdb</replaceable> .
+ </para>
+ </listitem></varlistentry>
+ <varlistentry><term><target> <path><replaceable>/dev</replaceable></path></term>
+ <listitem>
+ <para>
+ The file system <parameter>target</parameter> parameter with the <parameter>path</parameter> sub-parameter determines the location on the host file system to attach volumes created with this this storage pool.
+ </para>
+ <para>
+ For example, sdb1, sdb2, sdb3. Using <replaceable>/dev/</replaceable>, as in the example below, means volumes created from this storage pool can be accessed as <replaceable>/dev</replaceable>/sdb1, <replaceable>/dev</replaceable>/sdb2, <replaceable>/dev</replaceable>/sdb3.
+ </para>
+ </listitem></varlistentry>
+ <varlistentry><term><format type='<replaceable>gpt</replaceable>'/></term>
+ <listitem>
+ <para>
+ The <parameter>format</parameter> parameter specifies the partition table type. his example uses the <replaceable>gpt</replaceable> in the example below, to match the GPT disk label type created in the previous step.
+ </para>
+ </listitem></varlistentry>
+ </variablelist>
+
+
+ <!--<itemizedlist>
+ <listitem>
+ <para>
The <guibutton>Target Path</guibutton> is the directory on the local file system where the formatted device will be mounted. It does does not need to already exist, and it is generally better to allow <command>virsh</command> to create it in the next step.
</para>
- <para>
+ <para>
We use <replaceable>/guest_images</replaceable> in the example below.
</para>
- </listitem>
- <listitem>
- <para>
+ </listitem>
+ <listitem>
+ <para>
The <guibutton>Format</guibutton> field is the type of file system on the device.
</para>
- <para>
+ <para>
We use <replaceable>ext4</replaceable> in the example below.
</para>
- </listitem>
- <listitem>
- <para>
+ </listitem>
+ <listitem>
+ <para>
The <command>Source Path</command> is the device this storage pool will use.
</para>
- <para>
+ <para>
We use <replaceable>/dev/sdc1</replaceable> in the example below.
</para>
- </listitem>
- </itemizedlist>
- <para>
+ </listitem>
+ </itemizedlist>-->
+ <para>
Click the <guibutton>Finish</guibutton> button to complete the creation of the storage pool.
</para>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/virt-manager_storage_pools_add_fs_step_2_paths_and_format.png" format="PNG" scalefit="1" />
- </imageobject>
- </mediaobject>
- </step>
- </substeps>
- </step>
- <step>
- <title>Verify the new storage pool</title>
- <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/virt-manager_storage_pools_add_fs_step_2_paths_and_format.png" format="PNG" scalefit="1" />
+ </imageobject>
+ </mediaobject>
+ </step>
+ </substeps>
+ </step>
+ <step>
+ <title>Verify the new storage pool</title>
+ <para>
The new storage pool will appear in the list on the left after a few seconds. Verify the details are what you expect, <replaceable>458.20 GB Free</replaceable> in our example. Also verify the <guibutton>State</guibutton> field reports the new storage pool as <replaceable>Active</replaceable>.
</para>
- <para>
+ <para>
It is generally a good idea to have the <guibutton>Autostart</guibutton> check box enabled, to ensure the storage pool starts automatically with libvirtd.
</para>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/virt-manager_storage_pools_add_fs_step_3_result.png" format="PNG" scalefit="1" />
- </imageobject>
- </mediaobject>
- <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/virt-manager_storage_pools_add_fs_step_3_result.png" format="PNG" scalefit="1" />
+ </imageobject>
+ </mediaobject>
+ <para>
Close the Host Details dialog, as the task is now complete.
</para>
- </step>
- </procedure>
-
- <procedure>
- <title>Creating pre-formatted block device storage pools using virsh</title>
- <step>
- <title>
+ </step>
+ </procedure>
+ </section>
+ <section>
+ <title>Creating a partition-based storage pool using virsh</title>
+ <para>Intro</para>
+ <procedure>
+ <title>Creating pre-formatted block device storage pools using virsh</title>
+ <step>
+ <title>
Create the storage pool definition
</title>
- <para>
+ <para>
Use the virsh <command>pool-define-as</command> command to create a new storage pool definition. There are three options that must be provided to define a pre-formatted disk as a storage pool:
</para>
- <itemizedlist>
- <listitem>
- <para>
+ <itemizedlist>
+ <listitem>
+ <para>
The <parameter>name</parameter> of the storage pool. All further <command>virsh</command> command used for this storage pool use the name defined by this option.
</para>
- <para>
+ <para>
The name <replaceable>guest_images_fs</replaceable> is used in this example.
</para>
- </listitem>
- <listitem>
- <para>
+ </listitem>
+ <listitem>
+ <para>
The <parameter>/path/to/source</parameter> to the formatted file system. If the directory does not exist, the <command>virsh</command> command can create the directory.
</para>
- <para>
+ <para>
The directory <replaceable>/guest_images</replaceable> is used in this example.
</para>
- </listitem>
- <listitem>
- <para>
+ </listitem>
+ <listitem>
+ <para>
The <parameter>mountpoint</parameter> on the local file system where the formatted device will be mounted. If the mount point directory does not exist, the <command>virsh</command> command can create the directory.
</para>
- <para>
+ <para>
The directory <replaceable>/guest_images</replaceable> is used in this example.
</para>
- </listitem>
- </itemizedlist>
- <screen># virsh pool-define-as <replaceable>guest_images_fs</replaceable> fs - - <replaceable>/dev/sdc1</replaceable> - "<replaceable>/guest_images</replaceable>"
+ </listitem>
+ </itemizedlist>
+ <screen># virsh pool-define-as <replaceable>guest_images_fs</replaceable> fs - - <replaceable>/dev/sdc1</replaceable> - "<replaceable>/guest_images</replaceable>"
Pool guest_images_fs defined
-</screen><para>The new pool and mount points are now created.</para></step>
+</screen>
+ <para>The new pool and mount points are now created.</para>
+ </step>
-<step><title>Verify the new pool</title><para>List the present storage pools.</para>
-<screen># virsh pool-list --all
+ <step>
+ <title>Verify the new pool</title>
+ <para>List the present storage pools.</para>
+ <screen># virsh pool-list --all
Name State Autostart
-----------------------------------------
default active yes
<replaceable>guest_images_fs</replaceable> inactive no
#
-</screen></step>
-
+</screen>
+ </step>
- <step>
- <title>
+
+ <step>
+ <title>
Ceate the mount point
</title>
- <para>
+ <para>
Use the <command>virsh pool-build</command> command to create a mount point for a pre-formatted file system storage pool.
</para>
- <screen># virsh pool-build <replaceable>guest_images_fs</replaceable>
+ <screen># virsh pool-build <replaceable>guest_images_fs</replaceable>
Pool guest_images_fs built
# ls -la /<replaceable>guest_images</replaceable>
@@ -191,16 +235,16 @@ guest_images_fs inactive no
#
</screen>
- </step>
-
- <step>
- <title>
+ </step>
+
+ <step>
+ <title>
Start the storage pool
</title>
- <para>
+ <para>
Use the <command>virsh pool-start</command> command to mount the file system onto the mount point and make the pool available for use.
</para>
- <screen># virsh pool-start <replaceable>guest_images_fs</replaceable>
+ <screen># virsh pool-start <replaceable>guest_images_fs</replaceable>
Pool guest_images_fs started
# virsh pool-list --all
@@ -211,16 +255,16 @@ guest_images_fs active no
#
</screen>
- </step>
-
- <step>
- <title>
+ </step>
+
+ <step>
+ <title>
Turn on autostart
</title>
- <para>
+ <para>
By default, a storage pool is defined with <command>virsh</command> is not set to automatically start each time the <systemitem class="daemon">libvirtd</systemitem> starts. Turn on automatic start with the <command>virsh pool-autostart</command> command. The storage pool is now automatically started each time <systemitem class="daemon">libvirtd</systemitem> starts.
</para>
- <screen># virsh pool-autostart <replaceable>guest_images_fs</replaceable>
+ <screen># virsh pool-autostart <replaceable>guest_images_fs</replaceable>
Pool guest_images_fs marked as autostarted
# virsh pool-list --all
@@ -231,16 +275,16 @@ guest_images_fs active yes
#
</screen>
- </step>
-
- <step>
- <title>
+ </step>
+
+ <step>
+ <title>
Verify the storage pool
</title>
- <para>
+ <para>
Verify the storage pool was created correctly, the sizes reported are as expected, and the state is reported as <command>running</command>. Verify there is a "lost+found" directory in the mount point on the file system, indicating the device is mounted.
</para>
- <screen># virsh pool-info <replaceable>guest_images_fs</replaceable>
+ <screen># virsh pool-info <replaceable>guest_images_fs</replaceable>
Name: guest_images_fs
UUID: c7466869-e82a-a66c-2187-dc9d6f0877d0
State: running
@@ -257,8 +301,8 @@ dr-xr-xr-x. 25 root root 4096 May 31 19:38 ..
drwx------. 2 root root 16384 May 31 14:18 lost+found
#
</screen>
- </step>
- </procedure>
+ </step>
+ </procedure>
<!--
Testing which volume formats can be created inside pre-formatted block devices:
@@ -276,5 +320,6 @@ vpc: mostly works from virsh. has wrong xml info when created with virt-manager
Note # 2 - There appears to be GlusterFS specific code in the libvirt source for pre-formatted disks (src/storage/storage_backend_fs.c)
This may be worth taking a look at and writing up specific notes for.
-->
+ </section>
</section>
diff --git a/en-US/Storage_Pools_iSCSI.xml b/en-US/Storage_Pools_iSCSI.xml
index cec4748..970f5f0 100644
--- a/en-US/Storage_Pools_iSCSI.xml
+++ b/en-US/Storage_Pools_iSCSI.xml
@@ -223,7 +223,7 @@ Logout of [sid: 2, target: iqn.2010-05.com.example.server1:trial1, portal: 10.0.
</substeps>
</step>
- <substeps><step>
+ <step>
<title>Add a new pool (part 1)</title>
<para>
Press the <guilabel>+</guilabel> button (the add pool button). The <guilabel>Add a New Storage Pool</guilabel> wizard appears.
@@ -257,7 +257,7 @@ Logout of [sid: 2, target: iqn.2010-05.com.example.server1:trial1, portal: 10.0.
<para>
Press <guibutton>Finish</guibutton> to create the new storage pool.
</para>
- </step></substeps>
+ </step>
</procedure>
</section>
More information about the docs-commits
mailing list