GitLab

path.

Ok, not really any fundamental changes, mostly a source reorganization,
but some new features as well:

1. Split off FS specific code for all FS types into subdirectories.
   imagezip.c was just getting unwieldy.  You can now (in theory, I
   haven't enabled this in any easy way) build a version of imagezip
   with only the FSes you care about.

2. As part of the above, localize the filesystem specific headers in
   the subdirs instead of relying on the installed system headers.
   This allows easy building of, for example, BSD FS support under
   Linux.

3. Hacked up the GNUmakefiles some so that imagezip with all FS support
   will build (in the Emulab context) under Linux and FreeBSD 5.1 as
   well as FreeBSD 4.x.  Still a hack, for Linux you need to first do:
	setenv LINUX 1
	setenv HAVE_GCC3 1
	setenv HAVE_LOCALE 1
   and for FreeBSD 5.x:
	setenv HAVE_GCC3 1
	setenv HAVE_LOCALE 1
   these trigger ifdefs in some of the Makefiles to DTRT.  Imagezip
   and frisbee still need a standalone configure...

4. Added support for UFS2 (aka FreeBSD 5.x default filesystems).

5. Added "-S dos-type" option to imagezip.  This is the general form
   of the -b, -l, and -n options to force imagezip to treat the device
   as though it contains a filesystem of the indicated type.

from looking at the embedded (and deprecated) blockindex field in
the headers.  Now imagedump won't complain if you run it on a
piece of a split image.

Small change to make sure .forward files are owned by the user instead of root. Lots of them were getting left behind as root owned files.

and bandwidth data from the various plab websites and parses the ad-hoc
files into something that can be inserted into the widearea_recent
table.

Not a real daemon at the moment; it will run from crontab until
I have a chance to fully daemonize.

gets generated.  Here it is..

It isn't installed by the "install" make target.

 plabdaemon -v renew
 plabdaemon -v getfree
 plabmonitord

non-standard one.

Add an example state machine. There for drawing pretty pictures and as an example for people who use the other state machines.

Well, here it is:  The checkin implementing robust recovery/retry and
asynchronous safe termination in plab allocation/deallocation/setup.

Here are some of the more prominent changes/additions:

* Bounded plab agent communication
  Scripts should never hang waiting for plab xmlrpc commands to complete;
  they have their own internal timeouts.  Node.create() in libplab is an
  exception, but is always run under a timeout constraint in vnode_setup
  and can be changed easily if the need arises.

* Wrote functions in libplab to do the retry/recovery/timeout of remote
  command exection.

* Wrapped critical sections with a signal watcher.

* Added code to handle various error conditions properly

* Added a libtestbed function, TBForkCmd, which runs a given program in
  a child process, and can optionally catch incoming SIGTERMs and terminate
  the child (then exit itself).

* Fixed up vnode_setup to batch the 'plabnode free' operation along with
  a few other cleanups.  This should alleviate Jay's concern about how
  long it used to take to teardown a plab expt.

* Whacked plabmonitord into better shape; fixed a couple bugs, taught it how
  to daemonize, and implemented a priority list for testing broken plab nodes.
  This list causes new (as yet unseen) nodes to be tried first over ones that
  have been tested already.

a full-out explanation of the new way we add nodes to the testbed,
the new (well, not that new anymore) newnode MFS, web page, etc.

into a new file.

Remove reference to cvsup, since we're moving away from it.

Remove reference to dhcpd, since a better explanation is now in
setup-nodes.txt .

Fix up text about named.

change awkward "uncompress" to "decompress"

This will happen for plab nodes because of the way that we can get the
data. Not ideal, but not sure what to do about it.

what window is what.

pop up a save dialog box, no matter what the user's settings for the
mime type are.

information. Rather than pass it all in, which was getting very
cumbersome, and inconsistent between Cisco and Intel switches, the
modules query the database themselves (via a new function in
snmpit_lib.pm).

Also in this commit are two new options for switch stacks - the
ability to specify minimum and maximum VLAN number to use.