bbec5aa4d2
The XML root element of Docbook XML files should match the following format: <ELEMENT 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="THE_XML_ID_OF_THE_ELEMENT"> Change-Id: If8d27898af12af2edc2d2d13557ec2365a241656
38 lines
2.1 KiB
XML
38 lines
2.1 KiB
XML
<?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="section_cli_admin_manage_stacks">
|
|
<title>Launch and manage stacks</title>
|
|
<para>The Orchestration service provides a template-based orchestration engine
|
|
for the OpenStack cloud, which can be used to create and manage cloud
|
|
infrastructure resources such as storage, networking, instances, and
|
|
applications as a repeatable running environment.
|
|
</para>
|
|
<para>Templates are used to create stacks, which are collections of resources. For example,
|
|
a stack might include instances, floating IPs, volumes, security groups, or users.
|
|
The Orchestration service offers access to all OpenStack core services via a single modular template,
|
|
with additional orchestration capabilities such as auto-scaling and basic high availability.</para>
|
|
<para>For information about the:</para>
|
|
<para>
|
|
<itemizedlist>
|
|
<listitem>
|
|
<para>Basic creation and deletion of Orchestration stacks, refer to the
|
|
<link xlink:href="http://docs.openstack.org/user-guide/content/dashboard_stacks.html">End User Guide</link>.</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para><systemitem>heat</systemitem> CLI commands, see the <link
|
|
xlink:href="http://docs.openstack.org/cli-reference/content/"><citetitle>
|
|
OpenStack Command Line Interface Reference</citetitle></link>
|
|
</para>
|
|
</listitem>
|
|
</itemizedlist>
|
|
</para>
|
|
<para>As an administrator, you can also carry out stack functions on behalf of your users. For
|
|
example, to resume, suspend, or delete a stack, run:</para>
|
|
<screen><prompt>$</prompt> <userinput>action-resume <replaceable>stackID</replaceable></userinput>
|
|
<prompt>$</prompt> <userinput>action-suspend <replaceable>stackID</replaceable></userinput>
|
|
<prompt>$</prompt> <userinput>stack-delete <replaceable>stackID</replaceable></userinput></screen>
|
|
</section>
|