1. 03 Oct, 2016 1 commit
  2. 26 Sep, 2016 1 commit
  3. 22 Sep, 2016 2 commits
  4. 15 Sep, 2016 1 commit
  5. 14 Sep, 2016 1 commit
  6. 07 Sep, 2016 1 commit
  7. 01 Sep, 2016 1 commit
  8. 29 Aug, 2016 3 commits
  9. 09 Aug, 2016 1 commit
  10. 27 Jun, 2016 1 commit
  11. 24 Jun, 2016 1 commit
    • Leigh Stoller's avatar
      Change "genesis" to "portal" what the hell was I thinking when I · 040ea3be
      Leigh Stoller authored
      picked genesis. But this change actually has content; we need to
      distinguish between classic projects and emulab portal projects
      (new projects created via the portal, and used via the portal).  For now
      these are distinct until we decide to bring everyone up to the new
  12. 23 Jun, 2016 2 commits
  13. 17 Jun, 2016 1 commit
  14. 16 Jun, 2016 1 commit
  15. 10 Jun, 2016 3 commits
  16. 06 Jun, 2016 2 commits
  17. 27 May, 2016 1 commit
  18. 26 May, 2016 1 commit
  19. 25 May, 2016 1 commit
    • Gary Wong's avatar
      Add future reservations and admission control. · 294fade1
      Gary Wong authored
      Right now this is strictly advisory.  In particular, swap-ins go through
      the normal path and are NOT forced to comply with admission control
      wrt future reservations; therefore, reservations don't yet come with
      any guarantees at all.
  20. 24 May, 2016 1 commit
    • Mike Hibler's avatar
      Modify to include two additional user-related fields. · 5e6a83bd
      Mike Hibler authored
      Add a "last activity" timestamp indicating the last time the user was
      known to interact with Emulab by logging into the portal, logging into
      a node or performing some other activity that resulted in their home
      directory being exported (this latter may be dumb, not sure yet).
      This should provide additional information about whether a user is really
      using Emulab or is just someone who was in a project once and maybe
      graduated and moved on.
      Added a canonical "location" string to identify the user's home city.
      This is the "formatted name" returned by the Google Maps API call
      (with commas replaced by semicolons to prevent issues with CSV export
      of the data). This field is intended to be a canonical rendition of the
      city/state/country info the user enters.
      That script was also modified to include users that are "frozen" or
      "archived" by default. Unfortunately, just because they are in those
      states now, does not mean they were during the desired time range.
      Emulab keeps no indication of when they might have changed state.
      The new -U option can be used to elide records for users that we have
      determined were not active during the time range (i.e., their "last
      activity" timestamp above is before the indicated start time.
  21. 23 May, 2016 1 commit
  22. 18 May, 2016 1 commit
  23. 17 May, 2016 2 commits
  24. 16 May, 2016 1 commit
    • Leigh Stoller's avatar
      Deal with a corner case bug; if a node is already allocated to an · 17f3b0e5
      Leigh Stoller authored
      experiment in the project, but without a prereserve setting, then set the
      pre-reserve (as per Mike's request a few months back). But also need to
      check that if the node is allocated to the project, and it does have a
      pre-reserve, that pre-reserve must actually match the project and have the
      right reservation name.
  25. 29 Apr, 2016 1 commit
  26. 12 Apr, 2016 1 commit
  27. 11 Apr, 2016 2 commits
  28. 06 Apr, 2016 1 commit
  29. 25 Mar, 2016 1 commit
  30. 24 Mar, 2016 1 commit
    • Leigh Stoller's avatar
      # If NOT revoking the reservation, then we need to leave the reserved_pid · d4c4df64
      Leigh Stoller authored
          # set, but we have to do something with the reservation_name since we
          # need to be able to reuse the reservation name in a new one. We cannot
          # clear it, since a NULL reservation_name means it was reserved via the
          # web interface and not allowed to be messed with by the pre-reservation
          # code. Look at Node::CheckPreReserve() to see what I mean. So instead,
          # we set it to something not likely to be an actual reservation name.
      Another solution might be to actually set the reservation_name to the name
      of the administrator when using the web interface. That would provide some
      extra info, and remove this odd corner case above.
  31. 23 Mar, 2016 1 commit