dklenov's profile - activity

2015-05-20 02:08:44 -0600 received badge  Famous Question (source)
2014-07-15 07:42:35 -0600 received badge  Notable Question (source)
2014-07-09 07:32:47 -0600 received badge  Popular Question (source)
2013-03-16 00:51:29 -0600 answered a question Wait Conditions in HEAT

Thanks, Steven!

2013-03-15 23:06:09 -0600 asked a question Wait Conditions in HEAT

Hi,

We are going to use HEAT for needs of our customer and need to put some synchronizations between different resources.

Does HEAT support usage of Wait Conditions ( http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-waitcondition.html (http://docs.aws.amazon.com/AWSCloudFo...) ) and DependsOn attributes ( http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-attribute-dependson.html (http://docs.aws.amazon.com/AWSCloudFo...) ) in the template?

If not, when it is going to be implemented?

Thanks, Dmitry.

2013-03-15 00:02:31 -0600 answered a question Integation with different OpenStack releases

Hi Steven,

Thanks a lot for your answer. It perfectly clarifies the situation.

Dmitry.

2013-03-14 22:48:06 -0600 answered a question Integation with different OpenStack releases

Hi Clint!

Thanks for the clarification. And what is the situation with existing OpenStack releases? Does HEAT support Essex and Folsom? And if it is targeted for Grizzly mostly, how much efforts would it require to make it work with Folsom release? What is your feeling regarding this?

Thanks, Dmitry.

2013-03-14 19:58:48 -0600 asked a question Integation with different OpenStack releases

Hi Folks,

We are going to use HEAT for VM configuration and therefore would like to get more data regarding HEAT applicability for different OpenStack versions.

Can you please clarify, which OpenStack releases are supported by current HEAT version and which of them will be supported by upcoming HEAT version for Grizzly? Will HEAT for Grizzly be backward-compatible with older OpenStack releases? We are mostly interested in Essex and Folsom.

Thanks, Dmitry.