All new accounts created on Gitlab now require administrator approval. If you invite any collaborators, please let Flux staff know so they can approve the accounts.

  1. 11 Feb, 2019 1 commit
  2. 08 Feb, 2019 4 commits
    • Leigh B Stoller's avatar
      Changes to the snapshot modal as discussed on 1/21/2019: · 1de19201
      Leigh B Stoller authored
      * When the profile is script based, we cannot update the profile code,
        so do not show any choices (radios), proceed as image only.
      * Remove the "new profile" (3rd) option, it appears that no one at the
        meeting knew what that was about, so clearly mere users won't. Simplify!
      * Rearrange the options (whole disk, account), together at the bottom.
      * Swap the description and the image name inputs.
      * Cleanup the help popovers and impl.
    • Leigh B Stoller's avatar
      Another set of changes for new geni-lib parameters. · 59259db3
      Leigh B Stoller authored
      * Use an emulabfeature to control what projects use the new ppwizard and
        geni-lib code. The feature is applied to the profile's project, since
        who is instantiating and what project it is instantiated into, does
        not really matter, the incompatible changes are also associated with
        the profile.
      * Run both versions of the ppwizard side by side, and flip between them
        when the user is using the profile picker.
      * The new version of geni-lib is /usr/testbed/opsdir/lib/,
        we tell the genilab jail to use that directory when on the new path.
      * All of this is temporary.
    • Leigh B Stoller's avatar
      Checkpoint new geni-lib param code, working on making it selectable · dedc6495
      Leigh B Stoller authored
      via emulab features, for testing.
    • Leigh B Stoller's avatar
      Fix to Jacks constraint stuff: · 3c5e82d6
      Leigh B Stoller authored
      Problem: A user with a reservation at one cluster, was trying to start
      an experiment at a different cluster. But after selecting the other
      cluster and clicking next, that selection was being reset to the cluster
      with the reservation, as part of our overly helpful cluster picker code,
      which is fired off in a callback from Jacks.
      Question: Why is that happening when clicking next, to go from the
      Finalize step to the Schedule step, thus silently resetting the user's
      Reason: There is a call to SwitchJacks("small") to make sure that the
      small version of the topo was visible, in case the user goes back to the
      finalize step. Not sure why ... but in any event, every call to
      SwitchJacks(large|small) results in Jacks firing that callback, and
      resetting the user's cluster choice.
      Solution: Null out the callback when calling SwitchJacks().
      There is probably a better solution to this, perhaps as part of a code
      reorg on the entire instantiate page, which has grown many appendages
      over time.
  3. 07 Feb, 2019 1 commit
  4. 04 Feb, 2019 1 commit
  5. 01 Feb, 2019 3 commits
  6. 07 Jan, 2019 1 commit
  7. 02 Jan, 2019 1 commit
  8. 13 Dec, 2018 1 commit
  9. 12 Dec, 2018 3 commits
  10. 06 Dec, 2018 4 commits
  11. 30 Nov, 2018 1 commit
  12. 28 Nov, 2018 2 commits
  13. 27 Nov, 2018 1 commit
  14. 14 Nov, 2018 2 commits
  15. 08 Nov, 2018 2 commits
  16. 05 Nov, 2018 2 commits
    • Leigh B Stoller's avatar
      Changes to how we handle/report mapping failures that also fail the · 11074445
      Leigh B Stoller authored
      empty testbed test.
      Prior to this commit, we were not invoking the empty testbed case
      consitently. Now we do, but that exposed another problem; reporting that
      to the error to the Portal in a meaningful way. Basically, we can report
      a different error code for an impossible to map error, but then we lose
      the info we store now about what the actual failure was (which we show
      to the user with additional helpful info). Since we cannot (easily)
      change the Geni API for CreateSliver(), I have elected to continue the
      practice of returning the specific error codes (which also go into the
      database for long term historical info), and add more helpful text that
      for the Portal user that explains clearly that the mapping is impossible
      on the target cluster. This extra text also go into the database in the
      attached message field, so we ccan come back later and post process if
      we decide to do something different.
    • Leigh B Stoller's avatar
  17. 30 Oct, 2018 1 commit
  18. 29 Oct, 2018 1 commit
  19. 26 Oct, 2018 2 commits
    • Leigh B Stoller's avatar
      Silence the email when the certificate does not verify, we tell the user · a249493d
      Leigh B Stoller authored
      that and point them to the Geni portal to fix it.
    • 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().
  20. 24 Oct, 2018 1 commit
  21. 23 Oct, 2018 3 commits
  22. 11 Oct, 2018 1 commit
  23. 10 Oct, 2018 1 commit