Excerpts from Hugh Brock's message of 2014-01-31 04:53:11 -0800:
> > On Jan 31, 2014, at 1:30 AM, Clint Byrum wrote:
> >
> > Excerpts from Zane Bitter's message of 2014-01-30 19:30:40 -0800:
> >>> On 30/01/14 16:54, Clint Byrum wrote:
> >>> I'm pretty sure it is useful to model images in Heat.
>
Hi,
There is a stackforge project Mistral which is aimed to provide generic
workflow service. I believe Zane mentioned it in his previous e-mail.
Currently, this project is at a pilot stage. Mistral has working pilot with
all core components implemented and right now we are finalizing DSL syntax
f
> On Jan 31, 2014, at 1:30 AM, Clint Byrum wrote:
>
> Excerpts from Zane Bitter's message of 2014-01-30 19:30:40 -0800:
>>> On 30/01/14 16:54, Clint Byrum wrote:
>>> I'm pretty sure it is useful to model images in Heat.
>>>
>>> Consider this scenario:
>>>
>>>
>>> resources:
>>> build_done_ha
Excerpts from Zane Bitter's message of 2014-01-30 19:30:40 -0800:
> On 30/01/14 16:54, Clint Byrum wrote:
> > I'm pretty sure it is useful to model images in Heat.
> >
> > Consider this scenario:
> >
> >
> > resources:
> >build_done_handle:
> > type: AWS::CloudFormation::WaitConditionHandl
On 30/01/14 16:54, Clint Byrum wrote:
I'm pretty sure it is useful to model images in Heat.
Consider this scenario:
resources:
build_done_handle:
type: AWS::CloudFormation::WaitConditionHandle
build_done:
type: AWS::CloudFormation::WaitCondition
properties:
handle:
On Thu, Jan 30, 2014 at 1:54 PM, Clint Byrum wrote:
> Excerpts from Mark Washenberger's message of 2014-01-30 12:41:40 -0800:
> > On Wed, Jan 29, 2014 at 5:03 PM, Zane Bitter wrote:
> > > (I'm not touching the question of whether Heat should have a Glance
> Image
> > > resource at all, which I'm
Excerpts from Mark Washenberger's message of 2014-01-30 12:41:40 -0800:
> On Wed, Jan 29, 2014 at 5:03 PM, Zane Bitter wrote:
> > (I'm not touching the question of whether Heat should have a Glance Image
> > resource at all, which I'm deeply ambivalent about.)
> >
>
> Maybe I'm just missing the u
On Wed, Jan 29, 2014 at 5:03 PM, Zane Bitter wrote:
> On 29/01/14 19:40, Jay Pipes wrote:
>
>> On Wed, 2014-01-29 at 18:55 -0500, Zane Bitter wrote:
>>
>>> I've noticed a few code reviews for new Heat resource types -
>>> particularly Neutron resource types - where folks are struggling to find
>>
Zane
Thanks for putting this together. This will guide us as we develop some
resources in Heat.
As chmouel said it would be great if this can be converted to blog article.
thanks
prasadv
On Wed, Jan 29, 2014 at 11:09 PM, Chmouel Boudjnah wrote:
> Zane Bitter writes:
>
> > As I said, figuring t
Zane Bitter writes:
> As I said, figuring this all out is really hard to do, and the
> existing resources in Heat are by no means perfect (we even had a
> session at the Design Summit devoted to fixing some of them[1]). If
> anyone has a question about a specific model, feel free to ping me or
>
On Wed, 2014-01-29 at 20:03 -0500, Zane Bitter wrote:
> On 29/01/14 19:40, Jay Pipes wrote:
> > On Wed, 2014-01-29 at 18:55 -0500, Zane Bitter wrote:
> >> I've noticed a few code reviews for new Heat resource types -
> >> particularly Neutron resource types - where folks are struggling to find
> >>
On 29/01/14 19:40, Jay Pipes wrote:
On Wed, 2014-01-29 at 18:55 -0500, Zane Bitter wrote:
I've noticed a few code reviews for new Heat resource types -
particularly Neutron resource types - where folks are struggling to find
the appropriate way to model the underlying API in Heat. This is a
real
On Wed, 2014-01-29 at 18:55 -0500, Zane Bitter wrote:
> I've noticed a few code reviews for new Heat resource types -
> particularly Neutron resource types - where folks are struggling to find
> the appropriate way to model the underlying API in Heat. This is a
> really hard problem, and is ofte
I've noticed a few code reviews for new Heat resource types -
particularly Neutron resource types - where folks are struggling to find
the appropriate way to model the underlying API in Heat. This is a
really hard problem, and is often non-obvious even to Heat experts, so
here are a few tips th
14 matches
Mail list logo