Inverted check of return code from UpdateTable.

failure to allocate nodes; obviously the top mapped.

key so that existing delegations are not invalidated. In general this
is fine if the key has not been compromised. User has a choice, with
the check box.

idea).

New script and table to manage node pre reservations. Lets just look
at the script.

To create a reservation:

    myboss> wap prereserve -t pc850 testbed 2
    Node reservation request for 2 nodes has been created.

To see the reservation status for testbed

    myboss> wap prereserve -i testbed
    Project         Cnt (Cur)  Creator    When               Pri Types
    -------------------------------------------------------------
    testbed         1 (1)      stoller    2011-08-12 12:39:07 0   pc850

    which says 1 node is pending and 1 node has already been
    pre-reserved. 

To clear the above reservation request (and optionally, clean
reserved_pid from the nodes table).

    myboss> wap prereserve -c -r testbed

    The -r is optional, otherwise just the reservation request is
    cleared, and nodes continue to be pre-reserved to the project.

To see a list of all reservation requests:

    myboss> wap prereserve -l


So, when a node is released in nfree, we look at the reservation
status for the node and any pending reservation requests.

1. If the node has a reserved_pid and that request is still pending
   (still in the table), nothing is changed.

2. If the node has a reserved_pid, but the request has been cleared
   from the pending table, then clear reserved_pid.

3. If reserved_pid is null, and there are pending requests, then pick
   the highest priority, most recent dated, request, and set
   reserved_pid to that project.

Options:

* -n <pri> - is how you set a priority. Lowest is zero, choose a
  higher number if you want this reservation request to be considered
  before others. In a tie, look at the date of creation, and use the
  oldest.

* -t <typelist> - a comma separated list of types you want to
  consider. Types are considered in order, but not in the fancy way
  you might imagine.

idea).

New script and table to manage node pre reservations. Lets just look
at the script.

To create a reservation:

    myboss> wap prereserve -t pc850 testbed 2
    Node reservation request for 2 nodes has been created.

To see the reservation status for testbed

    myboss> wap prereserve -i testbed
    Project         Cnt (Cur)  Creator    When               Pri Types
    -------------------------------------------------------------
    testbed         1 (1)      stoller    2011-08-12 12:39:07 0   pc850

    which says 1 node is pending and 1 node has already been
    pre-reserved. 

To clear the above reservation request (and optionally, clean
reserved_pid from the nodes table).

    myboss> wap prereserve -c -r testbed

    The -r is optional, otherwise just the reservation request is
    cleared, and nodes continue to be pre-reserved to the project.

To see a list of all reservation requests:

    myboss> wap prereserve -l


So, when a node is released in nfree, we look at the reservation
status for the node and any pending reservation requests.

1. If the node has a reserved_pid and that request is still pending
   (still in the table), nothing is changed.

2. If the node has a reserved_pid, but the request has been cleared
   from the pending table, then clear reserved_pid.

3. If reserved_pid is null, and there are pending requests, then pick
   the highest priority, most recent dated, request, and set
   reserved_pid to that project.

Options:

* -n <pri> - is how you set a priority. Lowest is zero, choose a
  higher number if you want this reservation request to be considered
  before others. In a tie, look at the date of creation, and use the
  oldest.

* -t <typelist> - a comma separated list of types you want to
  consider. Types are considered in order, but not in the fancy way
  you might imagine.

1. Support for "one-shot" PXE booting ala the one-shot osid. Switches to
   pxelinux to boot WinPE and then switch back after done. Painful now
   because we have to HUP dhcpd everytime we change the PXE path, but we
   may be able to fix this in the future by going all-pxelinux-all-the-time.

2. Added pxe_select, analogous to os_select, for changing the pxe_boot_path
   including the one time path.

3. Added the WIMRELOAD state machine to shepherd a node through the process.
   Still has some rough edges and may need refining.

By convention, if $debug is set we always declare the swapin successful.
We were not doing that in a few places.

expiration warnings.

Might not be in its final form yet.

This only affects cases where -a and -p are both being used and there is a node of a type not allowed in the specified project with subnodes.

Can't build target client on Linux without it.

but has not been tested for actual Emulab. A typical elabinelab NS
file would look like:
    
    source tb_compat.tcl
    set ns [new Simulator]
    
    tb-elab-in-elab 1
    tb-elabinelab-singlenet
    tb-elab-in-elab-topology opsvm
    tb-set-elabinelab-attribute CONFIG_WINDOWS 0
    
    namespace eval TBCOMPAT {
        set elabinelab_maxpcs 1
        set elabinelab_hardware("boss") pc3000
    }
    $ns run

you can do this in your NS file:

tb-set-node-loadlist $myboss FBSD73-S2,FBSDXX-FOO

Note that this does not replace tb-set-node-os(), cause that is a
little too special. So in practice, you would do:

tb-set-node-os $myboss FBSD73-STD
tb-set-node-loadlist $myboss FBSD73-S2,FBSDXX-FOO

USERNODE, shortcut to exec only, without the ssh.

"/dev/da0" notation.

(jail) on boss. A typical NS file might look like this, although note
that windows support is not finished yet. 

source tb_compat.tcl
set ns [new Simulator]

tb-elab-in-elab 1
tb-elabinelab-singlenet
tb-elab-in-elab-topology opsvm
tb-set-elabinelab-attribute CONFIG_WINDOWS 0

namespace eval TBCOMPAT {
    set elabinelab_maxpcs 1
    set elabinelab_hardware("boss") pc3000
}
$ns run

    
    OPSVM_ENABLE=0
    OPSVM_MOUNTPOINT=""

OPSVM_ENABLE=changeme
OPSVM_MOUNTPOINT=changeme

CreateVnodes().

worked in the "new" version.  (It continues to work fine in
os_setup (no new).  The new version is used primary by GENI related
and Utah projects.)

instead of two slashes, if I want a single slash in the DB.