You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by ke...@apache.org on 2012/10/09 05:42:08 UTC
git commit: reducing line length to 80
Updated Branches:
refs/heads/master 9a27836ee -> fc30858fb
reducing line length to 80
Project: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/commit/fc30858f
Tree: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/tree/fc30858f
Diff: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/diff/fc30858f
Branch: refs/heads/master
Commit: fc30858fb45194321e63509023191a9d2ed3b251
Parents: 9a27836
Author: David Nalley <da...@gnsa.us>
Authored: Mon Oct 8 23:41:41 2012 -0400
Committer: David Nalley <da...@gnsa.us>
Committed: Mon Oct 8 23:41:41 2012 -0400
----------------------------------------------------------------------
docs/en-US/working-with-volumes.xml | 24 +++++++++++++++++++++---
1 files changed, 21 insertions(+), 3 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/fc30858f/docs/en-US/working-with-volumes.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/working-with-volumes.xml b/docs/en-US/working-with-volumes.xml
index f4fce71..8aa0420 100644
--- a/docs/en-US/working-with-volumes.xml
+++ b/docs/en-US/working-with-volumes.xml
@@ -24,7 +24,25 @@
<section id="working-with-volumes">
<title>Using Swift for Secondary Storage</title>
- <para>A volume provides storage to a guest VM. The volume can provide for a root disk or an additional data disk. &PRODUCT; supports additional volumes for guest VMs.</para>
- <para>Volumes are created for a specific hypervisor type. A volume that has been attached to guest using one hypervisor type (e.g, XenServer) may not be attached to a guest that is using another hypervisor type (e.g. vSphere, Oracle VM, KVM). This is because the different hypervisors use different disk image formats.</para>
- <para>&PRODUCT; defines a volume as a unit of storage available to a guest VM. Volumes are either root disks or data disks. The root disk has "/" in the file system and is usually the boot device. Data disks provide for additional storage (e.g. As "/opt" or "D:"). Every guest VM has a root disk, and VMs can also optionally have a data disk. End users can mount multiple data disks to guest VMs. Users choose data disks from the disk offerings created by administrators. The user can create a template from a volume as well; this is the standard procedure for private template creation. Volumes are hypervisor-specific: a volume from one hypervisor type may not be used on a guest of another hypervisor type.</para>
+ <para>A volume provides storage to a guest VM. The volume can provide for
+ a root disk or an additional data disk. &PRODUCT; supports additional
+ volumes for guest VMs.
+ </para>
+ <para>Volumes are created for a specific hypervisor type. A volume that has
+ been attached to guest using one hypervisor type (e.g, XenServer) may not
+ be attached to a guest that is using another hypervisor type (e.g.
+ vSphere, Oracle VM, KVM). This is because the different hypervisors use
+ different disk image formats.
+ </para>
+ <para>&PRODUCT; defines a volume as a unit of storage available to a guest
+ VM. Volumes are either root disks or data disks. The root disk has "/"
+ in the file system and is usually the boot device. Data disks provide
+ for additional storage (e.g. As "/opt" or "D:"). Every guest VM has a root
+ disk, and VMs can also optionally have a data disk. End users can mount
+ multiple data disks to guest VMs. Users choose data disks from the disk
+ offerings created by administrators. The user can create a template from
+ a volume as well; this is the standard procedure for private template
+ creation. Volumes are hypervisor-specific: a volume from one hypervisor
+ type may not be used on a guest of another hypervisor type.
+ </para>
</section>