Small changes to image access permissions checks. Root can get any image it wants, and frisbeelauncher only requires READINFO permissions, so that users can os_load shared images still. Also, have os_load pass its debug flag to frisbeelauncher if set.

obscure errors since we allow the path to be set to null. Setting the
path to null via the web page is probably not a good idea, but I just
did that by accident and noticed what happened ...

when loading the default image.

invoked from os_setup, which runs as the user.

supporting autocreating and autoloading images. The imageid form now
sports a field to specify a nodeid to create the image from; If set,
the backend create_image script is invoked. Thats the easy part.
Slightly harder is autoloading images based on the osid specified in
the NS file. To support this, I have added a new DB table called
osidtoimageid, which holds the mapping from osid/pctype to imageid.
When users create images, they must specify what node types that image
is good for. Obviously, the mappings have to be unique or it would be
impossible to figure it out! Anyway, once that image mapping is
in place and the image created, the user can specify that ID in the NS
file. I've changed os_setup to to look for IDs that are not loaded,
and to try and find one in the osidtoimageid. If found, it invokes
os_load. To keep things running in parallel as much as possible,
os_setup issues all the loads/reboots (could be more than a single set
of loads is multiple IDs are in the NS file) at once, and waits for
all the children to exit. I've hacked up os_load a bit to try and be
more robust in the face of PXE failures, which still happen and are
rather troublsesome. Need an event system!

Contained in this revision are unrelated changed to make the OS and
Image IDs per-project unique instead of globally unique, since thats a
pain for the users. This turns out to be very messy, since underneath
we do not want to pass around pid/ID in all the various places its
used. Rather, I create a globally unique name and extened the OS and
Image tables to include pid/name/ID. The user selects pid/name, and I
create the globally unique ID. For the most part this is invisible
throughout the system, except where we interface with the user, say in
the web pages; the user should see his chosen name where possible, and
the should invoke scripts (os_load, create_image, etc) using his/her
name not the internal ID. Also, in the front end the NS file should
use the user name not the ID. All in all, this accounted for a number
of annoying changes and some special cases that are unavoidable.

image is bigger than any previous image we have dealt with! Probably
need to make this dynamic in some way.

* Add appropriate goo to os/GNUMakefile so that Frisbee daemon is
  built and installed.

* Rework the frisbee launcher slightly. Aside from little changes
  (send email to tbops when frisbeed dies, new cmdline syntax to
  frisbeed), allow for frisbeed to exit gracefully after a period of
  inactivity (no client requests for 30 minutes, at present). In order
  to prevent a race condition with a new client being added (and
  rebooted) and frisbeed terminating before the client gets started,
  add a load_busy indicator to the images table (next to load_address
  slot) and set that to one each time to frisbeelauncher is invoked.
  When frisbeed exits, test and clear that bit atomically (lock
  tables) and go around another time (restart frisbeed for another 30
  minute period).

* Rework waitmode in os_load. Wait for all of the nodes to finish at
  once, and track which nodes never finish. Retry those nodes again by
  rebooting. The number of retries is configurable in the script, and
  is currently set to one. This should take care of some PXE boot
  related problems, although obviously not all.

* Got rid of -w option to os_load and made waitmode the default. The
  -s option can be used to start a reload, but not to wait for it to
  complete.

* Minor changes to sched_reload and reload_daemon; pass in -s option
  to os_load.

a '-n' option to use netdisk, and will respond properly to changing
TB_DEFAULT_RELOADTYPE in libdb.

os_load also got some fixes for the -w flag when used with Frisbee - it fires
off all nodes at once, rather than two at once.

TB_IMAGEID_READINFO - I was mistaken about the level of access implied
by TB_IMAGEID_ACCESS.

reloads for nodes in an experiment.
Change os_load to schedule a default image reload whenever a mereuser
loads an image that is not the default image for that node type.
Add some support stuff in libdb (TBSetSchedReload) and some constant
definitions for sched_reload and for nodelog.

	Usage: os_load [-s | -w] [-r] [-i <imageid>] <node> [node ...]
        Usage: sched_reload [-f | -p] [-r] [-i <imageid>] <node> [node ...]

The imageid is now an optional argument. After continually forgetting
what imageid to use, or just plain forgetting the argument, and having
it try to load imageid pc53 on pcXX, I decided this interface was
bogus. With now imageid, select the default imageid for each node
provided. This is actually convenient since you can load multiple
types of nodes in one shot.

1.13, but had somehow gone unnoticed until now.

to contain a list of reloads currently in processes. It is filled by
os_load, and is cleared out by the tmcd 'reset' command or by nfree.
The tmcd 'loadaddr' command now uses this table instead of the reloads table.

Also added Frisbee support to sched_reload, and changed the Frisbee command
line option to os_load to '-r' to avoid a conflict with sched_reload's '-f'
option.

switch to try it out. The main thing missing at this point is a way to tell
frisbee _which_ disk image to load - it will load whichever image there
happens to be a server running for.

Change occurrences of "@TESTMODE@" back to @TESTMODE@ like they were supposed to be in the first place...

Lots of small changes for turning our 'require lib*' lines into 'use lib*' lines. Proper modules declare themselves as a package, and use Exporter to export the names of the subroutines that should be visible from the outside world. Many of ours didn't do that, it was just a file with a bunch of subs in it. So now I've fixed many of them to be proper, and removed the requires and 'push(@INC,...)' hacks and changed it to the proper 'use lib @prefix@/lib/;' and use lib*.

groups (or 2 right now) and then wait for them to finish before moving
to the next group. This is to aid in issuing a mass reload, but not
causing the network to meltdown. Will all change with Frisbee of
course, but this will help Matt Dorsch out.

Added testmode. Won't update the database for netdisking, and won't reboot nodes. Will update partitions table as if the change had already happened.

Will be fixed later with addition of next_boot_osid.

repetition and clutter. Mostly a visual and convenience thing. I plan
to work through other scripts as time permits.

hopefully get bigger and reduce the amount of typing that we all
do. I hacked up sched_reload and os_load to use it. Pretty simple to
start with.

I'm not planning to go much further on this until we sync up with the
dbtoir branch since it will just create needless branch merge errors.

replaced by the "images" table. New os_info table is added. New web
pages to add and delete OSIDs to/from the os_info table, for use in
the NS file. tb-create-os is gone. handle_os no longer operates on the
tbcmds file, and no longer writes anything into the ir file. Moved the
setting up of os state (nodes table) from os_setup to handle_os, where
it should be. os_load and sched_reload now take a single argument, the
name of the imageid from the images table.

mere users. os_load and os_setup reworked to use node_reboot.

(or was it months)?

what names map to what IPs on what networks on what planets.

see something like either wd0 or wd0:s1 or wd0:s1a. This is to keep
the command line parsing simple in the face of allowing multiple loads
at a time on the command line.

the testbed list.

now, but don't actually do anything with the node. Leave that to
user to run the os_load script.