Changes between Version 5 and Version 6 of MTO

Show
Ignore:
Timestamp:
04/03/13 18:05:58 (12 years ago)
Author:
jorisborgdorff
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MTO

    v5 v6  
     1= Using MTO = 
     2The MUSCLE Transfer Overlay (MTO) is a daemon for forwarding traffic from MUSCLE 2. This service is often required when MUSCLE 2 is run on several sites with firewall restrictions. On each site, a MTO should be placed on a node that is less strict in its firewall policies, but that can be accessed from other MTO nodes. Often, clusters have an interactive node that is suitable for this purpose. 
     3 
     4If it is already installed, set up, and connected between all needed sites, all that is needed is that the `--intercluster` flag is added to the command-line, the rest stays the same. 
     5{{{ 
     6muscle2 -mc model.cxa.rb --intercluster sub1 
     7}}} 
     8The address of the simulation manager (suppose its `10.0.0.200:5002`) can then directly be used on another site: 
     9{{{ 
     10muscle2 -c model.cxa.rb --intercluster -M 10.0.0.200:5002 sub2 
     11}}} 
     12For convenience, the `--intercluster` also has the shorthand `-i`. 
     13 
    114= Configuration files = 
    2  
    3 The MUSCLE Transfer Overlay (MTO) is a daemon for forwarding traffic from MUSCLE 2. This service is often required when MUSCLE 2 is run on several sites with firewall restrictions. On each site, a MTO should be placed on a node that is less strict in its firewall policies, but that can be accessed from other MTO nodes. Often, clusters have an interactive node that is suitable for this purpose. 
    415 
    516MTO's configuration is stored in two files: