1. 16 Jan, 2002 4 commits
  2. 14 Jan, 2002 1 commit
  3. 10 Jan, 2002 5 commits
  4. 08 Jan, 2002 1 commit
  5. 07 Jan, 2002 1 commit
  6. 28 Dec, 2001 1 commit
  7. 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
  8. 21 Dec, 2001 1 commit
  9. 17 Dec, 2001 2 commits
  10. 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
  11. 05 Dec, 2001 1 commit
    • Leigh B. Stoller's avatar
      Minor changes to convert delays from ints to floats in the DB. Chris · cab46455
      Leigh B. Stoller authored
      did the lanlink change. assign_wrapper does not really need any
      changes at all, but I dropped a comment in. The only real change is
      needed in the client side to convert a floating point from tmcd, into
      an int to give to ipfw. Rather cheesy too, given that Perl does not
      have a real conversion function (int() truncates).
      cab46455
  12. 30 Nov, 2001 2 commits
  13. 29 Nov, 2001 1 commit
  14. 27 Nov, 2001 1 commit
  15. 20 Nov, 2001 1 commit
  16. 09 Nov, 2001 2 commits
  17. 06 Nov, 2001 2 commits
  18. 05 Nov, 2001 1 commit
  19. 02 Nov, 2001 3 commits
  20. 01 Nov, 2001 5 commits
  21. 31 Oct, 2001 1 commit
    • Leigh B. Stoller's avatar
      A bunch of backend delay node changes. Change the delays DB table to · fe13d60f
      Leigh B. Stoller authored
      hold separate values for each of the two pipes. This allows us to
      treat the links asymmetrically with respect to the delay node
      configuration. Changes to tmcd to return the expanded info, and rework
      (completely) delay_config to allow user to change the duplex
      characteristics (just like before), or just simplex characteristics by
      specifying the pipe number. By convention (I invented) pipe 0 is
      traffic coming in on iface0. Of course, none of the front end stuff
      has been changed, so the changing a single pipe does not cause
      anything in virt_lans to be changed, so those changes will be lost at
      swapout. Also get rid of all the ssh'ed pipe config stuff in
      delay_config. Instead, add a client side script called update_delays
      to /etc/testbed on the experiment nodes. After updating the delays
      table, just ssh over and run that script, which calls the existing
      code. Less distribution of knowledge.
      fe13d60f
  22. 29 Oct, 2001 1 commit
  23. 16 Oct, 2001 1 commit