1. 08 Feb, 2019 1 commit
  2. 19 Jun, 2015 1 commit
  3. 27 Mar, 2015 1 commit
  4. 10 Nov, 2014 1 commit
  5. 30 Oct, 2014 1 commit
  6. 02 Dec, 2013 2 commits
  7. 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
      (AGPLv3).
      
      Most Utah-copyrighted files related to ProtoGENI are distributed under
      the terms of the GENI Public License, which is a BSD-like open-source
      license.
      
      Some Utah-copyrighted files in the Emulab source tree are distributed
      under the terms of the GNU Lesser General Public License, version 2.1
      (LGPL).
      6df609a9
  8. 25 May, 2010 1 commit
  9. 22 Mar, 2010 1 commit
    • Leigh Stoller's avatar
      Finish up user deletion. The big visible change is that when a user is · 2965922b
      Leigh 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
      ambiguous. 
      
      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.
      2965922b
  10. 10 Jan, 2007 1 commit
  11. 13 Dec, 2006 1 commit
  12. 30 Nov, 2006 1 commit
  13. 15 Nov, 2006 1 commit
  14. 20 Oct, 2006 1 commit
    • Mike Hibler's avatar
      Wow, this should make me look important! · afa5e919
      Mike Hibler authored
      Two-day boondoggle to support "/scratch", an optional large, shared filesystem
      for users.  To do this, I needed to find all the instances where /proj is used
      and behave accordingly.  The boondoggle part was the decision to gather up all
      the hardwired instances of shared directory names ("/proj", "/users", etc.)
      so that they are set in a common place (via unexposed configure variables).
      This is a boondoggle because:
      
      1. I didn't change the client-side scripts.  They need a different mechanism
         (e.g., tmcd) to get the info, configure is the wrong way.
      
      2. Even if I had done #1 it is likely--no, certain--that something would
         fail if you tried to rename "/proj" to be "/mike".  These names are just
         too ingrained.
      
      3. We may not even use "/scratch" as it turns out.
      
      Note, I also didn't fix any of the .html documentation.  Anyway, it is done.
      To maintain my illusion in the future you should:
      
      1. Have perl scripts include "use libtestbed" and use the defined PROJROOT(),
         et.al. functions where possible.  If not possible, make sure they run
         through configure and use @PROJROOT_DIR@, etc.
      
      2. Use the configure method for python, C, php and other languages.
      
      3. There are perl (TBValidUserDir) and php (VALIDUSERPATH) functions which
         you should call to determine if an NS, template parameter, tarball or
         other file are in "an acceptable location."  Use these functions where
         possible.  They know about the optional "scratch" filesystem.  Note that
         the perl function is over-engineered to handles cases that don't occur
         in nature.
      afa5e919
  15. 15 Jun, 2006 1 commit
    • Leigh Stoller's avatar
      Quick fix to get Kevin past latest problem. We have several special · c693b991
      Leigh Stoller authored
      users in the emulab-ops project (elabman, elabckup, operator) all with
      the same email address. elabman is treated special (since it was the
      only special user way back), but now there are lots of places that
      either need to include tests for all special users, or we need to flag
      these users in the users table.
      
      For now I made a change to genelists.in to get past the problem. I
      will address the user table at a later date.
      c693b991
  16. 24 Feb, 2006 1 commit
  17. 04 Nov, 2005 1 commit
  18. 20 Oct, 2005 1 commit
  19. 14 Oct, 2005 1 commit
    • Leigh Stoller's avatar
      Fixup the mailman support so that instead of using @emulab.net · 75081528
      Leigh Stoller authored
      addresses in the list, use real email addresses. Why? Well, cause I'm
      a dope.  Oh, the real reason is that people cannot post to the lists
      if we use their @emulab.net addresses cause we close the lists (to
      avoid spammers). I did it this way originally cause it was easier;
      there is a lot more bookkeeping to do if using real addresses, and I
      never consider problem of not being able to post.
      75081528
  20. 07 Sep, 2005 1 commit
  21. 17 Aug, 2005 1 commit
  22. 15 Aug, 2005 1 commit
    • Leigh Stoller's avatar
      The bulk of the mailman support. Still not turned on by default (cause · a64593f3
      Leigh Stoller authored
      Jay has "comments"), but I do not want it hanging around in my source
      tree. Here is my mail message:
      
      * The "My Mailing Lists" is context sensitive (copied from Tim's
        changes to the My Bug Databases). It takes you to the *archives* for
        the current project (or subgroup) list. Or it takes you to your
        first joined project.
      
      * The showproject and showgroup pages have direct links to the project
        and group specific archives. If you are in reddot mode, you also
        get a link to the admin page for the list. Note that project and
        group leaders are just plain members of these lists.
      
      * The interface to create a new "user" list is:
      
      	https://www.emulab.net/dev/stoller/newmmlist.php3
      
        We do not store the password, but just fire it over in the list
        creation process.
      
        Anyone can create their own mailing lists. They are not associated
        with projects, but just the person creating the list. That person
        is the list administrator and is given permission to access the
        configuration page.
      
        This page is not hooked in yet; not sure where.
      
      * Once you have your own lists, you user profile page includes a link
        in the sub menu: Show Mailman Lists. From this page you can delete
        lists, zap to the admin page, or change the admin password (which is
        really just a subpage of the admin page).
      
      * As usual, in reddot mode you can mess with anyone else's mailman lists,
        (via the magic of mailman cookies).
      
      * Note on cross machine login. The mailman stuff has a really easy way
        to generate the right kind of cookie to give users access. You can
        generate a cookie to give user access, or to the admin interface for
        a list (a different cookie). Behind the scenes, I ssh over and get
        the cookie, and set it in the user's browser from boss. When the
        browser is redirected over to ops, that cookie goes along and gives
        the user the requested access. No passwords need be sent around,
        since we do the authentication ourselves.
      a64593f3
  23. 31 May, 2005 1 commit
  24. 11 Aug, 2004 1 commit
  25. 10 Aug, 2004 1 commit
  26. 09 Aug, 2004 1 commit
    • Leigh Stoller's avatar
      Some cleanups and performance improvements: · f604dc33
      Leigh Stoller authored
      * Be more selective about what lists are regenerated; we were generating
        way too many lists each time called. When calling from tbswap, use new
        -t option to generate just the active lists. When called from setgroups,
        use -p option to generate lists just for the project. Add update option
        for when user changes email address (and all lists really do need to be
        regenerated).
      
      * Add "diff" processing. Instead of blindly firing each new list over to
        ops with ssh, store a copy of all of the lists in
        /usr/testbed/lists. After we generate the new list, diff it against the
        stored copy. If the same, skip it. Otherwise stash new copy and fire it
        over. This should reduce the wait times by quite a bit since the lists
        rarely change (except for the activity lists of course).
      
      * Add -n (impotent) option for debugging; skips the ssh over to ops.
      
      * Reorg a lot of stuff; it was getting hard to follow.
      f604dc33
  27. 02 Oct, 2003 1 commit
  28. 18 Sep, 2003 1 commit
  29. 15 Sep, 2003 1 commit
  30. 24 Apr, 2003 1 commit
  31. 05 Mar, 2003 1 commit
  32. 25 Feb, 2003 1 commit
  33. 02 Dec, 2002 1 commit
  34. 14 Aug, 2002 2 commits
  35. 04 Jul, 2002 1 commit
  36. 05 Jun, 2002 1 commit
    • Leigh Stoller's avatar
      Changes to sshtb. Remove sshremote, and convert sshtb into a perl · 231fc2b1
      Leigh Stoller authored
      script that checks the database to see if local or remote. The problem
      with this is that the ssh syntax makes it hard to determine the host
      name by inspection. Would need to parse all the ssh args (bad idea),
      ot work backwards and try to figure out the difference between the
      command (which is not a string but a sequence of args) and the host
      and the preceeding ssh args. Hell with that! Changed sshtb to require
      a specific -host argument. Read the args and look for it. Error out of
      not found, to catch improper usage.
      
      The moral of this update: "sshtb [ssh args] -host <host> [more args ...]
      231fc2b1
  37. 08 Apr, 2002 1 commit
    • Leigh Stoller's avatar
      Add generation of per-project email lists, as per Dave's request. The · 8cac9c47
      Leigh Stoller authored
      lists are stored on users:/etc/mail/lists. For example, you can send
      email to ron-users@users.emulab.net. An alias entry is added (and
      newaliases run) if there is no alias in /etc/mail/aliases (by the proxy
      of course). There are two new options to genelists (on boss):
      
      	"Use the -a option to generate lists for all projects.\n".
      	"Use the -n option to generate lists for a new user.\n";
      
      With no options, generate the all users and active users lists
      (renamed to emulab-users and emulab-active-users). With the -n option
      (used by mkacct) regen the lists for all the projects the user is a
      member of.
      
      It would be nice to archive the email, but that requires a publically
      readable directory and a u+S archive file; the mailer daemon runs as
      user daemon, and the project tree is 770, so it cannot write the
      archive file. At some point we will have to go to majordomo or spam
      filtering, when the first list is spamm'ed. Sigh.
      8cac9c47
  38. 12 Feb, 2002 1 commit