You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oodt.apache.org by Imesha Sudasingha <im...@apache.org> on 2019/08/20 15:01:24 UTC
Re: [GSOC] OODT docker build meeting summary
On today's meeting, it was discussed to;
1. Write a user guide and overall blog post describing how to build and use
the docker images
2. Yasith will also work on a kubernetes services file
3. The OPSUI container is unable to contact resource manager. This issue
requires to be investigates and fixed.
Thanks,
Imesha
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon>
Virus-free.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
On Fri, 26 Jul 2019 at 11:59, Jayawardana, Yasith <ya...@cs.odu.edu> wrote:
> Hi Tom and Imesha,
>
> A quick follow up question: as we are soon going to have the dockerfile PR
> finalized, I believe what’s next is the deployment configuration for it. Is
> integrating the distributed configuration management in the scope for this
> project, or should we focus on creating the docker-compose/kubernetes
> service configurations as standalone (using the predefined configurations)
> for now? IMHO, if we get the standalone configuration completed and
> documented, then implementing the distributed configuration would be an
> extension of it, right? Or is it a completely goal effort to achieve?
>
> Best Regards,
> Yasith Jayawardana
>
> ------------------------------------------------
> Yasith Jayawardana
> PhD Student | Old Dominion University
> phone: +1 757 698 8978
>
> On Jul 26, 2019, at 2:20 AM, Jayawardana, Yasith <yasith@cs.odu.edu
> <ma...@cs.odu.edu>> wrote:
>
> Hi All,
>
> This is a quick update regarding the current status of the OODT Docker
> Deployment project, and what’s next.
>
> During the last two meetings with @Imesha, we decided to use docker named
> volumes to mount the /data directory, which contains the catalog and
> archive content. The other directories will use the default structure
> enforced by the RADiX build. However, if the user needs, they can mount
> directories on top of the existing ones to specify new policies, etc. But
> this will be outside the default dockerfiles and handled at Docker Compose
> level. Also, I will be working on the comments made by @Imesha on the PR
> and fix things along the way. I am also working on a new Documentation that
> discusses about the docker build process, and add it to the Confluence wiki
> in the upcoming weeks. Also I’ll be working on quick start guide using the
> docker build process, which will not be as extensive as the documentation,
> but serves as a barebones guide to get a user up and running.
>
> Best Regards,
> Yasith Jayawardana
>
> ------------------------------------------------
> Yasith Jayawardana
> PhD Student | Old Dominion University
> phone: +1 757 698 8978
>
> On Jul 24, 2019, at 12:50 AM, Imesha Sudasingha <imesha@apache.org<mailto:
> imesha@apache.org><ma...@apache.org>> wrote:
>
> Hi Yasith,
>
> Thanks for the PRs. I have added some comments to them. Could you check?
>
> On Wed, 17 Jul 2019 at 13:31, Jayawardana, Yasith <yasith@cs.odu.edu
> <ma...@cs.odu.edu>> wrote:
>
> Hi all,
>
> I created two PRs based on the discussion with @Imesha and @Tom over the
> last weeks. The two PRs are as follows:
>
> *
> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Foodt%2Fpull%2F100&data=02%7C01%7Cyasith%40cs.odu.edu%7Cec02797c980d42b08a1108d7119160b2%7C48bf86e811a24b8a8cb368d8be2227f3%7C0%7C0%7C636997188429111104&sdata=KnFaAMuAoaqiYPJRObje%2FOT6aLrbmm4s14YWZ2nWt74%3D&reserved=0
> - This contains the Dockerfiles
> and modifications to existing files to accommodate docker image creation
> workflow in radix. I moved this workflow into a separate build profile
> named “docker” so that it won’t break existing workflows.
>
> *
> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Foodt%2Fpull%2F99&data=02%7C01%7Cyasith%40cs.odu.edu%7Cec02797c980d42b08a1108d7119160b2%7C48bf86e811a24b8a8cb368d8be2227f3%7C0%7C0%7C636997188429111104&sdata=CCfyTy9%2B6uD3NjAVztK8a8sA%2FgbQMr53ML4WKe%2BSLcQ%3D&reserved=0
> - Updated maven-assembly-plugin
> references in the radix archetype from 2.2-beta to 2.6. This was due to
> encountering errors when extracting the tar on certain distros (for my case
> it was alpine linux) After updating the plugin version the error was
> resolved, so thought it was worth a PR.
>
> As it was suggested, both PRs are aimed at “development” branch and not
> the “master” branch. Appreciate if you all could take a look and review it,
> and any suggestions are welcome!
>
> Best Regards,
> Yasith Jayawardana
>
> ------------------------------------------------
> Yasith Jayawardana
> PhD Student | Old Dominion University
> phone: +1 757 698 8978
>
> On Jul 4, 2019, at 2:20 PM, Imesha Sudasingha <imesha@apache.org<mailto:
> imesha@apache.org><ma...@apache.org><mailto:
> imesha@apache.org<ma...@apache.org>>>
> wrote:
>
> Hi Yasith,
>
> Thanks for the update! No worries about recent quietness. Let's focus on
> getting file manager container to interact with solr as the next step and
> look at what volumes require to be mounted. Once that is done, we can see
> how we can accommodate your code within OODT.
>
> Thanks,
> Imesha
>
>
>
>
>
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon>
Virus-free.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>