GitLab

purpose, and avoid confusion with the current_reloads table.

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.

experiment so that Rob will stop stepping on the test version I
keep installing :-)

scripts and move to libdb (hardwired in one place of many!).

hwdown!

From the comment before the doreset funciton:

If next_pxe_boot_path is set, clear it. Otherwise, if next_boot_path
or next_boot_osid is set, clear both along with next_boot_cmd_line.
If neither is set, do nothing. Produces no output to the client.

Manages the launching of new frisbee servers, and recording the
addresses the use in the database. If called for an image that is
already associated with a running server, exits quitely. Otherwise,
registers the new server's address and goes into the background, waiting
for the frisbee server to die so that it can unregister the address.

to load its disk image. The reloads table is used to determine which image the
node is supposed to load. The appropriate address is then pulled from the
load_addres field of the images table.

This done in preparation for frisbee support.

the connection handshake. If the capture is active, it is going to
write status and close the socket on its end, which may or may not be
propogated back to the client side before/after/during the
sysread/syswrite. I guess that a miserable way of saying there is a
lot of asynchrony involved.

pass. Also change doaccounts to return the homedir, since that will
match what we return in the mounts command.

reload that will get picked up by the reload daemon instead of being
fired off immediately. The node is reserved to reloadpending EID,
which the reload daemon looks for. This is useful since until Frisbee
is fully operational, we cannot do mass reloads, so this approach
results in all the nodes getting reserved away and slowy reloaded and
freeed up later.

Remove the name of 'boss.emulab.net' as a tiny security measure.

second rack is essentially done.

Added better MB-recommend to also hopefully improve synchronization.

Added real CRC-32 checksums, to replace "fake" add-bytes-together
checksums.

firing off an os_load, just move the node from its current reservation
to emulab-ops/reloadpending. This moves the operation out of band from
the user's perspective (he gets more immediate response when an
experiment ends, and besides we cannot handle mass reloads anyway, and
so this approach is unusable until Frisbee.

Change the reload_daemon to look for free nodes that need a reload (as
before) *and* nodes in emulab-ops/reloadpending (as put there by nfree).
In this case, the imageid comes from the reloads table instead of the
node-types table. I also updated the reload_daemon to use libdb routines.

Also change testbed/reloading to emulab-ops/reloading. Maybe someday
I'll remove these hardwired strings.

remove these hardwired strings.

Also went over references to FreeBSD 4.0 and RedHat 6.2, and changed them
to 4.3 and 7.1 as appropriate

have been added as OSIDs so that the parser accepts them. os_setup
maps them into whatever equiv OSID is loaded on the target node,
according to the OS slot of the osid table entry. If no mapping can be
made (no equiv OS loaded, as defined by the partitions table) os_setup
fails. I've also changed the web page node control form so that the
only OSIDs you can set for a node are the ones loaded (partitions
table) or OSKit kernels (osid table entry has a path).

where UID==EUID so that perl is not unhappy about a setuid script
being invoked when EUID!=UID.