1. 02 Apr, 2003 1 commit
  2. 01 Apr, 2003 1 commit
    • Leigh B. Stoller's avatar
      Two unrelated changes. 1) Return the email address to version 9 · 4fa870b7
      Leigh B. Stoller authored
      clients so they can create a proper .forward file. 2) Add some
      test code for seeing how feasible it is to do accounts on ops/tips
      using tmcd instead of direct ssh. Initial results are not good; too
      many accounts; does not scale well. Going to need a smarter protocol
      for doing hundreds of accounts, but I will leave this code in place
      for now. Note, unlike testbed nodes, control nodes must connect with
  3. 24 Mar, 2003 1 commit
    • Leigh B. Stoller's avatar
      Bumb remote tmcc timeout to 30 seconds. · 42757a0c
      Leigh B. Stoller authored
      Add better timeout handling code to tmcc, which watches for progress
      instead of just dumping after the timeout. This lets really slow
      connections proceed okay, but still timeout out if nothing happens at
      This new tmcc has been installed into the sup trees for WIDE and RON.
  4. 14 Mar, 2003 2 commits
  5. 03 Feb, 2003 1 commit
  6. 06 Jan, 2003 1 commit
  7. 19 Dec, 2002 1 commit
    • Leigh B. Stoller's avatar
      Path changes (as discussed in other commit messages). All of the files · f389da45
      Leigh B. Stoller authored
      created by libsetup are now created in /var/emulab/boot; nothing is
      written into /etc/emulab or /usr/local/etc/emulab anymore. This was
      a requirement for jails, but is also a good thing to do anyway.
      There are a number of jail config changes to support the old vnodes
      and the new style jail vnodes; specifically, a setup routine to called
      from inside the jail when it first boots up to the get the usual
      assortmant of config info from tmcd. Also Merge local and remote
      update routines into one. Other various little changes for SFS and the
  8. 05 Dec, 2002 1 commit
  9. 11 Nov, 2002 1 commit
  10. 06 Nov, 2002 1 commit
    • Shashi Guruprasad's avatar
      NSE related changes: · 05bc3bd4
      Shashi Guruprasad authored
        - Fixes the routing problem
        - A new type "sim" has been created but not in the DB. node_types and
          nodes remain unchanged. This will change after we figure out how
          to represent in the DB the local multiple virtnodes in one phynode case
          The frontend tb_compat.tcl adds the sim type and ptopgen associates
          a huge number of sim nodes to all local PCs.
        - All simulated nodes go into one pc untill I finish coding the distributed
          nse case. Also, sim nodes go through assign but with an explicit
          "fix-node" directive in the top file. A random free pc is chosen using
          the avail script in assign_wrapper. If we don't fix node it, assign
          maps sim nodes to multiple phy nodes even when a valid all to one
          mapping is possible.
        - Syntax for nse:
         $ns make-simulated {
             set simnode1 [$ns node]
             set simnode2 [$ns node]
         The old syntax
         set nsenode [$ns nsenode]
         $nsenode make-simulated {
         is deprecated
        - All 38 frontend tests in the testsuite pass
        - A new table v2pmap has been added to handle multiple virt nodes to
          one phy node mapping. This is used in "tmcc hostnames" currently.
        - The phy node that is picked to run nse is loaded with a custom image
          FBSD45-NSE . This can use the default FBSD kernel if there is a mechanism
          to run at 1000HZ, have options IPFIREWALL_FORWARD and PERFMON turned on.
          The image is in the 'testbed' group. Do not delete this image.
        - Static routes now adds routes for the case dst == nexthop. The routing
          graph would be disconnected otherwise and I need to traverse this in
          assign_wrapper for nse. On the client side, such a route is filtered out in
        - sim nodes are also correctly visualized
  11. 20 Sep, 2002 1 commit
  12. 11 Sep, 2002 1 commit
  13. 10 Sep, 2002 1 commit
  14. 27 Aug, 2002 1 commit
  15. 21 Aug, 2002 1 commit
  16. 20 Aug, 2002 3 commits
  17. 19 Aug, 2002 2 commits
  18. 16 Aug, 2002 1 commit
  19. 29 Jul, 2002 1 commit
    • Leigh B. Stoller's avatar
      A wide array of little changes to improve the distribution of the · f066d2d9
      Leigh B. Stoller authored
      client software to widearea nodes. Most of these changes were to
      reduce the embarrassment factor. At some point we need a proper
      autoconf and such, but for now there is a makefile in the src dir for
      creating the distribution.
      I've tested it on a local linux node and mostly on a freebsd node, but
      I've moved things around and so updating the RON nodes will require
      some hand intervention by me at some point.
  20. 07 Jul, 2002 1 commit
  21. 21 Jun, 2002 1 commit
  22. 19 Jun, 2002 1 commit
    • Leigh B. Stoller's avatar
      Lots of changes. · 33254ef8
      Leigh B. Stoller authored
      * Add ability to control timeout when invoking tmcc, and whether to
        fatally die if tmcc fails. Related change was to allow more options
        to be passed into tmcc by way of an additional options argument.
      * Change to pubkey handling. tmcd now returns a list of pubkeys for
        each login. The entire list is written to the authkeys files, and
        the old is backed up (with mod time preserved).
      * tmcd now returns a serial number for each use to indicate when
        user info has changed (via the web pages). Only users with updated
        serial numbers get modified (and new authkeys file created). This
        should vastly reduce the passwd/authkeys churning on the ron nodes,
        which periodically check for account updates. The little db file now
        records the serial number too.
      * Change to os_usermod; Change the actual password string! Was not
        doing that before.
      * Conditionalize all the tmcc.foo stuff that Shashi added; don't want
        any of this on remote nodes yet.
      * Remove a bunch of printfs to reduce output clutter.
  23. 31 May, 2002 1 commit
  24. 21 May, 2002 1 commit
  25. 16 May, 2002 1 commit
  26. 15 May, 2002 1 commit
  27. 14 May, 2002 3 commits
  28. 08 May, 2002 2 commits
    • Leigh B. Stoller's avatar
    • Leigh B. Stoller's avatar
      Support for vnodes, plus some other changes: · 386c2778
      Leigh B. Stoller authored
      1) Merge in the accounts code that I did for ron. Instead of resetting
         the password file on each reboot, look at the node status to
         determine if the password/group file should be reset. If the
         node is free, reset it. Otherwise, we track changes to the password
         and group file now, so that users can change it and not have their
         changes wiped out at each reboot. I had to do this for the ron
         nodes so that the testbed software would not alter or delete
         already existing accounts; I keep a couple of little dbm files
         listing all the accounts/groups added. The only downside right now
         is if a node is reallocated before it is wiped clean; I plan to add
         an os_teardown phase to experiment termination asap.
      2) Add tunnels support. New DB table (tunnels) provides information
         for running vtund to link up to remote nodes. Creates a vtund.conf
         file on the fly, and fires them off. The complication is that you
         cannot do the ifconfigs or the routes until the tunnels are
         connected, so that stuff has to be configured within the vtund.conf
         file on a per tunnel basis. vtund.conf has some sections for
         running commands when tunnels are brought up or down.
      3) Damage the routing configuration code that Mike did. To support
         tunnels, as noted above, rc,route is no longer a simple list of
         commands, but a program that adds/dels routes based on the netmask,
         with a special "enable" section for the other stuff. This allows me
         to call it from vtund.conf for up/down on each tunnel'ed
         interfaces, as needed. Quite gross, but no way around it.
      4) For remote nodes, add a vnodesetup script, invoked from boss when
         experiments are setup/torndown. This gets the tunnel/route/trafgen
         configuration and runs them. It then goes into the background
         waiting for a death signal, at which time it brings them down and
         cleans out the vnode state.
  29. 16 Apr, 2002 1 commit
  30. 15 Apr, 2002 1 commit
  31. 03 Apr, 2002 2 commits
  32. 29 Mar, 2002 1 commit