GitLab

script that checks the database to see if local or remote. The problem
with this is that the ssh syntax makes it hard to determine the host
name by inspection. Would need to parse all the ssh args (bad idea),
ot work backwards and try to figure out the difference between the
command (which is not a string but a sequence of args) and the host
and the preceeding ssh args. Hell with that! Changed sshtb to require
a specific -host argument. Read the args and look for it. Error out of
not found, to catch improper usage.

The moral of this update: "sshtb [ssh args] -host <host> [more args ...]

to 4!). Add option to convert between multiplex mode and real node
mode. Also change code to make sure that dead nodes are not
considered, nor node that are allocated or have no free virtual nodes.

changes that have to go in now!

boss.

regen the ssh key if its missing. If there is still an authorized_keys
file, cat the new identity.pub onto the end of the authorized_keys
file.

experiment table fields that hold the solver weights that are set by
the user in the front end with the tb-set-wasolver-weights command.

state to REBOOTING, and then wait for the ISUP state to be set.  This
change reflected in the clientside startup scripts on remote nodes,
that now issues a REBOOTED event, and then an ISUP event after
everything is setup properly.

conditionalized on isadmin() status. These pages were mostly
overlapping anyway, and the nodecontrol_list.php3 page was done more
cleanly. No point in all the duplication. Dropped the Node Control
menu item from the list.
Add explicit "widearea" view to get remote nodes in their own page,
instead of listed after all the PCs. Also some minor formatting
changes.

project list for each user, do one big query for all users at the
beginning of the script.
Also some minor format changes.

watchdog at the moment, but it will be. Right now it does boot time
stuff; issues tmcc state event so the testbed knows (REBOOTED), does
an account update to get any accounts missed while dead, then sets up
and vnodes (tunnels and such) that where supposed to be running on
the node, then issues a tmcc ISUP event.

After that, goes into a loop doing periodic account update. At some
point it would be good to look for stale vnodes (that could not be
torn down because of network connectivity problems), but there are
some race conditions that I need to work out first.

node reboots. Currently, starts the watchdog daemon.

instead of account update. Doing an account update at boot is nice,
but hardly sufficient.

instead of waiting. This option used by new watchdog daemon that
runs on the RON nodes. No point in waiting if another is already
happening.

more thought, so just leave the directories.

files are generated.

	tb-set-wasolver-weights delay bw plr

Where I am told proper defaults are 1, 10, 500. Setting any to zero
effectively drops that metric from consideration when the solver runs.
I've updated the tb_compat files and the documentation.

each link.

Now, the problem with running tbreport on experiments that have
wide-area links, but are not swapped in, should _really_ be fixed.

 - Make configurable options specifiable on the command line (idle
   time, packets/hour, "freshness" time).
 - Check how fresh our data is, and mark it as stale if it is old.
 - Add display options. Default is show only inactive, swappable, non-stale.
   Use -s flag to show stale expts too, and -u flag to show unswappable
   ones. (-s and -u display whether they're active or not)
 - Changes in the database optimized the queries for me, so instead of
   taking 10-15 seconds to run, it now takes 1.
See usage (idlecheck -h) for more info.
We're now ready to put this in a cron job and in idle view of the expt
listing web page.

experiments early enough.

Then, switched to using the new TBWideareaNodeID call so that we can
report links that go between RON nodes and the testbed properly.

Also, made a new message, seperate from "No data available" for vnodes
that are on the same physical node, or that seem to be at the same
site.

returns the node ID that should be used in the widearea_* tables.
This is mainly so that we don't have to hardcode 'boss' as the local
representative in too many places (all local node are assumed to
have the same network characteristics as boss.)

with tb-set-wasolver-weights.

Properly detect and report failures while trying to start slothd, and remove the lock file before trying to start it if it isn't running.

that batch system will not be confused.

Return an error if a negative weight is passed to -1, -2, or -3.
Also, interpret negative values of minrounds as zero.
Also, interpret any negative value for maxrounds as -1.