GitLab

This is only a first step.  Though this is a common daemon, you still start
multiple copies, and it most likely won't handle all daemons we might want
to auto restart.

Add fix for:
  *** WARNING: batch_daemon:
  ***   dblog failed: Can't bless non-reference value at
  ***   /usr/testbed/lib/libdb.pm line 299.
which was caused by trying the blass an undefined value which is
happens when Mysql->connect failed.

These are all the pubs I could find by grep'ing through the papers, and by
attending the conference/workshops.

another ack IF at least N acks are outstanding.

Add "-archive <bool>" to $ns report which controls if "loghole
archive" is called.  Creating the archive zipfiles is redundant when
using the workbench.  It only serves to wastes space (and time when
committing then to the experiment archive).

were behaving badly. Basically, handle vtpVlanEditOperation failing.

Note: I cannot reproduce the problem, so I don't know if I've fixed
it for sure. But, my change at least does not break snmpit under
normal condidtions.

Fix intermittent one-way loss test failure.  Let bind() choose the src port in rude; any constant port like 3001 may be already in use.

In addition, current run bindings default to last run's bindings.
This is partly to address Kevin's request in FS#128 (although that
request is for the instance page).

 * allow for no server program to be run
 * allow for a program to be run on all nodes (including planet-*)
 * mods for the new improved dbmonitor

Also allow setting of use_magent=2 to indicate that it should start an
iperfd to listen for traffic on plab nodes rather than the stub.

This is in support of Jon's desire to have the stub not be a traffic
receiver.

Currently if the auto-magent.sh script is started up with the environment
variable MAGENT_NORECV set, it will use the magent option and also start
up an iperfd on what would have been the peer server port.

image. This is only for experts, and those people will be clueful
enough to ask about it anyway.

  - 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).