1. 06 Jan, 2006 5 commits
  2. 05 Jan, 2006 7 commits
  3. 04 Jan, 2006 7 commits
  4. 03 Jan, 2006 4 commits
  5. 02 Jan, 2006 5 commits
  6. 30 Dec, 2005 6 commits
  7. 29 Dec, 2005 1 commit
  8. 28 Dec, 2005 3 commits
    • Mike Hibler's avatar
      Stop relying on return code of $ssh as an indicator of success/failure/timeout. · 272cb767
      Mike Hibler authored
      What ssh returns in the case of a timeout depends on timing, and since we
      started using sshtb, even the check for a timeout return code wasn't working.
    • Leigh Stoller's avatar
      A fair number of changes. · 564d958d
      Leigh Stoller authored
      * The rest of the backend support for simplistic experiment duplication,
        either from an existing (current) experiment, or from a specific
        archive revision of a current or terminated experiment.
      * Rework the swapmod code so that the archive is committed at the exact
        end of the swapout phase. This required adding (and moving) some code
        from swapexp to tbswap sine that is where the actual swapout/swapin
        happens during a swapmod
      * Add a special directory called "archive" to the experiment
        directory, which is a place where users can store stuff they want
        saved away. This will eventually be a user defined set of
        directories, but this was good for getting the basic mechanism in
        place. Note that the when the contents of this directory are copied
        out for placement into the archive, it is an exact copy made with
      * No longer "clean" the contents of the temporary store between
        commits of the archive. This was creating a lot of headaches, and
        was also causing the revision history to get messed up. The downside
        of this is that we have to be more careful to explicitly delete
        files that the user no longer uses. I have not solved all these
        issues yet, so in the meantime files will get left in the archive
        even if the user no longer references them.
    • Leigh Stoller's avatar
      More "Duplicate Experiment" support, enabled for STUDLY() users only. · 9c8ddc33
      Leigh Stoller authored
      This change displays the tags and pointers to the Archive matching
      the experiment history and provides a "run" button to check out the
      NS file from an earlier run and turn that into a new experiment. Still
      very primitive.
  9. 27 Dec, 2005 2 commits
    • Mike Hibler's avatar
      Update some. · 3edbaf45
      Mike Hibler authored
    • Mike Hibler's avatar
      More tightly connect the notion of a firewall and the security level. · f1206314
      Mike Hibler authored
      If you specify an explicit firewall, you are implicitly assigned security
      level 2 and you cannot explicitly specify the security level.  Likewise,
      if you specify a security level, you cannot also specify a firewall.
      The reason for this is that security level 1 (aka "Blue") now has a slightly
      different meaning.  It is intended for protecting the inside from the outside
      rather than visa-versa.  The only practical implication of this is that for
      level 1, we don't do all the fancy power-off-boot-into-MFS-zapbootblock stuff
      that we do for higher levels.
      Anyway, I wanted to make sure that if you specify your own firewall, you
      DO have to go through the full cleansing swapout since we can't trust a
      firewall that the Average Joe sets up.