<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css">body {word-wrap: break-word; background-color:#ffffff;}</style>
</head>
<body>
<div style="font-family: sans-serif; font-size: 16px">Thanks Thomas. Good point.<br>
<br>
In that case, wwe could just consider the one within the blue area to have the label "Parser" and that should clarify matters. I'm happy to make tweaks to clarify it.<br>
<br>
Adrian</div>
<br>
<br>
-----Original message-----<br>
<blockquote style="; border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;">
<div style="font-family: sans-serif; font-size: 14px"><b>From: </b>Thomas Spatzier <thomas.spatzier@de.ibm.com><b><br>
To: </b>OpenStack Development Mailing List <openstack-dev@lists.openstack.org><b><br>
Sent: </b>Tue, Apr 16, 2013 14:22:07 GMT+00:00<b><br>
Subject: </b>Re: [openstack-dev] [Heat] Future Vision for Heat<br>
<br>
</div>
<div>
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
<div><font size="2"><span style="font-size:10pt;">
<div class="PlainText">Hi Adrian,<br>
<br>
thanks for taking writing this up to capture yesterday's discussions.<br>
I don't fully understand what the difference or overlap of the Model<br>
Interpreter inside the main blue box and the Model Interpreter in the green<br>
box is. My understanding was that a Model Interpreter would be something<br>
that translates an external format (such as CFN, TOSCA, whatever) to the<br>
core Heat DSL. And then there would be one component which looks at the<br>
common DSL model to derive the deployment plan (I think somebody said this<br>
is what the "parser" does today).<br>
I think having to partly re-implement the interpreter (in the sense of<br>
compiling a concrete deployment plan directly) for various external formats<br>
could be complicated.<br>
<br>
Adrian Otto <adrian.otto@rackspace.com> wrote on 16.04.2013 10:56:23:<br>
<br>
> From: Adrian Otto <adrian.otto@rackspace.com><br>
> To: OpenStack Development Mailing List<br>
<openstack-dev@lists.openstack.org>,<br>
> Date: 16.04.2013 10:57<br>
> Subject: [openstack-dev] [Heat] Future Vision for Heat<br>
><br>
> Heaters,<br>
><br>
> I attended the various sessions at the Design Summit today in<br>
> Portland, and assembled as many of the ideas for future planning as<br>
> I could. For the benefit of those who are not attending, or who<br>
> were not in these sessions, I created this Wiki page to express what<br>
> I think is an early consensus on where we could take things. Let's<br>
> tweak this if it's not a good direction.<br>
><br>
> <a href="https://wiki.openstack.org/wiki/Heat/Vision" target="_BLANK">https://wiki.openstack.org/wiki/Heat/Vision</a><br>
><br>
> Keith will be doing an Unconference session on the Workflow Service<br>
> idea… I believe on Wednesday afternoon.<br>
><br>
> Thanks,<br>
><br>
> Adrian<br>
> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> OpenStack-dev@lists.openstack.org<br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_BLANK">
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
OpenStack-dev@lists.openstack.org<br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_BLANK">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div>
</span></font></div>
</div>
</blockquote>
</body>
</html>