GitLab

stuck in the reload table!.

Frisbee, puts it in the emulab-ops/reloading experiment and runs
os_load for it, since the reload_daemon is not necessary with Frisbee.

In order for nfree to know what type of reload is desired, a new column was
added the the scheduled_reloads table, called reload_type. This gets set to
'frisbee' by sched_reload if called with the '-r' option.

nfree also now clears out the next_pxe_boot_path column for new nodes.

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.

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

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 these hardwired strings.

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*.

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.

anything (don't put an entry in the reloads table). Just exit with non
zero status to indicate that the node could not be loaded immediately.
This is for use by the reloading daemon that I am writing up.
Also did some house cleaning and removed lots of old cruft.

(or was it months)?

pid/eid before releasing from the reloads/reserve table, since an
admin initiated reload might be pending when a user does his own
load. Don't want to clear the reload state, or even worse, the
reserved state. There is a cross dependency created bewteen tmcd.c
and sched_reload on the pid/eid testbed/reloading. No biggie. I put in
a warning in both places.

the testbed list.

data in the database to be used when nfree runs.