UG Edits: Migrate Instances, Conf Drive
- Edits to the Migrate Instances and Conf Drive sections of the CLI chapter - Patch split from https://review.openstack.org/#/c/89581/ Change-Id: I7fef7f8e03aa1aa7362326169c961eb977d8d5c0
This commit is contained in:
Karin Levenstein
Gauvain Pocentek
parent
03ad8d3b2a
commit
9e10a47973
@ -9,36 +9,35 @@
|
||||
xml:id="config-drive">
|
||||
<title>Store metadata on a configuration drive</title>
|
||||
<para>You can configure OpenStack to write metadata to a special
|
||||
configuration drive that attaches to the instance when it
|
||||
boots. The instance can mount this drive and read files from
|
||||
it to get information that is normally available through the
|
||||
<link
|
||||
configuration drive that attaches to the instance when it boots. The
|
||||
instance can mount this drive and read files from it to get information
|
||||
that is normally available through the <link
|
||||
xlink:href="http://docs.openstack.org/admin-guide-cloud/content/section_metadata-service.html"
|
||||
>metadata service</link>.</para>
|
||||
<para>One use case for the configuration drive is to pass a
|
||||
networking configuration when you do not use DHCP to assign IP
|
||||
addresses to instances. For example, you might pass the IP
|
||||
configuration for the instance through the configuration
|
||||
drive, which the instance can mount and access before you
|
||||
configure the network settings for the instance.</para>
|
||||
<para>Any modern guest operating system that is capable of
|
||||
mounting an ISO9660 or VFAT file system can use the
|
||||
configuration drive.</para>
|
||||
>metadata service</link>. This metadata is different from the user
|
||||
data.</para>
|
||||
<para>One use case for using the configuration drive is to pass a networking
|
||||
configuration when you do not use DHCP to assign IP addresses to
|
||||
instances. For example, you might pass the IP address configuration for
|
||||
the instance through the configuration drive, which the instance can
|
||||
mount and access before you configure the network settings for the
|
||||
instance.</para>
|
||||
<para>Any modern guest operating system that is capable of mounting an ISO
|
||||
9660 or VFAT file system can use the configuration drive.</para>
|
||||
<section xml:id="requirements">
|
||||
<title>Requirements and guidelines</title>
|
||||
<para>To use the configuration drive, you must follow the following
|
||||
requirements for the compute host and image.</para>
|
||||
<itemizedlist>
|
||||
<title>Compute host requirements</title>
|
||||
<listitem>
|
||||
<para>The following hypervisors support the
|
||||
configuration drive: libvirt, xenserver, hyper-v,
|
||||
and vmware.</para>
|
||||
<para>The following hypervisors support the configuration drive:
|
||||
libvirt, XenServer, Hyper-V, and VMWare.</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>To use configuration drive with libvirt,
|
||||
xenserver, or vmware, you must first install the
|
||||
<package>genisoimage</package> package on each
|
||||
compute host. Otherwise, instances do not boot
|
||||
properly.</para>
|
||||
<para>To use configuration drive with libvirt, XenServer, or
|
||||
VMWare, you must first install the
|
||||
<package>genisoimage</package> package on each compute
|
||||
host. Otherwise, instances do not boot properly.</para>
|
||||
|
||||
<para>Use the <literal>mkisofs_cmd</literal> flag to
|
||||
set the path where you install the
|
||||
@ -49,15 +48,13 @@
|
||||
need to set this flag.</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>To use configuration drive with hyper-v, you
|
||||
must set the <literal>mkisofs_cmd</literal> value
|
||||
to the full path to an
|
||||
<literal>mkisofs.exe</literal> installation.
|
||||
<para>To use configuration drive with Hyper-V, you must set the
|
||||
<literal>mkisofs_cmd</literal> value to the full path to
|
||||
an <literal>mkisofs.exe</literal> installation.
|
||||
Additionally, you must set the
|
||||
<literal>qemu_img_cmd</literal> value in the
|
||||
<literal>hyperv</literal> configuration
|
||||
section to the full path to an
|
||||
<literal>qemu-img</literal> command
|
||||
<literal>hyperv</literal> configuration section to the
|
||||
full path to an <literal>qemu-img</literal> command
|
||||
installation.</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
@ -67,21 +64,18 @@
|
||||
<para>An image built with a recent version of the
|
||||
<package>cloud-init</package> package can
|
||||
automatically access metadata passed through the
|
||||
configuration drive. The
|
||||
<package>cloud-init</package> package version
|
||||
0.7.1 works with Ubuntu and Fedora-based images,
|
||||
such as RHEL.</para>
|
||||
configuration drive. The <package>cloud-init</package>
|
||||
package version 0.7.1 works with Ubuntu and Fedora based
|
||||
images, such as Red Hat Enterprise Linux.</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>If an image does not have the
|
||||
<package>cloud-init</package> package
|
||||
installed, you must customize the image to run a
|
||||
script that mounts the configuration drive on
|
||||
boot, reads the data from the drive, and takes
|
||||
appropriate action such as adding the public key
|
||||
to an account. See <xref
|
||||
linkend="config_drive_contents"/> for details
|
||||
on how data is organized on the configuration
|
||||
<package>cloud-init</package> package installed, you
|
||||
must customize the image to run a script that mounts the
|
||||
configuration drive on boot, reads the data from the drive,
|
||||
and takes appropriate action such as adding the public key
|
||||
to an account. See <xref linkend="config_drive_contents"/>
|
||||
for details about how data is organized on the configuration
|
||||
drive.</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
@ -94,21 +88,19 @@
|
||||
<itemizedlist>
|
||||
<title>Guidelines</title>
|
||||
<listitem>
|
||||
<para>Do not rely on the presence of the EC2 metadata
|
||||
present in the configuration drive, as this
|
||||
content might be removed in a future release. For
|
||||
example, do not rely on files in the
|
||||
<filename>ec2</filename> directory.</para>
|
||||
<para>Do not rely on the presence of the EC2 metadata in the
|
||||
configuration drive, because this content might be removed
|
||||
in a future release. For example, do not rely on files in
|
||||
the <filename>ec2</filename> directory.</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>When you create images that access configuration
|
||||
drive data and multiple directories are under the
|
||||
<filename>openstack</filename> directory,
|
||||
always select the highest API version by date that
|
||||
your consumer supports. For example, if your guest
|
||||
image supports the 2012-03-05, 2012-08-05,
|
||||
2013-04-13 versions, try 2013-04-13 first and fall
|
||||
back to a previous version if 2013-04-13 is not
|
||||
<para>When you create images that access configuration drive
|
||||
data and multiple directories are under the
|
||||
<filename>openstack</filename> directory, always select
|
||||
the highest API version by date that your consumer supports.
|
||||
For example, if your guest image supports the 2012-03-05,
|
||||
2012-08-05, and 2013-04-13 versions, try 2013-04-13 first
|
||||
and fall back to a previous version if 2013-04-13 is not
|
||||
present.</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
@ -121,39 +113,34 @@
|
||||
<literal>--config-drive=true</literal>
|
||||
parameter to the <command>nova boot</command>
|
||||
command.</para>
|
||||
<para>This example enables the configuration drive and
|
||||
passes user data, two files, and two key/value
|
||||
metadata pairs, all of which are accessible from
|
||||
the configuration drive:</para>
|
||||
<para>The following example enables the configuration drive and
|
||||
passes user data, two files, and two key/value metadata
|
||||
pairs, all of which are accessible from the configuration
|
||||
drive:</para>
|
||||
<screen><prompt>$</prompt> <userinput>nova boot --config-drive=true --image my-image-name --key-name mykey --flavor 1 --user-data ./my-user-data.txt myinstance --file /etc/network/interfaces=/home/myuser/instance-interfaces --file known_hosts=/home/myuser/.ssh/known_hosts --meta role=webservers --meta essential=false</userinput></screen>
|
||||
<para>You can also configure the Compute service to
|
||||
always create a configuration drive.</para>
|
||||
<para>Set this option in the
|
||||
<filename>/etc/nova/nova.conf</filename>
|
||||
file:</para>
|
||||
<para>You can also configure the Compute service to always
|
||||
create a configuration drive by setting the following option
|
||||
in the <filename>/etc/nova/nova.conf</filename> file:</para>
|
||||
<programlisting language="ini">force_config_drive=true</programlisting>
|
||||
<note>
|
||||
<para>If a user passes the
|
||||
<parameter>--config-drive=true</parameter>
|
||||
flag to the <command>nova boot</command>
|
||||
command, an administrator cannot disable the
|
||||
configuration drive.</para>
|
||||
<literal>--config-drive=true</literal> flag to the
|
||||
<command>nova boot</command> command, an
|
||||
administrator cannot disable the configuration
|
||||
drive.</para>
|
||||
</note>
|
||||
</step>
|
||||
<step>
|
||||
<para>The configuration drive has the
|
||||
<literal>config-2</literal> volume label. If
|
||||
your guest operating system supports accessing
|
||||
disk by label, you can mount the configuration
|
||||
drive as the
|
||||
<filename>/dev/disk/by-label/config-2</filename>
|
||||
device.</para>
|
||||
<para>For example:</para>
|
||||
<para>If your guest operating system supports accessing disk by
|
||||
label, you can mount the configuration drive as the
|
||||
<filename>/dev/disk/by-label/<replaceable>configurationDriveVolumeLabel</replaceable></filename>
|
||||
device. In the following example, the configuration drive
|
||||
has the <filename>config-2</filename> volume label.</para>
|
||||
<screen><prompt>#</prompt> <userinput>mkdir -p /mnt/config</userinput>
|
||||
<prompt>#</prompt> <userinput>mount /dev/disk/by-label/config-2 /mnt/config</userinput></screen>
|
||||
<note>
|
||||
<para>Make sure that you use at least version 0.3.1
|
||||
of CirrOS for configuration drive support.</para>
|
||||
<para>Ensure that you use at least version 0.3.1 of CirrOS
|
||||
for configuration drive support.</para>
|
||||
</note>
|
||||
<para>If your guest operating system does not use
|
||||
<literal>udev</literal>, the
|
||||
@ -175,8 +162,8 @@
|
||||
</procedure>
|
||||
<simplesect xml:id="config_drive_contents">
|
||||
<title>Configuration drive contents</title>
|
||||
<para>In this example, the contents of the configuration
|
||||
drive are:</para>
|
||||
<para>In this example, the contents of the configuration drive are
|
||||
as follows:</para>
|
||||
<screen><computeroutput>ec2/2009-04-04/meta-data.json
|
||||
ec2/2009-04-04/user-data
|
||||
ec2/latest/meta-data.json
|
||||
@ -195,11 +182,10 @@ openstack/latest/user_data</computeroutput></screen>
|
||||
<simplesect xml:id="os_metadata_format">
|
||||
<title>OpenStack metadata format</title>
|
||||
<para>The following example shows the contents of the
|
||||
<filename>openstack/2012-08-10/meta_data.json</filename>
|
||||
and
|
||||
<filename>openstack/latest/meta_data.json</filename>
|
||||
files. These files are identical. The file contents
|
||||
are formatted for readability:</para>
|
||||
<filename>openstack/2012-08-10/meta_data.json</filename> and
|
||||
<filename>openstack/latest/meta_data.json</filename> files.
|
||||
These files are identical. The file contents are formatted for
|
||||
readability.</para>
|
||||
<programlisting language="json"><xi:include parse="text" href="samples/meta_data.json"/></programlisting>
|
||||
<para>Note the effect of the <literal>--file
|
||||
/etc/network/interfaces=/home/myuser/instance-interfaces</literal>
|
||||
@ -214,10 +200,10 @@ openstack/latest/user_data</computeroutput></screen>
|
||||
<simplesect xml:id="ec2_metadata_format">
|
||||
<title>EC2 metadata format</title>
|
||||
<para>The following example shows the contents of the
|
||||
<filename>ec2/2009-04-04/meta-data.json</filename>,
|
||||
<filename>latest/meta-data.json</filename> files.
|
||||
These files are identical. The file contents are
|
||||
formatted to improve readability:</para>
|
||||
<filename>ec2/2009-04-04/meta-data.json</filename> and the
|
||||
<filename>ec2/latest/meta-data.json</filename> files. These
|
||||
files are identical. The file contents are formatted to improve
|
||||
readability.</para>
|
||||
<programlisting language="json"><xi:include href="samples/meta_data_ec2.json" parse="text"/></programlisting>
|
||||
</simplesect>
|
||||
<simplesect xml:id="user_data">
|
||||
@ -239,11 +225,10 @@ openstack/latest/user_data</computeroutput></screen>
|
||||
<filename>/etc/nova/nova.conf</filename>
|
||||
file:</para>
|
||||
<programlisting language="ini">config_drive_format=iso9660</programlisting>
|
||||
<para>By default, you cannot attach the configuration
|
||||
drive image as a CD drive instead of as a disk drive.
|
||||
To attach a CD drive, add this line to the
|
||||
<filename>/etc/nova/nova.conf</filename>
|
||||
file:</para>
|
||||
<para>By default, you cannot attach the configuration drive image as
|
||||
a CD drive instead of as a disk drive. To attach a CD drive, add
|
||||
the following line to the
|
||||
<filename>/etc/nova/nova.conf</filename> file:</para>
|
||||
<programlisting language="ini">config_drive_cdrom=true</programlisting>
|
||||
<para>For legacy reasons, you can configure the
|
||||
configuration drive to use VFAT format instead of ISO
|
||||
@ -260,8 +245,8 @@ openstack/latest/user_data</computeroutput></screen>
|
||||
</section>
|
||||
<section xml:id="config_reference">
|
||||
<title>Configuration drive reference</title>
|
||||
<para>The following table shows the configuration options for
|
||||
the configuration drive:</para>
|
||||
<para>The following table shows the configuration options for the
|
||||
configuration drive.</para>
|
||||
<xi:include href="../common/tables/nova-configdrive.xml"/>
|
||||
</section>
|
||||
</section>
|
||||
|
||||
@ -4,83 +4,73 @@
|
||||
xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"
|
||||
xml:id="cli_migrate_instances">
|
||||
<?dbhtml stop-chunking?>
|
||||
<title>Use snapshots to migrate instance</title>
|
||||
<title>Use snapshots to migrate instances</title>
|
||||
<para>To use snapshots to migrate instances from OpenStack projects to clouds, complete these steps.</para>
|
||||
<procedure>
|
||||
<step>
|
||||
<para>In the source project, perform the following steps:</para>
|
||||
<orderedlist>
|
||||
<listitem>
|
||||
<para><link xlink:href="#create_snapshot">Create a snapshot of the instance.</link></para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para><link xlink:href="#download_snapshot">Download the snapshot as an image.</link></para>
|
||||
</listitem>
|
||||
</orderedlist></step>
|
||||
<step>
|
||||
<para>In the destination project, perform the following steps:</para>
|
||||
<orderedlist>
|
||||
<listitem>
|
||||
<para><link xlink:href="#import_snapshot">Import the snapshot to the new environment.</link></para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para><link xlink:href="#boot_from_snapshot">Boot a new instance from the snapshot.</link></para>
|
||||
</listitem>
|
||||
</orderedlist></step>
|
||||
</procedure>
|
||||
<note>
|
||||
<para>Some cloud providers allow only administrators to
|
||||
perform these steps.</para>
|
||||
</note>
|
||||
<para>To use snapshots to migrate instances from OpenStack
|
||||
projects to clouds, complete these steps:</para>
|
||||
<orderedlist>
|
||||
<listitem>
|
||||
<para>Create a snapshot of the instance.</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Download the snapshot as an image.</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Import the snapshot to the new environment.</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Boot a new instance from the snapshot.</para>
|
||||
</listitem>
|
||||
</orderedlist>
|
||||
<note>
|
||||
<para>Perform the <xref linkend="create_snapshot"/> and <xref
|
||||
linkend="download_snapshot"/> procedures in the source
|
||||
project.</para>
|
||||
<para>Perform the <xref linkend="import_snapshot"/> and <xref
|
||||
linkend="boot_from_snapshot"/> in the destination
|
||||
project.</para>
|
||||
<para>Some cloud providers allow only administrators to perform this task.</para>
|
||||
</note>
|
||||
<section xml:id="create_snapshot">
|
||||
<title>Create a snapshot of the instance</title>
|
||||
<procedure>
|
||||
<step>
|
||||
<para>Always shut down the source VM before you take the
|
||||
snapshot to make sure that all data is flushed to
|
||||
disk.</para>
|
||||
<para>Shut down the source VM before you take the snapshot to ensure that all data is flushed to disk.
|
||||
If necessary, list the instances to view get the instance name.</para>
|
||||
<screen><prompt>$</prompt> <userinput>nova list</userinput>
|
||||
<computeroutput>+--------------------------------------+------------+--------+------------------------------+
|
||||
| ID | Name | Status | Networks |
|
||||
+--------------------------------------+------------+--------+------------------------------+
|
||||
| c41f3074-c82a-4837-8673-fa7e9fea7e11 | example | ACTIVE | private=10.0.0.3 |
|
||||
+--------------------------------------+------------+--------+------------------------------+</computeroutput></screen>
|
||||
<computeroutput>+--------------------------------------+------------+--------+------------------------------+
|
||||
| ID | Name | Status | Networks |
|
||||
+--------------------------------------+------------+--------+------------------------------+
|
||||
| c41f3074-c82a-4837-8673-fa7e9fea7e11 | myInstance | ACTIVE | private=10.0.0.3 |
|
||||
+--------------------------------------+------------+--------+------------------------------+</computeroutput></screen>
|
||||
<screen><prompt>$</prompt> <userinput>nova stop example</userinput></screen>
|
||||
</step>
|
||||
<step>
|
||||
<para>Confirm that the instance shows a <literal>SHUTOFF</literal>
|
||||
status.</para>
|
||||
<para>Use the <command>nova list</command> command to confirm that the instance shows a
|
||||
<literal>SHUTOFF</literal> status.</para>
|
||||
<screen><prompt>$</prompt> <userinput>nova list</userinput>
|
||||
<computeroutput>+--------------------------------------+------------+---------+------------------------------+
|
||||
| ID | Name | Status | Networks |
|
||||
+--------------------------------------+------------+---------+------------------------------+
|
||||
| c41f3074-c82a-4837-8673-fa7e9fea7e11 | example | SHUTOFF | private=10.0.0.3 |
|
||||
+--------------------------------------+------------+---------+------------------------------+</computeroutput></screen>
|
||||
<para/>
|
||||
<computeroutput>+--------------------------------------+------------+---------+------------------------------+
|
||||
| ID | Name | Status | Networks |
|
||||
+--------------------------------------+------------+---------+------------------------------+
|
||||
| c41f3074-c82a-4837-8673-fa7e9fea7e11 | myInstance | SHUTOFF | private=10.0.0.3 |
|
||||
+--------------------------------------+------------+---------+------------------------------+</computeroutput></screen>
|
||||
</step>
|
||||
<step>
|
||||
<para>Use the <command>nova
|
||||
image-create</command> command to take a snapshot. Use the <command>nova
|
||||
image-list</command> command to check the status until the status
|
||||
is <literal>ACTIVE</literal>:</para>
|
||||
<screen><prompt>$</prompt> <userinput>nova list</userinput>
|
||||
<computeroutput>+--------------------------------------+------------+---------+------------------------------+
|
||||
| ID | Name | Status | Networks |
|
||||
+--------------------------------------+------------+---------+------------------------------+
|
||||
| c41f3074-c82a-4837-8673-fa7e9fea7e11 | example | SHUTOFF | private=10.0.0.3 |
|
||||
+--------------------------------------+------------+---------+------------------------------+</computeroutput></screen>
|
||||
<screen><prompt>$</prompt> <userinput>nova image-create --poll <replaceable>example</replaceable> <replaceable>examplesnapshot</replaceable></userinput>
|
||||
<computeroutput>Instance snapshotting... 50% complete</computeroutput></screen>
|
||||
<screen><prompt>$</prompt> <userinput>nova image-create --poll myInstance myInstanceSnapshot</userinput>
|
||||
<computeroutput>Instance snapshotting... 50% complete</computeroutput></screen>
|
||||
<screen><prompt>$</prompt> <userinput>nova image-list</userinput>
|
||||
<computeroutput>+--------------------------------------+---------------------------------+--------+--------+
|
||||
| ID | Name | Status | Server |
|
||||
+--------------------------------------+---------------------------------+--------+--------+
|
||||
| 657ebb01-6fae-47dc-986a-e49c4dd8c433 | cirros-0.3.2-x86_64-uec | ACTIVE | |
|
||||
| 72074c6d-bf52-4a56-a61c-02a17bf3819b | cirros-0.3.2-x86_64-uec-kernel | ACTIVE | |
|
||||
| 3c5e5f06-637b-413e-90f6-ca7ed015ec9e | cirros-0.3.2-x86_64-uec-ramdisk | ACTIVE | |
|
||||
| f30b204e-1ce6-40e7-b8d9-b353d4d84e7d | examplesnapshot | ACTIVE | |
|
||||
+--------------------------------------+---------------------------------+--------+--------+</computeroutput></screen>
|
||||
<computeroutput>+--------------------------------------+---------------------------------+--------+--------+
|
||||
| ID | Name | Status | Server |
|
||||
+--------------------------------------+---------------------------------+--------+--------+
|
||||
| 657ebb01-6fae-47dc-986a-e49c4dd8c433 | cirros-0.3.2-x86_64-uec | ACTIVE | |
|
||||
| 72074c6d-bf52-4a56-a61c-02a17bf3819b | cirros-0.3.2-x86_64-uec-kernel | ACTIVE | |
|
||||
| 3c5e5f06-637b-413e-90f6-ca7ed015ec9e | cirros-0.3.2-x86_64-uec-ramdisk | ACTIVE | |
|
||||
| f30b204e-1ce6-40e7-b8d9-b353d4d84e7d | myInstanceSnapshot | ACTIVE | |
|
||||
+--------------------------------------+---------------------------------+--------+--------+</computeroutput></screen>
|
||||
</step>
|
||||
</procedure>
|
||||
</section>
|
||||
@ -90,16 +80,16 @@
|
||||
<step>
|
||||
<para>Get the image ID:</para>
|
||||
<screen><prompt>$</prompt> <userinput>nova image-list</userinput>
|
||||
<computeroutput>+--------------------------------------+------------------+--------+--------------------------------------+
|
||||
| ID | Name | Status | Server |
|
||||
+--------------------------------------+------------------+--------+--------------------------------------+
|
||||
| f30b204e-1ce6-40e7-b8d9-b353d4d84e7d | examplesnapshot | ACTIVE | c41f3074-c82a-4837-8673-fa7e9fea7e11 |
|
||||
+--------------------------------------+------------------+--------+--------------------------------------+</computeroutput></screen>
|
||||
<computeroutput>+--------------------------------------+-------------------+--------+--------------------------------------+
|
||||
| ID | Name | Status | Server |
|
||||
+--------------------------------------+-------------------+--------+--------------------------------------+
|
||||
| f30b204e-1ce6-40e7-b8d9-b353d4d84e7d | myInstanceSnapshot| ACTIVE | c41f3074-c82a-4837-8673-fa7e9fea7e11 |
|
||||
+--------------------------------------+-------------------+--------+--------------------------------------+</computeroutput></screen>
|
||||
</step>
|
||||
<step>
|
||||
<para>Download the snapshot by using the image ID that
|
||||
was returned in the previous step:</para>
|
||||
<screen><prompt>$</prompt> <userinput>glance image-download --file <replaceable>snapshot.raw</replaceable> <replaceable>f30b204e-1ce6-40e7-b8d9-b353d4d84e7d</replaceable></userinput> </screen>
|
||||
<screen><prompt>$</prompt> <userinput>glance image-download --file snapshot.raw f30b204e-1ce6-40e7-b8d9-b353d4d84e7d</userinput></screen>
|
||||
<note>
|
||||
<para>The <command>glance image-download</command>
|
||||
command requires the image ID and cannot use
|
||||
@ -110,30 +100,21 @@
|
||||
</note>
|
||||
</step>
|
||||
<step>
|
||||
<para>Make the image available to the new environment,
|
||||
either through http or with direct upload to a
|
||||
<para>Make the image available to the new environment, either through HTTP or with direct upload to a
|
||||
machine (<command>scp</command>).</para>
|
||||
</step>
|
||||
</procedure>
|
||||
</section>
|
||||
<section xml:id="import_snapshot">
|
||||
<title>Import the snapshot to new environment</title>
|
||||
<procedure>
|
||||
<step>
|
||||
<para>In the new project or cloud environment, import
|
||||
the snapshot:</para>
|
||||
<screen><prompt>$</prompt> <userinput>glance image-create --copy-from <replaceable>IMAGE_URL</replaceable></userinput> </screen>
|
||||
</step>
|
||||
</procedure>
|
||||
<screen><prompt>$</prompt> <userinput>glance image-create --copy-from <replaceable>IMAGE_URL</replaceable></userinput></screen>
|
||||
</section>
|
||||
<section xml:id="boot_from_snapshot">
|
||||
<title>Boot a new instance from the snapshot</title>
|
||||
<procedure>
|
||||
<step>
|
||||
<para>In the new project or cloud environment, use the
|
||||
snapshot to create the new instance:</para>
|
||||
<screen><prompt>$</prompt> <userinput>nova boot --flavor m1.tiny --image <replaceable>EXAMPLE_SNAPSHOT</replaceable> <replaceable>NEW_INSTANCE</replaceable></userinput></screen>
|
||||
</step>
|
||||
</procedure>
|
||||
<screen><prompt>$</prompt> <userinput>nova boot --flavor m1.tiny --image myInstanceSnapshot myNewInstance</userinput></screen>
|
||||
</section>
|
||||
</section>
|
||||
|
||||
Loading…
Reference in New Issue
Block a user