<div dir="ltr">Hi Igor,<div><br></div><div>Bareon by itself doesn't have any REST interface, Bareon is basically fuel_agent,</div><div>which is framework + CLI wrapper to use it as an agent.</div><div>In order to store and edit required entities in the database we need some wrapper,<br></div><div>which adds this functionality. This simple wrapper will be implemented in Bareon-API.</div><div>User should be able to use Bareon without any additional API/Database if she/he<br></div><div>wants to do some basic stuff without need to store the configuration, which is not</div><div>Fuel use case.</div><div>If the question was specifically about Bareon-API in separate repo, there is no</div><div>reason to store it in a single repo, since we may have separate teams working</div><div>on those sub-projects and those solve a bit different problems, user facing api</div><div>vs low level tools.</div><div><br></div><div>Thanks,</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Dec 17, 2015 at 5:33 PM, Igor Kalnitsky <span dir="ltr"><<a href="mailto:ikalnitsky@mirantis.com" target="_blank">ikalnitsky@mirantis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">> create Bareon-API repository, and start production ready implementation<br>
<br>
</span>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>
<div><div class="h5"><br>
On Thu, Dec 17, 2015 at 12:29 PM, Evgeniy L <<a href="mailto:eli@mirantis.com">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>
</div></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>
><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>
</blockquote></div><br></div>