[ 
https://issues.apache.org/jira/browse/OODT-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Imesha Sudasingha updated OODT-1004:
------------------------------------
    Skill Level: Committer (Medium) - This is for regular 
contributors/committers  (was: Don't Know (Unsure) - The default level)

> Make OODT deployment simple using docker and distributed configuration 
> management
> ---------------------------------------------------------------------------------
>
>                 Key: OODT-1004
>                 URL: https://issues.apache.org/jira/browse/OODT-1004
>             Project: OODT
>          Issue Type: Improvement
>          Components: file manager, resource manager, workflow manager
>            Reporter: Imesha Sudasingha
>            Priority: Major
>              Labels: GSoC2019, gsoc2019
>
> As a step to make OODT deployment and management simple, major OODT 
> components should be containerized including file manager, resource manager 
> and workflow manager.
>  * As a first step, each of those components should have it's own 
> [docker|https://www.docker.com/] image building execution in the maven build. 
> The [maven docker plugin|https://github.com/spotify/docker-maven-plugin] can 
> be used to achieve this.
>  * Then a suitable container management/orchestration tool should be used 
> create a OODT deployment. [Docker Compose|https://docs.docker.com/compose/] 
> can be used as the initial deployment tool.
>  * Then the [OODT Distributed Configuration 
> Management|https://cwiki.apache.org/confluence/display/OODT/OODT+Distributed+Configuration+Management]
>  implementation can be integrated to the deployment to handle dynamic 
> configuration management. This will provide the centralized ability to handle 
> configuration of running OODT components on the fly.
> Technologies including Docker, Docker Compose and Maven will be required to 
> carry out this project.
> As a later step, we can plan on upgrading the deployment to Kubernetes.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to