1. 01 Jul, 2003 1 commit
    • Leigh Stoller's avatar
      Commit SSH node menu option, and support. Heavily based/borrowed from · f4bf9b5c
      Leigh Stoller authored
      Chad's tiptunnel stuff. Requires ssh-mime.pl in the current directory,
      to be installed as a browser helper application on the users machine.
      Copied Chad's instructions for the tiptunnel from the FAQ, and stuck
      it into ssh-mime.html as a help file (not really FAQ material). The
      intent of this of course is to make ssh into jailed nodes easier, but
      not having to know port numbers, or directly log into ops first, when
      the jails are using control network IPs in our private IP space (not
      routable from outside).
      f4bf9b5c
  2. 17 Jun, 2003 1 commit
  3. 15 May, 2003 1 commit
    • Leigh Stoller's avatar
      Split the experiment stats table into two parts. The first is the · a382994d
      Leigh Stoller authored
      per-experiment instantiation with aggregate data like the number of
      swapins, the dates and the like. The other part is the per
      swapin/modify stats. These are number of pnodes, links, lans,
      etc. Long term, I think we want more precise swapin stats, and with
      experiment modify in the mix, we need to have multiple stat records
      per experiment, but do not need to duplicate all the stuff in the
      other table just mentioned.
      
      To reduce the amount the table size, we cross reference the tables by
      index only instead of with pid,eid and the like. We use exptidx to
      link experiments, experiment_stats, and the new experiment_resources
      table. experiment_resources and stats are linked by another index in
      the resources table, which indicates which is the current resource
      row. On a modify, a new resource record is created, and the stats
      record updated to point to the new (latest) resource record.
      
      Web Changes: Improve showstats and showexpstats. Make them user
      accessible so that mere users can see stats for themselves and for
      their projects. No ability for mere users (PIs) to look at another
      person's stats. Generally, these two pages need more work, but now
      they are more useful. I added Show Stats to the user info and project
      info pages to display per-usr/proj stats. Add more info in the
      showstats display, but the showexpstats display is still not pretty
      printed; just the raw tables.
      
      Rename a few fields, add some indexes, and otherwise make some minor
      changes that are sure to annoy everyone.
      a382994d
  4. 13 May, 2003 1 commit
  5. 28 Apr, 2003 1 commit
    • Leigh Stoller's avatar
      Add support for new {user,group,project,experiment}_stats tables. · 5e5508bf
      Leigh Stoller authored
      The first three are aggregate tables, while the experiment stats table
      gets a record for each new experiment, and is updated when an
      experiment is swapped in/out/modify or terminated. Look at the table
      to see what is tracked. Once the experiment_stats record is updated,
      the aggregate tables are updated as necessary. There are a bunch of
      ugly changes to assign_wrapper to get the stats. Note that pnodes is
      not incremented until an experiment sucessfully swaps in. This is in
      leu of getting status codes; I'm not tracking failed operations yet,
      nor creating the log file that Jay wants. I'll do that in the next
      round of changes when we see how useful these numbers are.
      
      Most of the changes are to create/delete table entries where
      appropriate, and to display the records. Display is only under admin
      mode, and the display is raw; just a dump of the assoc tables in php.
      The last 100 experiment stats records are available via the Experiment
      List page, using the "Stats" show option at the top. Bad place, but
      will do for now.
      5e5508bf
  6. 16 Apr, 2003 1 commit
  7. 27 Mar, 2003 2 commits
  8. 24 Jan, 2003 1 commit
  9. 11 Dec, 2002 1 commit
  10. 09 Dec, 2002 1 commit
  11. 06 Dec, 2002 1 commit
  12. 25 Nov, 2002 1 commit
  13. 16 Aug, 2002 1 commit
    • Chad Barb's avatar
      · 60529980
      Chad Barb authored
      The big one.
      
      New look;
      most of the changes are in menu.php3.
      
      A lot of the changes in other files are s/<TD>/<TH>/
      for table headers.
      
      Also closed some tags, tweaked some table styles, etc..
      
      No actual functionality should have changed.
      
      Will be installing soon...
      60529980
  14. 17 Jul, 2002 1 commit
  15. 07 Jul, 2002 1 commit
  16. 21 Jun, 2002 1 commit
  17. 22 May, 2002 1 commit
    • Leigh Stoller's avatar
      A large set of authorization changes. · d2360b6d
      Leigh Stoller authored
      * Cleanup! A lot of the structure derived from the early frame days,
        which had a noticable (and bad) effect on how I wrote the stuff.  I
        cleaned up most of that yuckyness.
      
      * In process, optimize a little bit on the queries. The old code did
        about 9 queries just to write out the menu options, and then
        repeated most of those queries again in the page guts. I've
        consolidated the queries as much as possible (to 3) and cache all
        the results.
      
      * Fix up problem with users who forget their passwords before
        verification. Basically, I fixed the more general problem of not
        being able to update your user info before verification/approval;
        users now get that menu option no matter their status.
      
      * Fix up problem of users being able to access pages before
        verification (but after approval) by going around the menu options.
        The page level check (after the menu is drawn) now checks all
        conditions (password expired, unverified, unapproved, timedout, and
        also nologins()).
      
      * Minor change in approveuser; do not show the new account to the
        project leader until the new user has verified his account.
      
      * Change verification method, as reqwuested by Dave.  In addition to
        providing the key, also provide a web link to take the user straight
        to verification. I actually take them direct to the login page, and
        pass the key in as an argument. If the user is already logged in,
        bypass and go directly to the verify page (not the form page of
        course).  If the user is not logged in, let him log in, and then
        forward the key onward to the verify page. Basically, bypass the
        form all the time, and just do the verification.
      
      * Minor change in showuser; Do not show pid/groups not approved in,
        and if the count is zero, do not draw the table headings.
      d2360b6d
  18. 17 Apr, 2002 1 commit
  19. 05 Apr, 2002 1 commit
  20. 25 Mar, 2002 1 commit
  21. 08 Feb, 2002 1 commit
  22. 20 Dec, 2001 1 commit
  23. 17 Dec, 2001 1 commit
  24. 10 Dec, 2001 1 commit
  25. 03 Dec, 2001 1 commit
  26. 17 Oct, 2001 1 commit
  27. 16 Oct, 2001 1 commit
  28. 18 Apr, 2001 1 commit
  29. 08 Dec, 2000 1 commit
  30. 29 Nov, 2000 1 commit
  31. 15 Nov, 2000 1 commit