Add tiplines table to inner DB state so we get the nifty console icon.

Entailed new instructions for manual setup as well as integration into
elabinelab framework.  First, the manual path:

setup.txt, setup-boss.txt, setup-ops.txt and new setup-fs.txt:
    Updated to reflect potential for separate fs node.  The org here
    is a little dicey and could be confusing with ops+fs vs. ops and fs.
    Has not been field tested yet.

*/GNUmakefile.in: new fs-install target.

configure, configure.in, defs-*:
    Somewhat unrelated, make min uid/gid to use be a defs setting.
    Also add config of fs-install.in script.

boss-install.in, ops-install.in and new fs-install.in:
    Handle distinct fs node.  If you have one, fs-install is run before
    ops-install.  All scripts rely on the defs file settings of FSNODE
    and USERNODE to determine if the fs node is seperate.

utils/checkquota.in:
    Just return "ok" if quotas are not used (i.e., if defs file FS_WITH_QUOTA
    string is null.

install/ports/emulab-fs:
    Meta ...

	'boss' -> 'boss+router'
	'ops'  -> 'ops+fs'
	'fs'      (new role)
	'router'  (new role)

These are in preparation for allowing configurations with split ops and fs
nodes (and sometime down the road, split boss and router nodes).

This checkin is just the DB state changes along with the scripts that look
at that state.  The Big One, which actually sets up separate nodes
automatically, is undergoing more testing but will be Coming Soon.

and other privs.

I fixed a couple of minor problems, but mostly this worked fine. Note that
I have tested this with the installed perl, *NOT* perl 5.8. I am just
making sure this stuff gets committed before too much more bitrot sets in.

ISUP or else they leave off at SHUTDOWN, which later confuses swapmod
(tbswap) which waits for them to reach ISUP, but of course they never
do. This is arguably a misfeature of os_setup, which should probably
not wait for nodes it didn't reboot, but I want to ponder that change.
Besides, doing this causes the nodes not to say SHUTDOWN in the web
interface.

Another change to add there (web interface) is to not say "possibly
down" for elabinelab nodes.

Firewalled experiments (see tbsetup/elabinelab.in for the other stuff).

* To support firewalled experiments, needed to add a new virt_firewalls
  table to split the existing firewalls table up, which included both
  virtual and physical stuff. There are the usual frontend changes and a
  few other things scattered around, including tmcd.c.

* The firewall code in tbswap got some beefing up to support adding and
  deleting nodes from the its special control net vlan. Note that I have
  not made any progress on containment of deleted nodes, just as we do not
  do anything now for teardown (unless its paniced, in which case the
  experiment cannot be modified anyway).

* ptopgen and assign_wrapper got some interesting modifications: Unlike
  regular swapmod, we cannot just tear down all the vlans since that would
  interrupt everything inside the inner elab. Instead, leave the vlans as
  is. The problem is that when assign runs, it can just as easily pick
  different interfaces on the same nodes, which would be a royal pain in
  the ass to deal with! So, ptopgen got a new option (-u) that assign
  wrapper uses to tell ptopgen that it should prune out unused interfaces
  from nodes that are already allocated to the experiment. This is, at
  best, as pathetically gross hack, but it makes sure that all the
  interfaces stay the same across swapmods.

* The unrelated revision of elabinelab has a bunch of new code for adding
  and deleting nodes from the inner elab. Mostly it deals with dhcpd (inner
  and outer, waiting for nodes to reboot, etc). It also deals with updating
  the vlans table in the DB, pruning out any nodes (ports) that are deleted
  but for which there are still interfaces in existing vlans. Said ports
  are them moved back to the default vlan with calls to snmpit. Also under
  another revision a a couple of weeks ago are the web interface changes to
  support the newnode MFS inside an inner Emulab.

* swapexp and endexp got some more checks for firewalled and paniced
  experiments, which were missing.

to get this change in cause it also includes some DHCPD conf changes and
Mike and I were messing each other up.

* The DHCPD change is that instead of using reserved.inner_elab_role
  as the flag to indicate a node should boot inside or outside, I
  added inner_elab_boot, which is a boolean that I set when its
  actually time to do this. This avoids two ElabInElab swapins at the
  same time from messing each other up! Basically avoids the obvious
  race.

* The rest of the changes are for swapmod itself, which are incomplete
  but should be harmless until the rest of the stuff is ready.

that we can administer the inner emulab more convienently.

  looking for /proj/$pid/exp/$eid/rc.mkelab. This file constantly
  changes, so its convenient to just copy it over (since it is the
  script that drives inner emulab creation).

* No longer copy over rc.inelab; let it get installed when the inner
  boss/ops is created, from the testbed source tree that gets copied
  over.

all of the nodes to boot up normally before I can turn them into an
inner elab (latter, after os_setup). That cannot happen with the
firewall rules in place. So, when an experiment is firewalled, reorder
the boot/wait list and wait for the firewall node first. Once that
hits ISUP, tell the elabinelab code (-f) option so that it can do what
it needs, which right now means an ssh over to the firewall node to
temporarily disable all the rules.

We still need to deal with teardown though.

boss node, which were coming from my home dir. Take them from the source
tree instead in /proj.

rules back on. The ipfw silently fails, but if I do it a second time,
it works fine. This is bogus of course ...

Do not die when turning firewall rules back on fails. This is a transient
error I do not understand yet.
When firewalled and paniced, skip clean shutdown of inner nodes since
they are going to be powered off anyway later, and besides, the control
network is shut off, so no way to talk to inner boss anyway.

firewall node and disable the rules during the inner elab setup, and
then turn them back on after the inner boss has rebooted. In the case
that an experiment is to be launched inside, launch the experiment
async and then turn rules back on. Technically, this should be proxied
through the firewall instead of directly, but this is okay for now.

As for experiment teardown, I am not doing anything yet since the
closed firewall lets ssh through, and thats all I need to teardown the
inner elab.

Also during teardown, if DHCPD cannot be killed on inner boss, then
skip rest of the steps and return okay so that the rest of experiment
teardown proceeds (if need be, inner nodes will be power cycled). Not
being be able to kill DHCPD can happen for lots of reasons (like,
experiment never setup in the first place).

  utility script to wait for them to reboot and reach PXEWAIT. This
  indicates inner emulab is raelly ready

* When an inner experiment is defined (elabinelab_eid in experiments
  table) fire that experiment off by doing an ssh into inner boss. I
  am currently doing this with -w (wait mode) but eventually will need
  to do it async for experiments in which the control net is turned
  off. Also, not actually swapping experiment in yet since multicast
  and frisbee are still broken inside.

* Add -k mode for cleaning up. The intent of this is to avoid power
  cycling all the nodes cause outer elab cannot reboot or ipod them.
  Goes like this:

  * Clear the inner_elab_role for experiment's nodes from the reserved
    table.

  * Clear def_boot_osid,next_boot_osid,temp_boot_osid for nodes. This
    is bogus cause os_select whines about doing this, but the point is
    to make sure that all nodes will go into PXEWAIT when they reboot.
    We could have them go into MFS, but thats bound to cause problems
    if inner elab has a lot of nodes (remember, cannot trust what is
    on disk). This needs more thought.

  * Regen and restart outer dhcpd. Nodes will become part of outer
    emulab on next boot cycle.

  * SSH into inner boss and kill inner DHCPD so that there will not be
    any DHCPD responses on inner control network.

  * SSH into inner boss and have it reboot all inner nodes.

  * Wait for node to reach PXEWAIT.

  The above needs more thought wrt firewalled experiments and isolated
  control network.

* Kill off some old MFS copy code since we now get those direct from
  website.

skip it.

* snmpit: When ElabInELabis true, use the routines in the new
  snmpit_remote.pm library for setting up and tearing down vlans for an
  experiment. At present, only these two operations are proxied out to
  the outer emulab.

* snmpit_remote.pm: A new little library that uses the XMLPRC server on
  the outer emulab to setup and destroy vlans for an inner experiment.
  This code is used from snmpit (see above).

* snmpit_lib.pm: A couple of minor changes for the server side of the
  proxy operation.

* snmpit.proxy.in: A new perl module that is invoked from the RPC
  server.  This proxy sets up and tears down vlans for an inner elab.
  The basic model is that the container experiment will have lots of
  vlans for various individual experiments running on the inner emulab.

* swapexp: A couple of minor elabinelab hacks.

* tbswap: For elabinelab experiments, reconfig/restart dhcpd when
  tearing down the experiment, and call out to new elabinelab script
  when setting up an elabinelab experiment. There is no provision for
  swapmod at this time.

* elabinelab: A new script to create the inner emulab. Does all kinds of
  gross DB stuff then more gross stuff on the inner ops and boss.