GitLab

- unbounded record time
- stats dump (by stdout) with USR1 signal

Need to delete latter after ~2 weeks.

that got mangled in last rev.

Also ensure DHCP is enabled on all connected interfaces.  Otherwise tmcc will fail.

boots up before attempting to reboot/reload the firewalled nodes.  Previously,
we would just let them beat their collective heads against the wall, PXEing
over and over, waiting for the firewall to come up.

hardwiring to 6 minutes.  Not using it yet, but it is there for the future.

Got rid of some more shark code.

* When adjusting the latency on very low bandwidth links, lets use 98
  bytes for the number of bytes on the wire. Where did 82 come from?

* Attempt to deal with session routing failures. Reworked the test
  code to do multiple trials (when session routing is active) in the
  hopes that routes will stabilize soon after trying to actually use
  the routes. Currently trying a second trial, with a delay of 60
  seconds + (0.25 * numberofnodes). I have no experimental basis for
  this number!

and a few other tweaks.  Also bumped parallelism from 10 to 25 rsyncs
at a time.

Add pid/eid to subject line of virtual node failure notification message.

Add a bit of additional output info, and fix a little bug in rc.inplab

event groups.

GNUmakefile: install camwce script (turns on SCSI write-cache) in freebsd MFS
slicefix: allow default= and label= names to start with a digit

Um, yeah, update the interfaces and widearea_nodeinfo tables too when a plab
node's attributes change.  Duh..  DB fixed up.

actual counts.

and now also tbres!

("correctly" here meaning "don't go down in flames", not "we should never
save the state of vnodes", that will have to be revisited)

Slice renewal updated to work with new PLC API.  Emulab-created plab slices
are no longer in danger of falling out from under our users!

Added the ability to use an "exceptions" file.

Added the ability to avoid starting new experiments if an experiment
failed to swapout and the ability to avoiding swapping out an
experient on unexpected failures.

Ignore a couple of plab nodes with duplicate MAC addrs until they are fixed.
These nodes won't be available for allocation in the meantime.

A few fixes for plab.

assign_wrapper:

Assign unique sshd port numbers.  This was only being done for pcvms for some
reason.

libplab.py:

Make 'nobody' the contact uid for newly createed plab nodes (instead of
Brent Chun).

rc.inplab"

Create /local/logs inside plab vservers.

The actual dump routine still needs to be added.

Updates to to Error Logging API Code.

You should start seeing much better error messages coming from my
system.  Errors coming from parse.proxy and assign (the two most
frequent sources of errors) should now be concise and to the point.
Errors coming from libosload/libreboot (the next most frequent source
of errors) should now also be much better, but not perfect.  Getting
perfect errors will likely a rework of how errors are handled in
libosload/libreboot, just adding tberror/tbwarn/tbnotice calls is not
enough.  I can do this at a latter date if necessary.

A few minor database changes.

Some changes to the API.  A few bug fixes. Lots of tberror/tbwarn/tbnotice
added to scripts.

Since assign is a C program, and at this time my API is perl only, I wrote a
second wrapper around assign, assign_wrapper2.  When assign fails errors are
now parsed in assign_wrapper2, sent to stderr and logged.  This means that
RunAssign() just returns when assign fails rather than echoing some of
assign.log output and then quiting.  The output to the activity log remains
unchanged.

Since "parse.proxy" is run from ops I couldn't use my API in it, even though
it is a perl program.  Instead I parse the errors coming form it in
parse-ns.

into the main NS files via the "source" command, and stuffing them
into the experiment archive.

would be no big deal, except that we want to retain user_stats for
deleted users, and rather then a deleted_user_stats table, I want to
retain stats for deleted users in the user_stats table, since that
is a more natural place for them.

The main problem is that we use the login (uid) as the cross table
reference slot all over the DB, which is fundamentally incorrect, if
we want to be able reuse uids and still know what historical data
refers to.

So, I have taken a few baby steps towards weaning us off the uid, and
towards permanently unique key for users, using the unix_uid integer
for now, but probably something slightly different later.

The user_stats is now indexed on this new key (called uid_idx in the
users_stats table) instead of the plain uid.

The unix_uid slot in the users table is no longer an auto_increment
field, but instead uses the emulab_indicies table for the next
available index.

(actually just stats gathering right now, no images are produced)