BBN_Emulab: defs-bbn-emulab

File defs-bbn-emulab, 7.9 KB (added by czhang@bbn.com, 10 years ago)
Line 
1#
2# This is an example definitions file for configure.
3#
4# This version has a non-routable control network; i.e., nodes must be
5# accessed via the multi-homed, publically routable "users" node.
6# The control network looks like:
7#
8# Complete:            192.168.0/22
9# "public" segment:      192.168.3/24
10# "private" segment:     192.168.2/24
11# "node control segment: 192.168.0/23 (aka: 192.168.0/24, 192.168.1/24)
12#
13# This configuration requires a router/firewall between the segments
14# (addreses 192.168.{0,2,3}.1).
15#
16# Use the --with-TBDEFS=filename to specify your own file.
17# If you add a variable, be sure to go and update configure.in.
18#
19
20# Enable the protogeni support
21PROTOGENI_SUPPORT=1
22PROTOGENI_DOMAIN="bbnemulab"
23
24# The name of this installation
25THISHOMEBASE=Emulab.Bbn.Com
26
27#
28# Various domain and host names
29#
30
31# Host name of our web server (or host:port)
32WWWHOST=geni-emuhost.bbn.com
33
34# Fully-quailified hostname of the boss node
35BOSSNODE=geni-emuhost.bbn.com
36
37# Fully-quailified hostname of the ops (also called users) node
38USERNODE=geni-ofctr.bbn.com
39
40# Fully-quailified hostname of the fileserver (will probably be the same
41# as the ops node)
42FSNODE=geni-ofctr.bbn.com
43
44#
45# Minimum Unix uid and gid values for Emulab users.
46# Emulab will create the initial user with these values and all additional
47# users will have values greater than these.  It would be unwise to make
48# these less than 1000 to avoid conflicts with "standard" BSD and Linux
49# users.  These can also be tweaked to avoid pre-existing accounts on the
50# fileserver machine.
51#
52MIN_UNIX_UID=10000
53MIN_UNIX_GID=6000
54
55#
56# Addresses to which email will be sent - These are expected to go to mailing
57# lists. You can either host the lists on your ops node, send them off to
58# some external server. If you chose to run them from the ops node, the
59# ops-install script sets up empty lists for you.
60#
61
62TBOPSEMAIL=czhang@bbn.com
63TBAPPROVALEMAIL=czhang@bbn.com
64TBLOGSEMAIL=czhang@bbn.com
65TBAUDITEMAIL=czhang@bbn.com
66TBWWWEMAIL=czhang@bbn.com
67TBSTATEDEMAIL=czhang@bbn.com
68TBTESTSUITEEMAIL=czhang@bbn.com
69TBUSERSARCHIVE=czhang@bbn.com
70TBACTIVEARCHIVE=czhang@bbn.com
71
72#
73# Real paths (no symlinks) to the directories that get exported from ops
74#
75# FSDIR_SCRATCH is optional.  The intent is that it provides per-project
76# space that is not "guaranteed" (for the Utah Emulab that means we do
77# not back it up to tape).  If defined, you would either set no quotas,
78# or higher quotas than for FSDIR_PROJ, on this filesystem.  If you are
79# not providing guarantees and are not doing quotas, you might as well
80# just put all your space in /proj and leave FSDIR_SCRATCH= blank.
81#
82FSDIR_GROUPS=/groups
83FSDIR_PROJ=/proj
84FSDIR_USERS=/users
85FSDIR_SHARE=/share
86FSDIR_SCRATCH=
87
88#
89# Filesystems on which quotas should be enforced.
90# Note that if multiple of the FSDIR_* vars above are on the same filesystem
91# (e.g., /q/proj and /q/groups) then you should only specify the base of the
92# common filesystem on which they all reside here (e.g., /q).
93# Set to the empty string to turn off quota checking.
94#
95FS_WITH_QUOTAS=
96
97#
98# SSL Certificate stuff. Used to customize config files in ssl directory.
99# Note that OrganizationalUnit is set in the cnf file.
100# CommonName is typically set to BOSSNODE and emailAddress to TBOPSEMAIL
101#
102SSLCERT_COUNTRY="US"
103SSLCERT_STATE="MA"
104SSLCERT_LOCALITY="Cambridge"
105SSLCERT_ORGNAME="BBN GENI Emulab"
106
107#
108# Control network configuration stuff.
109# Used primarily to generate initial named and dhcpd config files.
110# See doc/setup-network.txt for definitions of the private, public and
111# control segments.
112#
113
114#
115# Boss and users node IP addresses on the control network.
116# For boss this is an address on the private segment of the control net.
117# For users this is an address on the public segment of the control net.
118#
119BOSSNODE_IP=192.168.56.3
120USERNODE_IP=192.168.56.4
121FSNODE_IP=$USERNODE_IP
122
123#
124# If your boss/ops nodes are multihomed (and typically, one of the
125# networks is a public routable network, and the other is an internal
126# unroutable network), then define the the external addresses here (and
127# the internal addresses above).
128#
129EXTERNAL_BOSSNODE_IP=128.89.80.195
130EXTERNAL_USERNODE_IP=128.89.80.196
131EXTERNAL_FSNODE_IP=$EXTERNAL_USERNODE_IP
132
133#
134# Network definitions - see doc/setup-network.txt for a description of how
135# we recommend laying out your network
136#
137
138#
139# The overall control network range - this subnet should cover the
140# CONTROL, PRIVATE, and PUBLIC networks below.
141#
142TESTBED_NETWORK=192.168.56.0
143TESTBED_NETMASK=255.255.255.0
144
145#
146# As above, if you have internal and external networks, define the
147# external network here, and the internal network above.
148#
149EXTERNAL_TESTBED_NETWORK=128.89.80.0
150EXTERNAL_TESTBED_NETMASK=255.255.254.0
151
152#
153# The node control network segment.
154#
155CONTROL_ROUTER_IP=
156CONTROL_NETWORK=192.168.56.0
157CONTROL_NETMASK=255.255.255.0
158
159#
160# The private network segment.
161#
162PRIVATE_NETWORK=192.168.56.0
163PRIVATE_ROUTER=
164PRIVATE_NETMASK=255.255.255.0
165
166#
167# The public network segment.
168#
169PUBLIC_NETWORK=192.168.56.0
170PUBLIC_ROUTER=
171PUBLIC_NETMASK=255.255.255.0
172
173
174#
175# A range of addresses within the node control network segment
176# to use for new nodes being added to the testbed.
177# You need at least one.
178#
179DHCPD_DYNRANGE="192.168.56.200 192.168.56.249"
180
181#
182# If you have forwarders for your named, specify them here for named.conf
183# generation in the named directory.
184#
185NAMED_FORWARDERS="128.33.0.20 128.33.1.20"
186
187#
188# Windows support. Turn this on if you think you might want to use windows
189# XP images on your experimental nodes. Note though, that Utah cannot
190# provide those images to you (because of obvious licensing issues), so it
191# will be up to you to generate an XP image yourself and install the
192# Emulab client side that enables XP to work inside your testbed. Turning
193# Windows support will install and enable Samba on your ops node, so there
194# are firewall issues to be aware of (you want to block the appropriate ports
195# so that your ops samba server can be accessed from *only* your control
196# subnet!).
197#
198WINSUPPORT=0
199
200#
201# Virtual node network configuration (if you don't want virtual nodes,
202# just leave this as is)
203#
204# Needs at least a /16 network.  For a /16 the layout of an IP is:
205#       X.Y.<pnode>.<vnode>
206# where <pnode> is the physical host node and <vnode> is the virtual
207# node on that host.  Both are between 1 and 254.  If you have more than
208# 254 physical nodes then the assignment code will increment Y, meaning
209# that you had better have larger than a /16 network.  If you are using
210# the default 172.16/12, then you can have up to 16 * 254 physical hosts.
211# If you want more than 254 vnodes per pnode, you are screwed.
212#
213VIRTNODE_NETWORK=172.16.0.0
214VIRTNODE_NETMASK=255.240.0.0
215# XXX compat
216JAILIPBASE=$VIRTNODE_NETWORK
217JAILIPMASK=$VIRTNODE_NETMASK
218
219#
220# Selective disable of a couple of features.
221#
222# DISABLE_NAMED_SETUP   If you are not running a name server on your boss.
223#                       This will prevent you from using the virtual node
224#                       names (e.g., node1.eid.pid.<your-domain>).
225#
226# DISABLE_EXPORTS_SETUP Prevent dynamic configuration of the exports file
227#                       on your "fs" node.  You will need to use this if
228#                       your fs node is not running FreeBSD or is otherwise
229#                       not under your control.  If you set this option, you
230#                       will need to ensure that ALL your Emulab filesystems
231#                       (e.g., /proj, /users) are exported to ALL your nodes.
232#                       This has obvious security implications and YOU REALLY
233#                       SHOULD NOT DO THIS.
234#
235DISABLE_NAMED_SETUP=1
236DISABLE_EXPORTS_SETUP=0
237
238#
239# Only supported on the Mother Ship (emulab.net) right now.
240#
241WIKISUPPORT=0
242BUGDBSUPPORT=0
243MAILMANSUPPORT=0
244CVSSUPPORT=0
245CHATSUPPORT=0
246NFSTRACESUPPORT=0
247ARCHIVESUPPORT=0
248OPSDBSUPPORT=0
249SFSSUPPORT=0
250PELABSUPPORT=0
251PLABSUPPORT=0
252PLAB_ROOTBALL="plabroot-18.tar.bz2"
253
254#
255# You shouldn't have to change anything below this point
256#
257
258TBADMINGROUP=tbadmin
259TBDBNAME=tbdb
260IPBASE=10
261DELAYCAPACITY=2
262DISABLE_NSE=1
263FRISEBEEMCASTADDR="234.5.6"
264FRISEBEEMCASTPORT=3564
265
266# Sometimes the main page is down in a directory on WWWHOST
267# No trailing '/'!
268#WWW=www.example.emulab.net/emulab-www