commit 956399d8b64b911e39657c81e792d7152bb0959b Author: Chris Curran ccurran@redhat.com Date: Thu Jun 24 17:22:16 2010 +1000
still no clue where the error is
en-US/Storage_Concepts.xml | 50 +++++++++++++++---------------------------- 1 files changed, 18 insertions(+), 32 deletions(-) --- diff --git a/en-US/Storage_Concepts.xml b/en-US/Storage_Concepts.xml index 6792541..ebf685c 100644 --- a/en-US/Storage_Concepts.xml +++ b/en-US/Storage_Concepts.xml @@ -20,7 +20,7 @@ <para> - A storage pool is storage that can be divided up into smaller volumes or allocated directly to a guest. Volumes of a storage pool can be allocated to virtualised guests. There are two categories of storage pool available: + A storage pool is storage that can be divided up into smaller volumes or allocated directly to a guest. Volumes of a storage pool can be allocated to virtualised guests. There are two categories of storage pool available: </para> <formalpara> @@ -29,14 +29,12 @@ </para> </formalpara> <para>Local storage pools are useful for development, testing and small deployments that do not require migration or large numbers of virtualized guests. Local storage pools are not suitable for many production environments as local storage pools cannot support live migration.</para> - <formalpara> <title>Networked (shared) storage pools</title> <para>Networked storage pools covers storage devices shared over a network using standard protocols. </para> </formalpara> <para>Supported protocols for networked storage pools:</para> - <itemizedlist> <listitem> <para>Fibre Channel-based LUNs</para> @@ -53,15 +51,13 @@ <listitem> <para>SCSI RDMA protocols (SCSI RCP), the block export protocol used in Infiniband and 10GbE iWARP adapters.</para> </listitem> - <!-- What about RHEL TODO--> + <listitem> - <para> GlusterFS</para> + <para> GlusterFS <!-- What about RHEL TODO--></para> </listitem> </itemizedlist> <para>Networked storage is a requirement for migrating guest virtualized guests between hosts. Networked storage pools are managed by libvirt.</para> - - </section> <section id="sect-Virtualization-Storage_Concepts-Volumes"> @@ -77,9 +73,10 @@ To reference a specific volume, three approaches are possible: </para> </formalpara> + <variablelist> <varlistentry> - <term>The name of the volume and the storage pool </term> + <term>The name of the volume and the storage pool</term> <listitem> <para> A volume may be referred to by name, along with an identifier for the storage pool it belongs in. On the virsh command line, this takes the form <parameter>--pool</parameter> @@ -100,17 +97,13 @@ Allocation: 20.00 GB virsh #</screen> </listitem> </varlistentry> + <varlistentry> - - - <term> - The full path to the storage on the host system - </term> + <term>The full path to the storage on the host system</term> <listitem> <para> A volume may also be referred to by its full path on the file system. When using this approach, a pool identifier does not need to be included. - </para> - + </para> <para> For example, a volume named <replaceable>secondimage.img</replaceable>, visible to the host system as <replaceable>/images/secondimage.img</replaceable>. This can be refered to as <replaceable>/images/secondimage.img</replaceable>. </para> @@ -122,27 +115,24 @@ Allocation: 136.00 KB </screen> </listitem> </varlistentry> - <varlistentry> - <term> - The unique volume key - </term> + <varlistentry> + <term>The unique volume key</term> <listitem> <para> When a volume is first created in the virtualization system, a unique identifier is generated and assigned to it. The unique identifier is termed the <firstterm>volume key</firstterm>. The format of this volume key varies upon the storage used. </para> - - <para> + <para> When used with block based storage such as LVM, the volume key may follow this format: </para> - <screen>c3pKz4-qPVc-Xf7M-7WNM-WJc8-qSiz-mtvpGn</screen> - <para> +<screen>c3pKz4-qPVc-Xf7M-7WNM-WJc8-qSiz-mtvpGn</screen> + <para> When used with file based storage, the volume key may instead be a copy of the full path to the volume storage. </para> - <screen>/images/secondimage.img</screen> - <para> +<screen>/images/secondimage.img</screen> + <para> For example, a volume with the volume key of <replaceable>Wlvnf7-a4a3-Tlje-lJDa-9eak-PZBv-LoZuUr</replaceable>: </para> - <screen># virsh vol-info Wlvnf7-a4a3-Tlje-lJDa-9eak-PZBv-LoZuUr +<screen># virsh vol-info Wlvnf7-a4a3-Tlje-lJDa-9eak-PZBv-LoZuUr Name: <replaceable>firstimage</replaceable> Type: block Capacity: 20.00 GB @@ -171,8 +161,6 @@ Allocation: 20.00 GB </screen> </listitem> </varlistentry> - - <varlistentry> <term>vol-path</term> <listitem> @@ -190,13 +178,11 @@ Allocation: 20.00 GB <varlistentry> <term>The vol-key command</term> <listitem> - - - <para> + <para> Returns the volume key when provided with a volume path, or a storage pool identifier and volume name. </para> - <screen># virsh vol-key /dev/<replaceable>guest_images</replaceable>/<replaceable>firstimage</replaceable> +<screen># virsh vol-key /dev/<replaceable>guest_images</replaceable>/<replaceable>firstimage</replaceable> Wlvnf7-a4a3-Tlje-lJDa-9eak-PZBv-LoZuUr # virsh vol-key --pool <replaceable>guest_images</replaceable> <replaceable>firstimage</replaceable> Wlvnf7-a4a3-Tlje-lJDa-9eak-PZBv-LoZuUr </screen>
docs-commits@lists.fedoraproject.org