1. 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
  2. 05 Dec, 2006 1 commit
  3. 10 Dec, 2003 1 commit
  4. 19 Sep, 2002 1 commit
    • Robert Ricci's avatar
      Fix up bitrot in 'full' mode. Major changes: · 72f94a58
      Robert Ricci authored
      1) Set 'BOSSNODE' in the defs file to `hostname` - required for the
         event system
      2) Include virtual nodes, and randomize order, when picking nodes
         to run on
      3) Run exports_setup after allocating nodes, so they can mount
         homedirs, etc.
      4) Enable events in full mode
      5) When creating experiment in experiments table, set gid and testdb
      6) Run our own copy of stated, so that transitions get recorded
      72f94a58
  5. 17 Sep, 2002 1 commit
  6. 27 Jun, 2001 1 commit
    • Christopher Alfeld's avatar
      First version of the testing software. · d138f5cc
      Christopher Alfeld authored
      This is a functional check in.  To run the testing software do
      something like:
      	1. mkdir ~/testbed_test
      	2. cd ~/testbed_test
      	3. ~/testbed/testsuite/tbtest tbdb frontend
      alternately:
      	1. mkdir ~/testbed_test
      	2. cd ~/testbed/testsuite
      	3. tbtest -path ~/testbed_test tbdb frontend
      
      A lot of stuff will be placed in testbed_test, including a configured
      tree, an installed tree, a couple versions of the DB, and a whole
      bunch of log files.
      
      Interesting log files:
      
      The main log file of interest is test.log which is a copy of the
      output of tbtest.  The other log files are only useful if things fail.
      Usually the fail message will include which log file to look in.  Log
      files for tests are in tests/<test>/test.log .
      
      What's missing:
      
      1. Lot's of tests.  There's only one currently.
      
      2. DB checking support.
      
      3. A real README.  The current one is mainly a bunch of notes for the
      real README.
      
      4. Full support.  The current setup is only for testing the frontend.
      Although there are some hooks for supporting full testing runs a lot
      still needs to be done.
      d138f5cc