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. 24 Sep, 2015 1 commit
  2. 22 Sep, 2015 2 commits
  3. 17 Sep, 2015 1 commit
  4. 30 Jul, 2015 1 commit
  5. 27 Jul, 2015 1 commit
  6. 13 Jul, 2015 1 commit
  7. 10 Jul, 2015 1 commit
    • Robert Ricci's avatar
      Don't show the 'about' message for CloudLab · f1c514ed
      Robert Ricci authored
      Useless for two reasons:
      
      1) It just takes them back to a page they already had to go through to
      log in
      
      2) For some reason, it was linking the pre-release version of the site,
      before it went live, so the link was wrong anyway!
      f1c514ed
  8. 06 Jul, 2015 1 commit
  9. 02 Jul, 2015 1 commit
    • Robert Ricci's avatar
      Remove 'row' class from 'stepsContainer' · 83eef858
      Robert Ricci authored
      For some reason, the padding applied by bootstrap was causing this
      to make the container go slightly off-center. Removing this class seems
      to have no ill effects.
      83eef858
  10. 15 Jun, 2015 2 commits
  11. 28 May, 2015 2 commits
  12. 27 May, 2015 1 commit
  13. 22 May, 2015 9 commits
  14. 30 Apr, 2015 2 commits
  15. 22 Apr, 2015 1 commit
  16. 21 Apr, 2015 1 commit
  17. 10 Apr, 2015 1 commit
  18. 03 Apr, 2015 1 commit
  19. 01 Apr, 2015 1 commit
    • Leigh B Stoller's avatar
      Tighten up permissions granted to geni users coming from the GPO Portal. · 105c42e1
      Leigh B Stoller authored
      We now ask the portal for a the user's project membership list, and if the
      user is not a member of any (unexpired) projects, we do not allow them to
      create experiments (or much of anything else) in the Cloud Portal. I did
      this by setting the local holding project trust to "user" and setting the
      webonly bit in the users table. The user can use the picker to see public
      profiles, but the create button tells them no dice, go join a project at
      the GPO portal.
      
      We make the project check each time the user logs in via the trusted
      signer.
      105c42e1
  20. 31 Mar, 2015 1 commit
  21. 19 Mar, 2015 1 commit
  22. 13 Mar, 2015 1 commit
    • Leigh B Stoller's avatar
      Checkpoint various changes. · 0d09773b
      Leigh B Stoller authored
      * Various UI tweaks for profile versioning.
      
      * Roll out profile versioning for all users.
      
      * Disable/Hide publishing for now.
      
      * Move profile/version URLs into a modal that is invoked by a new Share
        button, that explains things a little better.
      
      * Unify profile permissions between APT/Cloudlab. Users now see just two
        choices; project or anyone, where anyone includes guest users in the APT
        interface, for now.
      
      * Get rid of "List on the front page" checkbox, all public profiles will be
        listed, but red-dot can still set that bit.
      
      * Return the publicURL dynamically in the status blob, and set/show the
        sliver info button as soon as we get it.
      
      * Console password support; if the aggregate returns the console password,
        add an item to the context menu to show it.
      
      * Other stuff.
      0d09773b
  23. 05 Mar, 2015 1 commit
  24. 02 Mar, 2015 1 commit
  25. 31 Jan, 2015 1 commit
  26. 30 Jan, 2015 1 commit
  27. 29 Jan, 2015 1 commit
  28. 27 Jan, 2015 1 commit
    • Leigh B Stoller's avatar
      Two co-mingled sets of changes: · 85cb063b
      Leigh B Stoller authored
      1) Implement the latest dataset read/write access settings from frontend to
         backend. Also updates for simultaneous read-only usage.
      
      2) New configure options: PROTOGENI_LOCALUSER and PROTOGENI_GENIWEBLOGIN.
      
         The first changes the way that projects and users are treated at the
         CM. When set, we create real accounts (marked as nonlocal) for users and
         also create real projects (also marked as nonlocal). Users are added to
         those projects according to their credentials. The underlying experiment
         is thus owned by the user and in the project, although all the work is
         still done by the geniuser pseudo user. The advantage of this approach
         is that we can use standard emulab access checks to control access to
         objects like datasets. Maybe images too at some point.
      
         NOTE: Users are not removed from projects once they are added; we are
         going to need to deal with this, perhaps by adding an expiration stamp
         to the groups_membership tables, and using the credential expiration to
         mark it.
      
         The second new configure option turns on the web login via the geni
         trusted signer. So, if I create a sliver on a backend cluster when both
         options are set, I can use the trusted signer to log into my newly
         created account on the cluster, and see it (via the emulab classic web
         interface).
      
         All this is in flux, might end up being a bogus approach in the end.
      85cb063b