1. 05 Aug, 2003 3 commits
    • Leigh Stoller's avatar
      The rest of the sync server additions: · 212cc781
      Leigh Stoller authored
      * Parser: Added new tb command to set the name of the sync server:
      
      	tb-set-sync-server <node>
      
        This initializes the sync_server slot of the experiment entry to the
        *vname* of the node that should run the sync server for that
        experiment. In other words, the sync server is per-experiment, runs
        on a node in the experiment, and the user gets to chose which node
        it runs on.
      
      * tmcd and client side setup. Added new syncserver command which
        returns the name of the syncserver and whether the requesting node
        is the lucky one to run the daemon:
      
          SYNCSERVER SERVER='nodeG.syncserver.testbed.emulab.net' ISSERVER=1
      
        The name of the syncserver is written to /var/emulab/boot/syncserver
        on the nodes so that clients can easily figure out where the server
        is.
      
        Aside: The ready bits are now ignored (no DB accesses are made) for
        virtual nodes; they are forced to use the new sync server.
      
      * New os/syncd directory containing the daemon and the client. The
        daemon is pretty simple. It waits for TCP (and UDP, although that
        path is not complete yet) connections, and reads in a little
        structure that gives the name of the "barrier" to wait for, and an
        optional count of clients in the group (this would be used by the
        "master" who initializes barriers for clients). The socket is saved
        (no reply is made, so the client is blocked) until the count reaches
        zero. Then all clients are released by writting back to the
        sockets, and the sockets are closed. Obviously, the number of
        clients is limited by the numbed of FDs (open sockets), hence the
        need for a UDP variant, but that will take more work.
      
        The client has a simple command line interface:
      
          usage: emulab-sync [options]
          -n <name>         Optional barrier name; must be less than 64 bytes long
          -d                Turn on debugging
          -s server         Specify a sync server to connect to
          -p portnum        Specify a port number to connect to
          -i count          Initialize named barrier to count waiters
          -u                Use UDP instead of TCP
      
          The client figures out the server by looking for the file created
          above by libsetup (/var/emulab/boot/syncserver). If you do not
          specify a barrier "name", it uses an internal default. Yes, the
          server can handle multiple barriers (differently named of course)
          at once (non-overlapping clients obviously).
      
          Clients can wait before a barrier in "initialized." The count on
          the barrier just goes negative until someone initializes the
          barrier using the -i option, which increments the count by the
          count. Therefore, the master does not have to arrange to get there
          "first." As an example, consider a master and one client:
      
      	nodeA> /usr/local/etc/emulab/emulab-sync -n mybarrier
      	nodeB> /usr/local/etc/emulab/emulab-sync -n mybarrier -i 1
      
          Node A waits until Node B initializes the barrier (gives it a
          count).  The count is the number of *waiters*, not including the
          master. The master is also blocked until all of the waiters have
          checked in.
      
          I have not made an provision for timeouts or crashed clients. Lets
          see how it goes.
      212cc781
    • Leigh Stoller's avatar
      c7157a2f
    • Leigh Stoller's avatar
      A couple of robots changes. · 0121e3fe
      Leigh Stoller authored
      * Change Home page title to: Emulab - Network Emulation Testbed Home
      
      * Change mainsite robot meta tags to include a description, set to the
        same as the new home page title above.
      
      * Remote now sites get standard "noindex" robot directive; crawlers will
        follow links on remote sites but not index them in their search engines.
      
      * Add a fixed link to www.emulab.net/netemu.php3 on all sites; used to
        be on mainsite only; that was dumb!
      
      * Minor cosmetic changes to netemu.php3.
      0121e3fe
  2. 04 Aug, 2003 11 commits
  3. 01 Aug, 2003 6 commits
  4. 31 Jul, 2003 4 commits
    • Leigh Stoller's avatar
      Some minor perf tweaks requested by Mr Zippy: Reduce the amount of · 9f6fbfb1
      Leigh Stoller authored
      syslogging to a fraction of its former self. Actually, its mostly been
      moved under if (verbose) tests. Instead, just syslog the number of
      bytes returned for each request.
      
      Added a signal handler to change the verbosity of a running tmcd.
      To turn on verbosity:
      
      	kill -USR1 `cat /var/run/tmcd.pid`
      
      To turn off verbosity:
      
      	kill -USR2 `cat /var/run/tmcd.pid`
      
      You can send the signal to individual children, but that would be
      silly and pointless.
      9f6fbfb1
    • Leigh Stoller's avatar
      Add Mike's NFS/NULL mount changes to mkjail.pl · 5b16105a
      Leigh Stoller authored
      Also a couple perf hacks:
      
      * Local vnodes can start with the password/group file from the
        physnode, since locally they will be the same anyway. This avoids a
        blizzard of accounts requests at startup, which is by far the
        biggest chunk of data returned (well, except for host tables).
      
      * To help serialize boot startup, vnodesetup now waits for the jail to
        finish starting up before it exits. It does this via a "goofy"
        mechanism I will not bother to describe.
      5b16105a
    • Leigh Stoller's avatar
      Add DBDIR def to paths. · 1c28424e
      Leigh Stoller authored
      1c28424e
    • Kirk Webb's avatar
      Minor changes: · 073c9473
      Kirk Webb authored
      1) Use libtb's reporting funcs rather than my own (the former are better)
      2) Produce more informational "malformed interface record" errors.
      073c9473
  5. 30 Jul, 2003 11 commits
  6. 29 Jul, 2003 5 commits