GitLab

if its equal to bossnode.

down on the amount of password file churning by adding new accounts
from the watchdog, but not updating mundane stuff like the gecos and
group list, except via the explicit push from emulab. Eventually this
needs a more complex solution to avoid more work than necessary,
probably by some batch queuing system that handles updates to nodes
that are down.

have checked in some other file with that long comment.

list of pubkeys per user from doaccounts. pub keys are stored in
the user_pubkeys table in the database. Currently, doaccounts is the
version support winner, with different return values for all 5
versions!

Added 1.75% zoom, made "more details" zoom to 1.75% (rather than 1.50%)

First, remove references to the IP columns, since those are now gone.

Second, we now support a "magic node" that is assumed to be equivalent
to the TBDB_WIDEAREA_LOCALNODE (ususally boss). Updates for the magic
node are also applied to the localnode. Right now, this magic node is
hardcoded in this script, on the assumption that no one but us will
ever use this script. But, we could move it to a configure variable or
even the DB if we need to.

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.