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

Doug Davis dug at us.ibm.com
Tue Apr 16 12:03:18 UTC 2013

  thanks for the write up. One question.. is there any reason the API
between the Model interpreter and the core Heat engine isn't a native API
instead of a REST API?  Is there a usecase for hosting the engine on a
separate host from the interpreters? Just wondering if it would keep the
management and deployment of the system easier if it didn't require another
HTTP layer.

STSM |  Standards Architect  |  IBM Software Group
(919) 254-6905  |  IBM 444-6905  |  dug at us.ibm.com
The more I'm around some people, the more I like my dog.

From:	Adrian Otto <adrian.otto at rackspace.com>
To:	OpenStack Development Mailing List
            <openstack-dev at lists.openstack.org>,
Date:	04/16/2013 05:06 AM
Subject:	[openstack-dev] [Heat] Future Vision for Heat


I attended the various sessions at the Design Summit today in Portland, and
assembled as many of the ideas for future planning as I could.  For the
benefit of those who are not attending, or who were not in these sessions,
I created this Wiki page to express what I think is an early consensus on
where we could take things. Let's tweak this if it's not a good direction.


Keith will be doing an Unconference session on the Workflow Service idea… I
believe on Wednesday afternoon.


OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130416/02e965ca/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130416/02e965ca/attachment.gif>

More information about the OpenStack-dev mailing list