Commit c9879a25 authored by Robert Ricci's avatar Robert Ricci

Change the instructions to use the packaged versions of ports

software.
parent 34c74524
......@@ -80,9 +80,25 @@ in:
cd ~/tbobj
~/testbed/configure --with-TBDEFS=/users/ricci/testbed/defs-ricci
##### Step 2 - Running the ops installation script
##### Step 2 - Installing packages
This part is brand-new, so please report any problems with it.
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.
Download the packages tarball from:
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
Of course, if you untarred it somewhere else, put in the correct path.
##### Step 3 - Running the ops installation script
In the object tree you've configured (in my example above, ~/tbobj), there's an
'install' subdirectory, with a script called 'ops-install'. Just run this
......@@ -102,7 +118,7 @@ sets up password-less 'sudo' for anyone in the 'wheel' group. If you don't want
these for security reasons, you can undo them after the installation script is
finished.
##### Step 3 - Installing from source
##### Step 4 - Installing from source
To install the actual testbed software, simply do a 'gmake ops-install' in your
object directory.
......@@ -116,7 +132,7 @@ addition, you'll need to build a custom kernel with the appropriate driver (you
may even need to get patches from Utah for some boards). You'll also need to
set up a few things (not yet automated), described in doc/adding_nodes.txt .
##### Step 4 - Setting up mailing lists
##### Step 5 - Setting up mailing lists
Optional. The ops-install script set up some mailing lists for the email
addresses you set up in the defs file, in /etc/mail/lists . If you want to run
......@@ -126,7 +142,7 @@ archive files, one per line. If you chose to use archive files, give a path
to the file you'd like sendmail to stick all correspondance in, and create
this file.
##### Step 5 - Other miscellaneous things to set up
##### Step 6 - Other miscellaneous things to set up
[Nothing at this time]
......
......@@ -108,28 +108,27 @@ This works the same as it did on ops:
cd ~/tbobj
~/testbed/configure --with-TBDEFS=/users/ricci/testbed/defs-ricci
##### Step 3 - Running the boss installation script
##### Step 3 - Installing packages
Again, this works the same as it did on ops, except that you run
install/boss-install in the object tree, instead of ops-install.
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 .
Part way through, this script will bail out and prompt you to install some
ports. This can take a long time (hours), and you want to be able to see what's
going on, right?
##### Step 4 - Running the boss installation script
So, just cd to /usr/ports/misc/emulab-boss/ and run (as root) a 'make install'.
When you're done, re-run the boss-install script.
Again, this works the same as it did on ops, except that you run
install/boss-install in the object tree, instead of ops-install.
Like the ops-install script, boss-install sets up paswordless sudo for anyone
in the wheel group.
##### Step 4 - Installing from source.
##### Step 5 - Installing from source.
In your object directory, do a 'gmake && gmake boss-install'. Then, as root, do
a 'gmake post-install'. The post-install target needs to run as root, so that
it can make certain scripts setuid, etc.
##### Step 5 - Setting up root ssh from boss to ops
##### Step 6 - Setting up root ssh from boss to ops
This step is now done as part of boss-install/ops-install. To confirm
this, make sure this works:
......@@ -140,7 +139,7 @@ If this *FAILS*, you will need to do this by hand, typing a password:
scp /root/.ssh/identity.pub ops:/root/.ssh/authorized_keys
##### Step 6 - Setting up named
##### Step 7 - Setting up named
The testbed software manipulates DNS zone files for two reasons. First, it
adds your nodes to them so that you don't have to. Second, it creates CNAMEs
......@@ -202,7 +201,7 @@ basically, you'll want to put the public addresses for boss, ops, etc. into
OURDOMAIN.db.head, and their private addresses into
OURDOMAIN.internal.db.head .
##### Step 7 - Other miscellaneous things to set up
##### Step 8 - Other miscellaneous things to set up
There are a few things we haven't been able to completely automate just yet,
though we hope to soon.
......@@ -240,11 +239,11 @@ find files as you're learning the system. This normally happends nightly, but
you can force it to happen now by running 'locate.updatedb' as root. This will
take several minutes. You can then find foo.conf by running 'locate foo.conf'.
##### Step 8 - Reboot boss
##### Step 9 - Reboot boss
Okay, go ahead and reboot boss now, and make sure it comes up okay.
##### Step 9 - Filling the database
##### Step 10 - Filling the database
See the file setup-db.txt in this directory for instructions on getting the
proper information about your site and nodes into the database.
......
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