That will be nice, I am in Taipei (GMT+8)
Best Regards,
Wei
On Thu, Aug 27, 2020 at 12:20 AM Daniel Takabayashi <
daniel.takabayashi@gmail.com> wrote:
> Guys if you prefer we could organize a call to discuss these more complex
> points. Maybe could be more productive.
>
> Em dom., 23 de ago. de 2020 às 22:39, Daniel Takabayashi <
> daniel.takabayashi@gmail.com> escreveu:
>
> > Hi Lucas,
> >
> > I am a little confused about your e-mail, I couldn't get your point.
> > Could you please be a little more specific?
> >
> > Thanks,
> > Taka
> >
> > Em sáb., 15 de ago. de 2020 às 14:32, Lucas Cardoso Silva <
> > cardosolucas61.lcs@gmail.com> escreveu:
> >
> >> Hi guys,
> >>
> >> To continue our goal to evaluate the architecture, we have to present
> the
> >> proposal for all involved. I will take the opportunity to discuss some
> >> points about the implementation of the daemon and new CLI.
> >>
> >> Each engine has a Dockerfile for development where all dependencies
> >> related
> >> to the operating system will be declared. When the CLI is invoked for
> the
> >> engine, the image is created and the container starts, with the daemon
> as
> >> the main execution. All modifications to the engine are saved directly
> to
> >> the files (via bind mount). All commands, except the creational and
> >> versioning commands, run on the daemon (called by the CLI). Do you agree
> >> with this approach? It’s a little different from that represented in the
> >> image, which represents the use of a volume.
> >>
> >> Architectural proposal image:
> >>
> >>
> https://github.com/lucasbm88/incubator-apache-marvin/wiki/Development-Resources#v005---refactoring-architecture
> >>
> >> Image of the current architecture:
> >>
> >>
> https://docs.google.com/drawings/d/1UOR8Bk0fpLAOnotdeAn4Ww1GBbRxhdtM5mfoTJKQNVo/edit?usp=sharing
> >>
> >> Thanks a lot,
> >> Lucas
> >>
> >
>
|