[openstack-dev] [Heat] Future Vision for Heat

Thomas Spatzier thomas.spatzier at de.ibm.com
Mon Apr 22 20:52:32 UTC 2013

Hi all,

a technical question or suggestion on the current architecture chart at the
Heat Vision wiki page: having multiple "Model Interpreter" boxes as in the
current diagram looks a bit confusing to me. What about having exactly one
interpreter in the final version, and this one interprets the core model
(Heat DSL) - probably this is what I would see in what is called "Model
Processor" at the moment. I.e. something that looks at a Heat DSL
Blueprint, analyzes the topology and derives the right steps from it.
The Heat REST API box would not need a "Model Interpreter" then. The box in
the green component on the upper right corner is something I would call a
"Model Translator" which takes an alternative format (like TOSCA, or later
cfn) as input and translates it to the core format which is then passed to
the Heat API.



> From: Steven Hardy <shardy at redhat.com>
> To: OpenStack Development Mailing List
<openstack-dev at lists.openstack.org>,
> Date: 22.04.2013 16:39
> Subject: Re: [openstack-dev] [Heat] Future Vision for Heat
> On Mon, Apr 22, 2013 at 01:47:59PM +0000, Tripp, Travis S wrote:
> > Hi All,
> >
> > Was there discussion on what is the "short" term vs "long" term?
> More specifically, how much of this do you think we can count on for
> Firstly note, as in my disclaimer at the top of the "Vision" page, that
> wiki page generated by Adrian, while useful to focus discussion, does not
> represent a formal roadmap produced by the Heat core team.
> As such there are a number of items on that page which do not feature in
> our current list of priorities at all (in particular the event processor
> and task system bits)
> That said, we have some BP's related to items in that page, so these
> be used as the definitive reference of what we're aiming at delivering
> havana (I'm still in the process of targeting/approving these):
> https://blueprints.launchpad.net/heat
> https://blueprints.launchpad.net/heat/havana
> The main BPs related to Adrian's Vison page/diagram are:
> https://blueprints.launchpad.net/heat/+spec/open-api-dsl
> https://blueprints.launchpad.net/heat/+spec/tosca-support
> https://blueprints.launchpad.net/heat/+spec/watch-ceilometer
> It may be that we define some additional BPs (in particular related to
> AutoScaling API and Workflow-library discussions), if/when it becomes
> that there are contributors willing to work on defining and implementing
> them.
> So the short answer to your Havana question is "it depends" - we
> have a very small core team, and as such are unlikely to have resources
> sufficient to implement all the interesting ideas discussed at Summit (or
> on Adrians wiki page) - so how much we achieve over the next cycle is
> absolutely dependent on the level of additional contribution we get from
> those interested in and defining, implementing, and maintining these new
> features.
> HTH!
> Steve
> >
> > Thanks,
> > Travis
> >
> > -----Original Message-----
> > From: Adrian Otto [mailto:adrian.otto at rackspace.com]
> > Sent: Thursday, April 18, 2013 3:10 AM
> > To: OpenStack Development Mailing List
> > Subject: Re: [openstack-dev] [Heat] Future Vision for Heat
> >
> > I have further refined the Vision Wiki page in accordance with
> further feedback from the core team. This is a shorter term vision
> that more closely matches what we will evolve toward in the short therm.
> >
> > https://wiki.openstack.org/wiki/Heat/Vision
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

More information about the OpenStack-dev mailing list