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
> An
Dmitry,
I suggest to move all needed Powershell scripts and etc. to the main
repository 'murano' in the separate folder.
On Tue, Mar 25, 2014 at 11:38 AM, Dmitry Teselkin wrote:
> Ruslan,
>
> What about murano-deployment repo? The most important part of it are
> PowerSheel scripts, Windows Imag
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 <
rkamaldi...@mirant
Joshua, I was talking about simple python sub-package inside existing
repository, in existing package. I am suggesting to add
muranoapi.engine. 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 PM
On Mon, Mar 24, 2014 at 10:08 PM, Joshua Harlow 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
> - https://github.com/stackforge/murano-common
> - https://
velopment Mailing List (not for usage questions)"
mailto: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
limitation
b
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
wrote:
> Hi Serg,
>
> Are you proposing to have a st
Alexander, to have simple sub-package in muranoapi.engine/muranoapi
On Mon, Mar 24, 2014 at 1:43 PM, Alexander Tivelkov
wrote:
> 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?
>
> --
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 wrote:
> Programming Language, AFAIK
>
>
> On Mon, Mar 24, 20
Programming Language, AFAIK
On Mon, Mar 24, 2014 at 11:46 AM, Oleg Gelbukh wrote:
> What does PL stand for, anyway?
>
> --
> Best regards,
> Oleg Gelbukh
>
>
> On Mon, Mar 24, 2014 at 11:39 AM, Serg Melikyan wrote:
>
>> >because 'dsl'/'language' terms are too broad.
>> Too broad in general, but
What does PL stand for, anyway?
--
Best regards,
Oleg Gelbukh
On Mon, Mar 24, 2014 at 11:39 AM, Serg Melikyan wrote:
> >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
>
>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 wrote:
> +1 for muranoapi.engine.murano_pl, because 'dsl'/'language' terms are t
+1 for muranoapi.engine.murano_pl, because 'dsl'/'language' terms are too broad.
On Mon, Mar 24, 2014 at 12:48 AM, Timur Nurlygayanov
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
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
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 1:
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
16 matches
Mail list logo
