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/11/15 07:32:00 UTC
[jira] [Created] (SUBMARINE-292) Merge workbench-server into
submarine server
Liu Xun created SUBMARINE-292:
---------------------------------
Summary: 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: Submarine Server, Submarine Workbench
Reporter: Liu Xun
Assignee: Liu Xun
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