f046b26f08
http://docs.openstack.org/user-guide-admin/cli_admin_manage_stacks.html Launch and manage stacks using the CLI 1.now the url link to the index, should directly to the heatcli 2.add heat to the beginning of the command This patch fix it Change-Id: I281c0785c61fa61fa2b7eac5e14efec8fcaee854 Closes-Bug: #1483270
35 lines
1.3 KiB
ReStructuredText
35 lines
1.3 KiB
ReStructuredText
======================================
|
|
Launch and manage stacks using the CLI
|
|
======================================
|
|
|
|
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.
|
|
|
|
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.
|
|
|
|
For information about the:
|
|
|
|
- Basic creation and deletion of Orchestration stacks, refer
|
|
to the `OpenStack End User Guide <http://docs.openstack.org/user-guide/dashboard_stacks.html>`_
|
|
|
|
- **heat** CLI commands, see the `OpenStack Command Line Interface Reference <http://docs.openstack.org/cli-reference/content/heatclient_commands.html>`_
|
|
|
|
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:
|
|
|
|
.. code::
|
|
|
|
$ heat action-resume stackID
|
|
$ heat action-suspend stackID
|
|
$ heat stack-delete stackID
|