1. 28 Oct, 2017 1 commit
  2. 19 Apr, 2017 1 commit
  3. 17 Apr, 2017 1 commit
  4. 02 Dec, 2016 1 commit
    • Leigh B Stoller's avatar
      A couple of little tweaks to deal with slow login: · b2c05d9c
      Leigh B Stoller authored
      1. Change initial query in instantiate.php to ask for just the few
         fields we need. Profiles have rspecs and scripts, and that is a lot
         of data to return, given that the average user has access to 300+
         profiles cause of all the ones marked public.
         But in general, there is a lot going on in instantiate.php, which is
         where most users are redirected to after login, and that causes a lot
         of delay.
      2. The MotherShip uses ZFS_NOEXPORT, so when logging in we have to see
         if we have to run exports_setup. exports_setup can take anywhere from
         5-25 seconds. The login path was forcing this once a day, but in fact
         exports_setup is using a week, so lets change the test to match that.
      3. Show a soothing modal after pressing the login button to keep the
         natives happy.
  5. 29 Jul, 2016 1 commit
  6. 26 Jul, 2016 1 commit
    • Leigh B Stoller's avatar
      Add new status for users, "inactive". Mostly to support not having so · 68e019a5
      Leigh B Stoller authored
      many ZFS mounts on ops. which on the Mothership is on the order of 8000
      or so. Deactivate/reactivate a user with:
      	boss> wap tbacct deactivate -u <user>
      	boss> wap tbacct reactivate -u <user>
      Deactivate will set the shell to nologin and set the ZFS mountpoint=none.
      Reactivate will undo that. Note that these do not HUP mountd.
  7. 14 Apr, 2016 1 commit
  8. 30 Jun, 2015 1 commit
  9. 10 Jun, 2015 1 commit
    • Leigh B Stoller's avatar
      Fixes for exports_setup taking too long for geni user login. · 40154974
      Leigh B Stoller authored
      1. I removed exports_setup from tbacct, we seem to have fixed all the
         places where we were touching the user home directory during account
      2. I also removed exports_setup from web login for nonlocal (geni) users,
         since nothing on the Cloudlab path touches the user home directory,
         including starting a new experiment (geni users are not allowed to use
         any other part of the web interface, so Emulab Classic is off limits).
  10. 02 Jun, 2015 1 commit
  11. 01 Apr, 2015 1 commit
  12. 27 Jan, 2015 1 commit
  13. 07 Jan, 2015 3 commits
  14. 14 Dec, 2014 1 commit
  15. 12 Sep, 2014 1 commit
  16. 02 Sep, 2014 1 commit
  17. 27 Aug, 2014 1 commit
    • Leigh B Stoller's avatar
      Large set of changes for using the Geni trusted signer tool, to · 980f6cbd
      Leigh B Stoller authored
      authenticate Geni users to CloudLab (who do not have Emulab accounts).
      CloudLab users must have an account to do anything (unlike APT which allows
      guest users). But instead of requiring them to go through the Emulab
      account creation (high bar), let then use their Geni credentials to prove
      who they are. We then build a local account for that new user, and save off
      the speaksfor credential so that we can act on their behalf when talking to
      the backend clusters (and their MA to get their ssh keys).
      These users do not have a local account password, so they cannot log into
      the web interface using the Emulab login page, nor do they have a shell on
      Once authenticated, we put the appropriate cookies into the browser via
      javascript, so they can use the Cloud (okay, APT) web interface (they
      appear logged in).
      I make use of the nonlocal_id field of the users table, which was not being
      used for anything else. Officially, these are "nonlocal" users in the code
      When a nonlocal user instantiates a profile, we use their speaksfor
      credential to ask their home MA for their ssh keys, which we then store in
      the DB, and then provide to the aggregate via the CreateSliver call.
      Note that no provision has been made for users who edit their profile and
      add keys; I am not currently expecting these users to stumble into the web
      interface (yet).
  18. 09 Aug, 2014 1 commit
  19. 11 Jul, 2014 1 commit
  20. 15 May, 2014 1 commit
  21. 22 Mar, 2014 1 commit
  22. 17 Jan, 2014 1 commit
  23. 06 Nov, 2013 1 commit
  24. 24 Sep, 2012 1 commit
    • Eric Eide's avatar
      Replace license symbols with {{{ }}}-enclosed license blocks. · 6df609a9
      Eric Eide authored
      This commit is intended to makes the license status of Emulab and
      ProtoGENI source files more clear.  It replaces license symbols like
      "EMULAB-COPYRIGHT" and "GENIPUBLIC-COPYRIGHT" with {{{ }}}-delimited
      blocks that contain actual license statements.
      This change was driven by the fact that today, most people acquire and
      track Emulab and ProtoGENI sources via git.
      Before the Emulab source code was kept in git, the Flux Research Group
      at the University of Utah would roll distributions by making tar
      files.  As part of that process, the Flux Group would replace the
      license symbols in the source files with actual license statements.
      When the Flux Group moved to git, people outside of the group started
      to see the source files with the "unexpanded" symbols.  This meant
      that people acquired source files without actual license statements in
      them.  All the relevant files had Utah *copyright* statements in them,
      but without the expanded *license* statements, the licensing status of
      the source files was unclear.
      This commit is intended to clear up that confusion.
      Most Utah-copyrighted files in the Emulab source tree are distributed
      under the terms of the Affero GNU General Public License, version 3
      Most Utah-copyrighted files related to ProtoGENI are distributed under
      the terms of the GENI Public License, which is a BSD-like open-source
      Some Utah-copyrighted files in the Emulab source tree are distributed
      under the terms of the GNU Lesser General Public License, version 2.1
  25. 07 Nov, 2011 1 commit
  26. 31 Aug, 2011 1 commit
  27. 30 Aug, 2011 1 commit
  28. 27 Dec, 2010 1 commit
  29. 23 Dec, 2010 1 commit
  30. 22 Dec, 2010 2 commits
  31. 28 Apr, 2010 4 commits
  32. 22 Mar, 2010 1 commit
    • Leigh B Stoller's avatar
      Finish up user deletion. The big visible change is that when a user is · 2965922b
      Leigh B Stoller authored
      deleted, they still remain in the user table with a status of
      "archived", but since all the queries in the system now use uid_idx
      instead of uid, it is safe to reuse a uid since they are no longer
      The reason for not deleting users from the users table is so that the
      stats records can refer to the original record (who was that person
      named "mike"). This is very handy and worth the additional effort it
      has taken.
      There is no way to ressurect a user, but it would not be hard to add.
  33. 17 Mar, 2010 1 commit
  34. 27 Jan, 2010 1 commit