liuxunorg opened a new pull request #3383: [ZEPPELIN-4104] Zeppelin Interpreter 
On Docker
URL: https://github.com/apache/zeppelin/pull/3383
 
 
   ### What is this PR for?
   Zeppelin service runs on local server. zeppelin is able to run the 
interpreter in the docker container, Isolating the operating environment of the 
interpreter through the docker container. Zeppelin can be easily used without 
having to install python, spark, etc. on the local node.
   
   #### Key benefits are
   1. Interpreter environment isolating
   2. Not need to install `python lib`, `spark binary package`, etc. 
environment on the local node
   3. Docker does not need to pre-install zeppelin binary package, 
Automatically upload local zeppelin interpreter lib files to the container
   4. Automatically upload local configuration files (such as `spark-conf`, 
`hadoop-conf-dir`, `keytab file`, ...) to the container, so that the running 
environment in the container is exactly the same as the local.
   5. Zeppelin server runs locally, making it easier to manage and maintain
   6. Support zeppelin all interpreter
   7. Support spark interpreter, `local[*]`, `cluster-client`, `cluster-yarn` 
mode.
   
   ### What type of PR is it?
   [Feature]
   
   
   ### What is the Jira issue?
   * https://issues.apache.org/jira/browse/ZEPPELIN-4104
   
   ### How should this be tested?
   * CI Pass
   
   ### Screenshots
   
   ### Sample1 : Spark(yarn-cluster mode) interpreter run docker
   
![sparkOnDocker1](https://user-images.githubusercontent.com/3677382/59410510-9a799100-8deb-11e9-9cb2-658ff3d4f552.gif)
   
   
   ### Sample2 : Spark(yarn-cluster mode) interpreter run docker
   
![sparkOnDocker2](https://user-images.githubusercontent.com/3677382/59410520-9ea5ae80-8deb-11e9-83ff-330cde39b15e.gif)
   
   
   
   ### Sample3 : Shell interpreter run docker
   
![shellOnDocker-800](https://user-images.githubusercontent.com/3677382/59410410-58e8e600-8deb-11e9-8948-531c2a8bea61.gif)
   
   
   
   ### Questions:
   * Does the licenses files need update? NO
   * Is there breaking changes for older versions? No
   * Does this needs documentation? YES
   

----------------------------------------------------------------
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:
us...@infra.apache.org


With regards,
Apache Git Services

Reply via email to