Bug 1042199

Cloned from launchpad blueprint https://blueprints.launchpad.net/heat/+spec/troubleshooting-low-level-control.

Description:

Problem:
When a Heat template is deployed and an error occurs, the VM's are rolled back and deleted.  Server logs can help to determine the problem, but often we need to log into the VM's being deployed to debug the scripts and environment.  This blueprint proposes pausing the template deployment at the point of error so that the user can inspect the partial stack for problem determination.
 
Proposed support:
Command line + API:

   - stack-create: add a debugging option
     - validation of template: pause and point to exact failure in template (better message, suggest solution), and continue stack create once correction is made in template
     - error during deployment:  Heat engine pauses deployment, leaving all resources/components as is.  Failed template is shown as in PAUSED_ERROR state

   - stack-show:  to inspect template, show info on the current state of each resources and components
     - successfully deployed
     - error with message
     - not yet deployed

   - logs collection as they are available

   - stack-continue:  new option to continue deployment 

 
Related blueprint:  
Use stack-update to attempt recovery of failed create or update
https://blueprints.launchpad.net/heat/+spec/retry-failed-update
 
Concern:
How to handle concurrency when pausing deployment:  
   - do nothing:  sufficient in many cases
   - serialize deployment during debugging: deterministic behavior but not guaranteed to reproduce error 
   - trace/replay deployment

Specification URL (additional information):

None