GitLab

trying to bring them back from the dead periodically by trying to
instantiate a vserver/vnode on them, and then tearing it down. If we
can do that, then the node is usable, and it gets moved back into the
normal holding experiment so that ptopgen will add it to ptop files.

This deamon is not turned on yet; waiting for other little bits and
pieces to be done.

There is an equiv change in os_setup that moves physnodes into hwdown
when a setup on a vnode fails.

Lbs

a little html.  Ref'ed from news page.  Installed om 9/22.

assign can attempt to spread an experimenter's nodes across sites.

tmcd (which is bad, since tying up the tmcd threads blocks all nodes
in the testbed). The old functionality is left in tmcd for now.

On the server side, a new web page (www/spewrpmtar.php3) receives a
request for a file, along with the nodeid (pcXXX) making the request,
and the secret key that is generated for each new experiment and
transfered to the node via tmcd. If the key matches, the operation is
handed off to tbsetup/spewrpmtar.in which verifies that the file is in
the list of rpm/tar files for that node, and then spits it out to
stdout. The web page uses fpassthru() to send the file out to the
client. The client is using wget, and is required to use https (the
web page checks).

At present, the external script is run as the creator of the
experiment, and gid of the experiment. Perhaps this is not a good
idea. In any event, the file must be in the list of rpm/tarfiles,
either owned by the experiment creator or with a group of the
experiment, and the file must reside in either /proj or /groups.
I use the realpath() function to make sure there are no symlink tricks
pointing to outside those filesystems. I use the standard NFS read goo to
prevent transient mount problems that we all know and love.

tmcd (which is bad, since tying up the tmcd threads blocks all nodes
in the testbed). The old functionality is left in tmcd for now.

On the server side, a new web page (www/spewrpmtar.php3) receives a
request for a file, along with the nodeid (pcXXX) making the request,
and the secret key that is generated for each new experiment and
transfered to the node via tmcd. If the key matches, the operation is
handed off to tbsetup/spewrpmtar.in which verifies that the file is in
the list of rpm/tar files for that node, and then spits it out to
stdout. The web page uses fpassthru() to send the file out to the
client. The client is using wget, and is required to use https (the
web page checks).

At present, the external script is run as the creator of the
experiment, and gid of the experiment. Perhaps this is not a good
idea. In any event, the file must be in the list of rpm/tarfiles,
either owned by the experiment creator or with a group of the
experiment, and the file must reside in either /proj or /groups.
I use the realpath() function to make sure there are no symlink tricks
pointing to outside those filesystems. I use the standard NFS read goo to
prevent transient mount problems that we all know and love.

nodetypeXpid_permissions table, since most users will be confused
to see free PCs that they cannot actually use.

This query is starting to become a bit complicated to be doing on
every page.

actually finding the youngest.

Luckily, it was not causing timeouts that were too short, only
timeouts that were too long.

causing problems.  Will investigate tomorrow.

finds that the pid returned from wait() doesn't match the one returned
from fork() earlier - this shouldn't happen, but it is.  I am checking for
errors - parhaps I'm missing something though.  This affects plabnode free
in vnode_setup since it vnode_setup doesn't fork when it runs this.

 - now creates <OBJROOT>/tmcd/plab/GNUmakefile for building the
   plab rootball from the source tree.  Not run or installed by
   default.

Updated vnode_setup to fork+exec plabnode (alloc|free) rather than invoking
it with system().  Now when the parent receives a SIGTERM from its parent
(the top-level vnode_setup), it will kill off it's plabnode child process before
exiting itself.  invocation of plabnode is now done via the plabnode()
function.  Needs some commenting.

Tested thoroughly.

 - regexp that matched the slice user wasn't working now that we're only
   looking for emulab_<exp_index>.  Witholding this change from libplab.py
   for now until we push out a new tarball with this file

A couple of quick bug fixes

 - extract/format traceback properly for email message
 - libplab.py is already disabling lin buffering for plabnode,
   so the code here to disable it has been removed.  We were led to believe
   there was a buffering problem from the plabnode scripts that were never
   actually getting killed off.

allocated to an experiment.

to the reboot all nodes option.

Also change awk scripts to exit after printing something.

server.

unbuffered.

imported lib fixes output ordering.

just print a warning and continue (don't die)

The last vnode created when a new plab node is entered into the DB is now
allocated to the special "plab-monitor" experiment where it will be used
to check the physnode's integrity.

2) Print the nodes' site, rather than our pname, in the 'hostnames'
section, with a summary of how many unique sites there were at the
top.

Current version of a file I started keeping end of last week.
Probably not complete.

fail in "plabnode alloc" or in the remote vnodesetup call. In the
former case, we do not want to "plabnode free" it later. In the later,
we want to plabnode free it right away, and make sure we do not try to
remote vnode teardown or plabfree it later. In either case, os_setup
needs to check so that it does not bother waiting for the node since
it is wasted time. I use an alternate dead state for this, but the
real solution is to move much of the vnode specific code from os_setup
to vnode_setup.

Note that this stuff is mostly untested since I need nodes to fail!
The normal path works fine though.