Implement a new set of heat commands as python-openstackclient plugins.
python-openstackclient is becoming the default command line client for many OpenStack projects. Heat would benefit from implementing all of its client commands as python-openstackclient plugins implemented in the python-heatclient repository.
The intent of this spec is to identify the commands to be implemented and establish conventions for command and argument names. This spec is not intented to be a full and correct specification of command and argument names. The details can be left to the code reviews for the commands themselves.
The following conventions will be adopted for argument flags:
The following heat commands will be implemented for openstack initially suggesting these command names:
heat stack-create openstack stack create heat stack-update openstack stack update heat stack-list openstack stack list heat stack-show openstack stack show heat stack-delete openstack stack delete heat output-list openstack stack output list heat output-show openstack stack output show
heat stack-abandon openstack stack abandon heat stack-adopt openstack stack adopt heat stack-cancel-update openstack stack update cancel heat stack-preview openstack stack update --dry-run heat action-check openstack stack check heat action-resume openstack stack resume heat action-suspend openstack stack suspend heat hook-clear openstack stack hook clear heat hook-poll openstack stack hook poll
heat resource-list openstack stack resource list heat resource-metadata openstack stack resource metadata show heat resource-show openstack stack resource show heat resource-signal openstack stack resource signal heat resource-type-list openstack orchestration resource type list heat resource-type-show openstack orchestration resource type show
heat template-show openstack stack template show heat template-validate openstack stack create --dry-run heat template-version-list openstack orchestration template version list heat resource-type-template openstack orchestration resource type show --format (hot|cfn)
heat event-list openstack stack event list heat event-show openstack stack event show
heat config-create openstack software config create heat config-delete openstack software config delete heat config-show openstack software config show heat config-list openstack software config list heat deployment-create openstack software deployment create heat deployment-delete openstack software deployment delete heat deployment-list openstack software deployment list heat deployment-metadata-show openstack software deployment metadata show heat deployment-output-show openstack software deployment output show heat deployment-show openstack software deployment show
heat stack-restore openstack stack snapshot restore heat stack-snapshot openstack stack snapshot create heat snapshot-delete openstack stack snapshot delete heat snapshot-list openstack stack snapshot list heat snapshot-show openstack stack snapshot show
heat build-info openstack orchestration build-info heat service-list openstack service list (need to integrate with existing command)
There are many commands to implement and implementation tasks would be easily shared among many developers. The launchpad blueprint whiteboard will be used to coordinate the implementation status of each command and who has assigned themself to implement each one.
Work items or tasks – break the feature up into the things that need to be done to implement it. Those parts might end up being done by different people, but we’re mostly trying to understand the timeline for implementation.
None, this is an independent piece of work