1. 27 Nov, 2018 1 commit
  2. 08 Nov, 2018 1 commit
  3. 29 Oct, 2018 1 commit
  4. 26 Oct, 2018 1 commit
    • Leigh B Stoller's avatar
      Changes to repo based profiles: · c40bf355
      Leigh B Stoller authored
      * Respect default branch at the origin; gitlab/guthub allows you to set
        the default branch on repo, which we ignoring, always using master.
        Now, we ask the remote for the default branch when we clone/update the
        repo and set that locally.
        Like gitlab/guthub, mark the default branch in the branchlist with a
        "default" badge so the user knows.
      * Changes to the timer that is asking if the repohash has changed (via a
        push hook), this has a race in it, and I have solved part of it. It is
        not a serious problem, just a UI annoyance I am working on
        fixing. Added a cheesy mechanism to make sure the timer is not running
        at the same time the user clicks on Update().
  5. 23 Oct, 2018 1 commit
  6. 02 Oct, 2018 1 commit
  7. 01 Oct, 2018 1 commit
  8. 28 Sep, 2018 2 commits
  9. 27 Sep, 2018 1 commit
  10. 21 Sep, 2018 2 commits
  11. 17 Sep, 2018 1 commit
  12. 14 Sep, 2018 1 commit
  13. 04 Sep, 2018 2 commits
  14. 08 Aug, 2018 1 commit
    • Leigh B Stoller's avatar
      Big set of changes for deferred/scheduled/offline aggregates: · 6f17de73
      Leigh B Stoller authored
      * I started out to add just deferred aggregates; those that are offline
        when starting an experiment (and marked in the apt_aggregates table as
        being deferable). When an aggregate is offline, we add an entry to the
        new apt_deferred_aggregates table, and periodically retry to start the
        missing slivers. In order to accomplish this, I split create_instance
        into two scripts, first part to create the instance in the DB, and the
        second (create_slivers) to create slivers for the instance. The daemon
        calls create_slivers for any instances in the deferred table, until
        all deferred aggregates are resolved.
        On the UI side, there are various changes to deal with allowing
        experiments to be partially create. For example used to wait till we
        have all the manifests until showing the topology. Now we show the
        topo on the first manifest, and then add them as they come in. Various
        parts of the UI had to change to deal with missing aggregates, I am
        sure I did not get them all.
      * And then once I had that, I realized that "scheduled" experiments was
        an "easy" addition, its just a degenerate case of deferred. For this I
        added some new slots to the tables to hold the scheduled start time,
        and added a started stamp so we can distinguish between the time it
        was created and the time it was actually started. Lots of data.
        On the UI side, there is a new fourth step on the instantiate page to
        give the user a choice of immediate or scheduled start. I moved the
        experiment duration to this step. I was originally going to add a
        calendar choice for termination, but I did not want to change the
        existing 16 hour max duration policy, yet.
  15. 07 Aug, 2018 1 commit
  16. 02 Aug, 2018 1 commit
  17. 16 Jul, 2018 2 commits
    • Leigh B Stoller's avatar
      Minor fixes. · ebe4ba23
      Leigh B Stoller authored
    • Leigh B Stoller's avatar
      Image handling changes: · fe8cc493
      Leigh B Stoller authored
      1. The primary change is to the Create Image modal; we now allow users
         to optionally specify a description for the image. This needed to be
         plumbed through all the way to the GeniCM CreateImage() API. Since
         the modal is getting kinda overloaded, I rearranged things a bit and
         changed the argument checking and error handling. I think this is the
         limit of what we want to do on this modal, need a better UI in the
      2. Of course, if we let users set descriptions, lets show them on the
         image listing page. While I was there, I made the list look more like
         the classic image list; show the image name and project, and put the
         URN in a tooltip, since in general the URN is noisy to look at.
      3. And while I was messing with the image listing, I noticed that we
         were not deleting profiles like we said we would. The problem is that
         when we form the image list, we know the profile versions that can be
         deleted, but when the user actually clicks to delete, I was trying to
         regen that decision, but without asking the cluster for the info
         again. So instead, just pass through the version list from the web
  18. 10 Jul, 2018 1 commit
  19. 09 Jul, 2018 5 commits
  20. 25 Jun, 2018 1 commit
  21. 22 Jun, 2018 1 commit
  22. 21 Jun, 2018 4 commits
  23. 18 Jun, 2018 1 commit
  24. 08 Jun, 2018 1 commit
  25. 04 Jun, 2018 1 commit
  26. 31 May, 2018 1 commit
  27. 30 May, 2018 2 commits
    • Leigh B Stoller's avatar
      Web UI changes for reservations, for backend/RPC changes in 039f27b1: · 26f77c59
      Leigh B Stoller authored
      1. Show current reservations on the admin extend page (if any) for the
         user who started the experiment.
      2. Add a reservation history page, to see historical reservations for a
      3. Changes to the reservation listing page.
      4. And then the main content of this commit is that for the pages above,
         show the experiment usage history for the project and the 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.
    • Leigh B Stoller's avatar
  28. 26 Apr, 2018 1 commit