You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@submarine.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2019/11/18 02:03:00 UTC
[jira] [Work logged] (SUBMARINE-292) Merge workbench-server into
submarine server
[ https://issues.apache.org/jira/browse/SUBMARINE-292?focusedWorklogId=345046&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-345046 ]
ASF GitHub Bot logged work on SUBMARINE-292:
--------------------------------------------
Author: ASF GitHub Bot
Created on: 18/Nov/19 02:02
Start Date: 18/Nov/19 02:02
Worklog Time Spent: 10m
Work Description: liuxunorg commented on pull request #93: SUBMARINE-292. Merge workbench server into submarine server
URL: https://github.com/apache/submarine/pull/93
### What is this PR for?
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.
### What type of PR is it?
Refactoring
### Todos
* [ ] - Task
### What is the Jira issue?
* https://issues.apache.org/jira/browse/SUBMARINE-292
### How should this be tested?
* [CI Pass](https://travis-ci.org/liuxunorg/submarine/builds/613280558)
### Screenshots (if appropriate)
```
|____bin
| |____common.sh
| |____submarine-daemon.sh
| |____submarine-env.sh
|____commons-runtime-0.3.0-SNAPSHOT.jar
|____conf
| |____log4j.properties
| |____log4j.properties.template
| |____submarine-env.sh.template
| |____submarine-site.xml
| |____submarine-site.xml.template
|____lib
| |____bcpg-jdk15on-1.61.jar
| |____bcpkix-jdk15on-1.61.jar
| |____hk2-utils-2.5.0-b42.jar
| |____interpreter
| | |____python
| | | |____python-interpreter-0.3.0-SNAPSHOT-shade.jar
| | |____spark
| | | |____scala-2.11
| | | | |____spark-scala-2.11-0.9.0-SNAPSHOT.jar
| | | |____spark-interpreter-0.3.0-SNAPSHOT-shade.jar
| |____j2objc-annotations-1.1.jar
| |____jackson-annotations-2.9.10.jar
| |____websocket-server-9.4.18.v20190429.jar
| |____workbench
| | |____workbench-web.war
|____LICENSE
|____licenses
| |____LICENSE-asm.txt
| |____LICENSE-hamcrest.txt
| |____LICENSE-slf4j.txt
| |____LICENSE-tony.txt
|____logs
| |____submarine.log
|____NOTICE
|____server
|____submarine-all-0.3.0-SNAPSHOT-hadoop-2.9.jar
|____submarine-client-0.3.0-SNAPSHOT.jar
|____submitter-yarn-0.3.0-SNAPSHOT.jar
|____tony-core-0.3.21.jar
```
### Questions:
* Does the licenses files need update? Yes/No
* Is there breaking changes for older versions? Yes/No
* Does this needs documentation? Yes/No
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 345046)
Remaining Estimate: 0h
Time Spent: 10m
> 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
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> 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