defs-example 5.92 KB
Newer Older
1 2 3 4 5 6 7
#
# This is an example definitions file for configure.
#
# Use the --with-TBDEFS=filename to specify your own file.
# If you add a variable, be sure to go and update configure.in.
#

8 9
# The name of this installation
THISHOMEBASE=Example.Emulab.Net
10 11 12 13 14

#
# Various domain and host names
#

15 16 17
# Host name of our web server (or host:port)
WWWHOST=www.example.emulab.net

18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73
# Fully-quailified hostname of the boss node
BOSSNODE=boss.example.emulab.net

# Fully-quailified hostname of the ops (also called users) node
USERNODE=ops.example.emulab.net

# Fully-quailified hostname of the fileserver (will probably be the same
# as the ops node)
FSNODE=fs.example.emulab.net

# 
# Addresses to which email will be sent - These are expected to go to mailing
# lists. You can either host the lists on your ops node, send them off to
# some external server. If you chose to run them from the ops node, the
# ops-install script sets up empty lists for you.
#

# Main address for the 'operations staff' - Copies of error messages, etc. will
# get sent to this address, and in some cases users are directed to this
# address if they have questions and/or problems.
TBOPSEMAIL=testbed-ops@example.emulab.net

# Notification of new projects requests get sent to this address for approval.
# Should have a few admin-types on it.
TBAPPROVALEMAIL=testbed-approval@example.emulab.net

# Logs, such as experiment creation/deletion go to this address. Probably no
# more than one person needs to be on this one.
TBLOGSEMAIL=testbed-logs@example.emulab.net

# Various auditing message about account maintenance go here. Again, probably
# only needs one member.
TBAUDITEMAIL=testbed-audit@example.emulab.net

# Some web reports get sent to this one.
TBWWWEMAIL=testbed-www@example.emulab.net

# Our node state management daemon sends mail to this address. Someone should
# be on this list, and reporting persistent error messages to Utah would be a
# good idea.
TBSTATEDEMAIL=testbed-stated@example.emulab.net

# We have a test suite to test the front end. This email is for the results
# of the testsuite, but is not used yet.
TBTESTSUITEEMAIL=testbed-testsuite@example.emulab.net

# We dynamically create two email addresses for notifications to users - one
# for all testbed users, and one for all users whose projects have active
# experiments. These addresses are included in the above lists, with the
# intent that they can be used to archive all mail sent to them.
TBUSERSARCHIVE=testbed-users-archive@example.emulab.net
TBACTIVEARCHIVE=testbed-active-users-archive@example.emulab.net

#
# Real paths (no symlinks) to the directories that get exported from ops
#
74
FSDIR_GROUPS=/groups
75 76 77
FSDIR_PROJ=/q/proj
FSDIR_USERS=/users
FSDIR_SHARE=/share
78
FS_WITH_QUOTAS="/q /groups /users"
79

80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103
#
# SSL Certificate stuff. Used to customize config files in ssl directory.
# Note that OrganizationalUnit is set in the cnf file.
# CommonName is typically set to BOSSNODE and emailAddress to TBOPSEMAIL
#
SSLCERT_COUNTRY="US"
SSLCERT_STATE="Utah"
SSLCERT_LOCALITY="Salt Lake City"
SSLCERT_ORGNAME="Utah Network Testbed"

#
# Control network configuration stuff.
# Used primarily to generate initial named and dhcpd config files.
# See doc/setup-network.txt for definitions of the private, public and
# control segments.
#

#
# Boss and users node IP addresses on the control network.
# For boss this is an address on the private segment of the control net.
# For users this is an address on the public segment of the control net.
#
BOSSNODE_IP=155.98.32.70
USERNODE_IP=155.98.33.74
104
FSNODE_IP=$USERNODE_IP
105

106 107 108 109 110 111 112 113
#
# If your boss/ops nodes are multihomed (and typically, one of the
# networks is a public routable network, and the other is an internal
# unroutable network), then define the the external addresses here (and
# the internal addresses above).
#
EXTERNAL_BOSSNODE_IP=$BOSSNODE_IP
EXTERNAL_USERNODE_IP=$USERNODE_IP
114
EXTERNAL_FSNODE_IP=$USERNODE_IP
115

116
#
117 118 119 120 121 122 123
# Network definitions - see doc/setup-network.txt for a description of how
# we recommend laying out your network
#

#
# The overall control network range - this subnet should cover the
# CONTROL, PRIVATE, and PUBLIC networks below.
124 125 126 127
#
TESTBED_NETWORK=155.98.32.0
TESTBED_NETMASK=255.255.240.0

128 129 130 131 132 133 134
#
# As above, if you have internal and external networks, define the
# external network here, and the internal network above.
# 
EXTERNAL_TESTBED_NETWORK=$TESTBED_NETWORK
EXTERNAL_TESTBED_NETMASK=$TESTBED_NETMASK

135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162
#
# The node control network segment.
#
CONTROL_ROUTER_IP=155.98.36.1
CONTROL_NETWORK=155.98.36.0
CONTROL_NETMASK=255.255.252.0

#
# The private network segment.
#
PRIVATE_NETWORK=155.98.32.0
PRIVATE_ROUTER=155.98.32.1
PRIVATE_NETMASK=255.255.255.0

#
# The public network segment.
#
PUBLIC_NETWORK=155.98.33.0
PUBLIC_ROUTER=155.98.33.1
PUBLIC_NETMASK=255.255.255.0

#
# A range of addresses within the node control network segment
# to use for new nodes being added to the testbed.
# You need at least one.
#
DHCPD_DYNRANGE="155.98.36.200 155.98.36.249"

163 164 165 166 167 168
#
# If you have forwarders for your named, specify them here for named.conf
# generation in the named directory.
#
NAMED_FORWARDERS="1.1.1.1 1.1.2.1"

169 170 171 172 173 174 175 176 177 178 179 180 181
#
# Windows support. Turn this on if you think you might want to use windows
# XP images on your experimental nodes. Note though, that Utah cannot
# provide those images to you (because of obvious licensing issues), so it
# will be up to you to generate an XP image yourself and install the
# Emulab client side that enables XP to work inside your testbed. Turning
# Windows support will install and enable Samba on your ops node, so there 
# are firewall issues to be aware of (you want to block the appropriate ports
# so that your ops samba server can be accessed from *only* your control
# subnet!).
#
WINSUPPORT=0

182 183 184 185 186 187
#
# You shouldn't have to change anything below this point
#

TBADMINGROUP=tbadmin
TBDBNAME=tbdb
188
IPBASE=10
189 190 191
DELAYCAPACITY=2
SFSSUPPORT=0
DISABLE_NSE=1
192 193
FRISEBEEMCASTADDR="234.5.6"
FRISEBEEMCASTPORT=3564
194 195 196 197

# Sometimes the main page is down in a directory on WWWHOST
# No trailing '/'!
#WWW=www.example.emulab.net/emulab-www
198