1. 07 Jul, 2002 1 commit
  2. 21 Jun, 2002 1 commit
  3. 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.
      33254ef8
  4. 31 May, 2002 1 commit
  5. 21 May, 2002 1 commit
  6. 16 May, 2002 1 commit
  7. 15 May, 2002 1 commit
  8. 14 May, 2002 3 commits
  9. 08 May, 2002 2 commits
    • Leigh B. Stoller's avatar
      63d2612e
    • 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.
      386c2778
  10. 16 Apr, 2002 1 commit
  11. 15 Apr, 2002 1 commit
  12. 03 Apr, 2002 2 commits
  13. 29 Mar, 2002 1 commit
  14. 19 Mar, 2002 1 commit
  15. 14 Mar, 2002 2 commits
  16. 12 Mar, 2002 1 commit
  17. 01 Mar, 2002 1 commit
  18. 27 Dec, 2001 1 commit
    • Leigh B. Stoller's avatar
      Another set of group changes. As discussed in email and meetings, · 8404af03
      Leigh B. Stoller authored
      group directories are now created in a different tree than the
      the project directory so that they can be exported independently of
      the project tree to the nodes in a group experiment. The tree is
      routed at /groups on boss/users and on nodes.
      
      1. mkgroup,rmgroup,mkproj - Minor changes to reflect new group
         directory location (/groups). We leave a symlink in the old spot to
         maintain compatability, and to reduce the number of different
         directories that a person needs to worry about. So, when a group is
         made, you get a real directory /groups/pid/gid, and a symlink
         /proj/pid/groups/gid that points to the former.
      
      2. tmcd/tmcd.c - Minor change to add the additional group directory mount
         in the mounts command. Only done when pid!=gid for the experiment.
      
      3. tmcd/libsetup.pm and friends - Minor changes to fix the fact that
         mkdir does not create subdirs along the way unless the -p option is
         specified. Needed to create the local directory for the mounts
         returned by tmcd for group dirs. Pushed them out to the sup trees,
         although 6.2 images older than the most recent one are not going to
         work right. No one is using those images though, and we should just
         flush the sup trees.
      
      4. exports_setup.in - Ah, the crux of the issue. I really dislike NFS
         at this point. The original idea was to export a third set of
         directories to nodes that were part of a group experiment. Those
         nodes would get /groups/pid/gid exported, and /proj/pid read-only.
         Well, no such luck. On users, /groups and /proj are both really on
         /q, and the old restriction of mountd not allowing an IP to
         specified more than once on the right hand side for any FS, reared
         its ugly head again. As far as mountd is concerned, /q/groups and
         /q/proj are the same thing, and so it bombed when I tried to export
         them on different lines, since that meant an IP was repeated twice.
         So, I reworked exports_setup, and now for any node that is part of
         a group experiment, it gets this:
      
      	/q/proj/pid /q/groups/pid/gid -maproot=root 155.101.132.26
      
         which at least allows the individual group dirs to be protected
         from each other, but does not allow /proj/pid to be exported read
         only. Sigh.
      8404af03
  19. 13 Dec, 2001 1 commit
    • Leigh B. Stoller's avatar
      Add "routing" support with new TMCD command that looks at the · 746f32c8
      Leigh B. Stoller authored
      routertype field in the nodes table. For eventual use when Mike is
      ready with gated stuff.
      
      Modify the dohostnames stuff as per dicussion with Rob and
      Mac. Instead semi-usless node-N names, set the name of the interface
      to node-LinkName, where the linkname comes from the virt_lans table,
      and is the name of the link/lan that interface is sitting on. This way
      the user can actually figure out the interface when doing his routing
      by assigning names to all links/lans in the NS file.
      
      One major bogousity is that in order to maintain backwards
      compatability, I've instituted a new hostnames commands (hostnamesV2).
      We need a good way to deal with versioning!
      746f32c8
  20. 30 Nov, 2001 1 commit
  21. 05 Nov, 2001 1 commit
  22. 16 Oct, 2001 1 commit
  23. 24 Sep, 2001 1 commit
    • Leigh B. Stoller's avatar
      The brave new world of client side configuration. Major highlights are · cedf74ed
      Leigh B. Stoller authored
      a "cleaner" separation of the OS independent and OS dependent parts.
      Lots of stuff moved to common libsetup.pm, shared by linux and
      freebsd. OS dependent stuff is in liblocsetup.pm in the subdirs.
      Other major change was to add "update" ability so that mounts and
      accounts can be updated on the fly, when directed to do so from boss.
      This is in support of shared experiments, so that as projects are
      added to the share list, the mounts and accounts can be updated
      without having to reboot.
      cedf74ed