openstack
/
openstack-manuals
Code Issues Proposed changes

Merge "Fix wrong description for nova image-create"

This commit is contained in:
Jenkins 2014-07-19 20:12:04 +00:00 committed by Gerrit Code Review
parent f149cf2d81 f73c08af9a
commit 974f657435
1 changed files with 40 additions and 31 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

71
doc/common/section_cli_nova_manage_images.xml
View File

@ -1,25 +1,18 @@
<?xml version="1.0" encoding="UTF-8"?>
<section xmlns="http://docbook.org/ns/docbook"
xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns:xlink="http://www.w3.org/1999/xlink"
version="5.0"
xml:id="nova_manage_images">
<section xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="nova_manage_images">
<title>Create an image (nova)</title>
<para>You can use the <command>nova</command> client to take a snapshot of a
running instance to create an image.</para>
<para>To minimize the potential for data loss and ensure that you create an
accurate image, you should shut down the instance before you take a
snapshot.</para>
<para>You cannot create a snapshot from an instance that has an attached
volume. Detach the volume, create the image, and remount the
volume.</para>
<para>You can use the <command>nova</command> client to take a snapshot of a running instance to
create an image.</para>
<para>To minimize the potential for data loss and ensure that you create an accurate image, you
should shut down the instance before you take a snapshot.</para>
<procedure>
<step>
<para>Write any buffered data to disk.</para>
<para>For more information, see <link xlink:href="http://docs.openstack.org/openstack-ops/content/snapshots.html"
>Taking Snapshots</link> in the
<citetitle>OpenStack Operations
Guide</citetitle>.</para>
<para>For more information, see <link
xlink:href="http://docs.openstack.org/openstack-ops/content/snapshots.html"
>Taking Snapshots</link> in the <citetitle>OpenStack Operations
Guide</citetitle>.</para>
</step>
<step>
<para>List instances to get the server name:</para>
@ -29,13 +22,30 @@
+--------------------------------------+----------------------+--------+------------+-------------+------------------+
| 84c6e57d-a6b1-44b6-81eb-fcb36afd31b5 | myCirrosServer | ACTIVE | None | Running | private=10.0.0.3 |
+--------------------------------------+----------------------+--------+------------+-------------+------------------+</computeroutput></screen>
<para>In this example, the server is named
<literal>myCirrosServer</literal>.</para></step>
<step><para>Use this server to create a snapshot:
<screen><prompt>$</prompt> <userinput>nova image-create myCirrosServer myCirrosImage</userinput></screen>The
command creates a qemu snapshot and automatically uploads the
image to your repository. Only the tenant that creates the image
has access to it.</para>
<para>In this example, the instance is named <literal>myCirrosServer</literal>.</para>
</step>
<step>
<para>Use this instance to create a snapshot:</para>
<screen><prompt>$</prompt> <userinput>nova image-create myCirrosServer myCirrosImage</userinput></screen>
<para>The command creates a snapshot and automatically uploads the image to your
repository.</para>
<note>
<para>For snapshots that you create from an instance that was booted from a
volume:</para>
<itemizedlist>
<listitem>
<para>The snapshot is based on the volume that is attached to the instance
through the Block Storage service.</para>
</listitem>
<listitem>
<para>No data is uploaded to the Image Service.</para>
</listitem>
<listitem>
<para>You can find information about the snapshot in the properties of the
image.</para>
</listitem>
</itemizedlist>
</note>
</step>
<step>
<para>Get details for your image to check its status:</para>
@ -73,15 +83,14 @@
| metadata kernel_id | df430cc2-3406-4061-b635-a51c16e488ac |
| metadata instance_type_ephemeral_gb | 0 |
+-------------------------------------+--------------------------------------+</computeroutput></screen>
<para>The image status changes from
<literal>SAVING</literal> to
<literal>ACTIVE</literal>. Only the tenant who
creates the image has access to it.</para>
<para>The image status changes from <literal>SAVING</literal> to
<literal>ACTIVE</literal>. Only the tenant who creates the image has access to
it.</para>
</step>
</procedure>
<para>To launch an instance from your image, include the image ID
and flavor ID, as in the following example:</para>
<screen><prompt>$</prompt> <userinput>nova boot newServer --image 7e5142af-1253-4634-bcc6-89482c5f2e8a \
<para>To launch an instance from your image, include the image ID and flavor ID, as in the
following example:</para>
<screen><prompt>$</prompt> <userinput>nova boot newServer --image 7e5142af-1253-4634-bcc6-89482c5f2e8a \
--flavor 3</userinput>
<?db-font-size 50%?><computeroutput>+-------------------------------------+--------------------------------------+
| Property | Value |