Re: OODT docker builds

t; > > > > From: Tom Barber > > Reply-To: "dev@oodt.apache.org" > > Date: Monday, October 15, 2018 at 9:44 AM > > To: Imesha Sudasingha , Chris Mattmann < > > mattm...@apache.org> > > Cc: dev > > Subject: Re: OODT docker buil

Re: OODT docker builds

> > > > > > From: Tom Barber > Reply-To: "dev@oodt.apache.org" > Date: Monday, October 15, 2018 at 9:44 AM > To: Imesha Sudasingha , Chris Mattmann < > mattm...@apache.org> > Cc: dev > Subject: Re: OODT docker builds > > > > Not at all

Re: OODT docker builds

tmann Cc: dev Subject: Re: OODT docker builds Not at all and if you want to run OODT on Kubernetes for example, that would be how you’d do it, that way you can upgrade, scale, restart and fail components without the entire stack falling over. In terms of disk space, don’t forget each imag

Re: OODT docker builds

, Chris Mattmann (mattm...@apache.org) wrote: Isn’t an image per component really heavyweight? *From:* Tom Barber *Date:* Monday, October 15, 2018 at 8:26 AM *To:* Imesha Sudasingha *Cc:* dev , Chris Mattmann *Subject:* Re: OODT docker builds Why aren’t we doing so?! :) Lack of cycles

Re: OODT docker builds

, Chris Mattmann *Subject: *Re: OODT docker builds Why aren’t we doing so?! :) Lack of cycles and young kids ;) I’ll take a stab at it and see where we get to outside of RADIX to get the stack in distinct containers and then we’ll look at integrating it into the main build then. Tom

Re: OODT docker builds

Isn’t an image per component really heavyweight? From: Tom Barber Date: Monday, October 15, 2018 at 8:26 AM To: Imesha Sudasingha Cc: dev , Chris Mattmann Subject: Re: OODT docker builds Why aren’t we doing so?! :) Lack of cycles and young kids ;) I’ll take a stab

Re: OODT docker builds

Why aren’t we doing so?! :) Lack of cycles and young kids ;) I’ll take a stab at it and see where we get to outside of RADIX to get the stack in distinct containers and then we’ll look at integrating it into the main build then. Tom On 15 October 2018 at 13:07:56, Imesha Sudasingha

Re: OODT docker builds

Yes. Agree with you. That is something I have been planning to ask you for long; why aren't we doing so. I like the idea of having a docker image per component and as you suggested we can create docker-compose or kubernetes setup for deployments. I like that direction ;-) As an starting point, we

Re: OODT docker builds

I was thinking about the outputs. Currently everything is 1 docker file which is fine for some deployments and not for others. In the RADIX build we should also build individual containers for each component. For the deployment we could also have a docker-compose file and a K8S Helm setup so that

Re: OODT docker builds

Hi Tom, I think this will be great since people are adopting docker more and more and even for a user once they have built a customized docker image, they can share it among the peers reducing the time spent for configuration by each individual. Also we have another option ;-) With distributed

OODT docker builds

I’m interested in the Dockerization of OODT but also conscious that most people use RADIX to build their stuff, which make’s overriding bits of a prebuilt image tricky. I’m wondering if its worth adding an optional Docker profile to RADIX to add a Docker build step to the backend of people’s