Commit 437d5438 authored by Leigh B. Stoller's avatar Leigh B. Stoller

Cleanup and fixes.

parent a5ec4b2b
......@@ -18,6 +18,10 @@ Make sure that you have the network correctly configured.
The following directories will need to exist on partitions that have enough
space to hold them:
/usr - Needs space for the ports tree and a system object tree.
At least 10GB. Be sure to build with plenty of
inodes (the ports tree itself uses about 200000, so
be safe and build with at least a million).
/usr/testbed/ - Needs space for testbed software and logs. A few gigs should be
plenty.
/users/ - Needs space for user home directories. Amount of space required
......@@ -46,9 +50,10 @@ a separate filesystem from anything that is exported read-write. So while
Make sure that, no matter how you decide to partition things up, you make
symlinks to the appropriate places. ie., if you make one big filesystem called
/z that has /users, /proj, and /groups in it, make sure you:
ln -s /z/users /users
ln -s /z/proj /proj
... etc.
ln -s /z/users /users
ln -s /z/proj /proj
... etc.
It's simplest if you don't create any users yet, and just log in a root for the
time being. Our software will create users later, once you get boss set up.
......@@ -58,27 +63,32 @@ time being. Our software will create users later, once you get boss set up.
To make sure that you're running with versions of software from the ports
collection that are known to work with our software, and to save you hours
of compile time, we provide pre-built binary packages of the ports required
by Emulab.
by Emulab. Download the packages tarball from:
Download the packages tarball from:
http://www.emulab.net/downloads/FreeBSD-4.10-20041102.tar.gz
http://www.emulab.net/downloads/FreeBSD-4.10-20041102.tar.gz
(You can use the FreeBSD 'fetch' command to download the file.)
Now, untar this someplace (you need about 70MB of space, so don't use /tmp).
Let's say you untarred it into /usr/tmp. You would then run:
env PKG_PATH=/usr/tmp/FreeBSD-4.10-20041102 pkg_add emulab-ops-1.4
env PKG_PATH=/usr/tmp/FreeBSD-4.10-20041102 pkg_add emulab-ops-1.4
Of course, if you untarred it somewhere else, put in the correct path.
At this point, you can now install other ports if you want to (ie. emacs or
vim). We have run into many, many problems with versions of the FreeBSD ports.
So, rather than using the /usr/ports tree that comes on the FreeBSD
installation media, we use one that we've tested against. You can grab our
'approved' copy of the ports tree from:
http://www.emulab.net/downloads/ports-20041102.tar.gz
Untar it, move it into place as /usr/ports, and install whatever ports you
want to make ops feel like 'home'...
Now you need to download a ports tree that corresponds to the above
packages. We have run into many, many problems with versions of the
FreeBSD ports. So, rather than using the /usr/ports tree that comes on the
FreeBSD installation media, we use one that we've tested against. You can
grab our 'approved' copy of the ports tree from:
http://www.emulab.net/downloads/ports-20041102.tar.gz
Untar it, move it into place as /usr/ports (rename the old directory
to ports.old), and install whatever ports you want to make ops feel
like 'home' (like emacs, jove, or whatever). NOTE: You must download and
copy the ports tree into place, even if you do not intend to install any
packages yourself.
##### Step 2 - Unpacking and running configure
......@@ -89,11 +99,11 @@ Unpack the testbed source, and run it's configure script. Use the --with-TBDEFS
option to configure to give it the path to your defs file.
For example, I have the testbed source in ~/testbed, my defs file in
/users/ricci/testbed/defs-ricci, and use the ~/tbobj directory to do my builds
in:
cd ~/tbobj
~/testbed/configure --with-TBDEFS=/users/ricci/testbed/defs-ricci
/users/ricci/testbed/defs-ricci, and use the ~/tbobj directory to do my
builds in:
cd ~/tbobj
~/testbed/configure --with-TBDEFS=/users/ricci/testbed/defs-ricci
##### Step 3 - Running the ops installation script
......
......@@ -68,22 +68,31 @@ Install FreeBSD on the machine you'll be using for your boss node, using the
standard FreeBSD installation process. When asked by the installer, it's best
to choose the 'Developer' distribution set - this gets you full sources. When
it asks if you want to install the ports collection, answer no.
You, will, however, have to make
sure that you create a partition large enough to hold /usr/testbed - in
addition to the testbed software, this is where many disk images will get
stored. The /var partition will need to be large enough to hold the database -
100MB extra for the database should be sufficient. Also, since we'll be
installing a lot of packages, you'll want to make sure that /usr is at least 2
GB.
You, will, however, have to make sure that you create a partition large
enough to hold /usr/testbed - in addition to the testbed software, this is
where many disk images will get stored. The /var partition will need to be
large enough to hold the database - 100MB extra for the database should be
sufficient. Also, since we'll be installing a lot of packages, you'll want
to make sure that /usr is at least 8GB and at least a million inodes.
If you want, you can go ahead and create an account for yourself on boss. For
now, just stick the home directory somewhere local, and move it to /users/ once
you've got it mounted from ops (the boss-install script will set this up). In
general, it's probably simpler to just use 'root' for now.
##### Step 1 - Unpacking source and creating a defs file
##### Step 1 - Installing packages
Again, almost the same as on ops. Download the same tarball, and follow
the same pkg_add procedure, except this time, you're going to install
the emulab-boss-1.8 package instead of emulab-ops.
Also grab a copy og our approved ports tree and install it, the same as
described in setup-ops.txt.
Unpack the source tarball somwhere with at least a few dozen megs free.
##### Step 2 - Unpacking source and creating a defs file
Unpack the source tarball somewhere with at least a few dozen MB free.
root's home directory is probably best for this.
Now, you'll need to create a 'defs file', which is used by the configure
......@@ -93,20 +102,12 @@ nodes, and email addresses that certain types of mail will be sent to.
Use the 'defs-example' file in the root of our source distribution as a
template. It contains comments explaining the important variables to set.
##### Step 2 - Configuring an object tree
##### Step 3 - Configuring an object tree
This works the same as it did on ops:
cd ~/tbobj
~/testbed/configure --with-TBDEFS=/users/ricci/testbed/defs-ricci
##### Step 3 - Installing packages
Again, almost the same as on ops. Download the same tarball, and follow
the same pkg_add procedure, excepth this time, you're going to install
the emulab-boss-1.8 package instead of emulab-ops .
You can download our approved ports tree and install ports at this point
if you wish.
cd ~/tbobj
~/testbed/configure --with-TBDEFS=/users/ricci/testbed/defs-ricci
##### Step 4 - Running the boss installation script
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment