Github user Leemoonsoo commented on the issue:

    https://github.com/apache/zeppelin/pull/2986
  
    Thanks @zjffdu for the improvement. 
    
    Overall looks good to me. I'd like to see CI goes green before merge while 
it change code a lot.
    
    One question. Let's say in the future, zeppelin have capability to run 
interpreter as a container in the remote machine for scalability. For example, 
run interpreter in in k8s cluster or docker host in remote machine. Initiating 
communication between ZeppelinServer and interpreter will require firewall 
setup, port export/mapping on container service.
    
    What would be the simplest connectivity model in this case?
    
    I guess initiating one connection from Interpreter -> ZeppelinServer is 
simplest way? Because of interpreter running in container on remote host 
doesn't need to allow incoming connection (no firewall, container port 
mapping). Only single known port of ZeppelinServer need to accept the 
connection from all interpreters running remotely. Will there be other 
connectivity model keep network configuration simple?
    
    With the consideration with connectivity model that minimize user's network 
configuration, what would be the future direction of bidirectional rpc between 
ZeppelinServer and Interpreter?


---

Reply via email to