1. 19 Dec, 2005 2 commits
    • Kevin Atkinson's avatar
      · 45f997fd
      Kevin Atkinson authored
      Updates to to Error Logging API Code.
      
      You should start seeing much better error messages coming from my
      system.  Errors coming from parse.proxy and assign (the two most
      frequent sources of errors) should now be concise and to the point.
      Errors coming from libosload/libreboot (the next most frequent source
      of errors) should now also be much better, but not perfect.  Getting
      perfect errors will likely a rework of how errors are handled in
      libosload/libreboot, just adding tberror/tbwarn/tbnotice calls is not
      enough.  I can do this at a latter date if necessary.
      
      A few minor database changes.
      
      Some changes to the API.  A few bug fixes. Lots of tberror/tbwarn/tbnotice
      added to scripts.
      
      Since assign is a C program, and at this time my API is perl only, I wrote a
      second wrapper around assign, assign_wrapper2.  When assign fails errors are
      now parsed in assign_wrapper2, sent to stderr and logged.  This means that
      RunAssign() just returns when assign fails rather than echoing some of
      assign.log output and then quiting.  The output to the activity log remains
      unchanged.
      
      Since "parse.proxy" is run from ops I couldn't use my API in it, even though
      it is a perl program.  Instead I parse the errors coming form it in
      parse-ns.
      45f997fd
    • Leigh B. Stoller's avatar
      Add support for moving deleted users to a deleted users table. This · b4231fbf
      Leigh B. Stoller authored
      would be no big deal, except that we want to retain user_stats for
      deleted users, and rather then a deleted_user_stats table, I want to
      retain stats for deleted users in the user_stats table, since that
      is a more natural place for them.
      
      The main problem is that we use the login (uid) as the cross table
      reference slot all over the DB, which is fundamentally incorrect, if
      we want to be able reuse uids and still know what historical data
      refers to.
      
      So, I have taken a few baby steps towards weaning us off the uid, and
      towards permanently unique key for users, using the unix_uid integer
      for now, but probably something slightly different later.
      
      The user_stats is now indexed on this new key (called uid_idx in the
      users_stats table) instead of the plain uid.
      
      The unix_uid slot in the users table is no longer an auto_increment
      field, but instead uses the emulab_indicies table for the next
      available index.
      b4231fbf
  2. 15 Dec, 2005 1 commit
  3. 13 Dec, 2005 3 commits
  4. 07 Dec, 2005 1 commit
  5. 06 Dec, 2005 2 commits
  6. 01 Dec, 2005 1 commit
  7. 29 Nov, 2005 1 commit
  8. 28 Nov, 2005 1 commit
    • Kirk Webb's avatar
      · 2483e886
      Kirk Webb authored
      Added plab_mapping table to the DB to help track plab node identity.
      2483e886
  9. 15 Nov, 2005 1 commit
  10. 11 Nov, 2005 1 commit
    • Kevin Atkinson's avatar
      · 8e106f7c
      Kevin Atkinson authored
      Add "priorities" to exported_tables in libtblog.sql.
      8e106f7c
  11. 09 Nov, 2005 1 commit
  12. 08 Nov, 2005 1 commit
  13. 04 Nov, 2005 2 commits
  14. 31 Oct, 2005 1 commit
  15. 25 Oct, 2005 1 commit
  16. 20 Oct, 2005 1 commit
    • Kirk Webb's avatar
      · 5326988f
      Kirk Webb authored
      New node_attributes facility and table.
      
      Auxiliary node attributes, such as service tag #, BIOS version, etc., are
      should now be placed into the node_attributes table.  This can be accomplished
      by either using the node_attributes command line tool, or by using the
      modnodeattributes_form.php3 form (not linked in anywhere yet, but will be
      in a moment).  Attribute names and values are checked for sanity using
      table_regex entries.  Also note that I started with the nodecontrol stuff
      as a template.
      
      The command line tool and web form (which simply calls the command line tool
      to actually do the modifications) can add, delete, and/or remove attributes.
      
      Finally, note that the bios_version column has been moved from the nodes
      table to the node_attributes table.  The Node Information page will show
      the list of current attributes at the bottom of the info table.
      5326988f
  17. 19 Oct, 2005 1 commit
  18. 17 Oct, 2005 3 commits
    • Kirk Webb's avatar
      · 31090a2d
      Kirk Webb authored
      Add the ability to set the BIOS version, serial number, and service tag from
      the nodecontrol page and command line util.  Must be admin.
      31090a2d
    • Kirk Webb's avatar
      · e4f564c7
      Kirk Webb authored
      Oops - change length of varchar to 32 (was 64).
      e4f564c7
    • Kirk Webb's avatar
      · c045b869
      Kirk Webb authored
      Add serial and service_tag columns to the database for tracking machines.
      c045b869
  19. 12 Oct, 2005 1 commit
    • Leigh B. Stoller's avatar
      Add some hacky stuff to allow people in NSDI temporary project to · b538978f
      Leigh B. Stoller authored
      see experiments of other people in the NSDI project.
      
      Added sitevar "general/open_showexplist" which when set to the name of
      a project (NSDI), will allow users in that project to view all the
      experiments that are swapped in by other members of the project, even
      if the experiments are within another project.
      
      Also quickly hacked showuser page to only show project/group listing
      of overlapping projects, not all projects. This avoids some leakage.
      b538978f
  20. 11 Oct, 2005 1 commit
  21. 06 Oct, 2005 2 commits
  22. 30 Sep, 2005 1 commit
  23. 20 Sep, 2005 1 commit
  24. 07 Sep, 2005 3 commits
    • Mike Hibler's avatar
      Inner-elab role changes: · 88926d1c
      Mike Hibler authored
      	'boss' -> 'boss+router'
      	'ops'  -> 'ops+fs'
      	'fs'      (new role)
      	'router'  (new role)
      
      These are in preparation for allowing configurations with split ops and fs
      nodes (and sometime down the road, split boss and router nodes).
      
      This checkin is just the DB state changes along with the scripts that look
      at that state.  The Big One, which actually sets up separate nodes
      automatically, is undergoing more testing but will be Coming Soon.
      88926d1c
    • Leigh B. Stoller's avatar
      Fix a typo found by Keith Sklower. · 24b8d2d2
      Leigh B. Stoller authored
      24b8d2d2
    • Robert Ricci's avatar
      Added a 'global_vtypes' table, which contains vtypes that get · 970f7244
      Robert Ricci authored
      defined for everyone. Admins can use this, for example, to make
      type aliases.
      970f7244
  25. 01 Sep, 2005 1 commit
  26. 19 Aug, 2005 3 commits
  27. 18 Aug, 2005 1 commit
  28. 17 Aug, 2005 1 commit
    • Leigh B. Stoller's avatar
      The Emulab Knowledge Base! · 6f08c442
      Leigh B. Stoller authored
      Okay, I implemented a primitive Knowledge Base! The current contents are
      *all* the existing FAQ entries, which I entered manually. Here are the
      details.
      
      * My reason for doing this is that we need something very simple. The wiki
        is too much of a barrier, and its search capabilities are pathetic.
      
      * The search page for the Knowledge Base is:
      
      	https://www.emulab.net/kb-search.php3
      
        Fairly primitive keyword search. Turns out that mysql 4.0 has a bunch for
        really good text searching functions built in, but we run 3.23 ... so I
        had to roll it myself. So, its a simple keyword (space or comma
        separated) search, no regular expressions.
      
      * Each DB record has a "faq_entry" flag, so creating the current FAQ on the
        fly from the DB is easy. See:
      
      	https://www.emulab.net/kb-faq.php3
      
      * In reddot mode, you can add new KB entries:
      
      	https://www.emulab.net/kb-manage.php3
      
        The form is fairly obvious but here are details anyway:
      
          Section Name: Choose an existing title, or make up a new one.
          Title:        The title of the KB (or FAQ) entry.
          Faq Entry:    Check this box if the new entry should show up in the FAQ.
          X Ref Tag:    A token so you can refer to other KB entries by name,
                        instead of by its index. Within the KB entry you would
                        write: <a href=kb-show.php3?xref_tag=sometag>
          Body:         Whatever you like. I took the existing FAQ entries and
                        stuck them with no changes except for the xref_tag
                        mentioned about (since some entries referenced other
                        entries).
      
      * Once you click on sumbit, you will see the entry as it will appear to
        users, along with a submenu to Modify/Delete/Add entries. You can modify
        the current entry from that menu. Mere users do not see this menu, only
        when in reddot mode.
      
      * The intent here is that we can generate new entries really easy, right
        from email if you like (with appropriate <pre> or <xmp> tags around it).
      
      * I have added sql/knowlbase-create.sql and a makefile target to
        generate that file when creating a distribution. I also added a section
        to install/boss-install to insert the entries into the new DB.
      
      * I hooked the search function into the existing Search Documentation link.
        We know search both the Knowledge Base *and* the Documentation on doc
        searches. This probably needs a little more work to get right.
      
      * I changed a lot of faq links to be more consistent and to reference
        the proper xref_tags (#swapping instead of #UTT-34).
      6f08c442