openstack/openstack-manuals
Code Issues Proposed changes

Included 'Launch a stack' using dashboard procedure

Browse Source 
New section 'Launch a stack' in the Dashboard chapter of User guide

Change-Id: I8212093d25982eede1c00b565f681f9eff898742
This commit is contained in:
Deepti Navale 2013-10-10 10:24:56 +10:00
parent 40c8b72b59
commit 6314b61c08
2 changed files with 99 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/user-guide/ch_dashboard.xml
View File

@ -27,4 +27,6 @@
<xi:include href="section_dashboard_create_networks.xml"/>
<?hard-pagebreak?>
<xi:include href="section_dashboard_manage_volumes.xml"/>
<?hard-pagebreak?>
<xi:include href="section_dashboard_stacks.xml"/>
</chapter>

97
doc/user-guide/section_dashboard_stacks.xml Normal file
View File

@ -0,0 +1,97 @@
<?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_stacks">
<title>Launch a stack</title>
<?dbhtml stop-chunking?>
<para>Heat is a service used to orchestrate multiple composite cloud applications using the AWS CloudFormation template format, through both an OpenStack-native ReST API and a CloudFormation-compatible Query API.</para>
<para>The purpose of Heat is to provide a template based orchestration for describing a cloud application by executing appropriate OpenStack API calls to generate running cloud applications, integrate other core components of OpenStack into a one-file template system. The templates allow creation of most OpenStack resource types such as instances, floating ips, volumes, security groups, users, etc.</para>
<procedure>
<title>Launch a stack</title>
<step>
<para>Log in to the OpenStack dashboard, choose a project,
and, click the <guibutton>Stacks</guibutton> in the <guilabel>Orchestration</guilabel> category.</para>
</step>
<step>
<para>Click <guibutton>Launch Stack</guibutton> button.</para>
<para>A <guilabel>Select Template</guilabel> window opens.</para>
</step>
<step><para>Choose between the template source options from the dropdown list.</para>
<para>Your options are URL, File or Direct Input.</para>
</step>
<step><para>Enter the URL, browse to the file location or directly include the template based on your selection in the previous step.</para>
<para>The <guilabel>Launch Stack</guilabel> window opens.</para>
</step>
<step>
<para>In the <guilabel>Launch Stack</guilabel> window, specify the following
values.</para>
<informaltable rules="all" width="75%">
<col width="30%"/>
<col width="70%"/>
<tbody>
<tr>
<td><para><guilabel>Stack
Name</guilabel></para></td>
<td><para>A name to identify the stack.</para></td>
</tr>
<tr>
<td><para><guilabel>Creation Timeout (minutes)</guilabel></para></td>
<td><para>Creation Timeout in minutes.</para></td>
</tr>
<tr>
<td><para><guilabel>Rollback On Failure</guilabel></para></td>
<td><para>Check this option if you want Heat to rollback on failure.</para></td>
</tr>
<tr>
<td><para><guilabel>Password for user "demo"</guilabel></para></td>
<td><para>Password for the user logged in.</para></td>
</tr>
<tr>
<td><para><guilabel>DBUsername</guilabel></para></td>
<td><para>Database user name.</para></td>
</tr>
<tr>
<td><para><guilabel>LinuxDistribution</guilabel></para></td>
<td><para>Linux Distribution used in the stacks.</para></td>
</tr>
<tr>
<td><para><guilabel>DBRootPassword</guilabel></para></td>
<td><para>Database root password.</para></td>
</tr>
<tr>
<td><para><guilabel>KeyName</guilabel></para></td>
<td><para>Name of the keypair.</para></td>
</tr>
<tr>
<td><para><guilabel>DBName</guilabel></para></td>
<td><para>Database name.</para></td>
</tr>
<tr>
<td><para><guilabel>DBPassword</guilabel></para></td>
<td><para>Database password.</para></td>
</tr>
<tr>
<td><para><guilabel>InstanceType</guilabel></para></td>
<td><para>Flavor of the instance.</para></td>
</tr>
</tbody>
</informaltable>
</step>
<step>
<para>Click <guilabel>Launch</guilabel> to create a
stack.</para>
</step>
<step>
<para>The dashboard shows the stack in the
<guilabel>Stacks</guilabel> category.</para>
</step>
</procedure>
<para>Once the stack is created, you can click on the stack name to see the following stack details, <guibutton>Topology</guibutton>, <guibutton>Overview</guibutton>, <guibutton>Resources</guibutton> and <guibutton>Events</guibutton>.</para>
</section>