1. 07 Jan, 2010 1 commit
  2. 06 Jan, 2010 6 commits
    • Leigh B. Stoller's avatar
    • Leigh B. Stoller's avatar
      Minor fix. · b11f7ab4
      Leigh B. Stoller authored
    • Leigh B. Stoller's avatar
      Tweak comment. · f730349e
      Leigh B. Stoller authored
    • Leigh B. Stoller's avatar
      Run xmllint over the rspec in GetTicket. Return the XML errors. · 7046b6c3
      Leigh B. Stoller authored
      Change all the test scripts to print the errors.
    • Leigh B. Stoller's avatar
    • Leigh B. Stoller's avatar
      Slice expiration changes. The crux of these changes: · 5c63cf86
      Leigh B. Stoller authored
      1. You cannot unregister a slice at the SA before it has expired. This
         will be annoying at times, but the alphanumeric namespace for slice
         ames is probably big enough for us.
      2. To renew a slice, the easiest approach is to call the Renew method
         at the SA, get a new credential for the slice, and then pass that
         to renew on the CMs where you have slivers.
      The changes address the problem of slice expiration.  Before this
      change, when registering a slice at the Slice Authority, there was no
      way to give it an expiration time. The SA just assigns a default
      (currently one hour). Then when asking for a ticket at a CM, you can
      specify a "valid_until" field in the rspec, which becomes the sliver
      expiration time at that CM. You can later (before it expires) "renew"
      the sliver, extending the time. Both the sliver and the slice will
      expire from the CM at that time.
      Further complicating things is that credentials also have an
      expiration time in them so that credentials are not valid forever. A
      slice credential picks up the expiration time that the SA assigned to
      the slice (mentioned in the first paragraph).
      A problem is that this arrangement allows you to extend the expiration
      of a sliver past the expiration of the slice that is recorded at the
      SA. This makes it impossible to expire slice records at the SA since
      if we did, and there were outstanding slivers, you could get into a
      situation where you would have no ability to access those slivers. (an
      admin person can always kill off the sliver).
      Remember, the SA cannot know for sure if there are any slivers out
      there, especially if they can exist past the expiration of the slice.
      The solution:
      * Provide a Renew call at the SA to update the slice expiration time.
        Also allow for an expiration time in the Register() call.
        The SA will need to abide by these three rules:
        1. Never issue slice credentials which expire later than the
           corresponding slice
        2. Never allow the slice expiration time to be moved earlier
        3. Never deregister slices before they expire [*].
      * Change the CM to not set the expiration of a sliver past the
        expiration of the slice credential; the credential expiration is an
        upper bound on the valid_until field of the rspec. Instead, one must
        first extend the slice at the SA, get a new slice credential, and
        use that to extend the sliver at the CM.
      * For consistency with the SA, the CM API will changed so that
        RenewSliver() becomes RenewSlice(), and it will require the
        slice credential.
  3. 05 Jan, 2010 9 commits
  4. 29 Dec, 2009 3 commits
  5. 28 Dec, 2009 2 commits
  6. 23 Dec, 2009 6 commits
    • Robert Ricci's avatar
      Bugfix: tell getopt not to ingore case · ab749191
      Robert Ricci authored
    • Leigh B. Stoller's avatar
      A couple of changes that attempt to cut short the waiting when · 28ac96a5
      Leigh B. Stoller authored
      a node has failed.
      * In the main wait loop, I check the eventstate for the node, for
        TBFAILED or PXEFAILED. Neither of these should happen after the
        reboot, so it makes sense to quit waiting if they do.
      * I added an event handler to libosload, specifically to watch for
        nodes entering RELOADSETUP or RELOADING, after the reboot. Because
        of the race with reboot, this was best done with a handler instead
        of polling the DB state like case #1 above. The idea is that a node
        should hit one of these two states within a fairly short time (I
        currently have it set to 5 minutes). If not, something is wrong and
        the loop bails on that node. ÊWhat happens after is subject to the
        normal waiting times.
      I believe that these two tests will catch a lot of cases where osload
      is waiting on something that will never finish.
    • Robert Ricci's avatar
      Add a -T option that lets you test on a branch other than master · d26eab09
      Robert Ricci authored
      Fix a problem with the -h flag - I was forgetting to exit()
    • Robert Ricci's avatar
      Add an option for 'extra' command line args to be passed to 'git show' · 1c8d87dd
      Robert Ricci authored
      so that I can add '-p' (show patch) to my public repository.
      Also, fixed up an existing config option that had a character
      illegal for 'git config' (underscores are not allowed).
    • Ryan Jackson's avatar
      Fixes for git-cvspush and modified cvsexportcommit · efded17a
      Ryan Jackson authored
      Make git-diff-tree generate more context (8 lines).
      Also, keep track of the last commit successfully pushed to CVS and start
      there when doing a cvspush if the local repo is up to date.  This should
      prevent duplicate commits and allow new commits to be pushed before the
      central Git repo is updated from CVS.
    • Leigh B. Stoller's avatar
      Minor fix to previous commit. · f9f745ec
      Leigh B. Stoller authored
  7. 22 Dec, 2009 13 commits