described in my final project paper.

from configure. Followed the cvs renaming advice in
http://www.loria.fr/~molli/fom-serve/cache/287.html

forms. Add a view[] array to hide various parts of the form, and
a view_style to use a predefined set of view[] options. Also, allow
formfields to be passed in to provide defaults for a user.

PAGEHEADER() now takes a vew array, which can turn on and off display
of things like the sidebar and banner.

In the future, some of this information will likely be grabbed from
the user somehow (new and/or plab users may get a different view than
others).

Also added the functions to draw a 'topbar' of options that goes
across the top of the page, rather than down the left side. A simple
topbar for planetlab nodes is included.

trivial simulated links. This is coz existing sim node support that
goes on 1 pnode can't handle this. Also added a 'sim' type in the
node_types table and a issimnode column in it.

Now, the old sim node support is working and demoable.

pc170-1 until those nodes actually have e1000 cards installed (next week).

Need to use ethtool instead of mii-tool to do this.  My comment:

  #
  # Linux is apparently changing from mii-tool to ethtool but some drivers
  # don't support the new interface (3c59x), some don't support the old
  # interface (e1000), and some (eepro100) support the new interface just
  # enough that they can report success but not actually do anything.  Sweet!
  #

This requires that we load ethfind on the nodes, though the script will
continue to work if it isn't (though will not work for e1000 cards).

sethostname script properly sets the hostname, but sometimes that hostname
gets overridden by one of the static boot scripts which sets the hostname
back to "localhost".  The sequence is something like:
	pump runs on eth0 and fires off our sethostname script
	sethostname blocks
	ifup of eth1 starts, determines that hostname hasn't been
	  set (i.e., is set to "localhost") and remembers (NEEDHOSTNAME)
	sethostname finishes by setting the host name
	ifup of eth1 finishes, seeing NEEDHOSTNAME is set but doesn't
	  have anything to set it to so resets to "localhost"
Weird.  Hack is to make sure it never thinks it needs to set the hostname
by setting it to something that is not "localhost".  We do this once we
identify the control net interface (and thus know we will be running pump RSN).

alleviate this weird caching race with vnode CNAMEs

and a template. The idea is that it's a general tool for generating
NS files for standard topologies (ie. LANs), filling in some
user-supplied values. Has some features that are useful for NS files,
like default values and skipping or commenting out sections if values
for variables are not given.

Could probably use some better error checking on the the XML file.

Does not yet get installed.

solution, but no time today.

rest of the infrastructure is in place. Right now, it just does an exit 0.

* Make the NS file an optional argument to swapexp modify; when not
  given the prerun phase is skipped. Instead, go directly to tbswap
  (run assign, etc).

* Add NSESWAP event so that Shashi can fire off the above modify using
  tevc from an experimental node.

	tevc -e pid/eid now ns nseswap

* Change event scheduler to react to above event, and fire off:

	nseswap pid eid

  as the user. The script should do its thing, and *exec* swapexp with
  the proper args as quickly as possible (so that the event scheduler
  is not hung up for too long. The script is invoked as the user,
  since the event scheduler is running as the user.

of virt_tables so that it is saved and restored like the rest of
the virtual state.

optional when using tevc (dynamic events). So:

	tevc -e testbed/progagents now prog0 start

will simply rerun whatever the last command was.

its going to get replaced at some point by a busy state. The swap
scripts properly set the next state before unlocking the experiments
table, which possibly leaves some small races as experiments
transition through states (which happens with the table unlocked,
cause I used to have this really handy variable called expt_locked,
which no one really likes anymore).

We either have to use more table locking, fix up expt_locked, or punt
and say it won't happen more than once in a few thousand operations!

instead of testbed-ops. Either way, Mike gets to see it.

state machine (state). All of the stuff that was previously handled by
using batchstate is now embedded into the one state machine. Of
course, these mostly overlapped, so its not that much of a change,
except that we also redid the machine, adding more states (for
example, modify phases are now explicit. To get a picture of the
actual state machine, on boss:

		stategraph -o newstates EXPTSTATE
		gv newstates.ps

Things to note:

* The "batchstate" slot of the experiments table is now used solely to
  provide a lock for batch daemon. A secondary change will be to
  change the slot name to something more appropriate, but it can
  happen anytime after this new stuff is installed.

* I have left expt_locked for now, but another later change will be to remove
  expt_locked, and change it to active_busy or some such new state name in
  the state machine. I have removed most uses of expt_locked, except those
  that were necessary until there is a new state to replace it.

* These new changes are an implementation of the new state machine,
  but I have not done anything fancy. Most of the code is the same as
  it was before.

* I suspect that there are races with the batch daemon now, but they
  are going to be rare, and the end result is probably that a
  cancelation is delayed a little bit.

* Add slots to users table to track number of failures in the last N
  seconds. If a threshold is passed (currently 4 failures in the last
  minute), the web login is disabled. Note that I do not disable the
  ops shell login at this time. Aging is passive; the values are cleared
  when login is successful, or when more then one minute has passed
  since the last failure. In other words, a burst of failures will
  disable the login, but failures over time are okay.

* Add login_failures table to do exactly the same as above, except it
  is on an IP basis (REMOTE_ADDR in the server). Currently the
  threshold is 8 failures in the last two minutes, at which time all
  logins from that IP are disabled.

In both cases email is sent to tbops (and the user).

The constants are defined at the top of www/tbauth.in, rather then as
site variables, to avoid pounding the DB when an attack is being
launched.

To clear a user freeze, go to the user profile page and use the
"toggle" near the bottom.

To clear an IP freeze: delete from login_failures were IP='1.1.1.1'

for tracking login attacks.

enthusiasm of those who want to replace expensive commercial solutions
(and so I don't have to tell people over and over...)

Currently, this only means defining a signature file and creating a
utility to make them and check them against a disk.  The signature file
is not used by frisbee/imageunzip yet.

object coz it is currently disallowed.