All new accounts created on Gitlab now require administrator approval. If you invite any collaborators, please let Flux staff know so they can approve the accounts.

Commit 11e67e7a authored by Robert Ricci's avatar Robert Ricci

Re-order package installation and configuring testbed software, in

case there are any dependancies.
parent 1ccf10eb
......@@ -53,21 +53,7 @@ ln -s /z/proj /proj
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.
##### Step 1 - Unpacking and running configure
At this point, you'll need to make a 'defs' file - see setup.txt for
instructions for doing so. You'll use the same defs file on boss and ops.
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
##### Step 2 - Installing packages
##### Step 1 - Installing packages
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
......@@ -94,6 +80,21 @@ 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'...
##### Step 2 - Unpacking and running configure
At this point, you'll need to make a 'defs' file - see setup.txt for
instructions for doing so. You'll use the same defs file on boss and ops.
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
##### Step 3 - Running the ops installation script
In the object tree you've configured (in my example above, ~/tbobj), there's an
......
......@@ -81,7 +81,13 @@ 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 - Create a defs file
##### Step 1 - Unpacking and running configure
This works the same as it did on ops:
cd ~/tbobj
~/testbed/configure --with-TBDEFS=/users/ricci/testbed/defs-ricci
##### Step 2 - Create a defs file
The defs file will describe some of your setup, such as the hostnames of your
boss and ops nodes, and email addresses that certain types of mail will be sent
......@@ -90,12 +96,6 @@ 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 - Unpacking and running configure
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
......
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