Open Stack

Hi Adrian,

thanks for taking writing this up to capture yesterday's discussions.
I don't fully understand what the difference or overlap of the Model
Interpreter inside the main blue box and the Model Interpreter in the green
box is. My understanding was that a Model Interpreter would be something
that translates an external format (such as CFN, TOSCA, whatever) to the
core Heat DSL. And then there would be one component which looks at the
common DSL model to derive the deployment plan (I think somebody said this
is what the "parser" does today).
I think having to partly re-implement the interpreter (in the sense of
compiling a concrete deployment plan directly) for various external formats
could be complicated.

Adrian Otto <adrian.otto at rackspace.com> wrote on 16.04.2013 10:56:23:

> From: Adrian Otto <adrian.otto at rackspace.com>
> To: OpenStack Development Mailing List
<openstack-dev at lists.openstack.org>,
> Date: 16.04.2013 10:57
> Subject: [openstack-dev] [Heat] Future Vision for Heat
>
> Heaters,
>
> 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.
>
> https://wiki.openstack.org/wiki/Heat/Vision
>
> Keith will be doing an Unconference session on the Workflow Service
> idea… I believe on Wednesday afternoon.
>
> Thanks,
>
> Adrian
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>