From fa004545733e1f7b909c7a88e3360593de7d883a Mon Sep 17 00:00:00 2001 From: KATO Tomoyuki Date: Mon, 6 Jun 2016 20:45:00 +0900 Subject: [PATCH] [admin-guide] use openstack CLI instead of heat CLI The heat CLI is deprecated at now. Change-Id: I3e0493c6b2b958919b87852b68380c6d1ef7cdc7 Partial-Bug: #1581726 --- .../source/cli_admin_manage_stacks.rst | 18 ++++++++++++------ .../orchestration-stack-domain-users.rst | 4 ++-- 2 files changed, 14 insertions(+), 8 deletions(-) diff --git a/doc/admin-guide/source/cli_admin_manage_stacks.rst b/doc/admin-guide/source/cli_admin_manage_stacks.rst index 484195516b..fd9241ce6e 100644 --- a/doc/admin-guide/source/cli_admin_manage_stacks.rst +++ b/doc/admin-guide/source/cli_admin_manage_stacks.rst @@ -19,10 +19,16 @@ high availability. For information about: - basic creation and deletion of Orchestration stacks, refer - to the `OpenStack End User Guide `_ + to the `OpenStack End User Guide + `_ -- **heat** CLI commands, see the `OpenStack Command Line Interface Reference - `_ +- **openstack** CLI, see the `OpenStack Command-Line Interface + Reference `_ + +.. note:: + + The ``heat`` CLI is deprecated in favor of ``python-openstackclient``. + For a Python library, continue using ``python-heatclient``. As an administrator, you can also carry out stack functions on behalf of your users. For example, to resume, suspend, @@ -30,6 +36,6 @@ or delete a stack, run: .. code-block:: console - $ heat action-resume stackID - $ heat action-suspend stackID - $ heat stack-delete stackID + $ openstack stack resume STACK + $ openstack stack suspend STACK + $ openstack stack delete STACK diff --git a/doc/admin-guide/source/orchestration-stack-domain-users.rst b/doc/admin-guide/source/orchestration-stack-domain-users.rst index 303a84acca..4f2b8530bb 100644 --- a/doc/admin-guide/source/orchestration-stack-domain-users.rst +++ b/doc/admin-guide/source/orchestration-stack-domain-users.rst @@ -147,6 +147,6 @@ or:: GET v1/​{stack_domain_project_id}​/stacks/​{stack_name}​/​\ {stack_id}​/resources/​{resource_name}​/metadata -The stack owner uses the former (via ``heat resource-metadata -{stack_name} {resource_name}``), and any agents in the instance +The stack owner uses the former (via ``openstack stack resource metadata +STACK RESOURCE``), and any agents in the instance use the latter.