Steve Baker sba...@redhat.com wrote on 18.07.2013 00:00:40:
From: Steve Baker sba...@redhat.com
To: openstack-dev@lists.openstack.org,
Date: 18.07.2013 00:08
Subject: Re: [openstack-dev] [Heat] Long-term, how do we make heat
image/flavor name agnostic?
On 07/18/2013 08:53 AM, Gabriel Hurley
On 18/07/13 08:14, Thomas Spatzier wrote:
Steve Baker sba...@redhat.com wrote on 18.07.2013 00:00:40:
On 07/18/2013 08:53 AM, Gabriel Hurley wrote:
I spent a bunch of time working with and understanding Heat in H2,
and I find myself with one overarching question which I wonder if
anyone's
Robert,
On Jul 18, 2013, at 3:08 AM, Robert Collins robe...@robertcollins.net
wrote:
On 18 July 2013 08:53, Gabriel Hurley gabriel.hur...@nebula.com wrote:
I spent a bunch of time working with and understanding Heat in H2, and I
find myself with one overarching question which I wonder if
Excerpts from Adrian Otto's message of 2013-07-18 06:31:10 -0700:
Robert,
On Jul 18, 2013, at 3:08 AM, Robert Collins robe...@robertcollins.net
wrote:
On 18 July 2013 08:53, Gabriel Hurley gabriel.hur...@nebula.com wrote:
I spent a bunch of time working with and understanding Heat in
Generally spot-on with what Adrian said, but I have one question from that
email:
Mappings is one of the high level concepts in CFN that I think can be
completely eliminated with auto-discovery.
What do you mean by this? What kind of autodiscovery, and where? I'm all for
eliminating mappings
I spent a bunch of time working with and understanding Heat in H2, and I find
myself with one overarching question which I wonder if anyone's thought about
or even answered already...
At present, the CloudFormation template format is the first-class means of
doing things in Heat.