1. 20 Oct, 2006 1 commit
    • Mike Hibler's avatar
      Wow, this should make me look important! · afa5e919
      Mike Hibler authored
      Two-day boondoggle to support "/scratch", an optional large, shared filesystem
      for users.  To do this, I needed to find all the instances where /proj is used
      and behave accordingly.  The boondoggle part was the decision to gather up all
      the hardwired instances of shared directory names ("/proj", "/users", etc.)
      so that they are set in a common place (via unexposed configure variables).
      This is a boondoggle because:
      
      1. I didn't change the client-side scripts.  They need a different mechanism
         (e.g., tmcd) to get the info, configure is the wrong way.
      
      2. Even if I had done #1 it is likely--no, certain--that something would
         fail if you tried to rename "/proj" to be "/mike".  These names are just
         too ingrained.
      
      3. We may not even use "/scratch" as it turns out.
      
      Note, I also didn't fix any of the .html documentation.  Anyway, it is done.
      To maintain my illusion in the future you should:
      
      1. Have perl scripts include "use libtestbed" and use the defined PROJROOT(),
         et.al. functions where possible.  If not possible, make sure they run
         through configure and use @PROJROOT_DIR@, etc.
      
      2. Use the configure method for python, C, php and other languages.
      
      3. There are perl (TBValidUserDir) and php (VALIDUSERPATH) functions which
         you should call to determine if an NS, template parameter, tarball or
         other file are in "an acceptable location."  Use these functions where
         possible.  They know about the optional "scratch" filesystem.  Note that
         the perl function is over-engineered to handles cases that don't occur
         in nature.
      afa5e919
  2. 19 Oct, 2006 2 commits
  3. 18 Oct, 2006 4 commits
  4. 17 Oct, 2006 2 commits
  5. 16 Oct, 2006 2 commits
  6. 14 Oct, 2006 2 commits
  7. 13 Oct, 2006 3 commits
  8. 12 Oct, 2006 7 commits
    • Mike Hibler's avatar
      Same harmless typo, different file. · 2bab9559
      Mike Hibler authored
      Yes, I grepped for it everywhere this time!
      2bab9559
    • Mike Hibler's avatar
      Fix harmless typo · b1bfd91c
      Mike Hibler authored
      b1bfd91c
    • Leigh B. Stoller's avatar
      17d642ca
    • Leigh B. Stoller's avatar
    • Leigh B. Stoller's avatar
      Add debug timestamps. · dedc71cf
      Leigh B. Stoller authored
      dedc71cf
    • Leigh B. Stoller's avatar
      By popular demand, give user a choice of where to get the next set of · bb996961
      Leigh B. Stoller authored
      (initial) parameters for a new run. Three choices right now; from the
      template itself, from the instance, or from the previous run. On the
      web interface this is presented as three buttons. On ops, it is the
      the -y option, which takes one of template,instance,lastrun as its
      argument (you can of course combine the -y option with an XML file to
      override specific params).
      
      At present, there is no default. Lets give it a chance to sink in
      before I pick something that will annoy 50% of the people 75% of the
      time.
      bb996961
    • Kirk Webb's avatar
      · 471d1d26
      Kirk Webb authored
      Change the way vnode_setup handles plab nodes a bit to avoid a couple of
      buggy situations.
      
        * Don't try vnodesetup -h on plab nodes
      
      This can hang, or even fail.  Since nothing useful is conveyed by this
      step, just skip it, set the node's state to SHUTDOWN, and ask pl_conf
      on the node to remove the vserver.
      
        * Set plab node's alloc state to TBDB_ALLOCSTATE_RES_INIT_DIRTY after
          instantiation.
      
      This avoids a bug where Emulab cluster nodes fail to come up, and so
      os_setup never waits on the plab vnodes (now that they are started in
      parallel with physical node setup).  Previously their alloc state made
      them look clean, and so the vservers would not be reaped during
      teardown.
      471d1d26
  9. 10 Oct, 2006 10 commits
  10. 09 Oct, 2006 7 commits