<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>
<div>IIRC the understanding is/was that the "native" heat primatives that make up the target for any Model Interpreter *should* be sufficient to support either approach.</div>
<br>
<br>
<br>
-------- Original message --------<br>
From: Adrian Otto <adrian.otto@rackspace.com> <br>
Date: 04/16/2013 10:22 AM (GMT-08:00) <br>
To: OpenStack Development Mailing List <openstack-dev@lists.openstack.org> <br>
Cc: OpenStack Development Mailing List <openstack-dev@lists.openstack.org> <br>
Subject: Re: [openstack-dev] [Heat] Future Vision for Heat <br>
<br>
<br>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Ziad,<br>
<br>
Yes, if an alternate API were added that uses an imperative modeling style, it may not translate cleanly to the native (declarative) Heat DSL.<br>
<br>
I suppose the imperative plan could be passed through the native API, or there may be a way to bypass the native API and stimulate the downstream parts of the system as needed. Clearly if there is a way for everything to go through the same API, that may be
cleaner. We have not considered this use case in enough depth yet to be certain.<br>
<br>
Adrian<br>
<br>
On Apr 16, 2013, at 6:49 AM, "Ziad Sawalha" <ziad@sawalha.com> wrote:<br>
<br>
> If I understood this correctly, the native HEAT API is going to be declarative (yay!) and would go through a model interpreter which would spit out an imperative plan for execution (script, workflow, whatever). That is all good.<br>
> <br>
> But if I have an API that is imperative, would I not need to bypass the model interpreter and go straight to an engine. Is my logic correct? And if so, how do we accommodated for that in this design?<br>
> <br>
> <br>
> On Apr 16, 2013, at 3:56 AM, Adrian Otto <adrian.otto@rackspace.com> wrote:<br>
> <br>
>> Heaters,<br>
>> <br>
>> 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.<br>
>> <br>
>> <a href="https://wiki.openstack.org/wiki/Heat/Vision">https://wiki.openstack.org/wiki/Heat/Vision</a><br>
>> <br>
>> Keith will be doing an Unconference session on the Workflow Service 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">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
> <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">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">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div>
</span></font>
</body>
</html>