Open Stack

Does "heat resource-list" and "heat event-list" help?

[gyliu at drsserver hadoop_heat(keystone_admin)]$ heat resource-list a1
+----------------------------+------------------------------------------+--------------------+----------------------+
| logical_resource_id        | resource_type                            |
resource_status    | updated_time         |
+----------------------------+------------------------------------------+--------------------+----------------------+
| CfnUser                    | AWS::IAM::User                           |
CREATE_COMPLETE    | 2014-02-28T16:50:11Z |
| HadoopM                    | AWS::EC2::Instance                       |
CREATE_IN_PROGRESS | 2014-02-28T16:50:11Z |
| HadoopMasterWaitHandle     | AWS::CloudFormation::WaitConditionHandle |
CREATE_COMPLETE    | 2014-02-28T16:50:11Z |
| HadoopSlaveKeys            | AWS::IAM::AccessKey                      |
CREATE_IN_PROGRESS | 2014-02-28T16:50:11Z |
| HadoopMasterWaitCondition  | AWS::CloudFormation::WaitCondition       |
INIT_COMPLETE      | 2014-02-28T16:50:31Z |
| LaunchConfig               | AWS::AutoScaling::LaunchConfiguration    |
INIT_COMPLETE      | 2014-02-28T16:50:31Z |
| HadoopSGroup               | AWS::AutoScaling::AutoScalingGroup       |
INIT_COMPLETE      | 2014-02-28T16:50:52Z |
| HadoopSlaveScaleDownPolicy | AWS::AutoScaling::ScalingPolicy          |
INIT_COMPLETE      | 2014-02-28T16:50:52Z |
| HadoopSlaveScaleUpPolicy   | AWS::AutoScaling::ScalingPolicy          |
INIT_COMPLETE      | 2014-02-28T16:50:52Z |
| MEMAlarmHigh               | AWS::CloudWatch::Alarm                   |
INIT_COMPLETE      | 2014-02-28T16:50:52Z |
| MEMAlarmLow                | AWS::CloudWatch::Alarm                   |
INIT_COMPLETE      | 2014-02-28T16:50:52Z |
+----------------------------+------------------------------------------+--------------------+----------------------+

[gyliu at drsserver hadoop_heat(keystone_admin)]$ heat event-list -r
HadoopMasterWaitCondition a1
+---------------------------+-------+------------------------+--------------------+----------------------+
| logical_resource_id       | id    | resource_status_reason |
resource_status    | event_time           |
+---------------------------+-------+------------------------+--------------------+----------------------+
| HadoopMasterWaitCondition | 37389 | state changed          |
CREATE_IN_PROGRESS | 2014-02-28T16:51:07Z |
| HadoopMasterWaitCondition | 37390 | state changed          |
CREATE_COMPLETE    | 2014-02-28T16:52:46Z |
+---------------------------+-------+------------------------+--------------------+----------------------+

Thanks,

Jay


2014-02-28 15:28 GMT+08:00 Qiming Teng <tengqim at linux.vnet.ibm.com>:

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



-- 
Thanks,

Jay
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140228/a28eb398/attachment.html>