1. 09 Dec, 2003 1 commit
    • Leigh B. Stoller's avatar
      Add drop down menu to approve project form that allows admin person to · 9d882479
      Leigh B. Stoller authored
      select the default user interface for a project. The choice is current
      'emulab or 'plab', defaults to 'emulab'. New users that join emulab
      get the default user interface from the first project they join.
      Also generalize the plab_user bit as new "user_interface" slot of the
      users table, which is an enum of interface tokens, currently either
      'emulab' or 'plab', defaults to 'emulab'. The plab_user bit will be
      removed later.
  2. 12 May, 2003 1 commit
  3. 11 Apr, 2003 1 commit
  4. 21 Mar, 2003 1 commit
  5. 25 Feb, 2003 1 commit
    • Robert Ricci's avatar
      Make sure that the head uid of a project is 'active' or 'unapproved' · 1ebdf309
      Robert Ricci authored
      before allowing a project to be approved. (In approveproject_form,
      this meant removing the automatic transition from 'newuser' to
      Since this check is done in two places, once in the form, and once in
      the page that does the work, it's possible for this to get out of
  6. 13 Feb, 2003 1 commit
  7. 01 Oct, 2002 1 commit
    • Robert Ricci's avatar
      Add a box to change the head of a project on the project approval · 39eb481b
      Robert Ricci authored
      'action' page. This will be used when a student applies to start
      a project - we'll have the professor, PI, etc. apply to join the
      project, then change the head UID when we approve it.
      Changing the head uid is repected when _any_ action is taken
      (postponing, more info requests, etc.) Any mail gets sent to the
      new head, and NOT the old head.
  8. 29 Jul, 2002 1 commit
    • Leigh B. Stoller's avatar
      Widearea permission changes: · d3c6f9c8
      Leigh B. Stoller authored
      * Two new fields on the new project page that ask the project leader to
        specify how many ron and pcplab nodes they need. There is a link to a
        page that should describe these nodes, but thats blank.
      * The project approval page will add a couple of checkboxes for ron and
        pcplab nodes. This will allow the project to be approved independent of
        the ron/pcplab usage. So, you can approve the project but decline the
        request to use those nodes types (or just one of them).
      * The project table in the DB has a "list" of remote node types for which
        accounts should be built. Its implemented as a set and it can contain
        just two node types (pcron, pcplab) right now. The set is created in
        the approval page, and someday we can add a page to operate on that
        set directly if we need it.
  9. 07 Jul, 2002 1 commit
  10. 16 Oct, 2001 1 commit
  11. 30 Aug, 2001 1 commit
  12. 18 Apr, 2001 1 commit
  13. 08 Dec, 2000 1 commit
  14. 15 Nov, 2000 1 commit
  15. 14 Nov, 2000 1 commit
  16. 07 Nov, 2000 4 commits
  17. 06 Nov, 2000 2 commits