openstack-manuals/doc/user-guide/section_dashboard_launch_instances.xml
Diane Fleming 64b6c9261e Folder rename, file rename, flattening of directories
Current folder name	New folder name	        Book title
----------------------------------------------------------
basic-install 	        DELETE
cli-guide	        DELETE
common	                common
NEW	                admin-guide-cloud	Cloud Administrators Guide
docbkx-example	        DELETE
openstack-block-storage-admin 	DELETE
openstack-compute-admin 	DELETE
openstack-config 	config-reference	OpenStack Configuration Reference
openstack-ha 	        high-availability-guide	OpenStack High Availabilty Guide
openstack-image	        image-guide	OpenStack Virtual Machine Image Guide
openstack-install 	install-guide	OpenStack Installation Guide
openstack-network-connectivity-admin 	admin-guide-network 	OpenStack Networking Administration Guide
openstack-object-storage-admin 	DELETE
openstack-security 	security-guide	OpenStack Security Guide
openstack-training 	training-guide	OpenStack Training Guide
openstack-user 	        user-guide	OpenStack End User Guide
openstack-user-admin 	user-guide-admin	OpenStack Admin User Guide
glossary	        NEW        	OpenStack Glossary

bug: #1220407

Change-Id: Id5ffc774b966ba7b9a591743a877aa10ab3094c7
author: diane fleming
2013-09-08 15:15:50 -07:00

154 lines
6.5 KiB
XML

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE section [
<!-- Some useful entities borrowed from HTML -->
<!ENTITY ndash "&#x2013;">
<!ENTITY mdash "&#x2014;">
<!ENTITY hellip "&#x2026;">
]>
<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">
<title>Launch and manage instances</title>
<para>Instances are virtual machines that run inside the cloud.</para>
<para>You can <link
xlink:href="dashboard_launch_instances_from_image">launch
an instance from an OpenStack image</link>. The OpenStack
Image Service provides a pool of images that are accessible to
members of different projects.</para>
<para>You can also <link
xlink:href="dashboard_launch_instances_from_volume">launch
an instance from an image that you have copied to a
persistent volume</link>. The instance boots from the
volume, which is provided by <systemitem class="service"
>nova-volume</systemitem> through iSCSI. When you launch
an instance from a volume, especially note the following
steps:</para>
<itemizedlist>
<listitem>
<para>To select from which volume to boot, launch an
instance from an arbitrary image. The image you select
does not boot. It is replaced by the image on the
volume that you choose in the next steps.</para>
<para>To boot a Xen image from a volume, the image you
launch in must be the same type, fully virtualized or
paravirtualized, as the one on the volume.</para>
</listitem>
<listitem>
<para>Select the volume or volume snapshot from which to
boot. Enter a device name. Enter
<literal>vda</literal> for KVM images or
<literal>xvda</literal> for Xen images.</para>
</listitem>
</itemizedlist>
<?hard-pagebreak?>
<xi:include
href="section_dashboard_launch_instances_from_image.xml"/>
<?hard-pagebreak?>
<xi:include
href="section_dashboard_launch_instances_from_volume.xml"/>
<?hard-pagebreak?>
<section xml:id="ssh-into-instance">
<title>SSH in to your instance</title>
<para>To SSH into your instance, you use the downloaded
keypair file.</para>
<note>
<para>The username is ubuntu for the Ubuntu cloud images
on TryStack.</para>
</note>
<procedure>
<step>
<para>Copy the IP address for your instance.</para>
</step>
<step>
<para>Use the SSH command to make a secure connection
to the instance. For example:</para>
<screen><prompt>$</prompt> <userinput>ssh -i MyKey.pem ubuntu@10.0.0.2</userinput></screen>
</step>
<step>
<para>At the prompt, type
<literal>yes</literal>.</para>
</step>
</procedure>
</section>
<section xml:id="track_usage">
<title>Track usage for instances</title>
<para>You can track usage for instances for each tenant, also known as a project. You
can track costs per month by showing metrics like number
of VCPUs, disks, RAM, and uptime for all your
instances.</para>
<procedure>
<!-- <title>To track usage</title> -->
<step>
<para>Log in to the OpenStack dashboard, choose a
project, and click the
<guilabel>Overview</guilabel> category.</para>
</step>
<step>
<para>To query the instance usage for a month, select
a month and click
<guibutton>Submit</guibutton>.</para>
</step>
<step>
<para>To download a summary, click <guibutton>Download
CSV Summary</guibutton>.</para>
</step>
</procedure>
</section>
<section xml:id="instance_snapshots">
<title>Create instance snapshots</title>
<procedure>
<step>
<para>Log in to the OpenStack dashboard, choose a
project, and click the
<guilabel>Instances</guilabel>
category.</para>
</step>
<step>
<para>Select the instance from which to create a
snapshot. From the <guilabel>Actions</guilabel>
drop-down list, select <guilabel>Create
Snapshot</guilabel>.</para>
</step>
<step>
<para>In the <guilabel>Create Snapshot</guilabel>
window, enter a name for the snapshot. Click
<guibutton>Create Snapshot</guibutton>. The
<guilabel>Images &amp; Snapshots</guilabel>
category shows the instance snapshot.</para>
</step>
<step>
<para>To launch an instance from the snapshot, select
the snapshot and click
<guibutton>Launch</guibutton>. Proceed with
<xref
linkend="dashboard_launch_instances_from_image"
/>.</para>
</step>
</procedure>
</section>
<section xml:id="control_instance_states">
<title>Control the state of an instance</title>
<procedure>
<!--<title>To control the state of an instance</title> -->
<step>
<para>Log in to the OpenStack dashboard, choose a
project, and click the
<guilabel>Instances</guilabel>
category.</para>
</step>
<step>
<para>Select an instance.</para>
</step>
<step>
<para>In the <guilabel>More</guilabel> drop-down list
in the <guilabel>Actions</guilabel> column, select
the state.</para>
<para>Depending on the current state of the instance,
you can choose to pause, resume, suspend, soft or
hard reboot, or terminate an instance.</para>
</step>
</procedure>
</section>
</section>