1. 08 Jun, 2018 1 commit
  2. 04 Jun, 2018 1 commit
  3. 01 Jun, 2018 1 commit
  4. 31 May, 2018 1 commit
  5. 30 May, 2018 1 commit
    • Leigh Stoller's avatar
      Several backend/RPC changes for reservations: · 8266ae51
      Leigh Stoller authored
      1. Return current set of reservations (if any) for a user when getting
         the max extension (piggy backing on the call to reduce overhead).
      
      2. Add RPC to get the reservation history for a user (all past
         reservations that were approved).
      
         Aside; the reservation_history table was not being updated properly,
         only expired reservations were saved, not deleted (but used)
         reservations, so we lost a lot of history. We could regen some of it
         from the history tables I added at the Portal for Dmitry, but not
         sure it is worth the trouble.
      
      3. And then the main content of this commit is that for both of the
         lists above, also return the experiment usage history for the project
         an dthe user who created the reservation. This takes the form of a
         time line of allocation changes so that we can graph node usage
         against the reservation bounds, to show graphically how well utilized
         the reservation is.
      8266ae51