3b584b8f4f
This change fixes the documentation explaining how to obtain deployment status. - Deployment status is now determined based on the local file, instead of Heat + Mistral. - The workflow subcommands no longer work since Mistral was removed. - The openstack overcloud failures command was removed by [1]. [1] 7cef22cc68d6af316ef9fbf60cb093c209c31215 Change-Id: I4bc8a691a75438471d36ee866f6de25e4ec7ee92
34 lines
1.1 KiB
ReStructuredText
34 lines
1.1 KiB
ReStructuredText
Deployment Status
|
|
^^^^^^^^^^^^^^^^^
|
|
Since Heat is no longer the source of authority on the status of the overcloud
|
|
deployment, a new tripleoclient command is available to show the overcloud
|
|
deployment status::
|
|
|
|
openstack overcloud status
|
|
|
|
The output will report the status of the deployment, taking into consideration
|
|
the result of all the steps to do the full deployment. The following is an
|
|
example of the output::
|
|
|
|
[stack@undercloud ]$ openstack overcloud status
|
|
|
|
+------------+-------------------+
|
|
| Stack Name | Deployment Status |
|
|
+------------+-------------------+
|
|
| overcloud | DEPLOY_SUCCESS |
|
|
+------------+-------------------+
|
|
|
|
A different stack name can be specified with ``--stack``::
|
|
|
|
[stack@undercloud ]$ openstack overcloud status --stack my-deployment
|
|
|
|
+---------------+-------------------+
|
|
| Stack Name | Deployment Status |
|
|
+-----------+-----------------------+
|
|
| my-deployment | DEPLOY_SUCCESS |
|
|
+---------------+-------------------+
|
|
|
|
The deployment status is stored in the YAML file, generated at
|
|
``$HOME/overcloud-deploy/<stack>/<stack>-deployment_status.yaml`` in
|
|
the undercloud node.
|