<div dir="ltr"><div>Dmitry,<br><br></div>I suggest to move all needed Powershell scripts and etc. to the main repository 'murano' in the separate folder.<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Tue, Mar 25, 2014 at 11:38 AM, Dmitry Teselkin <span dir="ltr"><<a href="mailto:dteselkin@mirantis.com" target="_blank">dteselkin@mirantis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Ruslan,<div><br></div><div>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?</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote"><div class="">On Mon, Mar 24, 2014 at 10:29 PM, Ruslan Kamaldinov <span dir="ltr"><<a href="mailto:rkamaldinov@mirantis.com" target="_blank">rkamaldinov@mirantis.com</a>></span> wrote:<br>
</div><div><div class="h5"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>On Mon, Mar 24, 2014 at 10:08 PM, Joshua Harlow <<a href="mailto:harlowja@yahoo-inc.com" target="_blank">harlowja@yahoo-inc.com</a>> wrote:<br>
> Seeing that the following repos already exist, maybe there is some need for<br>
> cleanup?<br>
><br>
> - <a href="https://github.com/stackforge/murano-agent" target="_blank">https://github.com/stackforge/murano-agent</a><br>
> - <a href="https://github.com/stackforge/murano-api" target="_blank">https://github.com/stackforge/murano-api</a><br>
> - <a href="https://github.com/stackforge/murano-common" target="_blank">https://github.com/stackforge/murano-common</a><br>
> - <a href="https://github.com/stackforge/murano-conductor" target="_blank">https://github.com/stackforge/murano-conductor</a><br>
> - <a href="https://github.com/stackforge/murano-dashboard" target="_blank">https://github.com/stackforge/murano-dashboard</a><br>
> - <a href="https://github.com/stackforge/murano-deployment" target="_blank">https://github.com/stackforge/murano-deployment</a><br>
> - <a href="https://github.com/stackforge/murano-docs" target="_blank">https://github.com/stackforge/murano-docs</a><br>
> - <a href="https://github.com/stackforge/murano-metadataclient" target="_blank">https://github.com/stackforge/murano-metadataclient</a><br>
> - <a href="https://github.com/stackforge/murano-repository" target="_blank">https://github.com/stackforge/murano-repository</a><br>
> - <a href="https://github.com/stackforge/murano-tests" target="_blank">https://github.com/stackforge/murano-tests</a><br>
</div>> ...(did I miss others?)<br>
<div>><br>
> Can we maybe not have more git repositories and instead figure out a way to<br>
> have 1 repository (perhaps with submodules?) ;-)<br>
><br>
> It appears like murano is already exploding all over stackforge which makes<br>
> it hard to understand why yet another repo is needed. I understand why from<br>
> a code point of view, but it doesn't seem right from a code organization<br>
> point of view to continue adding repos. It seems like murano<br>
> (<a href="https://github.com/stackforge/murano" target="_blank">https://github.com/stackforge/murano</a>) should just have 1 repo, with<br>
</div>> sub-repos (tests, docs, api, agent...) for its own organizational usage<br>
<div>> instead of X repos that expose others to murano's internal organizational<br>
> details.<br>
><br>
> -Josh<br>
<br>
<br>
</div>Joshua,<br>
<br>
I agree that this huge number of repositories is confusing for newcomers. I've<br>
spent some time to understand mission of each of these repos. That's why we<br>
already did the cleanup :) [0]<br>
<br>
And I personally will do everything to prevent creation of new repo for<br>
Murano.<br>
<br>
Here is the list of repositories targeted for the next Murano release (Apr 17):<br>
* murano-api<br>
* murano-agent<br>
* python-muranoclient<br>
* murano-dashboard<br>
* murano-docs<br>
<br>
The rest of these repos will be deprecated right after the release. Also we<br>
will rename murano-api to just "murano". murano-api will include all the<br>
Murano services, functionaltests for Tempest, Devstack scripts, developer docs.<br>
I guess we already can update README files in deprecated repos to avoid further<br>
confusion.<br>
<br>
I wouldn't agree that there should be just one repo. Almost every OpenStack<br>
project has it's own repo for python client. All the user docs are kept in a<br>
separate repo. Guest agent code should live in it's own repository to keep<br>
number of dependencies as low as possible. I'd say there should be<br>
required/comfortable minimum of repositories per project.<br>
<br>
<br>
And one more nit correction:<br>
OpenStack has it's own git repository [1]. We shoul avoid referring to github<br>
since it's just a convinient mirror, while [1] is an official<br>
OpenStack repository.<br>
<br>
[0] <a href="https://blueprints.launchpad.net/murano/+spec/repository-reorganization" target="_blank">https://blueprints.launchpad.net/murano/+spec/repository-reorganization</a><br>
[1] <a href="http://git.openstack.org/cgit/" target="_blank">http://git.openstack.org/cgit/</a><br>
<br>
<br>
<br>
Thanks,<br>
Ruslan<br>
<div><div><br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div></div></div><span class="HOEnZb"><font color="#888888"><br><br clear="all"><div><br></div>-- <br><div dir="ltr"><div>Thanks,</div>Dmitry Teselkin<br>Deployment Engineer<br>
Mirantis<br>
<a href="http://www.mirantis.com/" target="_blank">http://www.mirantis.com</a></div>
</font></span></div>
<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br><div dir="ltr"><font color="#888888"><font color="#888888"><br></font></font><div style="font-family:arial;font-size:small">Timur,</div><div style="font-family:arial;font-size:small">
QA Engineer</div><div style="font-family:arial;font-size:small">OpenStack Projects</div><div style="font-family:arial;font-size:small">Mirantis Inc<br></div></div>
</div>