On Tue, Jun 23, 2015 at 12:06:27PM +0100, Steven Hardy wrote:
> tripleo-heat-templates/controller/cinder_backends/enable_netapp.yaml
>
...
>
> OS::TripleO::EnableCinderBackends: [enable_netapp.yaml, enable_foo.yaml, ...]
Correction, I realised this should probably be more declarative, e.g not
th
On Mon, Jun 22, 2015 at 01:21:29PM -0400, Jay Dobies wrote:
>
>
> On 06/22/2015 12:19 PM, Steven Hardy wrote:
> >Hi all,
> >
> >Lately I've been giving some thought to how we might enable easier
> >composability, and in particular how we can make it easier for folks to
> >plug in deeply nested op
On 23/06/15 06:49, Thomas Spatzier wrote:
From: Jay Dobies
To: openstack-dev@lists.openstack.org
Date: 22/06/2015 19:22
Subject: Re: [openstack-dev] [heat][tripleo]Recursive validation for
easier composability
On 06/22/2015 12:19 PM, Steven Hardy wrote:
Hi all,
Lately I've been giving
> From: Jay Dobies
> To: openstack-dev@lists.openstack.org
> Date: 22/06/2015 19:22
> Subject: Re: [openstack-dev] [heat][tripleo]Recursive validation for
> easier composability
>
>
>
> On 06/22/2015 12:19 PM, Steven Hardy wrote:
> > Hi all,
> >
> > L
On 06/22/2015 12:19 PM, Steven Hardy wrote:
Hi all,
Lately I've been giving some thought to how we might enable easier
composability, and in particular how we can make it easier for folks to
plug in deeply nested optional extra logic, then pass data in via
parameter_defaults to that nested tem
Hi all,
Lately I've been giving some thought to how we might enable easier
composability, and in particular how we can make it easier for folks to
plug in deeply nested optional extra logic, then pass data in via
parameter_defaults to that nested template.
Here's an example of the use-case I'm de
