394538384b
Included the new options available in the Launch an Instance window for launching an instance in the Dashboard chapter of End User Guide. Also removed link to the 'launch instance from volume' section as the steps seems redundant. Add a .htacces redirection to handle the removed file (boot from volume). Partial-Bug: #1279133 Change-Id: I7f29aa45211d84e2dfab772235891a776492686d
230 lines
11 KiB
XML
230 lines
11 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<!DOCTYPE section [
|
|
<!-- Some useful entities borrowed from HTML -->
|
|
<!ENTITY ndash "–">
|
|
<!ENTITY mdash "—">
|
|
<!ENTITY hellip "…">
|
|
]>
|
|
<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="dashboard_launch_instances_from_image">
|
|
<title>Launch an instance</title>
|
|
<?dbhtml stop-chunking?>
|
|
<para>When you launch an instance from an image, OpenStack creates
|
|
a local copy of the image on the compute node where the
|
|
instance starts.</para>
|
|
<procedure>
|
|
<step>
|
|
<para>Log in to the dashboard, choose a project,
|
|
and click the <guilabel>Images &
|
|
Snapshot</guilabel> category.</para>
|
|
<para>The dashboard shows the images that have been
|
|
uploaded to OpenStack Image Service and are available
|
|
for this project.</para>
|
|
<para>For details on creating images, see <link
|
|
xlink:href="http://docs.openstack.org/image-guide/content/ch_creating_images_manually.html">
|
|
Creating images manually</link> in the <citetitle>OpenStack Virtual
|
|
Machine Image Guide</citetitle>.</para>
|
|
</step>
|
|
<step>
|
|
<para>Select an image and click
|
|
<guibutton>Launch</guibutton>.</para>
|
|
</step>
|
|
<step>
|
|
<para>In the <guilabel>Launch Instance</guilabel> window,
|
|
specify the following values:</para>
|
|
<informaltable rules="all" width="75%">
|
|
<col width="30%"/>
|
|
<col width="70%"/>
|
|
<thead>
|
|
<tr>
|
|
<th colspan="2" align="center"
|
|
><guilabel>Details</guilabel> tab</th>
|
|
</tr>
|
|
</thead>
|
|
<tbody>
|
|
<tr>
|
|
<td><para><guilabel>Availability Zone</guilabel></para></td>
|
|
<td>
|
|
<para>By default, this value is set to the availability
|
|
zone given by the cloud provider (for example,
|
|
<literal>us-west</literal> or <literal>apac-south</literal>).
|
|
Though, it could be <literal>nova</literal> for most cases.
|
|
</para>
|
|
</td>
|
|
</tr>
|
|
<tr>
|
|
<td><para><guilabel>Instance Name</guilabel></para></td>
|
|
<td><para>The name to assign to the virtual machine.
|
|
</para>
|
|
<note>
|
|
<para>The name you assign here becomes the initial host
|
|
name of the server. After the server is built, if you
|
|
change the server name in the API or change the host
|
|
name directly, the names are not updated in the dashboard.</para>
|
|
<para>Server names are not guaranteed to be unique when
|
|
created so you could have two instances with the same
|
|
host name.</para>
|
|
</note>
|
|
</td>
|
|
</tr>
|
|
<tr>
|
|
<td>
|
|
<para><guilabel>Flavor</guilabel></para></td>
|
|
<td><para>The size of the virtual machine to
|
|
launch.</para></td>
|
|
</tr>
|
|
<tr>
|
|
<td><para><guilabel>Instance
|
|
Count</guilabel></para></td>
|
|
<td><para>To launch multiple instances, enter
|
|
a value greater than 1. Default is 1.
|
|
</para></td>
|
|
</tr>
|
|
<tr>
|
|
<td>
|
|
<para>
|
|
<guilabel>Instance Boot Source</guilabel>
|
|
</para>
|
|
</td>
|
|
<td><para>Your options are:</para>
|
|
<itemizedlist>
|
|
<listitem>
|
|
<para>
|
|
<guilabel>Boot from image</guilabel> - If you choose
|
|
this option, a new field for <guilabel>Image Name</guilabel>
|
|
displays. You can select the image from the
|
|
dropdown list.
|
|
</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>
|
|
<guilabel>Boot from snapshot</guilabel> - If you
|
|
choose this option, a new field for <guilabel>Instance Snapshot</guilabel>
|
|
displays. You can select the snapshot from
|
|
the dropdown list.
|
|
</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>
|
|
<guilabel>Boot from volume</guilabel> - If you
|
|
choose this option, a new field for <guilabel>Volume</guilabel>
|
|
displays. You can select the volume from the
|
|
dropdown list.
|
|
</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>
|
|
<guilabel>Boot from image (creates a new volume)
|
|
</guilabel> - With this option, you can boot from
|
|
an image and create a volume by entering the <guilabel>Device Size</guilabel>
|
|
and <guilabel>Device Name</guilabel> for your
|
|
volume.
|
|
</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>
|
|
<guilabel>Boot from volume snapshot (creates a new
|
|
volume)</guilabel> - Using this option, you can
|
|
boot from a volume snapshot and create a new
|
|
volume by choosing <guilabel>Volume Snapshot</guilabel>
|
|
from a dropdown list and adding a <guilabel>Device Name</guilabel>
|
|
for your volume.
|
|
</para>
|
|
</listitem>
|
|
</itemizedlist>
|
|
<para>Since you are launching an instance from an image,
|
|
<guilabel>Boot from image</guilabel> is chosen by
|
|
default.</para>
|
|
</td>
|
|
</tr>
|
|
<tr>
|
|
<td>
|
|
<para>
|
|
<guilabel>Image Name</guilabel>
|
|
</para>
|
|
</td>
|
|
<td>
|
|
<para>This field changes based on your previous selection.
|
|
Since you have chosen to launch an instance using an image,
|
|
the <guilabel>Image Name</guilabel> field displays.
|
|
Select the image name from the dropdown list.</para>
|
|
</td>
|
|
</tr>
|
|
<tr>
|
|
<th colspan="2" align="center"
|
|
><guilabel>Access &
|
|
Security</guilabel> tab</th>
|
|
</tr>
|
|
<tr>
|
|
<td><para><guilabel>Keypair</guilabel></para></td>
|
|
<td><para>Select a keypair from the dropdown list.</para>
|
|
<para>In case an image uses a static root
|
|
password or a static key set (neither
|
|
is recommended), you do not need to
|
|
provide a keypair to launch the
|
|
instance.</para></td>
|
|
</tr>
|
|
<tr>
|
|
<td><para><guilabel>Security
|
|
Groups</guilabel></para></td>
|
|
<td><para>Activate the security groups that
|
|
you want to assign to the
|
|
instance.</para>
|
|
<para>Security groups are a kind of cloud
|
|
firewall that define which incoming
|
|
network traffic is forwarded to
|
|
instances. For details, see <xref
|
|
linkend="security_groups_add_rule"
|
|
/>.</para>
|
|
<para>If you have not created any security
|
|
groups, you can assign only the
|
|
default security group to the
|
|
instance.</para></td>
|
|
</tr>
|
|
<tr>
|
|
<th colspan="2" align="center"
|
|
><guilabel>Networking</guilabel>
|
|
tab</th>
|
|
</tr>
|
|
<tr>
|
|
<td><para><guilabel>Selected Networks</guilabel></para></td>
|
|
<td><para>To add a network to the instance, click the
|
|
<guibutton>+</guibutton> in the <guilabel>Available
|
|
Networks</guilabel> field.</para></td>
|
|
</tr>
|
|
<tr>
|
|
<th colspan="2" align="center"
|
|
><guilabel>Post-Creation</guilabel>
|
|
tab</th>
|
|
</tr>
|
|
<tr>
|
|
<td><para><guilabel>Customization
|
|
Script</guilabel></para></td>
|
|
<td><para>A customization script that runs after your
|
|
instance launches.</para></td>
|
|
</tr>
|
|
</tbody>
|
|
</informaltable>
|
|
</step>
|
|
<step>
|
|
<para>Click <guibutton>Launch</guibutton>. The instance
|
|
starts on a compute node in the cloud.</para>
|
|
</step>
|
|
<step>
|
|
<para>The <guilabel>Instances</guilabel> category shows
|
|
the instance name, its private and public IP
|
|
addresses, size, status, task, and power state.</para>
|
|
</step>
|
|
<step>
|
|
<para>If you did not provide a keypair, security groups,
|
|
or rules so far, users can only access the instance
|
|
from inside the cloud through VNC. Even pinging the
|
|
instance is not possible. To access the instance
|
|
through a VNC console, see <xref
|
|
linkend="instance_console"/>.</para>
|
|
</step>
|
|
</procedure>
|
|
</section>
|