GitLab

queries..

This uses the pxe booted freebsd kernel and MFS. In addition, I use
the standard testbed mechanism of specifying a startup command to
run, which will do the imagezip to NFS mounted /proj/<pid>/.... The
controlling script on paper sets up the database, reboots the node,
and then waits for the startstatus to change. Then it resets the DB
and reboots the node so that it returns back to its normal OS. The
format of operation is:

	create_image <node> <imageid> <filename>

Node must be under the user's control of course. The filename must
reside in the node's project (/proj/<pid>/whatever) since thats the
directory that is mounted by the testbed config software when the
machine boots. The imageid already exists in the DB, and is used to
determine what part of the disk to zip up (say, using the slice option
to the zipper). Since this operation is rather time consuming, it does
the usual trick of going to background and sending email status later.

Fix up the print statements so that DOS slice numbering is consistent.
Remove a few printfs that were not under the debug flag.

and produces a ns file that will produce an identical topology to the one
stored in the DB.  It does not keep virtual ports the same but does map IP
addresses to connections correctly.  I.e. the topology is the same even
though the virt_nodes table differ slightly.

defaulting to sockets based first. This is handy cause we oftern want
to talk to a real tty device (like the power controllers).

subdirectories are now accounted for.

which is primarily supported by NSF grant ANI-00-82493 and Cisco
Systems.

at the tutorial section describing the node_reboot command.

good thing to do, but no longer does. Anyway, this fixes some problems.

since have no pubs here.

via the dhclient script in FreeBSD, and the pump "script" directive in
Linux.

Fixed some warnings in assign_wrapper that were subsequently caught.

exitonwarn is a library that, when used in a script, causes it to exit 255
when warnings are sent.  It still shows all warnings, just does an ugly
perl hack to error on script termination.

fixing a bug in the debugging output.

delay nodes for 10Mbit links.  This last feature is currently disabled
until we get the backend in place to set port speeds.

to avoid a blizzard of reboots all at once. This might solve the
problem of sharks rebooting okay, but failing to become proper members
of the testbed. A good thing to do in any event, especially with
people trying to run 50 node experiments. The reason for 8 of course
is that I want to isolate each shelf (after sorting the list). I pause
15 seconds between each shelf, and 10 seconds between each batch of 8
pcs.

place. As an added bonus, it will optionally split out the shelf and
unit number and return them in reference variables provided. Returns
0/1 exit status either way.

"skip" region so that you can have an unknown slice anyplace on the
disk and it will just look like a free region to be skipped over.

1. 'tb-set-hardware ... shark' and 'tb-set-hardware ... dnard' are now
functionally identical.  Previously only the former worked but both passed
the parser.

2. Assign will now exit very quickly in the case that, for a given virtual
nodes, there are no physical nodes that could match in type.  This should
never happen as the parser and assign_wrapper have checks that usually
prevent this.  However, in the case of problems in the code (such as #1)
this'll make it easier to debug.  In addition, as we add more types of
nodes and our estimates becoming increasingly inaccurate cases where this
might occur could slip in.  All calling code treats this identically to an
'insufficient resources' failure.

plastic. Useful for when plastic reboots, although it needs to be
run from paper of course. We should probably set up some kind of
reboot utility for when plastic reboots, since when capture fires up,
the "acl" files are all in the wrong group/mode. On the other hand,
this shared file based permission scheme is going to end up changing
anyway soon, since it won't work when the serial lines are on other
machines. Will need a tip permserver at that point.

of pty/tty based (since they have several annoying problems
associated). Note that permission is granted via the use of an "acl"
file; /dev/tip/machine.acl, which must be set to the group of the
project the node is in, so the user can read out the process id number
and the random bits that are used by capture to grant permission to
use (tip sends the random bits across first thing). This handshake is
due to change to a request/challenge scheme as described by Dave in
email to the testbed list.

RedHat