Changes between Version 3 and Version 4 of MTO

Timestamp:

04/03/13 17:51:59 (12 years ago)

Author:

jorisborgdorff

Comment:

--

MTO

@@ -1 +1 @@
 = Configuration files =
-The MUSCLE Transfer Overlay (MTO) configuration is stored in two files:
+
+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.
+
+MTO's configuration is stored in two files:
  * global topology file (`MUSCLE_HOME/etc/mto-topology.cfg`)
 {{{
@@ -31 +34 @@
 internalAddress = private-address
 }}}
+
+For MUSCLE 2 commands, the second file is of importance: it implies that it can only use a limited port range on a given cluster, and how it should contact the MTO. To make this information available to MUSCLE 2, create the file `MUSCLE_HOME/etc/muscle.defaults` matching the `mto-config.cfg` file, containing
+{{{
+export MUSCLE_MTO=private-address:5001
+export MUSCLE_PORT_MIN=5002
+export MUSCLE_PORT_MAX=5099
+}}}
+
+When MUSCLE_HOME/etc/muscle.profile is sourced, these variables are then also set.
 = starting MTO =
  * debug mode