Changes between Version 20 and Version 21 of MTO
- Timestamp:
- 11/26/13 13:24:59 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
MTO
v20 v21 16 16 Before running MTO, its configuration files must be set to connect all clusters that will be used in a simulation. 17 17 18 MTO's configuration is stored in t wofiles:19 * global topology file (`$MUSCLE_HOME/etc/mto-topology.cfg`)20 {{{18 MTO's configuration is stored in three files: 19 * The global topology file (`$MUSCLE_HOME/etc/mto-topology.cfg`) that states what clusters will be connected by the MTO and on which port it will listen for connecting MTOs. The file should be the same for all participating MTOs. 20 {{{ 21 21 // Comment 22 22 # Comment … … 30 30 C localhost 31 31 D localhost 5300 32 }}}33 * local mto config file ( `$MUSCLE_HOME/etc/mto-config.cfg`)34 {{{32 }}} 33 * The local configuration file ( `$MUSCLE_HOME/etc/mto-config.cfg`) that states how the MTO can be contacted by MUSCLE 2 within the cluster. It also specifies a limited port range on a given cluster, which should be different for each participating cluster. The `internalAddress` may be set to an IP-address or hostname that is accessible from all nodes in the cluster. If the host has multiple internet interfaces, the wildcard address `*` may also be specified here. For example, the wildcard is useful for aliasing the hostnames `localhost` and the fully qualified domain name and for running the MTO in a virtual machine. 34 {{{ 35 35 # Name of this MTO as in mto-copology.cfg 36 36 myName = A … … 46 46 internalPort = 5001 47 47 internalAddress = private-address 48 }}} 49 50 The global topology file states what clusters will be connected by the MTO and on which port it will listen for connecting MTOs. The file should be the same for all participating MTOs. 51 52 The local configuration states how the MTO can be contacted by MUSCLE 2 within the cluster. It also specifies a limited port range on a given cluster, which should be different for each participating cluster. The `internalAddress` may be set to an IP-address or hostname that is accessible from all nodes in the cluster. If the host has multiple internet interfaces, the wildcard address `*` may also be specified here. For example, the wildcard is useful for aliasing the hostnames `localhost` and the fully qualified domain name and for running the MTO in a virtual machine. 53 54 To make the information about the local MTO available to MUSCLE 2, create the file `$MUSCLE_HOME/etc/muscle.defaults` matching the `mto-config.cfg` file, containing 55 56 {{{ 48 }}} 49 * The MUSCLE 2 configuration (`$MUSCLE_HOME/etc/muscle.defaults`) that makes the information about the local MTO available to MUSCLE 2. This should match the local `mto-config.cfg` file. 50 {{{ 57 51 # Make the MTO available to MUSCLE. 58 52 export MUSCLE_MTO=private-address:5001 59 53 export MUSCLE_PORT_MIN=5002 60 54 export MUSCLE_PORT_MAX=5099 61 }}} 62 63 Whenever `$MUSCLE_HOME/etc/muscle.profile` is sourced, these variables are set. If a wildcard address was set in `mto-config.cfg`, a definite address still needs to be set for the `MUSCLE_MTO` variable. 55 }}} 56 Whenever `$MUSCLE_HOME/etc/muscle.profile` is sourced, these environment variables are set. If a wildcard address was set in `mto-config.cfg`, a definite address still needs to be set for the `MUSCLE_MTO` variable. 64 57 = Starting MTO = 65 58 The MTO can be started in two modes:
