1. 08 Jan, 2006 1 commit
  2. 02 Jan, 2006 1 commit
    • Timothy Stack's avatar
      · bd20dd17
      Timothy Stack authored
      First cut at a daemon that does regular checkups of the testbed
      hardware/software.
      
      	* configure, configure.in: Add tbsetup/checkup directory.
      
      	* db/audit.in: Add a listing of stuck checkups.
      
      	* install/boss-install.in: Add 'elabckup' user.
      
      	* rc.d/3.testbed.sh.in: Startup the checkup_daemon.
      
      	* sql/database-create.sql, sql/database-migrate.txt: Add the
      	checkups tables.
      
      	* tbsetup/GNUmakefile.in: Descend into the checkup directory.
      
      	* tbsetup/checkup: The checkup daemon, man page, and
      	  associated scripts.
      
      	* tbsetup/ptopgen.in: Add a feature with a value of 0.9 to
      	  prereserved nodes to keep them from being allocated unless
      	  they're really wanted.
      
      	* utils/firstuser.in: Add some other options so the script can be
      	  used to create other pseudo users.
      bd20dd17
  3. 14 Nov, 2005 1 commit
  4. 24 Oct, 2005 1 commit
  5. 26 Sep, 2005 1 commit
  6. 15 Sep, 2005 1 commit
  7. 14 Sep, 2005 1 commit
    • Mike Hibler's avatar
      Changes related to allowing seperate 'fs' (file server) node. · c53d5827
      Mike Hibler authored
      Entailed new instructions for manual setup as well as integration into
      elabinelab framework.  First, the manual path:
      
      setup.txt, setup-boss.txt, setup-ops.txt and new setup-fs.txt:
          Updated to reflect potential for separate fs node.  The org here
          is a little dicey and could be confusing with ops+fs vs. ops and fs.
          Has not been field tested yet.
      
      */GNUmakefile.in: new fs-install target.
      
      configure, configure.in, defs-*:
          Somewhat unrelated, make min uid/gid to use be a defs setting.
          Also add config of fs-install.in script.
      
      boss-install.in, ops-install.in and new fs-install.in:
          Handle distinct fs node.  If you have one, fs-install is run before
          ops-install.  All scripts rely on the defs file settings of FSNODE
          and USERNODE to determine if the fs node is seperate.
      
      utils/checkquota.in:
          Just return "ok" if quotas are not used (i.e., if defs file FS_WITH_QUOTA
          string is null.
      
      install/ports/emulab-fs:
          Meta port for fs node specific stuff.  Also a patch for the samba port
          Makefile so it doesn't drag in CUPs, etc.  Note that the current samba
          port Makefile has this change, I am just backporting to our version.
      
      Elabinelab specific changes:
      
      elabinelab-withfs.ns:
          NS fragment used in conjunction with
      	tb-elab-in-elab-topology "withfs"
          to setup inner-elab with fs node.
      
      elabinelab.ns:
          The hard work on the boss side.  Recognize seperate-fs config and handle
          running of rc.mkelab on that node.  fs setup happens before ops setup.
      
      rc.mkelab:
          The hard work on the client side.  Recognize FsNode setup as well as
          differentiate ops+fs from ops setup.
      
      Related stuff either not part of the repo or checked in previously:
          emulab-fs package
      c53d5827
  8. 17 Aug, 2005 1 commit
    • Leigh Stoller's avatar
      The Emulab Knowledge Base! · 6f08c442
      Leigh 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
  9. 28 Jul, 2005 1 commit
  10. 26 May, 2005 1 commit
  11. 17 May, 2005 1 commit
  12. 10 May, 2005 1 commit
  13. 06 May, 2005 6 commits
  14. 05 May, 2005 2 commits
    • Leigh Stoller's avatar
      Change to how we get the password for elabman (firstuser). Instruct · 185014d4
      Leigh Stoller authored
      user to make sure root has a password, and just take the encrypted
      string from the password file. The elabman account is used for very
      little anyway.
      
      Also install the rsync port if it is not present; this is a temp hack
      until we figure out the package stuff.
      185014d4
    • Kirk Webb's avatar
      · c907ee66
      Kirk Webb authored
      Added FBSD-JAIL osid to rows initially created in os_info.
      c907ee66
  15. 04 May, 2005 2 commits
  16. 29 Apr, 2005 1 commit
  17. 28 Apr, 2005 1 commit
  18. 30 Mar, 2005 1 commit
    • Kirk Webb's avatar
      · 267a3f98
      Kirk Webb authored
      The ports-install script neglects to copy the ulsshblahblah port into
      the ports tree, causing mayhem and havoc at remote site.  Updated.
      267a3f98
  19. 29 Mar, 2005 2 commits
  20. 24 Mar, 2005 1 commit
  21. 16 Feb, 2005 1 commit
    • Mike Hibler's avatar
      Comment out lines in syslog.conf that send messages to logged in "root" · 34b10294
      Mike Hibler authored
      users.  These messages were appearing in linktest output to users because
      the linktest proxy runs on ops as root with a "full" tty ("-t -t") which
      apparently makes it look like a logged in user.
      
      Since no one logs in as root on ops, there was no legit recipient for these
      messages anyway.  Since the messasge all go to log files, I don't think we
      are losing anything.
      34b10294
  22. 12 Feb, 2005 1 commit
    • Kirk Webb's avatar
      · dede658b
      Kirk Webb authored
      Fixed up ops-install for new way of handling smb.conf file.  We copy in an
      smb.conf.head file now, and copy that to smb.conf initially on ops.
      exports_setup[.proxy] takes care of updating the share permissions for
      samba dynamically.
      dede658b
  23. 11 Feb, 2005 1 commit
    • Kirk Webb's avatar
      · 51472343
      Kirk Webb authored
      Removed some unneeded shares now that we autogen them.
      51472343
  24. 28 Jan, 2005 1 commit
  25. 27 Jan, 2005 1 commit
  26. 26 Jan, 2005 2 commits
  27. 25 Jan, 2005 1 commit
    • Kirk Webb's avatar
      · 2023c936
      Kirk Webb authored
      Add a Samba template config file.  The listening interface, globally allowed
      access list, and workgroup are defined as follows:
      
         workgroup = @OURDOMAIN@
         hosts allow = @CONTROL_NETWORK@/@CONTROL_NETMASK@
         interfaces = @FSNODE_IP@
      
      I believe this is what we want, but am not sure about the workgroup setting.
      Note that this should ultimately just be the head of the smb.conf file, with
      the tail generated vis-a-vis /etc/exports .  For now it has some hard wired
      shares for /proj and /users, which is OK for the very short term on an
      inner elab.
      2023c936
  28. 03 Jan, 2005 1 commit
  29. 03 Dec, 2004 1 commit
    • Leigh Stoller's avatar
      Two small changes: · edf6838c
      Leigh Stoller authored
      * Do not fetch the cisco MIBS inside an ElabInElab; takes too long and
        they are not needed.
      
      * Add some timestamp output to "Phase" so I can see where the time is
        going. I'll pull this out later.
      edf6838c
  30. 29 Nov, 2004 1 commit
  31. 08 Nov, 2004 1 commit