[openstack-dev] Separating our Murano PL core in own package
smelikyan at mirantis.com
Mon Mar 24 07:11:07 UTC 2014
Timur, I don't know about plans to support different languages for Murano
Engine. I think Murano PL may be valuable as standalone library, so I think
we should extract Murano PL code to separate package, and if we will need
it as a library it will be easy to extract to.
On Mon, Mar 24, 2014 at 12:48 AM, Timur Nurlygayanov <
tnurlygayanov at mirantis.com> wrote:
> Hi Serg,
> This idea sounds good, I suggest to use name 'murano.engine.murano_pl'
> (not just common name like 'language' or 'dsl', but name, which will be
> based on 'MuranoPL')
> Do we plan to support the ability to define different languages for Murano
> Thank you!
> On Sun, Mar 23, 2014 at 1:05 PM, Serg Melikyan <smelikyan at mirantis.com>wrote:
>> There is a idea to separate core of Murano PL implementation from engine
>> specific code, like it was done in PoC. When this two things are separated
>> in different packages, we will be able to track and maintain our language
>> core as clean as possible from engine specific code. This will give to us
>> an ability to easily separate our language implementation to a library.
>> Questions is under what name we should place core of Murano PL?
>> 1) muranoapi.engine.language;
>> 2) muranoapi.engine.dsl;
>> 3) suggestions?
>> Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
>> http://mirantis.com | smelikyan at mirantis.com
>> +7 (495) 640-4904, 0261
>> +7 (903) 156-0836
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
> QA Engineer
> OpenStack Projects
> Mirantis Inc
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelikyan at mirantis.com
+7 (495) 640-4904, 0261
+7 (903) 156-0836
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev