1. 26 Jan, 2006 13 commits
    • Robert Ricci's avatar
      Fix a problem with data reporting - make sure it gets printed at · fde58889
      Robert Ricci authored
      intervals of exactly QUANTA.
      
      However, it's my view that having stubm and stubd seperate is a bad
      idea, since one is basically a copy of the other. They should be
      merged back together so we don't have to fix the same bugs in both
      places.
      fde58889
    • Leigh B. Stoller's avatar
      Add some initial configure stuff for the pelab subdir, so I get my · 6c6d1a69
      Leigh B. Stoller authored
      GNUmakefile auto generated.
      6c6d1a69
    • Robert Ricci's avatar
    • Russ Fish's avatar
      0a1e6400
    • Kevin Atkinson's avatar
      · 05015359
      Kevin Atkinson authored
      Merged in changes from tblog-2-branch:
      
                Move parts of libtblog into libtblog_simple.  Libtblog simple
                provided the basic logging functions but doesn't touch anything.
                Moreover including libtblog_simple doesn't automatically start
                the logging subsystem.  It also doesn't have testbed dependencies
                which mean 1) it can be used in the core testbed libraries (such
                as libdb, libtestbed) without introducing a circular dependency
                and 2) can be used independently.
      
                Reworked DBFatal and DBWarn to use tblog.  It will still email
                testbed-ops, however.
      
                Make use of the "cause" field to determine the cause of the bug.
                In particular tblog_find_error will look at the value of this
                field and report the "cause".  In the future different actions
                can be taken based on the ultimate "cause" of the bug, such as if
                testbed-ops should be notified.
      
                Change format of Error Message reported by libtblog.  As per the
                email "Format or Error Messages" ro testbed-dev.
      
                Have libtblog use its own Database handle to avoid problems with
                locked tables.
      
                Also set DBCONN_MAXTRIES to 3 for most important queries.  For
                queries that are not important don't send mail on error.
      05015359
    • Timothy Stack's avatar
    • Timothy Stack's avatar
      For the real NS parser, simulate the way raw object names work in the · f91efbbe
      Timothy Stack authored
      testbed parser.  For example, in:
      
        set node [$ns node]
      
      The "set" creates a variable named node, but the testbed parser also
      renames the object to be "node".  Doing a similar rename is hard in
      the real NS parser since we have to change any existing references to
      the object.  Instead, we dynamically create a procedure with the name
      that forwards methods to the actual object.
      
      And so, the corrupting of my soul continues.
      f91efbbe
    • Russ Fish's avatar
      Tweak route setup retry logic. · 5693f7de
      Russ Fish authored
      5693f7de
    • Timothy Stack's avatar
    • Timothy Stack's avatar
      · 4b938465
      Timothy Stack authored
      Some pelab/plab event system hacks.
      
      	* event/lib/event.h, event/lib/event.c: Add event_subscribe_auth
      	which lets you specify whether any authentication should be done
      	for events received through this subscription.
      
      	* event/sched/event-sched.c: Handle EVPROXY objects.  Add a
      	separate subscription for EVPROXY UPDATE events for each plab
      	pnode (which might be too many...).  Also, need to update the EXPT
      	field for events received through a noauth subscription so the
      	proxies can figure out which experiments are active.
      
      	* lib/libtb/tbdefs.h, lib/libtb/tbdefs.c: Add UPDATE event defs.
      
      	* xmlrpc/emulabserver.py.in: Inject __plab_setup and
      	__plab_teardown timelines into the eventlist when an experiment
      	has plab nodes.  The __plab_setup timeline sends EVPROXY UPDATE
      	events to each physical node while the __plab_teardown sends
      	EVPROXY CLEAR events.  The __plab_setup timeline is run when the
      	scheduler starts up, the __plab_teardown isn't run automatically
      	yet.
      4b938465
    • Leigh B. Stoller's avatar
      Minor cleanup to the menu. · 726ac4ab
      Leigh B. Stoller authored
      726ac4ab
    • Leigh B. Stoller's avatar
      Re-expose linktest ... · a80649b8
      Leigh B. Stoller authored
      a80649b8
    • Timothy Stack's avatar
      Add EVPROXY event_objecttype · 0e4c30e0
      Timothy Stack authored
      0e4c30e0
  2. 25 Jan, 2006 14 commits
  3. 24 Jan, 2006 4 commits
  4. 23 Jan, 2006 9 commits