<div dir="ltr">Mike, <div><br></div><div>Yes, probably the best place to describe further plans is README file. I'll create a patch. </div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div>Vladimir Kozhukalov</div></div></div>
<br><div class="gmail_quote">On Tue, Dec 1, 2015 at 8:30 PM, Mike Scherbakov <span dir="ltr"><<a href="mailto:mscherbakov@mirantis.com" target="_blank">mscherbakov@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">Vladimir,<div>if you've been behind of this, could you please share further plans in separate email thread or (better) provide plans in README in the repo, so everyone can be aware of planned changes and can review them too? If you or someone else propose a change, please post a link here... </div><div><br></div><div>Thanks,</div></div><div class="HOEnZb"><div class="h5"><br><div class="gmail_quote"><div dir="ltr">On Tue, Dec 1, 2015 at 6:27 AM Vladimir Kozhukalov <<a href="mailto:vkozhukalov@mirantis.com" target="_blank">vkozhukalov@mirantis.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Thomas,<div><br></div><div>You are right about two independent modules in the repo. That is because the former intention was to get rid of fuel-mirror (and fuel-createmirror) and perestroika and leave only packetary there. Packetary is to be developed so it is able to build not only repositories but packages as well. So we'll be able to remove perestroika once it is ready. Two major capabilities of fuel-mirror are:</div><div>1) create mirror (and partial mirror) and packetary can be used for this instead</div><div>2) apply mirror to nailgun (which is rather a matter of python-fuelclient)</div><div>So fuel-mirror also should be removed in the future to avoid functionality duplication. </div><div><br></div><div>Those were the reasons not to put them separately. (C) "There can be only one".</div><div><br></div><div><br></div><div><br></div><div><br></div></div><div class="gmail_extra"></div><div class="gmail_extra"><br clear="all"><div><div><div>Vladimir Kozhukalov</div></div></div></div><div class="gmail_extra">
<br><div class="gmail_quote">On Tue, Dec 1, 2015 at 1:25 PM, Thomas Goirand <span dir="ltr"><<a href="mailto:zigo@debian.org" target="_blank">zigo@debian.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 12/01/2015 09:25 AM, Mike Scherbakov wrote:<br>
> 4. I don't quite understand how repo is organized. I see a lot of<br>
<span>> Python code regarding to fuel-mirror itself and packetary, which is<br>
> used as fuel-mirrors core and being written and maintained mostly by<br>
> Bulat [5]. There are seem to be bash scripts now related to<br>
> Perestroika, and. I don't quite get how these things relate each to<br>
> other, and if we expect core reviewers to be merging code into both<br>
> Perestroika and Packetary? Unless mission of repo, code gets clear,<br>
> I'd abstain from giving +1...<br>
<br>
</span>Also, why isn't packetary living in its own repository? It seems wrong<br>
to me to have 2 python modules living in the same source repo, unless<br>
they share the same egg-info. It feels weird to have to call setup.py<br>
install twice in the resulting Debian source package. That's not how<br>
things are done elsewhere, and I'd like to avoid special cases, just<br>
because it's fuel...<br>
<br>
Cheers,<br>
<br>
Thomas Goirand (zigo)<br>
<div><div><br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br></div>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div></div></div><span class="HOEnZb"><font color="#888888"><div dir="ltr">-- <br></div><div dir="ltr">Mike Scherbakov<br>#mihgen</div>
</font></span><br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>