1. 30 Jul, 2008 1 commit
  2. 27 Jun, 2008 1 commit
  3. 13 Jul, 2007 1 commit
  4. 12 Jul, 2007 1 commit
    • Russ Fish's avatar
      Check that the inner elab db schema isn't out of date wrt the outer one, · b54ae4da
      Russ Fish authored
        since we import a bunch of dumped db state from the outer to the inner db.
        Added/removed columns in the schema misalign row data, causing much chaos.
      
      tbsetup/elabinelab.in - Dump and send the outer db schema with the db state.
        Runs mysqldump just like schemacheck does.
      
      tmcd/common/config/rc.mkelab - Add the schema check using schemadiff.
      
      utils/schemadiff - Add an option to ignore table creates and drops.
      b54ae4da
  5. 17 May, 2007 1 commit
  6. 23 Apr, 2007 1 commit
  7. 02 Mar, 2007 2 commits
  8. 21 Feb, 2007 2 commits
  9. 12 Feb, 2007 1 commit
  10. 16 Jan, 2007 1 commit
  11. 12 Jan, 2007 1 commit
  12. 11 Jan, 2007 1 commit
  13. 10 Jan, 2007 1 commit
  14. 04 Dec, 2006 1 commit
  15. 29 Nov, 2006 1 commit
    • Leigh B. Stoller's avatar
      Keith Sklower's changes to support a single control network model for · 08737f67
      Leigh B. Stoller authored
      ElabInElab experiments, so as not to consume an interface.
      
      I actually modified Keith's changes so that we can dynmaically choose
      the single or dual model in the NS file (Keith's changes hardwired the
      system to only single control network) since the single network model
      has the disadvantage of not allowing new nodes to be added to an inner
      elab, which would make it impossible to test some things (like the
      newnode path!).
      
      To choose the single control network model, place this in your NS file:
      
      	tb-elabinelab-singlenet
      
      other it defaults to the older dual network model.
      08737f67
  16. 24 Oct, 2006 1 commit
  17. 20 Oct, 2006 2 commits
    • Mike Hibler's avatar
      ac91d0f3
    • 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
  18. 21 Jun, 2006 2 commits
  19. 15 Jun, 2006 2 commits
  20. 14 Jun, 2006 2 commits
  21. 12 Jun, 2006 2 commits
  22. 09 Jun, 2006 2 commits
  23. 05 Jun, 2006 1 commit
  24. 10 Apr, 2006 2 commits
  25. 06 Mar, 2006 1 commit
  26. 02 Mar, 2006 1 commit
  27. 26 Feb, 2006 1 commit
  28. 24 Feb, 2006 1 commit
    • Leigh B. Stoller's avatar
      Two main changes: · be69c6e4
      Leigh B. Stoller authored
      * Add mailman to the install process. This includes the package
        install, all the setup needed in ops-install, and the little patches
        we apply locally.
      
        Note: Only under 6.0: no point in going backwards since its a pain
        in the ass to build these packages for the 4.10 image.
      
      * Push more of the package install back down into the ops/boss install
        scripts. This improves testing within those scripts, and avoids
        duplication. There are some changes in rc.mkelab that will temp
        mount the package dir on /packages for the benefit of the scripts.
      be69c6e4
  29. 22 Feb, 2006 1 commit
  30. 21 Feb, 2006 1 commit
  31. 17 Feb, 2006 1 commit