I've been trying to use openstack overcloud node delete and I noticed some issues we probably want to address:
1. --stack option is mandatory. We should default this to "overcloud" the same as the deploy command? If you don't pass --stack, the command fails obscurely:
u'message': u"Failed to run action [action_ex_id=55d1ba25-c280-4e2b-9343-d6e1b7897db1, action_cls='<class 'mistral.actions.action_factory.ScaleDownAction'>', attributes='{}', params='{u'nodes': [u'bc04d434-7a4f-46d7-a4d5-f1189ce722f2'], u'container': u'', u'timeout': 240}']\n ERROR: 404 Not Found\n\nThe resource could not be found.\n\n ",
u'status': u'FAILED'}
So we probably also need to output a more meaningful error in the case where the --stack option is wrong (references a non-existent stack)
2. The command exits before the scale-down is completed. It sits for a while, then exits, but the scaledown is still running:
[stack@instack ~]$ openstack overcloud node delete --stack overcloud bc04d434-7a4f-46d7-a4d5-f1189ce722f2
deleting nodes [u'bc04d434-7a4f-46d7-a4d5-f1189ce722f2'] from stack overcloud
Started Mistral Workflow tripleo.scale.v1.delete_node. Execution ID: f46a2ed5-cc8d-419c-8201-e6be8585ed2f
[stack@instack ~]$ nova list
+--------------------------------------+-------------------------+--------+------------+-------------+---------------------+
| ID | Name | Status | Task State | Power State | Networks |
+--------------------------------------+-------------------------+--------+------------+-------------+---------------------+
| 8e00f89c-4490-4bbf-a7a3-0392a03d5d59 | overcloud-controller-0 | ACTIVE | - | Running | ctlplane=192.0.2.7 |
| bc04d434-7a4f-46d7-a4d5-f1189ce722f2 | overcloud-novacompute-0 | ACTIVE | - | Running | ctlplane=192.0.2.16 |
| 0950c9ff-2c44-40f2-89fe-17e4775ab379 | overcloud-novacompute-1 | ACTIVE | - | Running | ctlplane=192.0.2.15 |
+--------------------------------------+-------------------------+--------+------------+-------------+---------------------+
[stack@instack ~]$ heat stack-list
WARNING (shell) "heat stack-list" is deprecated, please use "openstack stack list" instead
+--------------------------------------+------------+--------------------+----------------------+----------------------+
| id | stack_name | stack_status | creation_time | updated_time |
+--------------------------------------+------------+--------------------+----------------------+----------------------+
| a7516e44-3e9f-4223-9c7a-f7efb9f6b4b2 | overcloud | UPDATE_IN_PROGRESS | 2016-11-09T11:04:07Z | 2016-11-10T11:35:07Z |
3. Related to the above, there's no indication of status. We should probably poll for events and display them exactly like the deploy command does?
Also the docs http://