GitLab

  - Added "LIBAUDIT_FANCY" option to AuditStart.  When this option is
    used libaudit will send a different email than it normally sends,
    and on error call tblog_find_error() to determine the error.

  - Also add audit function AddAuditInfo which adds add additional
    information for libaudit to use in SendAuditMail when AUDIT_FANCY
    is set.

  - Modify template_swapin, template_instantiate, and template_create
    to use the new audit functionality.

  - Suppressing calling tblog_find_error and sending the error email
    when auditing in swapexp and batchexp

tblog changes:

  - Shorten the message sent to the user when the error in unknown.
    Remove all parts about lack of free nodes as it no longer really
    applies as tblog now correctly identified those errors and handles
    them separately.  The message is now just "Please look at the log
    below to see what happened."

  - Improve algo. used to determine the other error when canceled.
    Will now work by removing all errors related to the cancel request
    and the essentially rerunning tblog_find_error.  If the cause of
    the error is still canceled, repeat and try again until the cause
    is something other than canceled or no errors are left.

  - Refactor tblog_find_error, which involves creating new internal
    functions: tblog_determine_single_error, tblog_store_error,
    tblog_dump_error

  - Add section on Primary vs Secondary Errors to the inline POD
    documentation.

  - Other minor enhancements and bug fixes.

This forces all metadata values to be plain text values for now.

consistent and easy to use.

Add better explanation for the hack to get around "(in cleanup) Can't
call method "FETCH" on an undefined value..." in libdb.pm

Fix warning in spewconlog:
        (in cleanup) Can't call method "FETCH" on an undefined value at /usr/local/lib/perl5/site_perl/5.8.8/mach/Mysql.pm line 91 during global destruction.
and probably other places.

so the rules for checking the values based on the type were not being
applied. This allowed Eric to select a TID that was not valid later
when it was used as an eid.

instantiate and start run page. Hover over the parameter name ...

variables are setup before writing them!

term archiving of firstclass objects like users, projects, and of
course templates.

* Projects, Users, and Groups are now uniquely identified inside the
  DB by a index value that will not be reused. If necessary, this
  could easily be a globally unique identifier, but without federation
  there is no reason to do that yet.

* Currently, pid, gid, and uid still need to be locally unique until
  all of the changes are in place (which is going to take a fairly
  long time since the entire system operates in terms of those, except
  for the few places that I had to change to get the ball rolling).

* We currently archive deleted users to the deleted_users table (their
  user_stats are kept forever since they are indexed by the new index
  column). Eventually do the same with projects (not sure about
  groups) but since we rarely if ever delete a project, there is no
  rush on this one.

* At the same time, I have started a large reorg of the code, to move
  all of the user, group, project code into modules, both in php and
  perl, turning them into first class "objects" (as far as that goes
  in php and perl). Eventually, the number of query statements
  scattered around the code will be manageable, or so I hope.

* Another related part of this reorg is to make it easier to move the
  new user/project/group code in the perl backend so that it can be
  made available via the xmlrpc interface (without duplication of the
  code).

Added a utility which will take two netmond files, and a log file, and generate tri-colored xplots of them. This correlates offered load seen by the stub and the monitor, and the bandwidth figures sent by the stub to the monitor.

various template operations to get lost. Also fixed the code in
mungelog.js that was supposed to handle bailing out if there was no
response from the server in a reasonable amount of time; if that code
had been working, no one would have even noticed all the other problems!

Also some cleanup in parts of mungelog.js and showlogfile_sup.php3;
slowly migrating parts of this to emulab_sup.js since we use some of
the same code in other places.

Now must add attributes as well.

same view, instead of always to the vis view. Also, change the
template graph generator to append &show=graph so that when you click
on a template in the graph, you got to that template, but stay in the
graph view.

rather than the wifiX VAP device that findif reports.

yesterday (or was it the day before?).

This loses the --ignore-failed-read option, which is only in GNU tar.

like the layout of our partition table.

on filesystems that are case insensitive!

the virtual interface name given the tmcc-returned ifconfig info.  tmcc
just returns the physical interface underlying a virtual interface, so it
is no good for setting up, e.g., the gated config.

This is needed for multiplexed links which use tagged VLANs as their
implementation.  For these links, it is possible at initial swapin time
that the VLAN tag has not been setup in the DB by the time we query it.
So if we get back a 0 tag, we sleep awhile and try again.

is a member is 'ipv4' then we report the control net IP rather than the
(non-existent in this case) experimental net IP.

ipv4 protocol is only used in PELAB to group planetlab nodes into a LAN so
that link tracing can be performed.  Now these nodes in this LAN will be able
to name each other as "planet-1", etc.

than we can physically make on the switches.

Give explicit widths to integers in sql/tbreport.sql as per Keith
Sklower:
  The sql/tbreport.sql file does not have the same width of integers
  as database_create.sql.  This causes schema_check to burp when you have
  updgraded an existing database, but at least the output can be fed back in.

datatypes. This should keep me busy for a long time!

would kill capserver.  This would happen during nmap scans.

  Make an attempt to discover what the error was before an swap-* was
  canceled, if any.  Both the main error (canceled) and the other error
  are stored in the error table.  To support this a new column in the
  error table is added "rank".  The primary error has a rank 0 while the
  other error has a rank 1.

  Make an attempt to determine when an error is a "me too" error or the
  real cause of the problem.  "Me too" errors are errors which are
  generally reported when the callie script determined that the caller
  script fails.  The caller script should have reported the error, but
  in some cases the error didn't make it into the database.  Thus if a
  "me too" is reported as the cause of a "swap-*" more info is needed to
  determine the true cause.  When a "me too" error is reported it is
  followed by a "..." on it's own line.  It is also recorded in the
  errors table under the new column "need_more_info".

  Add inferred column to the errors table.  This is the same value as
  the inferred variable in tblog_find_error.

  Add revision column to errors table to make it easy to tell which
  algorithm was used to determine the error.

to talk to bgmon to accelerate data collection.  Also handle the 1.0
PLR rates that are recorded in the DB to indicate down links.

across from the Contact link.

Yep, want to encourage more use of flyspray for reporting bugs and
requesting features. Maybe not possible but lets try!