1. 24 Sep, 2018 1 commit
    • David Johnson's avatar
      Fix an IsFeasible bug where start and end of different reservations overlap. · a7089186
      David Johnson authored
      When IsFeasible processes the list of events (i.e. reservation
      start/end, expt start/end), it processes them in sorted order of event
      time, but if times are equal, there is no secondary sort, and thus the
      additive (incoming) reservation might be processed before the reductive
      (outgoing) reservation), which would create a false negative hole in the
      forecast.  This commit adds the secondary sort.
      a7089186
  2. 18 Jun, 2018 1 commit
    • Leigh Stoller's avatar
      Add automated cancellation of reservations that are not used: · 67a0e58e
      Leigh Stoller authored
      * If unused at six hours, schedule for cancel in three hours and send
        email.
      
      * If reservation becomes used within those three hours, rescind the
        cancellation.
      
      * Add an override bit so that cancel/uncancel on the command line
        supercedes (so explicit cancel or rescinding a cancel, means do not
        make any more automated checks for unused).
      
      * Rework cancel to be more library friendly.
      67a0e58e
  3. 08 Jun, 2018 1 commit
  4. 04 Jun, 2018 1 commit
  5. 01 Jun, 2018 1 commit
  6. 31 May, 2018 1 commit
  7. 30 May, 2018 5 commits
    • Leigh Stoller's avatar
      Bug fix. · 5d264a32
      Leigh Stoller authored
      5d264a32
    • Leigh Stoller's avatar
      Minor fixes to previous revision(s). · 428d54d3
      Leigh Stoller authored
      428d54d3
    • 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
    • Leigh Stoller's avatar
      Improve stringify function. · 0547bdab
      Leigh Stoller authored
      0547bdab
    • Leigh Stoller's avatar
      More changes to reservation history; since these are history tables, · bf26c03b
      Leigh Stoller authored
      need uid_idx and pid_idx. Also store the cancel date.
      
      Fix bug; we were not storing a history entry for deleted reservations,
      so we lost all those entries even though they were reservations that
      were used.
      bf26c03b
  8. 23 May, 2018 1 commit
  9. 10 May, 2018 1 commit
  10. 02 Apr, 2018 2 commits
  11. 29 Mar, 2018 1 commit
    • Leigh Stoller's avatar
      Reservations system changes: · df90d7a7
      Leigh Stoller authored
      1) Rework so that instead of relying on swapin__last + autoswap timeout,
         set expt_expires for classic experiments at the beginning of swapin
         time. This is cause swapin_last is not set till the end of swapin,
         and so during swapin the res system is in an inconsistent state since
         there is no way to determine when the experiment ends.
      
      2) On the Geni path, simplify expiration handling; do not allow a slice
         modification and expiration change at the same time; the bookkeeping
         and failure rollback is a pain, especially wrt reservation system,
         and this rarely ever actually happens, so get rid of a lot of
         complication.
      df90d7a7
  12. 30 Jan, 2018 2 commits
  13. 12 Jan, 2018 1 commit
  14. 02 Jan, 2018 2 commits
  15. 01 Jan, 2018 1 commit
    • Leigh Stoller's avatar
      Changes to reservation system wrt classic interface: · dc90a087
      Leigh Stoller authored
      1. Reservation system now groks experiment lockdown and swappable. When
         swapping in, lockdown and swappable mean the expected end of the
         experiment is never.
      
      2. Reservation library now handles changes to lockdowm, swappable, and
         autoswap (timeout). editexp now hands these changes off to a new
         script called manage_expsettings, which can be called by hand since
         we might need to force a change (I am not changing the classic UI, if
         a change is not allowed by the res system, we have to do it by hand).
      
      3. Minor fixes to reservation library.
      dc90a087
  16. 30 Nov, 2017 2 commits
  17. 27 Nov, 2017 1 commit
  18. 19 Nov, 2017 1 commit
  19. 13 Oct, 2017 3 commits
  20. 11 Oct, 2017 1 commit
  21. 21 Sep, 2017 1 commit
  22. 08 Aug, 2017 1 commit
  23. 04 Aug, 2017 1 commit
  24. 27 Jul, 2017 1 commit
  25. 24 May, 2017 2 commits
  26. 17 May, 2017 1 commit
  27. 09 May, 2017 2 commits
  28. 08 May, 2017 1 commit