Changes between Version 12 and Version 13 of MTO

Timestamp:

04/05/13 11:07:50 (12 years ago)

Author:

jorisborgdorff

Comment:

--

MTO

@@ -1 +1 @@
 = Using MTO =
-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.
+The MUSCLE Transfer Overlay (MTO) is a daemon for forwarding traffic from MUSCLE 2. This service is often required when MUSCLE 2 is must communicate between several sites with firewall restrictions. On each site, a MTO should be placed on a node that is accessible within the cluster and from the outside world. Often, clusters have an interactive node that is suitable for this purpose.
 
-If MTO 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.
+If MTO is already installed, set up, and connected between all relevant sites, all that is needed from MUSCLE to use the MTO is to add the `--intercluster` flag to the command-line:
 {{{
 muscle2 -mc model.cxa.rb --intercluster sub1
 }}}
-The address of the simulation manager (suppose its `10.0.0.200:5002`) can then directly be used on another site:
+The address that the simulation manager prints (suppose its `10.0.0.200:5002`) can then directly be used on another site:
 {{{
 muscle2 -c model.cxa.rb --intercluster -M 10.0.0.200:5002 sub2
 }}}
 For convenience, the `--intercluster` flag also has the shorthand `-i`.
-
 = Configuration files =