openstack/openstack-manuals
Code Issues Proposed changes

Re-word the Building Blocks first paragraph

Browse Source 
The first paragraph of the building block section of the compute admin
guide implies that an ephemeral instance will loose it's state on
shutdown of the instance.  Shutdown may imply deletion, but as there
is a shutdown state that does not remove the ephemeral volume, it
is more appropriate to talk about the deletion of the virtual
instance.  This change addresses that inconsistency.

Removed excess spaces
Removed Nova-Volume reference

Change-Id: If00ef49fecdf864f74efc7171850bbacd60dbcd0
This commit is contained in:
Robert Starmer 2014-07-28 23:34:03 -07:00
parent b830c8adc2
commit f93554870f
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -318,12 +318,13 @@
from an image stored in the OpenStack Image Service. This
is the most common case and results in an ephemeral
instance that starts from a known template state and loses
all accumulated states on shutdown. It is also possible to
put an operating system on a persistent volume in the
Nova-Volume or Cinder volume system. This gives a more
all accumulated states on virtual machine deletion. It is
also possible to put an operating system on a persistent
volume in the Cinder volume system. This gives a more
traditional persistent system that accumulates states,
which are preserved across restarts. To get a list of
available images on your system run:
which are preserved on the Cinder volume across the
deletion and re-creation of the virutal machine. To get a
list of available images on your system run:
<screen><prompt>$</prompt> <userinput>nova image-list</userinput>
<?db-font-size 50%?><computeroutput>+--------------------------------------+-------------------------------+--------+--------------------------------------+
| ID | Name | Status | Server |