<div dir="ltr">-1 to make changes now<div>+1 to Alexandra</div><div><br></div><div>Let's finish fuel-client first. Also, it is about prioritization. We have many things to be resolved in 6.1 (e.g. package the rest of the stuff which not yet packaged into RPM/DEB; split repos openstack/fuel/linux, etc.), and fuel agent in particular has pretty low priority to me in 6.1.</div><div><br></div><div>In examples I have provided, which are essential for 6.1, we are experiencing lack of hands. Let's see if we can focus our work on those items and many other essential things, and come to this question later.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jan 26, 2015 at 10:29 PM, Aleksandra Fedorova <span dir="ltr"><<a href="mailto:afedorova@mirantis.com" target="_blank">afedorova@mirantis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">It seems that we have general agreement about the idea, but to make it happen we need much more detailed proposal.</p>
<p dir="ltr">Even with python-fuelclient it is not quite clear right now, which version of nailgun should be used to test it, and the opposite: which version of fuelclient we have to use in iso builds. We also don't handle it in the build system very well right now, as we use git hashes, and not fixed versions, or packages.</p>
<p dir="ltr">Maybe we should complete the python-fuelclient transformation first and see how it is going to work for us?</p><div class="HOEnZb"><div class="h5">
<div class="gmail_quote">On Jan 26, 2015 8:59 PM, "Roman Prykhodchenko" <<a href="mailto:me@romcheg.me" target="_blank">me@romcheg.me</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Vladimir,<br>
<br>
As a fuel-separatist I give this initiative a big +1 because of the following advantages I can see:<br>
<br>
- Git is designed for keeping smaller single-compoent repos, keeping everything to one repo is a discouraged pattern<br>
- Having a separate -core group that will only contain active core reviewers for fuel-agent project so getting core-reviews will be easier.<br>
- It makes possible to re-use some of the existing jobs in OpenStack CI<br>
- Making independent releases becomes possible<br>
<br>
AFAIK fuel-agent is positioned as an independent provisioning tool which will not be exclusively used by Fuel. There is a work in progress to integrate it with Ironic. Integrating it to any other provisioning system should also be possible then. From that perspective putting it into its own repo also brings the following advantages:<br>
<br>
- Connecting 3rd party CI will be possible<br>
- Getting involved for the new folks will be much easier<br>
<br>
<br>
- romcheg<br>
<br>
<br>
> 26 січ. 2015 о 17:42 Vladimir Kozhukalov <<a href="mailto:vkozhukalov@mirantis.com" target="_blank">vkozhukalov@mirantis.com</a>> написав(ла):<br>
><br>
> Fuelers,<br>
><br>
> As most of you might know we have a bunch of projects inside fuel-web repo which are not directly related to Fuel Web application. Some of them are tested together and it seemed we could end up with a set of incompatibility issues if we separated them and stopped tracking their versions on the git level (instead of release level).<br>
><br>
> Recent activities about separating Fuel Client from Nailgun (api) make me think we are mature enough to move all other not related project out of fuel-web repo and bring them together not earlier than on the stage of system/functional testing.<br>
><br>
> Next step would be moving out Fuel Agent project. The reason is that it is independent and potentially could be used even out of Fuel because its data parsing mechanism is implemented so as to be agnostic to the data format. Some people could be potentially interested in using it independently with their own data format. It is tested together with other Fuel components during system testing only.<br>
><br>
><br>
><br>
> Vladimir Kozhukalov<br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</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>
<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</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>
</div></div><br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</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"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr">Mike Scherbakov<br>#mihgen<br><br></div></div>
</div>