/share.  I made it a FAQ question, if you can't tell from the commit!

not have to wait 3 minutes for it to finish before he can watch his
experiment swapin fail for some other reason.

I adopted the same pid mechanism as in eventsys_control.in, which uses
a slot in the experiments table.

Running "prerender" puts the render into the background and stores
the pid. Running "prerender -r" kills a running prerender and removes
the existing info from the DB.

Fixed the problem with swapmod not restoring the old vis; swapmod now
kills any running prerender, and restarts one if the swapmod fails
(the prerun of the new NS file starts up another prerender in the
background).

Add setpriority() call in prerender to nice it and children to 15.

nodes that there were in the top file.

recognizes it properly.

unretryable error, so Mike doesn't have to kill assign off 20 times!

already reserved nodes (for swapmod obviously). Looks like:

	lappend reserved_list "nodeG"
	set reserved_type(nodeG) "pc850"
	set reserved_node(nodeG) "pc52"

So, you can iterate through the list of reserved nodes, and find their
type and pnode.

Remove more old commented out code from modifyexp.

breaking routes and jail interfaces.

showexp page that its a batch experiment, by the menu options. Same
deal in the swapexp output, plus some other minor cleanup. The only
bug I found while trying to figure out the batchmode problem reported
this morning by the FileMover people, is that the cancelflag is not
cleared after swaping a running batch experiment out, so even after
reinjecting it into the queue, it will not run. Still, that does seem
to be what the FileMover people reported.

doing the boss-install, to remove confusion about a possible circular
dependancy.

going on.

changes to the backend a while ago, but the form changes never got
made cause of the ongoing delay in the new form commit. So, you can
preload a batch experiment now.

size of the file.

nodes) from outside, rather than defining it in the .c file.

Change the DEFAULT_PATH to freebsd.newnode . (It's harmless for a
'known' node to boot this by accident.)

little new icon if there are new nodes waiting.

can't make it look anything but ugly....

Handle interfaces we didn't find on the switch.

Use newnode_reboot to reboot nodes, since they won't yet be at their
'permanent' IP addresses.

Changed my mind again on what state the new nodes should be put into
once they've been created. Now, they go into emulab-ops/hwdown, and
boot into the FreeBSD MFS. This way, the admins have a chance to look
at them before they loose them on the world, and they're booted into
something that runs SSH, so we don't lose control over nodes that
don't have power controllers (which newnode doesn't currently handle,
anyway.)

database yet, so using node_reboot on them would be catastrophic.
Uses the special newnode MFS's ssh key.

Also, when a node has booted or the first time, it may be up on a
temporary IP address rather than its permanent one, so we pass the
node's IP rather than node_id on the command line.

Only tries ssh.

to make this MFS another of the zillion things we have to customize
for each site, so rather than putting boss's SSH key on it, I've made
a new one, only for use in that MFS.

Note - the key HAS to be mod 600, or ssh will refuse to use it, which
leaves us in the regrettable position of having to make the script
that uses it setuid root. But, it's gotta be done.

now be ready for the main tree!

       being used in an experiment (node, virthost, delaynode,
       simnode). This is for helping to simplify the swapmod code
       support in assign, and to eventually fix the delaynode problem.

also.

final time, so that we can see how long things take. As per Jay's
request.

final time, so that we can see how long things take. As per Jay's
request.

is turned on; 60MB of exports files is not really needed these days.

tbswap to use this version inside the testbed project only! All other
projects will see the old version for now; there are just too many
things to test, and the testsuite gets just a fraction of them. Some
highlights (which I will expand on later when I commit this version to
the main version):

* New -t option to create the TOP file, and then exit. The only other
  side effect of this is to update the min/max nodes for the
  experiment in the DB, unles new option -n (impotent mode) is given.

* New -n option to operate in impotent mode; do not allocate nodes and
  do not modify the DB. Okay, so this option is not as great as it
  sounds. I eventually hit the point of diminishing returns, with
  trying to make things work right without DB modification. At some
  point I just throw in the towel and exit. This currently happens after
  interpolating the link results of assign. But, I have found it very
  useful, and could get better with time. Being able to run assign on
  the main DB without sucking up the nodes is nice for debugging.

* Lots of data structure organization, mostly on the virtual topology
  side of assign (you can think of assign as two sections, the part
  that interprets the DB tables and creates the TOP file, and the part
  that reads the results of assign and sets up all the physical stuff
  in the DB). I removed numerous global hashes, and combined them into
  aggregate data structures, such as they are in Perl. My approach for
  this was to read the tables from the DB, and keep them handy,
  extending them as needed with stuff that assign_wrapper generates as
  it proceeds. This has the side effect of cutting down on the number
  of queries as well.

  The next task is to do the physical side reorg, but not up for that
  yet.

utlimate solution to this whole problem is to change the experiment
state so that we can distinguish between real swapout and swapout
caused by swapmod/retry/error. Or, we need to add more intermediate
allocstates for the nodes. Not sure yet.

can I say? This page is public, and linked from various places.

recreated at jail reboot. Note this file is *inside* the jail and
consists of the common routes (gateway, loopback, etc).