[virtualization-guide] editing the Dedicated storage section
Chris Curran
tsagadai at fedoraproject.org
Tue Jun 8 05:44:14 UTC 2010
commit 71fa4049e2059ccba7d53c1d521c98ae0cb40f6f
Author: Chris Curran <ccurran at redhat.com>
Date: Tue Jun 8 15:44:00 2010 +1000
editing the Dedicated storage section
en-US/Storage_Pools_Dedicated_Disk.xml | 114 ++++++++++++++-----------------
en-US/Storage_Pools_LVM.xml | 8 +-
2 files changed, 56 insertions(+), 66 deletions(-)
---
diff --git a/en-US/Storage_Pools_Dedicated_Disk.xml b/en-US/Storage_Pools_Dedicated_Disk.xml
index 3a2dbc0..147735c 100644
--- a/en-US/Storage_Pools_Dedicated_Disk.xml
+++ b/en-US/Storage_Pools_Dedicated_Disk.xml
@@ -30,7 +30,7 @@
Create a GPT disk label on the disk
</title>
<para>
- The disk Relabel the disk with a <firstterm>GUID Partition Table</firstterm> (GPT) disk label. GPT disk labels allow for creating a large number of partitions (up to 128, more with configuration) on each device, many more than the previous <computeroutput>msdos</computeroutput> style partition table.
+ The disk must be relabeled with a <firstterm>GUID Partition Table</firstterm> (GPT) disk label. GPT disk labels allow for creating a large numbers of partitions, up to 128 partitions, on each device. GPT partition tables can store partition data for far more partitions than the <computeroutput>msdos</computeroutput> partition table.
</para>
<screen># parted /dev/sdb
GNU Parted 2.1
@@ -64,11 +64,11 @@ Note the "format" type below is set to "unknown". This has been filed as BZ # 5
<allocation>0</allocation>
<available>0</available>
<source>
- <device path='/dev/sdb'/>
+ <device path='/dev/sdb'/>
<format type='unknown'/> <-=== problem here
</source>
- <target>
- <path>/dev</path>
+ <target>
+ <path>/dev</path>
<permissions>
<mode>0700</mode>
<owner>0</owner>
@@ -79,112 +79,104 @@ Note the "format" type below is set to "unknown". This has been filed as BZ # 5
#
-->
- <step>
+ <step><title>Create the storage pool configuration file</title>
<para>
- Create a temporary text file containing the storage pool information we will be using.
+ Create a temporary XML text file containing the storage pool information required for the new device.
</para>
<para>
- It must be in the format demonstrated below, and contain these fields:
+ The file must be in the format shown below, and contain the follwoing fields:
</para>
- <itemizedlist>
- <listitem>
+ <variablelist>
+
+ <varlistentry><term><name>guest_images_disk</name></term><listitem>
<para>
- The <command>name</command> of the Storage Pool. We use the name <replaceable>guest_images_disk</replaceable> in the example below.
+ 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>
+ </listitem></varlistentry>
+ <varlistentry><term> <device path='<replaceable>/dev/sdb</replaceable>'/></term>
<listitem>
<para>
- The <command>device path</command>. This is the path to the disk device we will be using for the storage pool. We use <replaceable>/dev/sdb</replaceable> in the example below.
+ 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>
+ </listitem></varlistentry>
+ <varlistentry><term><target> <path><replaceable>/dev</replaceable></path></term>
<listitem>
<para>
- The file system <command>target path</command>. This is the location on the host file system to attach volumes created from this storage pool.
+ 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.
+ 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>
+ </listitem></varlistentry>
+ <varlistentry><term><format type='<replaceable>gpt</replaceable>'/></term>
<listitem>
<para>
- The partition table <command>format</command>. We use <replaceable>gpt</replaceable> in the example below, to match the GPT disk label type created in the previous step.
+ 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>
- </itemizedlist>
- <screen># vi ~/guest_images_disk.xml
-# cat /etc/libvirt/storage/guest_images_disk.xml
-
-<pool type='disk'>
-<name><replaceable>guest_images_disk</replaceable></name>
-<source>
-<device path='<replaceable>/dev/sdb</replaceable>'/>
-<format type='<replaceable>gpt</replaceable>'/>
-</source>
-<target>
-<path><replaceable>/dev</replaceable></path>
-</target>
-</pool>
-#
-</screen>
- </step>
+ </listitem></varlistentry>
+ </variablelist>
+ <para>Create the XML file for the storage pool device with a text editor.</para><example><title>Dedicated storage device storage pool</title><screen><pool type='disk'>
+ <name><replaceable>guest_images_disk</replaceable></name>
+ <source>
+ <device path='<replaceable>/dev/sdb</replaceable>'/>
+ <format type='<replaceable>gpt</replaceable>'/>
+ </source>
+ <target>
+ <path><replaceable>/dev</replaceable></path>
+ </target>
+ </pool>
+</screen></example>
+
+</step>
+
- <step>
+ <step><title>Attach the device</title>
<para>
- Add the storage pool definition using virsh with this XML configuration file.
+ Add the storage pool definition using the <command>virsh pool-define</command> command with the XML configuration file created in the previous step.
</para>
<screen># virsh pool-define ~/guest_images_disk.xml
Pool guest_images_disk defined from /root/guest_images_disk.xml
-
# virsh pool-list --all
Name State Autostart
-----------------------------------------
default active yes
guest_images_disk inactive no
-
-#
</screen>
</step>
- <step>
+ <step><title>Start the storage pool</title>
<para>
- Start the storage pool.
+ Start the storage pool with the <command>virsh pool-start</command> command. Verify the pool is started with the <command>virsh pool-list --all</command> command.
</para>
<screen># virsh pool-start <replaceable>guest_images_disk</replaceable>
Pool guest_images_disk started
-
# virsh pool-list --all
Name State Autostart
-----------------------------------------
default active yes
guest_images_disk active no
-
-#
</screen>
</step>
- <step>
- <para>
- Turn on <firstterm>autostarting</firstterm> for the storage pool.
- </para>
+ <step><title>Turn on autostart</title>
<para>
- This causes the storage pool to be available for use when libvirtd is started.
+ Turn on <parameter>autostart</parameter> for the storage pool. Autostart configures the <systemitem class="daemon">libvirtd</systemitem class="daemon"> service to start the storage pool when the service starts.
</para>
+
<screen># virsh pool-autostart <replaceable>guest_images_disk</replaceable>
Pool guest_images_disk marked as autostarted
-
# virsh pool-list --all
Name State Autostart
-----------------------------------------
default active yes
guest_images_disk active yes
-
-#
</screen>
</step>
- <step>
+ <step><title>Verify the storage pool configuration</title>
<para>
- Verify the storage pool was created correctly, the sizes reported are what you expect them to be, and the State is <command>running</command>.
+ Verify the storage pool was created correctly, the sizes reported correctly, and the state reports as <computeroutput>running</computeroutput>.
</para>
<screen># virsh pool-info <replaceable>guest_images_disk</replaceable>
Name: guest_images_disk
@@ -193,27 +185,25 @@ State: running
Capacity: 465.76 GB
Allocation: 0.00
Available: 465.76 GB
-
# ls -la /dev/sdb
brw-rw----. 1 root disk 8, 16 May 30 14:08 /dev/sdb
# virsh vol-list guest_images_disk
Name Path
-----------------------------------------
-
-#
</screen>
</step>
- <step>
+ <step><title>Optional: Remove the temporary configuration file</title>
<para>
- Remove the temporary storage pool definition file you initially created, as it's no longer needed.
+ Remove the temporary storage pool XML configuration file if it is not needed.
</para>
- <screen># rm ~/guest_images_disk.xml
-#
+ <screen># rm ~/<replaceable>guest_images_disk</replaceable>.xml
+
</screen>
</step>
</procedure>
+ <para>A dedicated storage device storage pool is now available.</para>
</section>
</section>
diff --git a/en-US/Storage_Pools_LVM.xml b/en-US/Storage_Pools_LVM.xml
index 47ad512..9271662 100644
--- a/en-US/Storage_Pools_LVM.xml
+++ b/en-US/Storage_Pools_LVM.xml
@@ -17,16 +17,16 @@
</warning>
<procedure>
- <title>Creating an LVM storage pool using the Virtual Machine Manager GUI</title>
+ <title>Creating an LVM storage pool using virt-manager</title>
<step>
<title>Edit the Storage Pools definition</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 Edit menu and select Host Details
+ Open the <guilabel>Edit</guilabel> menu and select Host Details
</para>
<mediaobject>
<imageobject>
@@ -37,7 +37,7 @@
<step>
<para>
- Click on the Storage tab of the Host Details window.
+ Click on the <guilabel>Storage</guilabel> tab of the Host Details window.
</para>
<mediaobject>
<imageobject>
More information about the docs-commits
mailing list