openstack-manuals/doc/admin-guide-cloud/source/dashboard_admin_manage_stacks.rst
Andreas Jaeger 211e44e1c1 Fix config-reference and admin-guide-cloud builds
nova-ec2 was removed from nova for mitaka, remove the file ec2-api now.
A previous change already removed nova-ec2 table.

File compute/nova-logs was renamed to compute/logs, but was referenced
by other files. Add label so that reference works.

Replace internal references to non-existing documents in
admin-guide-cloud with external links.

Note: We hit these bugs in local tests depending on python package
versions, the packages in the gate ignore the error.

Change-Id: Idece9d7186321b8b40b3020f701531908f88b6a5
2016-02-23 12:55:33 +01:00

1.2 KiB

Launch and manage stacks using the Dashboard

The Orchestration service provides a template-based orchestration engine for the OpenStack cloud. Orchestration services create and manage cloud infrastructure resources such as storage, networking, instances, and applications as a repeatable running environment.

Administrators use templates 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:

  • administrative tasks on the command-line, see the OpenStack Admin User Guide.

    Note

    There are no administration-specific tasks that can be done through the Dashboard.

  • the basic creation and deletion of Orchestration stacks, refer to the OpenStack End User Guide.