Re: [openstack-dev] Separating our Murano PL core in own package

2014-03-25 Thread Serg Melikyan
Joshua, I was talking about simple python sub-package inside existing repository, in existing package. I am suggesting to add muranoapi.engine.name sub-package, and nothing more. On Mon, Mar 24, 2014 at 10:29 PM, Ruslan Kamaldinov rkamaldi...@mirantis.com wrote: On Mon, Mar 24, 2014 at 10:08

Re: [openstack-dev] Separating our Murano PL core in own package

2014-03-25 Thread Dmitry Teselkin
Ruslan, What about murano-deployment repo? The most important part of it are PowerSheel scripts, Windows Image Builder, package manifests, and some other scripts that better to keep somewhere. Where do we plan to move them? On Mon, Mar 24, 2014 at 10:29 PM, Ruslan Kamaldinov

Re: [openstack-dev] Separating our Murano PL core in own package

2014-03-25 Thread Alexander Tivelkov
Hi, I suggest to move all needed Powershell scripts and etc. to the main repository 'murano' in the separate folder. +1 on this. The scripts will not go inside the PyPi package, they will be just grouped in a subfolder. Completely agree on the repo-reorganization topic in general. However And

Re: [openstack-dev] Separating our Murano PL core in own package

2014-03-24 Thread Serg Melikyan
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

Re: [openstack-dev] Separating our Murano PL core in own package

2014-03-24 Thread Timur Sufiev
+1 for muranoapi.engine.murano_pl, because 'dsl'/'language' terms are too broad. On Mon, Mar 24, 2014 at 12:48 AM, Timur Nurlygayanov tnurlygaya...@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

Re: [openstack-dev] Separating our Murano PL core in own package

2014-03-24 Thread Serg Melikyan
because 'dsl'/'language' terms are too broad. Too broad in general, but we choose name for sub-package, and in murano term 'language' mean Murano PL. +1 for language On Mon, Mar 24, 2014 at 11:26 AM, Timur Sufiev tsuf...@mirantis.com wrote: +1 for muranoapi.engine.murano_pl, because

Re: [openstack-dev] Separating our Murano PL core in own package

2014-03-24 Thread Oleg Gelbukh
What does PL stand for, anyway? -- Best regards, Oleg Gelbukh On Mon, Mar 24, 2014 at 11:39 AM, Serg Melikyan smelik...@mirantis.comwrote: because 'dsl'/'language' terms are too broad. Too broad in general, but we choose name for sub-package, and in murano term 'language' mean Murano PL.

Re: [openstack-dev] Separating our Murano PL core in own package

2014-03-24 Thread Serg Melikyan
Programming Language, AFAIK On Mon, Mar 24, 2014 at 11:46 AM, Oleg Gelbukh ogelb...@mirantis.comwrote: What does PL stand for, anyway? -- Best regards, Oleg Gelbukh On Mon, Mar 24, 2014 at 11:39 AM, Serg Melikyan smelik...@mirantis.comwrote: because 'dsl'/'language' terms are too

Re: [openstack-dev] Separating our Murano PL core in own package

2014-03-24 Thread Alexander Tivelkov
Hi Serg, Are you proposing to have a standalone git repository / stack forge project for that? Or just a separate package inside our primary murano repo? -- Regards, Alexander Tivelkov On Mon, Mar 24, 2014 at 12:00 PM, Serg Melikyan smelik...@mirantis.comwrote: Programming Language, AFAIK

Re: [openstack-dev] Separating our Murano PL core in own package

2014-03-24 Thread Serg Melikyan
Alexander, to have simple sub-package in muranoapi.engine/muranoapi On Mon, Mar 24, 2014 at 1:43 PM, Alexander Tivelkov ativel...@mirantis.comwrote: Hi Serg, Are you proposing to have a standalone git repository / stack forge project for that? Or just a separate package inside our primary

Re: [openstack-dev] Separating our Murano PL core in own package

2014-03-24 Thread Stan Lagun
I like dsl most because it is a. Short. This is especially good when you have that awesome 79-chars limitation b. It leaves a lot of room for changes. MuranoPL can change name. DSL - not :) On Mon, Mar 24, 2014 at 1:43 PM, Alexander Tivelkov ativel...@mirantis.comwrote: Hi Serg, Are you

Re: [openstack-dev] Separating our Murano PL core in own package

2014-03-24 Thread Joshua Harlow
Development Mailing List (not for usage questions) openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] Separating our Murano PL core in own package I like dsl most because it is a. Short. This is especially good when you have that awesome 79-chars

Re: [openstack-dev] Separating our Murano PL core in own package

2014-03-24 Thread Ruslan Kamaldinov
On Mon, Mar 24, 2014 at 10:08 PM, Joshua Harlow harlo...@yahoo-inc.com wrote: Seeing that the following repos already exist, maybe there is some need for cleanup? - https://github.com/stackforge/murano-agent - https://github.com/stackforge/murano-api -

[openstack-dev] Separating our Murano PL core in own package

2014-03-23 Thread Serg Melikyan
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

Re: [openstack-dev] Separating our Murano PL core in own package

2014-03-23 Thread Timur Nurlygayanov
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 Engine? Thank you! On Sun, Mar 23, 2014 at