source: fedkit/testbeds.example @ 2edec46

axis_examplecompt_changesinfo-opsversion-3.01version-3.02
Last change on this file since 2edec46 was f64fa81, checked in by Ted Faber <faber@…>, 17 years ago

event stuff

  • Property mode set to 100644
File size: 2.6 KB
Line 
1# Each testbed's parameters follow the bracketed testbed label.  The parameters
2# are bound to testbeds in the experiment when the label in brackets in this
3# file matches the string following tb-set-node-testbed command in the script.
4# For example the nodes with tb-set-node-testbed $n "deter" will be allocated
5# to the first testbed below.
6
7[deter]
8# On DETER, when running on users, use localhost so that the remote execution
9# commands work
10OpsNode: localhost
11
12# Change this field in all the testbeds to be one you can access.  Ssh commands
13# to ops are issued as this user.
14User: faber
15
16# Make sure it starts with a dot.
17Domain: .isi.deterlab.net
18Project: emulab-ops
19ConnectorType: pc3000_tunnel
20ConnectorImage: FBSD61-TUNNEL2
21
22# These run on the slave testbeds.  They are passed to csh by emulab, hence the
23# >& redirections.  This file assumes DETER will be the master and these
24# haven't been run.
25SlaveNodeStartCmd: echo FEDDIR GWCONF >& /tmp/startup
26SlaveConnectorStartCmd: sudo -H /users/faber/fed-tun.pl -t .deter.emulab.net >& /tmp/bridge.log
27
28# Master testbed commands.  These are appropriate for DETER as master.
29MasterNodeStartCmd: sudo -H FEDDIR/make_hosts FEDDIR/hosts
30MasterConnectorStartCmd: sudo -H FEDDIR/fed-tun.pl -f GWCONF >& /tmp/bridge.log
31
32# These are passed through directly to the connector and client configurations,
33# with Domain (above) appended.
34FileServer: fs
35Boss: boss
36EventServer: event-server
37
38# This needs to be true on DETER
39TunnelCfg: true
40
41# End of DETER specifications
42[wail]
43OpsNode: users
44User: faber
45Domain: .schooner.wail.wisc.edu
46Project: Deter
47ConnectorType: pc
48ConnectorImage: FBSD61-TUNNEL2
49
50# These slave commands are appropriate for generic testbeds, which emulab and
51# WAIL are.  The -H on sudo is crucial when calling federate.sh
52SlaveNodeStartCmd: sudo -H /bin/sh FEDDIR/fed_bootstrap >& /tmp/federate
53SlaveConnectorStartCmd: sudo -H FEDDIR/fed-tun.pl -f GWCONF>& /tmp/bridge.log
54
55# These master commands are placeholders
56MasterNodeStartCmd: sudo -H /bin/sh FEDDIR/fed_bootstrap &> /tmp/mfederate
57MasterConnectorStartCmd: sudo -H /users/faber/fed-tun.pl >& /tmp/bridge.log
58FileServer: fs
59Boss: boss
60EventServer: event-server
61TunnelCfg: false
62
63[emulab]
64OpsNode: users
65User: faber
66Domain: .emulab.net
67Project: DETER
68ConnectorType: pc
69ConnectorImage: FBSD61-TUNNEL2
70SlaveNodeStartCmd: sudo -H /bin/sh FEDDIR/fed_bootstrap >& /tmp/federate
71SlaveConnectorStartCmd: sudo -H FEDDIR/fed-tun.pl -f GWCONF>& /tmp/bridge.log
72MasterNodeStartCmd: sudo -H /bin/sh FEDDIR/fed_bootstrap &> /tmp/mfederate
73MasterConnectorStartCmd: sudo -H /users/faber/fed-tun.pl >& /tmp/bridge.log
74FileServer: fs
75Boss: boss
76EventServer: event-server
77TunnelCfg: false
78
Note: See TracBrowser for help on using the repository browser.