[SUBMARINE-292] Merge workbench-server into submarine server

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.3.0
• Component/s: Backend Server, Workbench
• Labels: pull-request-available
• Assignee: Liu Xun
• Reporter: Liu Xun
• Created: 15/Nov/19 07:31
• Updated: 16/Dec/19 07:43
• Resolved: 19/Nov/19 07:47

Description

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.

Issue Links

• links to: GitHub Pull Request #93