<div dir="ltr"><div>Does "heat resource-list" and "heat event-list" help?<br><br>[gyliu@drsserver hadoop_heat(keystone_admin)]$ heat resource-list a1<br>+----------------------------+------------------------------------------+--------------------+----------------------+<br>
| logical_resource_id        | resource_type                            | resource_status    | updated_time         |<br>+----------------------------+------------------------------------------+--------------------+----------------------+<br>
| CfnUser                    | AWS::IAM::User                           | CREATE_COMPLETE    | 2014-02-28T16:50:11Z |<br>| HadoopM                    | AWS::EC2::Instance                       | CREATE_IN_PROGRESS | 2014-02-28T16:50:11Z |<br>
| HadoopMasterWaitHandle     | AWS::CloudFormation::WaitConditionHandle | CREATE_COMPLETE    | 2014-02-28T16:50:11Z |<br>| HadoopSlaveKeys            | AWS::IAM::AccessKey                      | CREATE_IN_PROGRESS | 2014-02-28T16:50:11Z |<br>
| HadoopMasterWaitCondition  | AWS::CloudFormation::WaitCondition       | INIT_COMPLETE      | 2014-02-28T16:50:31Z |<br>| LaunchConfig               | AWS::AutoScaling::LaunchConfiguration    | INIT_COMPLETE      | 2014-02-28T16:50:31Z |<br>
| HadoopSGroup               | AWS::AutoScaling::AutoScalingGroup       | INIT_COMPLETE      | 2014-02-28T16:50:52Z |<br>| HadoopSlaveScaleDownPolicy | AWS::AutoScaling::ScalingPolicy          | INIT_COMPLETE      | 2014-02-28T16:50:52Z |<br>
| HadoopSlaveScaleUpPolicy   | AWS::AutoScaling::ScalingPolicy          | INIT_COMPLETE      | 2014-02-28T16:50:52Z |<br>| MEMAlarmHigh               | AWS::CloudWatch::Alarm                   | INIT_COMPLETE      | 2014-02-28T16:50:52Z |<br>
| MEMAlarmLow                | AWS::CloudWatch::Alarm                   | INIT_COMPLETE      | 2014-02-28T16:50:52Z |<br>+----------------------------+------------------------------------------+--------------------+----------------------+<br>
<br>[gyliu@drsserver hadoop_heat(keystone_admin)]$ heat event-list -r HadoopMasterWaitCondition a1<br>+---------------------------+-------+------------------------+--------------------+----------------------+<br>| logical_resource_id       | id    | resource_status_reason | resource_status    | event_time           |<br>
+---------------------------+-------+------------------------+--------------------+----------------------+<br>| HadoopMasterWaitCondition | 37389 | state changed          | CREATE_IN_PROGRESS | 2014-02-28T16:51:07Z |<br>| HadoopMasterWaitCondition | 37390 | state changed          | CREATE_COMPLETE    | 2014-02-28T16:52:46Z |<br>
+---------------------------+-------+------------------------+--------------------+----------------------+<br><br></div>Thanks,<br><br>Jay<br><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">2014-02-28 15:28 GMT+08:00 Qiming Teng <span dir="ltr"><<a href="mailto:tengqim@linux.vnet.ibm.com" target="_blank">tengqim@linux.vnet.ibm.com</a>></span>:<br>

<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
The creation a stack is usually a time costly process, considering that<br>
there are cases where software packages need to be installed and<br>
configured.<br>
<br>
There are also cases where a stack consists of more than one VM instance<br>
and the dependency between instances.  The instances may have to be<br>
created one by one.<br>
<br>
Are Heat people considering adding some progress updates during the<br>
deployment?  For example, a simple log that can be printed by heatclient<br>
telling the user what progress has been made:<br>
<br>
Refreshing known resources types<br>
Receiving template <...><br>
Validating template <...><br>
Creating resource my_lb [AWS::EC2:LoadBalancer]<br>
Creating resource lb_instance1 [AWS::EC2::Instance]<br>
Creating resource latency_watcher [AWS::CloudWatch::Alarm]<br>
....<br>
...<br>
<br>
<br>
This would be useful for users to 'debug' their templates, especially<br>
when the template syntax is okay but its activities are not the intended<br>
one.<br>
<br>
Do we have to rely on heat-cfn-api to get these notifications?<br>
<br>
Any thoughts?<br>
<br>
  - Qiming<br>
<br>
Research Staff Member<br>
IBM Research - China<br>
tengqim AT cn DOT ibm DOT com<br>
<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div><br><br clear="all"><br>-- <br><div dir="ltr"><div>Thanks,<br><br></div>Jay<br></div>
</div></div></div></div>