From fc90b85bf847fdfe76d2826a1846f73582ff81ea Mon Sep 17 00:00:00 2001 From: Steve Baker Date: Fri, 5 Apr 2013 11:35:28 +1300 Subject: [PATCH] Replace deprecated commands with current equivalents Change-Id: I871d7f0e5cd0a22a284a6e6733607feafbbb52a2 --- doc/source/getting_started/on_devstack.rst | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/doc/source/getting_started/on_devstack.rst b/doc/source/getting_started/on_devstack.rst index 1d4d629c..cbfacb41 100644 --- a/doc/source/getting_started/on_devstack.rst +++ b/doc/source/getting_started/on_devstack.rst @@ -39,7 +39,7 @@ Before any heat commands can be run, the authentication environment needs to be You can confirm that Heat is running and responding with this command :: - heat list + heat stack-list This should return an empty line @@ -60,7 +60,7 @@ Launching a stack ----------------- Now lets launch a stack, assuming that DEST is left as the default /opt/stack:: - heat create teststack -f + heat stack-create teststack -f /opt/stack/heat/templates/WordPress_Single_Instance.template -P "InstanceType=m1.large;DBUsername=wp;DBPassword=verybadpassword;KeyName=heat_key;LinuxDistribution=F16" Which will respond:: @@ -76,7 +76,7 @@ List stacks ~~~~~~~~~~~ List the stacks in your tenant:: - heat list + heat stack-list List stack events ~~~~~~~~~~~~~~~~~ @@ -90,7 +90,7 @@ Describe the wordpress stack Show detailed state of a stack:: - heat describe teststack + heat stack-show teststack Note: After a few seconds, the stack_status should change from IN_PROGRESS to CREATE_COMPLETE. @@ -107,5 +107,5 @@ Delete the instance when done Note: The list operation will show no running stack.:: - heat delete teststack - heat list + heat stack-delete teststack + heat stack-list -- 2.45.2