On 01/04/16 12:31, Steven Hardy wrote:
On Fri, Apr 01, 2016 at 04:15:30PM +0200, Thomas Herve wrote:
On Fri, Apr 1, 2016 at 3:21 AM, Zane Bitter wrote:
On 31/03/16 18:10, Zane Bitter wrote:
I'm in favour of some sort of variable-based implementation for a few
reasons.
On 05/04/16 06:43, Steven Hardy wrote:
On Fri, Apr 01, 2016 at 04:39:02PM +, Fox, Kevin M wrote:
Why is imperative programming always brought up when discussing
conditionals in the templates? We are not wanting anything imperative. The
heat engine still picks the final ordering
On Fri, Apr 01, 2016 at 04:39:02PM +, Fox, Kevin M wrote:
>Why is imperative programming always brought up when discussing
>conditionals in the templates? We are not wanting anything imperative. The
>heat engine still picks the final ordering of things. We just want to give
>it
> parameters:
> env:
>type: string
>default: prod
>
> is_prod:
> type: boolean
> default: {equals: {get_param, env}}
>
> From an interface standpoint this seems much cleaner and more intuitive than
> the other solutions discussed IMHO, but I suspect it's potentially harder
)
Subject: Re: [openstack-dev] 答复: [Heat] Re-evaluate conditions specification
On Fri, Apr 01, 2016 at 04:15:30PM +0200, Thomas Herve wrote:
> On Fri, Apr 1, 2016 at 3:21 AM, Zane Bitter <zbit...@redhat.com> wrote:
> > On 31/03/16 18:10, Zane Bitter wrote:
> >>
> >>
: [openstack-dev] 答复: [Heat] Re-evaluate conditions specification
On Thu, Mar 31, 2016 at 2:25 PM, Huangtianhua <huangtian...@huawei.com> wrote:
> The conditions function has been requested for a long time, and there have
> been several previous discussions, which all ended up
On Fri, Apr 01, 2016 at 04:15:30PM +0200, Thomas Herve wrote:
> On Fri, Apr 1, 2016 at 3:21 AM, Zane Bitter wrote:
> > On 31/03/16 18:10, Zane Bitter wrote:
> >>
> >>
> >> I'm in favour of some sort of variable-based implementation for a few
> >> reasons. One is that (5) seems
On 01/04/16 10:15, Thomas Herve wrote:
On Fri, Apr 1, 2016 at 3:21 AM, Zane Bitter wrote:
On 31/03/16 18:10, Zane Bitter wrote:
I'm in favour of some sort of variable-based implementation for a few
reasons. One is that (5) seems to come up fairly regularly in a complex
On Fri, Apr 1, 2016 at 3:21 AM, Zane Bitter wrote:
> On 31/03/16 18:10, Zane Bitter wrote:
>>
>>
>> I'm in favour of some sort of variable-based implementation for a few
>> reasons. One is that (5) seems to come up fairly regularly in a complex
>> deployment like TripleO.
On 31/03/16 18:10, Zane Bitter wrote:
I'm in favour of some sort of variable-based implementation for a few
reasons. One is that (5) seems to come up fairly regularly in a complex
deployment like TripleO. Another is that Fn::If feels awkward compared
to get_variable.
I actually have to revise
On 31/03/16 10:10, Thomas Herve wrote:
On Thu, Mar 31, 2016 at 2:25 PM, Huangtianhua wrote:
The conditions function has been requested for a long time, and there have been
several previous discussions, which all ended up in debating the
implementation, and no result.
+1. This sounds good. The lack of any conditionals at all has caused a lot of
pain.
Thanks,
Kevin
From: Huangtianhua
Sent: Thursday, March 31, 2016 5:25:29 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] 答复: [Heat] Re
On Thu, Mar 31, 2016 at 09:21:43AM -0400, Rabi Mishra wrote:
> If I understand the suggestion correctly, the only relation it has with
> conditions is,
> conditions are nothing but variables(boolean).
>
> conditions: {
> 'for_prod': {equals: [{get_param: env_type}, 'prod']}
> }
>
>
On Thu, Mar 31, 2016 at 2:25 PM, Huangtianhua wrote:
> The conditions function has been requested for a long time, and there have
> been several previous discussions, which all ended up in debating the
> implementation, and no result.
>
> The conditions function has been requested for a long time, and there have
> been several previous discussions, which all ended up in debating the
> implementation, and no result.
> https://review.openstack.org/#/c/84468/3/doc/source/template_guide/hot_spec.rst
>
The conditions function has been requested for a long time, and there have been
several previous discussions, which all ended up in debating the
implementation, and no result.
https://review.openstack.org/#/c/84468/3/doc/source/template_guide/hot_spec.rst
16 matches
Mail list logo