Now the limit is pid=48 and gid=32.

Note that the FreeBSD clients croak on NFS mounts that are too long
(way shorter then MAXPATHLEN!). Sigh.

Includes support for adding new nodes/interfaces/interface-types/wires.
Also includes sample xml files.

check at BBN's Emulab. No clues yet.

five days out. The user can bypass this though since the time is in
hours, and they can just set it everyday. But, most people will not
catch onto that.

No more frisbeelauncher or assorted subboss frisbee stuff.

"tb-set-tarfiles" is like "tb-set-node-tarfiles" except that it
distributes the tarfile to all nodes rather than just one and that it
uses frisbee to distribute the file.

These changes involved 1) refactoring frisbee info from images table
into a new table, frisbee_blobs, 2) a new experiment_blobs table, and
3) a new tmcd command so the node knows how to get the files from the
server.

The changes where designed to be general purpose enough to eventually
support:
  1) Distributing arbitrary files (not just tarfiles) to nodes
  2) Perform arbitrary actions on those files
  3) Use arbitrary methods to get the files

As such the tmcd line is as follows:
  URL=* ACTION=*

where URL is currently:
  frisbee.mcast://<ADDR>/<FILE>
for example
  frisbee.mcast://234.16.184.192:18092/users/kevina/home-dir.tar.gz
and when we get around to using a master Frisbee server it could be
  frisbee://*
or it could be a file://, http://, etc.

and ACTION is currently:
  unpack:<LOCATION>
for example
  unpackt:/users
with future syntax to be determined.

Basically, we cannot create an image descriptor without any types
defined, and we cannot create any types without a default image
descriptor. I broke the circle by adding a stub pc type into the
database fill file so that all Emulabs start with a predefined type.
Then you can load the descriptor file, create your actual types, and
then go back and edit the image descriptors to set the types those
images run on (you always had to do this).

only one osid,pctype maps to an image (osid2imageid).

this got dropped, but I guess we do not make these very often. But I
need it to work for the new version of load-descriptors on a new
installation.

process, to add the base descriptors.

the tb-set-node-os command with a second optional argument; if that is
present, the first arg is the child OS and the second is the parent OS.
We add some new features in ptopgen (OS-parentOSname-childOSname) based
off a new table that maps which child OSes can run on which parents, and
the right desires get added to match.  We setup the reloads in os_setup
along with the parents.  Also needed a new opmode, RELOAD-PCVM, to handle
all this.

For now, users only have to specify that their images can run on pcvms, a
special hack for which type the images can run on.  This makes sense in
general since there is no point conditionalizing childOS loading on
hardware type at the moment, but rather on parentOS.  Hopefully this stuff
wiill mostly work on shared nodes too, although we'll have to be more
aggressive on the client side garbage collecting old frisbee'd images for
long-lived shared hosts.

I only made these changes in libvtop, so assign_wrapper folks are left in
the dark.

Currently, the client side supports frisbee.  Only in openvz for now, and
this probably breaks libvnode_xen.pm.  Also in here are some openvz
improvements, like ability to sniff out which network is the public
control net, and which is the fake virtual control net.

at once with Frisbee (excludes the actual MFS changes).

Os_load now takes take a list of comma serrated image names for the
"-i" and "-m" options.  The default OS is the OS for the last image
specified in the list.  I also changed the "-p" option of osload to
search both the project specified and emulab-ops for the image rather
than just the project specified in order to simplify specifying
multiple images (and because I personally found that behavior annoying
when using osload).

I modified the current_reloads table to be able to specify more than one
image for a node by adding an "idx" column which controls the order of
the reloads.  I also added a "prepare" column to the table (explained
below)

I modified tmcd to basically loop over the entries in the table and
create a multiline LOADINFO responsive, and modified rc.frisbee to
handle the multiline response and load each image in turn.

I modified os_load to take a new option "-P" which will tell rc.frisbee
to zap the superblocks even if a whole disk image is not specified.
To do this I set the prepare entry for the first image in the
current_reloads table to true.  Tmcd than passes this into to
rc.frisbee in the LOADINFO line.  When rc.frisbee sees this it will
make sure to zap the superblock before loading that image.

To support having multiple images as the default, "default_imageid"
can now be a comma separated list.  I implemented a hack to be able to
set multiple imageids via editnodetype.php3.  Basically the form
splits default_imageid into default_imageid_0, default_imageid_1, etc
and than adds an empty default_imageid_# slot to allow adding an
imageid.  Multiple images can be added by adding one image, than
submitting the form, and than adding another into the empty slot.  Not
the best, but I don't thing this will be a very common operation.
When the form is submitted it will than combine all default_imageid_#
into a comma separated list ignoring any that are deleted or set to
"No ImageID" (ie 0).

Everything will work fine with old MFSs as long as only one image is
loaded.  If multiple images are loaded with an old MFS, an email will
be sent to testbed-ops.  This works by having tmcd detect old MFS's by
using the version number and setting the state to RELOADOLDMFS.  Stated
will pick up on the and send the email to testbed-ops via a trigger.

image.

 * when creating an image from a node, make sure the new image
   gets the MBR version used by the existing image
 * when loading a single-partition image that requires a different
   MBR, invalidate all other existing partition ("invalidate" in the
   sense that we remove any partitions table entries, we don't do anything
   to the disk)

I'm sure there was a reason for this at one time, but I don't recall it...

Fix Ticket #211 by reporting all the unacceptable node types at once.

the User Name (or id) in various tables.  This also involved adding
the field to the newproject, joinproject, and moduserinfo forms.

Note: also modified 4.149 database-migrate.txt entry to add a note
to add the necessary "slot" to table_regex.

checking.

I think this fixes flyspray bug #51.

creating a whole disk image with the "Easy" form.

the script to not add the leader to the new group (membership list).

isadmin checks).