Merge "dashboad_admin_manage_stacks migration to RST"
This commit is contained in:
commit
ed6b45db28
doc/playground-user-guide/source
@ -34,3 +34,4 @@ sizes of server instances.
|
||||
dashboard_set_quotas
|
||||
dashboard_manage_resources.rst
|
||||
dashboard_manage_host_aggregates.rst
|
||||
dashboard_admin_manage_stacks.rst
|
||||
|
@ -0,0 +1,35 @@
|
||||
.. meta::
|
||||
:scope: admin_only
|
||||
|
||||
========================
|
||||
Launch and manage stacks
|
||||
========================
|
||||
|
||||
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:
|
||||
|
||||
* administrative tasks on the command line, see the section called
|
||||
“Launch and manage stacks”;
|
||||
|
||||
.. 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
|
||||
`End User Guide`.
|
||||
|
||||
.. TODO: add link to the new End User Guide on line 30 (old link: <http://docs.
|
||||
openstack.org/user-guide/content/dashboard_stacks.html>`_), and reference
|
||||
to Launch and manage stacks on the line 23 (old link: <http://docs.openstack.
|
||||
org/user-guide-admin/content/section_cli_admin_manage_stacks.html>`_) (OL)
|
Loading…
x
Reference in New Issue
Block a user