to swap in/out/modify an experiment, so we can do proper accounting.

dojailconfig: Do not return a jail config unless the node is really
jailed.

doifconfig: Look at the node name, and return ifconfig info specific
to the name instead of always returning all info for the machine. Upon
boot, virtual interfaces will not be setup, but instead will be setup
when the jail is setup. When the jail requests ifconfig info, it gets
only its list of interfaces to setup.

dolinkdelays: Ditto, since linkdelays will be setup after per-jail
interfaces are setup.

real life.

There's a small window in time (typically a few seconds, but maybe 10's of
seconds on occasion) between the time nodes get nalloc'd and the time they
get rebooted during a swapin. If idlemail runs (or someone views a web
page) during this time, the expt can appear idle because the nodes haven't
had any activity. It can cause an incorrect email or a false positive on
the web page.

The fix is to have nalloc register some external node activity, like
node_reboot does, when it allocates a node.

before was idle view of the expt list. Now it shows in all (non-thumb)
views.

I also added it to the right hand table in the expt page.

It also shows in the little expt lists in the user, group, and proj pages.
(I'm already really glad those got consolidated into a single function.)

Also cleaned up idle view a bit. Now that we show staleness and idle
ignore anyway, we don't need text tags for them, and we no longer need the
red dot that links to swap requests because of idlemail. So there's no
longer the weird double-column thing in idle view.

I'm still looking for a good way to non-intrusively mark expts in the expt
list as being unswappable, so if you think of anything, let me know.
(Maybe boldface, or a little lock icon or something?)

a lone stray " .

 - Don't use the image, just use a text link. (Note: the text link in the
   middle is different than the button link on the left, since the button
   doesn't set refer=1.) (From Rob/Chad)
 - Don't jump back into admin mode just because I was before. Let it dump
   me back to green dot when I log back in. (From Leigh)

Linked in publications and classes under
new "Emulab Users" top-level menu item.
Moved project list from the top-level underneath this.

For non-Utah emulabs, the project list remains
on the top level.

jailed nodes from veths for plain emulated links between phys nodes,
which we might generally allow at some point for supporting emulated
links (rather than using IP aliases). My plan is to use this im tmcd
to determine what ifconfig returns; no point in returning jailed veth
configuration when the node boots, but should wait until the jail is
setup (this is further complicated by rtabids, but thats another
story).

Some changes Jay wanted,
plus put some of the "H" in HTML (links to papers).

to allocate and swapin when the max_concurrent is already reached for
the OSIDs requested. Should work properly with the batch system.

is not a string of bits, but really 0 when the type is unsigned.
Sheesh. Add link from testbed_stats to experiment_resources to get
better info in showstats.

tbswap can return - they use their return value to communicate some
information. Text is from Chad.

per-experiment instantiation with aggregate data like the number of
swapins, the dates and the like. The other part is the per
swapin/modify stats. These are number of pnodes, links, lans,
etc. Long term, I think we want more precise swapin stats, and with
experiment modify in the mix, we need to have multiple stat records
per experiment, but do not need to duplicate all the stuff in the
other table just mentioned.

To reduce the amount the table size, we cross reference the tables by
index only instead of with pid,eid and the like. We use exptidx to
link experiments, experiment_stats, and the new experiment_resources
table. experiment_resources and stats are linked by another index in
the resources table, which indicates which is the current resource
row. On a modify, a new resource record is created, and the stats
record updated to point to the new (latest) resource record.

Web Changes: Improve showstats and showexpstats. Make them user
accessible so that mere users can see stats for themselves and for
their projects. No ability for mere users (PIs) to look at another
person's stats. Generally, these two pages need more work, but now
they are more useful. I added Show Stats to the user info and project
info pages to display per-usr/proj stats. Add more info in the
showstats display, but the showexpstats display is still not pretty
printed; just the raw tables.

Rename a few fields, add some indexes, and otherwise make some minor
changes that are sure to annoy everyone.

Now fortified with alphabetization!

Modify experiment is now deployed/documented...
We can announce it tomorrow.

per-OS. Also, moved the functionality to check for this into libdb,
so we can call it from other places (like the batch daemon.)

Synchronized expubs with what we presented in the proposal
(left out "submitted for publication" papers.)

initialization (liblocsetup) which was blindly turning on fast
forwarding.

documentation.

Generates dummy packets on all interfaces, so that the switch will
learn their MAC addresses.

entities. All that means is that you can use them independent of
jails by doing something like this in your NS file:

	set link0 [$ns duplex-link $node6 $node9 40Mb 0ms DropTail]

	tb-set-multiplexed $link0 1
	tb-set-useveth     $link0 1

For now, must use OSID FBSD47-JAIL, but that will change when I create
new images. The fallback without useveth is IP aliases like before,
which is nice cause that will work on Linux too.

There are some other minor cleanups included.

and the ps in doc, and the gif in www/doc/, where it is linked into the
web appropriately.

to interfaces) so that we return the MAC of the virtual interface not
the physical interface.  I do not much like this arrangement.  We
store veth interfaces in another dynamic table, so must join with both
interfaces and veth_interfaces to see which iface each linkdelay
corresponds to. If there is a veth entry use that, else use the normal
interfaces entry. Maybe we should use the regular interfaces table,
with type veth, entries added/deleted on the fly. I avoided that cause
I view the interfaces table as static and pertaining to physical
interfaces only, but the current arrangement does not scale well
(although if it only ever has to scale to veth_interfaces, so be it).

show{user,group,proj,exp}.php3 pages.

While I'm at it, move the triplicated code into a single function inside
showstuff.php.

stale entries where in the DB ...

know not what they do.