openstack/openstack-manuals
Code Issues Proposed changes

Edit typos in Compute chapter of Cloud Admin Guide

Browse Source 
Edit Section 1.1.5 Block Storage and Compute
Fix typos and edit grammar and style
Delete duplicate sentences

Change-Id: I71e281bcb86621c4b5cf4e42185d87e427d967e8
This commit is contained in:
nerminamiller 2013-10-14 20:14:55 -04:00
parent 77f5b721c0
commit c6a1d680ef
1 changed files with 32 additions and 45 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

77
doc/admin-guide-cloud/ch_compute.xml
View File

@ -244,64 +244,51 @@
</section> </section>
<section xml:id="section_storage-and-openstack-compute"> <section xml:id="section_storage-and-openstack-compute">
<title>Block Storage and Compute</title> <title>Block Storage and Compute</title>
<para>OpenStack provides two classes of block storage, ephemeral storage and persistent <para>OpenStack provides two classes of block storage: ephemeral storage and persistent
volumes. Ephemeral storage exists only for the life of an instance. It persists volumes. Ephemeral storage exists only for the life of an instance. It persists
across reboots of the guest operating system, but when the instance is deleted so is across reboots of the guest operating system, but when the instance is deleted so is
the associated storage. All instances have some ephemeral storage. Volumes are the associated storage. All instances have some ephemeral storage. Volumes are
persistent virtualized block devices independent of any particular instance. Volumes persistent virtualized block devices independent of any particular instance. </para>
may be attached to a single instance at a time, but may be detached or reattached to
a different instance while retaining all data, much like a USB drive.</para>
<simplesect xml:id="section_about-ephemeral-storage"> <simplesect xml:id="section_about-ephemeral-storage">
<title>Ephemeral storage</title> <title>Ephemeral storage</title>
<para>Ephemeral storage is associated with a single <para>Ephemeral storage is associated with a single
unique instance. Its size is defined by the flavor unique instance. Its size is defined by the flavor
of the instance.</para> of the instance.</para>
<para>Data on ephemeral storage ceases to exist when the instance it is associated <para>Terminating the instance associated with ephemeral storage causes the loss of
with is terminated. Rebooting the VM or restarting the host server, however, data from that ephemeral storage. Rebooting the VM or restarting the host
does not destroy ephemeral data. In the typical use case, an instance's root server, however, does not destroy ephemeral data. In a typical use case, an
file system is stored on ephemeral storage. This is often an unpleasant surprise instance's root file system is stored on ephemeral storage. </para>
for people unfamiliar with the cloud model of computing.</para> <para>In addition to the ephemeral root volume, all flavors except the smallest,
<para>In addition to the ephemeral root volume, all m1.tiny, provide an additional ephemeral block device whose size ranges from 20
flavors except the smallest, m1.tiny, provide an GB for m1.small to 160 GB for m1.xlarge. You can configure these sizes. This is
additional ephemeral block device whose size presented as a raw block device with no partition table or file system.
ranges from 20 GB for m1.small to 160 GB for Cloud-aware operating system images may discover, format, and mount this device.
m1.xlarge. You can configure these sizes. This is For example, the cloud-init package included in Ubuntu's stock cloud images
presented as a raw block device with no partition format this space as an ext3 file system and mount it on
table or file system. Cloud aware operating system <filename>/mnt</filename>. It is important to note this a feature of the
images may discover, format, and mount this guest operating system. OpenStack only provisions the raw storage.</para>
device. For example the cloud-init package
included in Ubuntu's stock cloud images format
this space as an ext3 file system and mount it on
<filename>/mnt</filename>. It is important to
note this a feature of the guest operating system.
OpenStack only provisions the raw storage.</para>
</simplesect> </simplesect>
<simplesect xml:id="section_about-persistent-storage"> <simplesect xml:id="section_about-persistent-storage">
<title>Volume storage</title> <title>Volume storage</title>
<para>Volume storage is independent of any particular <para>Volumes are created by users and their size may go up to the quota and
instance and is persistent. Volumes are user availability limits. Upon initial creation, volumes are raw block devices
created and within quota and availability limits without a partition table or a file system. To partition or format volumes, you
may be of any arbitrary size.</para> must attach them to an instance. After you attach them to an instance, you may
<para>When first created volumes are raw block devices use volumes much like you would an external disk drive. You may attach volumes
with n partition table and no file system. They to one instance at a time. However, you may detach and reattach volumes to
must be attached to an instance to be partitioned either the same or a different instance.</para>
and/or formatted. Once this is done they may be <para>You may configure a volume so that it is bootable and provides a persistent
used much like an external disk drive. Volumes may virtual instance similar to traditional non-cloud-based virtualization systems.
attached to only one instance at a time, but may Typically, the resulting instance may still have ephemeral storage depending on
be detached and reattached to either the same or the flavor selected, but the root file system (and possibly others) may be on
different instances.</para> the persistent volume and its state may be maintained even if the instance is
<para>It is possible to configure a volume so that it is bootable and provides a shut down. The details of this configuration are discussed in the
persistent virtual instance similar to traditional non-cloud-based <citetitle>OpenStack Configuration Reference</citetitle> .</para>
virtualization systems. In this use case, the resulting instance may still have
ephemeral storage depending on the flavor selected, but the root file system
(and possibly others) is on the persistent volume and its state is maintained
even if the instance it shut down. Details of this configuration are discussed
in the <citetitle>OpenStack Configuration Reference</citetitle> .</para>
<para>Volumes do not provide concurrent access from multiple instances. For that, <para>Volumes do not provide concurrent access from multiple instances. For that,
you need either a traditional network file system like NFS or CIFS or a cluster you need either a traditional network file system like NFS or CIFS or a cluster
file system such as GlusterFS. These may be built within an OpenStack cluster or file system such as GlusterFS. These systems may be built within an OpenStack
provisioned outside of it, but are not features provided by the OpenStack cluster or provisioned outside of it, but OpenStack software does not provide
software.</para> such features.</para>
</simplesect> </simplesect>
</section> </section>
</section> </section>