Changes between Version 2 and Version 3 of QCG_libraries_and_cross-cluster_communication

Show
Ignore:
Timestamp:
05/12/11 17:55:13 (13 years ago)
Author:
bartek
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • QCG_libraries_and_cross-cluster_communication

    v2 v3  
    1313The Port Range technique is a simple approach that makes the deployment of parallel environments firewall friendly. Most of the existing parallel environments use random ports by default to listen for incoming TCP/IP traffic. This makes cross-domain application execution almost impossible as most of system administrators often forbid to open all inbound ports to the Internet due to security reasons. By forcing the parallel environments to use only predefined, unprivileged range of ports, it is much easier for administrators to configure the firewall in a way to allow incoming MPI and !ProActive traffic without exposing critical system services to the Internet. Basing on the first presented figure, each of the site administrators has to choose a range of ports to be used (e.g. 5000-5100) for the parallel communication and configure the firewall appropriately. One should note that the port range technique solves the problem of the cross-cluster connectivity for computing clusters where all worker nodes have public IP addresses.  
    1414 
     15[[Image(QCG-PortRange.png, center, width=360px)]] 
     16 
    1517== Proxy technique == 
    1618In the second category of the clusters, where worker nodes have IP private addresses, the Port Range technique is not sufficient as all the worker nodes are not addressable from the outside networks. Therefore, in addition to the Port Range technique helping to separate incoming and outgoing traffics we adopted a new proxy technique. In our approach, additional SOCKS proxy services have to be deployed on front-end machines to route incoming traffic to the MPI and !ProActive processes running inside clusters on local worker nodes. The new Proxy based technique is briefly presented 
    1719on the second figure. 
     20 
     21[[Image(QCG-ProxySOCKS.png, center, width=460px)]]