home page and My Emulab page.

are listed in the ntpinfo table.

to assume that the leader of a stack is the switch after which it was named -
we can now name stacks things like 'Control' or 'Experiment'.

Some cleanup of the robot vision system:

	* Makeconf.in: Add INSTALL_INCDIR for includes, EVENTSYS for
	whether or not the event system is available, HAVE_MEZZANINE for
	whether or not we'll be building mezzanine, and GTK_CONFIG which
	refers to the gtk-config binary, if there is one.

	* config.h.in: Add HAVE_LINUX_VIDEODEV_H and HAVE_MEZZANINE
	defines.

	* configure, configure.in: Check for the robot vision system
	dependencies.  Add mezzanine template files.

	* robots/GNUmakefile.in: Add some conditionals for directories
	that depend on the event-system and mezzanine.

	* robots/mezzanine/GNUmakefile.in,
	robots/mezzanine/libfg/GNUmakefile.in,
	robots/mezzanine/libmezz/GNUmakefile.in,
	robots/mezzanine/mezzanine/GNUmakefile.in,
	robots/mezzanine/mezzcal/GNUmakefile.in,
	robots/mezzanine/rtk2/GNUmakefile.in: Fold mezzanine into the
	testbed's build system.

	* robots/vmcd/GNUmakefile.in: When building the vmc-client, use
	the mezzanine that we build locally instead of an installed
	version.

	* robots/vmcd/test_vmc-client.sh.in, robots/vmcd/test_vmcd.sh.in,
	robots/vmcd/test_vmcd2.sh, robots/vmcd/test_vmcd3.sh,
	robots/vmcd/test_vmcd4.sh: Bring the test cases up-to-date with
	respect to the actual code.

	* robots/vmcd/vmc-client.c: A bunch of cleanups and bug fixes: add
	comments, set TCP_NODELAY on the client sockets (doh), etc...

rules back on. The ipfw silently fails, but if I do it a second time,
it works fine. This is bogus of course ...

but never made use of. Moved to its own file (www/xmlrpc.php3.in)
and made to be more like the perl library I did a couple of months ago,
that presents an interface to an sslxmlrpc server, via the sslxmlrpc
client program operating in "raw" mode (takes raw xml on stdin, and
returns raw xml on stdout).

Added ELABINELAB code to nodetipacl.php3 so that you can click on
console icon on an inner emulab web page, and it will ask the outer
emulab sslxmlrpc server for the stuff it needs, and return that to the
user.

variable in the defs file. Nice for elabinelab to avoid inner named
from having to do too much work.

the inner web interface can return the stuff that tiptunnel needs.
Tim already had a node.console routine that does this, so I just
invoke it from the elabinelab class, after elabinelab permission
checks.

loading emulabserver.py from the main tree.

nodes, and then if allocated and person has permission, the vname and
pid/eid.

Note that tip tool ballons have no formatting capabilities at all;
just a simple text string.

If we want fancier, I found some javascript code that will popup real
windows, and then kill them like a tool tip after a short pause or
when the user mouses out. The downside of the real window is that with
some window managers, you still get a status bar along the top, and so
it looks icky. The upside is that we can put real information and
formatting directives in the popup.

XMLRPC, but for now avoid the warnings.

Do not die when turning firewall rules back on fails. This is a transient
error I do not understand yet.
When firewalled and paniced, skip clean shutdown of inner nodes since
they are going to be powered off anyway later, and besides, the control
network is shut off, so no way to talk to inner boss anyway.

You can specify any display resolution you want; it doesn't have to be
one of the "normal" ones.  And you can switch back and forth by just starting
a new rdesktop and "grabbing" the rlogin session away from the previous one.

But once an rdesktop is started up, its display resolution is fixed.  If you make it
smaller than the previous one, it will push your windows around to fit.

web interface you are talking to!

the web interface.

is not currently working. Simple revert to previous revision when
camera is fixed.

Right now, these have to be built on ibapah, because it's got the
cross compiler neeeded.

Includes some of Kirk's SGGPIO code. This should probably get moved
to some other directory and made into more of a library.

PAGEHEADER() and PAGEFOOTER(). Pop it up in a new window.

* tbsetup/panic.in: New backend script to implement the panic button
  feature. When used, it will cut the severe the connection to the
  firewall node by using snmpit to disable the port. Sets the panic
  bit (and date) in the experiments table, and changes the state of
  the experiment from "active" to "paniced" to ensure that the
  experiment cannot be messed with (swapped out or modified). Sends
  email to tbops when the panic button is pressed.

  Used with -r option, reverses the above. State is set back to
  active, the panic bit is cleared, and the port is renabled with
  snmpit.

* tbsetup/tbswap.in: During swapout, a firewalled experiment that has
  been paniced will get a cleaning; The nodes are powered off, then
  the osids for all the nodes are reset (with os_select) so that they
  will boot the MFS, and then the nodes are powered on. Then the
  control network is turned back on, and then I wait for the nodes to
  reboot (this is simply cause we do not record in the DB that a node
  is turned off, and if I do not wait, the reload daemon will end
  hitting the power button again if they do not reboot in time. We can
  fix this later.

  I am not planning to apply this to general firewalled experiments
  yet as the power cycling is going to be hard on the nodes, so would
  rather that we at least have a 1/2 baked plan before we do that.

* www/showexp.php3: If experiment is firewalled, show the Panic
  Button, linked to the panic button web script. If the experiment has
  already had the panic button pressed, show a big warning message and
  explain that user must talk to tbops to swap the experiment out.
  Also fiddle with menu options so that the terminate link is gone,
  and the swap link is visible only in admin mode. In other words, only
  an admin person can swap an experiment once it is paniced. And of
  course, an admin person can the backend panic script above with the
  -r option, but thats not something to be done lightly.

* db/libdb.pm.in: Add "paniced" as an experiment state (EXPTSTATE_PANICED).
  Add utility functions: TBExptSetPanicBit(), TBExptGetPanicBit(), and
  TBExptClearPanicBit().

* tbsetup/swapexp.in: Minor state fiddling so that an experiment can
  be swapped while in paniced state, but only when in admin mode. Also
  clear the panic bit when experiment is swapped out.

* www/dbdefs.php3.in: Add "paniced" as an experiment state. Add a
  utility function TBExptFirewall() to see if experiment is firewalled.

* www/panicbutton.php3: New web script to invoke the backend panic
  script mentioned above, after the usual confirm song and dance.

* www/panicbutton.gif: New gif of a red panic button that I stole off
  the net. If anyone has sees/has a better one, feel free to replace
  this one.

* utils/node_statewait.in: Add -s option so that I can pass in the
  state I want to wait for (used from tbswap above to wait for nodes
  to reach ISUP after power on).

(hopefully) fixed up the completely twisted and fucked up left handed world coordinate thing. (Transpose x,y)

Changed angle tolerance to about 5 degrees, and decreased max retries to 3

after we flash the mote.

We can probably make this work (I hope), but this hack will have to
do for now.

   - Changes to force an x and y offset to be passed on the command line
     so I can do a camera coord->world coord transform (basically, ensure
that emulab sees coords in its space, not coords from individual cameras).