<div dir="ltr">Hi Aleksey,<div><br></div><div>Since Fuel's FF is on 2nd of March, I don't think that full switch from</div><div>fuel-agent + nailgun volume manager to Bareon will happen.</div><div>Also Bareon will have separate from Fuel release cycle, so you will have</div><div>to land the feature first into Bareon and then to Fuel.</div><div><br></div><div>Could you please provide a bit more information on what features are</div><div>needed in the agent for 9.0 Fuel release?</div><div><br></div><div>Thanks,</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Dec 29, 2015 at 1:38 PM, Aleksey Zvyagintsev <span dir="ltr"><<a href="mailto:azvyagintsev@mirantis.com" target="_blank">azvyagintsev@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"><div><div><br></div>Guys, do you have any plans to achieve integration for fuel9\fuel-next ?(and final switching from fuel-agent to BareOn will be...?) <br></div>We are going to implement some new features for fuel - and the main question should we push it into fuel-agent or in newer BareOn? <div><br></div></div><div class="gmail_extra"><div><div class="h5"><br><div class="gmail_quote">On Mon, Dec 28, 2015 at 11:56 PM, Tomasz Napierala <span dir="ltr"><<a href="mailto:tnapierala@mirantis.com" target="_blank">tnapierala@mirantis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I agree with Evgeny: from work organization it would more optimal to have 2 repos. API and system facing programming are completely different domains, requiring different skill sets. In my opinion separation would lower the entry barriers.<br>
<br>
Regards,<br>
<div><div><br>
> On 17 Dec 2015, at 15:53, Evgeniy L <<a href="mailto:eli@mirantis.com" target="_blank">eli@mirantis.com</a>> wrote:<br>
><br>
> Hi Igor,<br>
><br>
> Bareon by itself doesn't have any REST interface, Bareon is basically fuel_agent,<br>
> which is framework + CLI wrapper to use it as an agent.<br>
> In order to store and edit required entities in the database we need some wrapper,<br>
> which adds this functionality. This simple wrapper will be implemented in Bareon-API.<br>
> User should be able to use Bareon without any additional API/Database if she/he<br>
> wants to do some basic stuff without need to store the configuration, which is not<br>
> Fuel use case.<br>
> If the question was specifically about Bareon-API in separate repo, there is no<br>
> reason to store it in a single repo, since we may have separate teams working<br>
> on those sub-projects and those solve a bit different problems, user facing api<br>
> vs low level tools.<br>
><br>
> Thanks,<br>
><br>
> On Thu, Dec 17, 2015 at 5:33 PM, Igor Kalnitsky <<a href="mailto:ikalnitsky@mirantis.com" target="_blank">ikalnitsky@mirantis.com</a>> wrote:<br>
> > create Bareon-API repository, and start production ready implementation<br>
><br>
> For what reason do we need a separate repo? I thought API will be a<br>
> part of bareon repo. Or bareon is just a provisioning agent, which<br>
> will be driven by bareon-api?<br>
><br>
> On Thu, Dec 17, 2015 at 12:29 PM, Evgeniy L <<a href="mailto:eli@mirantis.com" target="_blank">eli@mirantis.com</a>> wrote:<br>
> > Hi,<br>
> ><br>
> > Some time ago, we’ve started a discussion [0] about Fuel modularisation<br>
> > activity.<br>
> > Due to unexpected circumstances POC has been delayed.<br>
> ><br>
> > Regarding to partitioning/provisioning system, we have POC with a demo [1]<br>
> > (thanks to Sylwester), which shows how the integration of Fuel and Bareon<br>
> > [2] can<br>
> > be done.<br>
> ><br>
> > To summarise the implementation:<br>
> > * we have a simple implementation of Bareon-API [3], which stores<br>
> > partitioning<br>
> > related data and allows to edit it<br>
> > * for Nailgun new extension has been implemented [4], which uses Bareon-API<br>
> > to store partitioning information, so we will be able to easily switch<br>
> > between<br>
> > classic volume_manager implementation and Bareon-API extension<br>
> > * when provisioning gets started, extensions retrieves the data from<br>
> > Bareon-API<br>
> ><br>
> > Next steps:<br>
> > * create Bareon-API repository, and start production ready implementation<br>
> > * create a spec for Fuel project<br>
> > * create a spec for Bareon project<br>
> ><br>
> > If you have any questions don’t hesitate to ask them in this thread, also<br>
> > you can<br>
> > find us on #openstack-bareon channel.<br>
> ><br>
> > Thanks!<br>
> ><br>
> > [0]<br>
> > <a href="http://lists.openstack.org/pipermail/openstack-dev/2015-October/077025.html" rel="noreferrer" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/2015-October/077025.html</a><br>
> > [1] <a href="https://www.youtube.com/watch?v=GTJM8i7DL0w" rel="noreferrer" target="_blank">https://www.youtube.com/watch?v=GTJM8i7DL0w</a><br>
> > [2]<br>
> > <a href="http://lists.openstack.org/pipermail/openstack-dev/2015-December/082397.html" rel="noreferrer" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/2015-December/082397.html</a><br>
> > [3] <a href="https://github.com/Mirantis/bareon-api" rel="noreferrer" target="_blank">https://github.com/Mirantis/bareon-api</a><br>
> > [4] <a href="https://review.openstack.org/#/c/250864/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/250864/</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" 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>
><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>
> __________________________________________________________________________<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>
</div></div><span><font color="#888888">--<br>
Tomasz 'Zen' Napierala<br>
Product Engineering - Poland<br>
</font></span><div><div><br>
<br>
<br>
<br>
<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" 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><br clear="all"><br></div></div><span class="">-- <br><div><div dir="ltr"><div>---<br>Best regards,<br></div> Aleksey Zvyagintsev<br></div></div>
</span></div>
<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>