Hey Evgeniy,
> if we drop containers, those will be just rpm/deb packages and
> dependencies between them
Despite the fact I'm a big fan of Docker and the ideas it brings to us
(build, ship & deploy fast), I'd prefer to go with RPM/DEB packages.
Simply because it would be easy to support and
Thanks Eugene. I'd recommend to start integration as early as possible...
On Tue, Oct 20, 2015 at 2:11 AM Evgeniy L wrote:
> Hi Mike,
>
> 1. our plan is to have working partitioning/provisioning in a couple of
> weeks,
> networking is more complicated and it's better to
Hi Mike,
1. our plan is to have working partitioning/provisioning in a couple of
weeks,
networking is more complicated and it's better to ask Vladimir/Ryan.
2, 3. here we have just some general ideas, we should have independent
releases on pypi,
each component should have responsible
Hey Evgeniy.
This is awesome news1 I believe that microservices is way to go.
Despite the fact that them bring a set of classical problems (e.g.
duplication of domain entities) we will win more than loose. :)
If there will be any specs or design meetings, please send me invite -
I'd gladly join
This is great start, Evgeny.
I have a few questions:
1. When do you expect to have POC to show?
2. Do you plan to put new services into separate repos?
3. How do you plan to package those - will you create RPM package for
each, as well as Docker container (as we have everything in
Hi,
We are starting Fuel modularization POC activity which is basically in one
sentence
can be explained as "Use Fuel without Fuel", it means that we want to
provide
for a user a way to use some good things from Fuel, without entire master
node and
other parts which user doesn't need.
Currently