1. 28 May, 2007 1 commit
    • Leigh Stoller's avatar
      Implement two requests by Eric: · e12ea1e2
      Leigh Stoller authored
      * The checkout directory now includes just the datastore directory and
        tbdata/nsfile.ns. This removes a bunch of clutter.
      
      * You can now run template_commit in any subdir of a checkout; the
        python wrapper will crawl upwards looking for the .template file.
      
        Note that I removed the option that allowed you to do a commit from
        the template tree in /proj/pid/templates since that directory will
        ultimately go away (or at least hide from view), and cause it
        conflicted with the new option and I didn't want to make things any
        messier for no reason.
      e12ea1e2
  2. 24 May, 2007 1 commit
  3. 23 May, 2007 2 commits
    • Leigh Stoller's avatar
    • Leigh Stoller's avatar
      First cut at template checkout and commit from a checkout. The interface · b674bc7b
      Leigh Stoller authored
      described is the one exported to ops via the XMLRPC interface. This is
      just playing aroundl no doubt this stuff is going to change.
      
      * template_checkout guid/vers
      
        Checkout a copy of the template to the current working directory.
      
      * template_commit
      
        Modify the previous template checkout, using the nsfile contained in
        the tbdata directory (subdir of the current directory). In other words,
        the current template is modified, creating a new template in the
        current working directory (the current directory refers to the new
        template).
      
        The datastore subdir is imported into the new template, but that is
        the only directory that is imported at present. Might change that.
      
      So this sounds much cooler then it really is. Why?
      
      * This only works from ops.
      
      * The "current directory" must be one of the standard approved directories
        (/proj, /users, /groups).
      
      * Cause, boss reads and writes that directory via NFS, as told to it
        by the xmlrpc client.
      
      At some point in the future it would be nice to support something
      fancier, using a custom transport, but lets see how this goes.
      b674bc7b
  4. 18 May, 2007 1 commit
  5. 17 May, 2007 2 commits
  6. 16 May, 2007 1 commit
  7. 15 May, 2007 4 commits
    • David Johnson's avatar
      1fadb8ca
    • Leigh Stoller's avatar
      Symlink trick to deal with the fact that we switched to archiving the · d4bcc494
      Leigh Stoller authored
      entire experiment directory, which now that we zip files, was putting
      thinks in the wrong place.
      d4bcc494
    • David Johnson's avatar
      Add comon data to its own table so that we can use it in joins. Add · 13c6cc7e
      David Johnson authored
      nodehist metrics to their own table for the same reason.
      13c6cc7e
    • Leigh Stoller's avatar
      Checkpoint changes that have been discussed in the last few weeks: · c4f53202
      Leigh Stoller authored
      * Records are now "help open" when a run is stopped. When the next run
        is started, a check is made to see if the files
        (/project/$pid/exp/$eid) have changed, and if so a new version of the
        archive is committed before the next run is started.
      
      * Change the way swapmod is handled within an instance. A new option
        on the ShowExp page called Modify Resources. The intent is to allow
        an instance to be modified without having to start and stop runs,
        which tends to clutter things up, according to our user base. So, if
        you are within a run, that run is reset (reused) after the swapmod is
        finished. You can do this as many times as you like. If you are
        between runs (last operation was a stoprun), do the swapmod and then
        "speculatively" start a new run. Subsequent modifies reuse the that
        run again, as above.
      
        I think this is what Kevin was after ... there are some UI issues
        that may need to be resolved, will wait to hear what people have to
        say.
      
      * Revising a record is now supported. Export, change in place, and
        then use the Revise link on the ShowRun page. Currently this has to
        happen from the export directory on ops, but eventually allow an
        upload (to correspond to downloaded exports)
      
      * Check to see if export already exists, and give warning. Added a
        checkbox that allows user to overwrite the export.
      
      * A bunch of minor UI changes to the various template pages.
      c4f53202
  8. 11 May, 2007 2 commits
  9. 09 May, 2007 1 commit
  10. 08 May, 2007 1 commit
  11. 07 May, 2007 3 commits
  12. 03 May, 2007 2 commits
  13. 30 Apr, 2007 1 commit
  14. 26 Apr, 2007 3 commits
  15. 25 Apr, 2007 7 commits
  16. 24 Apr, 2007 2 commits
  17. 23 Apr, 2007 1 commit
  18. 20 Apr, 2007 1 commit
  19. 19 Apr, 2007 2 commits
  20. 17 Apr, 2007 1 commit
  21. 16 Apr, 2007 1 commit