You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@submarine.apache.org by "Liu Xun (Jira)" <ji...@apache.org> on 2019/12/16 07:44:00 UTC
[jira] [Updated] (SUBMARINE-292) Merge workbench-server into
submarine server
[ https://issues.apache.org/jira/browse/SUBMARINE-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Liu Xun updated SUBMARINE-292:
------------------------------
Parent Issue: SUBMARINE-224 (was: SUBMARINE-291)
> Merge workbench-server into submarine server
> --------------------------------------------
>
> Key: SUBMARINE-292
> URL: https://issues.apache.org/jira/browse/SUBMARINE-292
> Project: Apache Submarine
> Issue Type: Sub-task
> Components: Backend Server, Workbench
> Reporter: Liu Xun
> Assignee: Liu Xun
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.3.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Now submarine has 2 services, submarine server and workbench server. These two services have no conflicts.
> Originally divided into two services, it is for the development of sub-modules, easy to develop.
> But this way
> 1) Users need to maintain two service processes, which increases the cost of use and maintenance of users and administrators.
> 2) Because we need to be able to run the service on multiple resource scheduling systems(YARN/K8s/Docker), the two services create the complexity of the launcher module.
> So, now the service in the workbench server is migrated to the submarine server. But the code for the workbench server remains the same.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@submarine.apache.org
For additional commands, e-mail: dev-help@submarine.apache.org