Many changes and updates for handling new types. The db now has types like 'pc600', 'pc850', and 'dnard', and each type has a class like 'pc' or 'shark'. This updates scripts that use types to use classes where appropriate, and to handle the new types where there were hardcoded things that couldn't be eliminated right now.

In failure messages, make errors more obvious by showing logged output before showing the ns file they submitted. Now things like 'Insufficient Nodes' will appear within the first 15 lines of the message, where they are easy to see. This also matches the format of the successful configuration messages.

to tell it how to parse interswitch links from assign.

It still assumes a single VLAN domain.

now precomputers the shortest path between all pairs of switches and uses
this to computer paths through the switch fabric.  In the process of
writing this I also removed the limitations of two switch hops.  Packets
can now travel through any number of switches to reach their destination.
Of course, the longer the path the more it costs so assign will prefer
shorter paths.

Also did various other tweaks in the process.  We now use strings almost
everywhere instead of char*'s and the makefile is cleaner.

lease when it boots.

script.

script.

own account information. It was failing from the web UI when random
user would change their info.

    From: "Patrick Tullmann 'tullmann'" <tullmann@cs.utah.edu>
    Subject: Re: TESTBED: aclement janos Project Join Request

    First the reply-to: address for approval mails should be
    testbed-ops@fast (right?).

    Second, Austin isn't listed on my testbed user approval page.  I
    assume Mike or a testbed person approved him (which is good because
    who knows when I'd get around to it. :)

    An option like "remove" or "ignore" or something like that for just
    nuking requests without a reply would be useful (I've got some guy
    from yahoo.com who wants to join Janos).

    Also, the date of the join request would be nice to know (e.g., for
    the above, I think he tried joining 4 or 5 months ago).

    he documentation above the table is out of synch with the pull-down
    boxes.

This version has my algorithm implemented and works correctly with all kinds of topology. It generates the nam file with LAN topology too !!
                  - Indrajeet

email, for the case when someone other than creator does the
termination.

to console and /var/log/messages.

degree of bit rot. Updated the create batch web page to do
local/remote NS file spec. Switched to libdb interface in the batch
mode scripts. Removed estimated pc/shark slots since we don't support
that anymore, and because the new parser returns proper exit status
when not enough nodes are available. The DB will be updated at that
point, and we can incorporate that info (have not done so yet).
Incorporated node boot status into isexpdone(), since a failed node
will never report startcommand exit status. Clean up email code so
that email goes to user/tblogs/tbops in the proper situations.

a bootstatus field to the nodes table. os_setup sets this to one of
okay, failed, unknown. This is to be used with the still to be defined
method of specifying certain nodes that can fail reboot on experiment
creation. Right now sharks are wired to this, and this information is
presented in the web page. Its also essential for the batch system,
which needs to consider nodes that failed to reboot, or else batch
experiments would never end. Might still need a way for an experiment
to tell the batch system its done though.

commit.

sharks and delay nodes.

per-experiment level DB redirect. This makes it easier to tolerate
testing harness failures.

its hardwired to the shark type, but needs to come from DB somehow
later. Mail is sent to the user (CC'ed to testbed-ops) when a node
fails but the experiment continues setup.

easily allows tests to be shared across sets.

sessions. (advanced use only)

Made test failure messages more meaningful.

customization for the log paths. Also added an increase of max
connections to 200.

Minor cleanups in os_setup, and move some code to libdb.

a development tree.