Open Stack

On 16/04/13 09:05, Thomas Spatzier wrote:
> Hi Adrian,
>
> Adrian Otto <adrian.otto at rackspace.com> wrote on 16.04.2013 17:24:56:
>> From: Adrian Otto <adrian.otto at rackspace.com>
>> To: OpenStack Development Mailing List
> <openstack-dev at lists.openstack.org>,
>> Date: 16.04.2013 17:26
>> Subject: Re: [openstack-dev] [Heat] Future Vision for Heat
>>
>> Thanks Thomas. Good point.
>>
>> 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.
>
> Maybe we can also come up with a better term than "parser". Would be
> interested what the Heat core team thinks.

For historical reasons, "parser" is the name of the module that 
essentially runs the Heat orchestration engine. It's a terrible name 
that doesn't really reflect what it actually does, so I'm definitely in 
favour of changing it.

This diagram is also showing it in the wrong place, so we have some more 
work to do to figure out some better terminology and get everyone on the 
same page.

cheers,
Zane.

>
> Regards,
> Thomas
>
>>
>> Adrian
>>
>>
>> -----Original message-----
>> From: Thomas Spatzier <thomas.spatzier at de.ibm.com>
>> To: OpenStack Development Mailing List
> <openstack-dev at lists.openstack.org>
>> Sent: Tue, Apr 16, 2013 14:22:07 GMT+00:00
>> Subject: Re: [openstack-dev] [Heat] Future Vision for Heat
>
>> 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
>>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>