Hi Aleksey,
Since Fuel's FF is on 2nd of March, I don't think that full switch from
fuel-agent + nailgun volume manager to Bareon will happen.
Also Bareon will have separate from Fuel release cycle, so you will have
to land the feature first into Bareon and then to Fuel.
Could you please provide
Guys, do you have any plans to achieve integration for fuel9\fuel-next
?(and final switching from fuel-agent to BareOn will be...?)
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?
On Mon, Dec 28, 2015 at 11:56 PM,
In general - fuel-bootstrap improvements (actually- fuel-agent manager and
utils)
So, looks like no option for 9.0 - we will work with fuel-agent, and then
with porting(re-writing) it to bareon.
On Tue, Dec 29, 2015 at 1:09 PM, Evgeniy L wrote:
> Hi Aleksey,
>
> Since Fuel's
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.
Regards,
> On 17 Dec 2015, at 15:53, Evgeniy L
+1 For Evgeniy,
Also guys, as you know - fuel-agent now uses for a lot of different things
: IBP\bootstrap\ironic\disk_managment at many other.
I hope you are not going to remove all this functionality with re-factoring
process.
On Thu, Dec 17, 2015 at 4:53 PM, Evgeniy L
Hi,
Some time ago, we’ve started a discussion [0] about Fuel modularisation
activity.
Due to unexpected circumstances POC has been delayed.
Regarding to partitioning/provisioning system, we have POC with a demo [1]
(thanks to Sylwester), which shows how the integration of Fuel and Bareon
[2] can
> create Bareon-API repository, and start production ready implementation
For what reason do we need a separate repo? I thought API will be a
part of bareon repo. Or bareon is just a provisioning agent, which
will be driven by bareon-api?
On Thu, Dec 17, 2015 at 12:29 PM, Evgeniy L
Hi Igor,
Bareon by itself doesn't have any REST interface, Bareon is basically
fuel_agent,
which is framework + CLI wrapper to use it as an agent.
In order to store and edit required entities in the database we need some
wrapper,
which adds this functionality. This simple wrapper will be