Commit f0a40367 authored by Leigh Stoller's avatar Leigh Stoller

Besides a few minor tweaks, remove the DHCPD section from setup-nodes,

since that is now done automatically. I do mention it, but in setup
where other little misc bits are mentioned (stuff that boss-install
does).
parent 11e67e7a
......@@ -12,9 +12,10 @@ with local nodes - they can be skipped in a widearea-only testbed.
In order to proceed, you should have the following working (from the boss and
ops setup documentation):
NFS mounts between boss and ops
Root ssh keys (so that root on boss can ssh to ops without a password)
The web interface (you don't need to be able to log in yet)
NFS mounts between boss and ops
Root ssh keys (so that root on boss can ssh to ops without a password)
The web interface (you don't need to be able to log in yet)
Run the 'firstuser' script on boss. This will get put in the utils subdirectory
of your object tree. (Note: configure will not set the executable bit on the
......@@ -88,7 +89,8 @@ Just as you need to go 'red dot' to use admin privileges on the web interface,
you must also explicitly enable them on the command line. To do this, prefix
the command you want to run with 'withadminprivs'. For example, I might invoke
unixgroups like this:
withadminprivs unixgroups -a ricci tbadmin wheel
withadminprivs unixgroups -a ricci tbadmin wheel
(Note: withadminprivs and many other admin-type commands live in
/usr/testbed/sbin - you'll want to put this and /usr/testbed/bin in your
......
......@@ -88,34 +88,13 @@ We'll start by bringing up the first node in the testbed, to make sure things
are working, and so that you can set some initial values. If we haven't already
given it to you, ask Utah for the 'newnode' MFS.
Setting up dhcpd -
We use dhcpd to assign addresses to nodes when they boot. We don't normally do
this in a dynamic way (the D in dhcp) - we hardwire MAC addresses to IP
addresses. However, at this point, we don't know those MAC and IP addresses, so
we have to set up DHCP to actually do some dynamic stuff. Copy
dhcpd.conf.template from the dhcpd/ directory of the source tree into
/usr/local/etc . Edit it to get your actual boss IP, domain, control network
subnet and mask, etc. into it. For things to function properly, boss will need
to be listed as the nameserver in this file. Now, see that line that says
'range ...'? Uncomment that line, and put in a range of IP addresses that is
in the control network, but is _not_ going to be used by nodes. Ideally, this
range should be large enough to fit all the nodes into it. If it's smaller,
remember this for later, when we get to bringing up the rest of the nodes. Make
the config file from the template with:
/usr/testbed/sbin/dhcpd.makeconf dhcpd.conf.template > dhcp.conf
... then (re) start dhcpd with:
/usr/local/etc/rc.d/2.dhcpd.sh restart
If you have more than one interface in boss, dhcpd might complain that it has
nothing to do on some of them. That's fine - just make sure there are no other
errors.
Okay, now we're ready to try to boot the first node. What's going to happen as
we bring nodes up is that they should boot into the 'newnode' MFS, which is a
stripped down version of FreeBSD that runs out of a memory filesystem. This MFS
reports in to boss, informing it of it's existence and key things such as it's
MAC addresses. Do the BIOS setup detailed above on this node, and fire it up.
By the time it's got a FreeBSD login prompt on the console, it should have
reported in. This will send mail to the local testbed-ops list.
What's going to happen as we bring nodes up is that they should boot into
the 'newnode' MFS, which is a stripped down version of FreeBSD that runs
out of a memory filesystem. This MFS reports in to boss, informing it of
it's existence and key things such as it's MAC addresses. Do the BIOS setup
detailed above on this node, and fire it up. By the time it's got a
FreeBSD login prompt on the console, it should have reported in. This will
send mail to the local testbed-ops list.
Now, let's take a look at the web page where nodes that have checked in, and
are awaiting creation as 'real' nodes, show up. Log into the web interface as
......@@ -172,9 +151,9 @@ very painful! If there are some nodes you simply can't bring up, because of bad
hardware, etc. write these down, and we'll fix things up later.
Important note: Remember the size of the dynamic range you picked for dhcp
above? Well, that will limit how many of these node you can bring up at a time.
If you run out of IP addresses, continue on with the nodes you have up, and
repeat these steps later with the remainder.
in the defs file? Well, that will limit how many of these node you can
bring up at a time. If you run out of IP addresses, continue on with the
nodes you have up, and repeat these steps later with the remainder.
Okay, got all the nodes up? Good. At this point, you can fix things up for any
you had to skip, using the 'Add to Node ID suffix' box. If, for example, you
......
......@@ -159,7 +159,7 @@ sure:
/etc/named/named.conf
If you have more than one class-C subnet for your testbed, you'll need a
copy of the reverse zone file for each one. You want to out boss, ops, and
copy of the reverse zone file for each one. You want to put boss, ops, and
any 'infrastructure' equipment (such as routers and switches) into the zone
files. These zone files do not need to include the nodes - the nodes will
be added to them automatically. Be sure to edit /etc/named/named.conf if
......@@ -214,7 +214,16 @@ to boss's domain name).
boss-install already generated a temporary no-passhrase certificate for you
and placed them in the locations specified above. However, we recommend
that you get a "real" certificate from Verisign (or one of the others).
that you get a "real" certificate from Verisign (or one of the
others).
DHCPD - boss-install generated a dhcpd.conf.template and installed it in
/usr/local/etc (the template is derived from information you provided in
defs file). It then generated an actual dhcpd.conf file and started up
dhcpd for you. Do not edit the dhcpd.conf file directly! If you need need to
make changes, change the template instead and then run:
/usr/testbed/sbin/dhcpd_makeconf -i -r
tftpboot - There are a few bootloaders, mini-kernels, and MFSes that are used
to boot, reload, etc. testbed machines, which live in /tftpboot . For the time
......
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