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. 11 Jul, 2012 1 commit
    • Leigh Stoller's avatar
      Add reverse DNS lookup for the jail network. · bee73f22
      Leigh Stoller authored
      The GPO wants this for the protogeni racks. We now build reverse
      map files for the 172.16 subnet, although we do it on a /16 boundry
      to avoid a zillion zone files.
      
      I am not planning to write an update script for this, since it would
      require scripting changes to named.conf, which I am loath to do. So I
      will do it by hand in Utah, and new sites (racks) will get it. If a
      site wants it:
      
      	boss> cd obj/named
      
      Copy all of the 172 files to /etc/named/reverse
      Copy all of the 172 zone entries from named.conf to /etc/named/named.conf
      
      	boss> named_setup
      bee73f22
  3. 25 Feb, 2012 1 commit
  4. 11 Aug, 2011 1 commit
  5. 10 Aug, 2011 1 commit
    • Leigh Stoller's avatar
      Add support for making OPS a jail on boss. This works for elabinelab, · aefe785a
      Leigh Stoller authored
      but has not been tested for actual Emulab. A typical elabinelab NS
      file would look like:
          
          source tb_compat.tcl
          set ns [new Simulator]
          
          tb-elab-in-elab 1
          tb-elabinelab-singlenet
          tb-elab-in-elab-topology opsvm
          tb-set-elabinelab-attribute CONFIG_WINDOWS 0
          
          namespace eval TBCOMPAT {
              set elabinelab_maxpcs 1
              set elabinelab_hardware("boss") pc3000
          }
          $ns run
      aefe785a
  6. 22 Dec, 2010 1 commit
  7. 08 Jul, 2008 1 commit
  8. 26 Jun, 2008 1 commit
  9. 05 Sep, 2007 1 commit
  10. 16 Jul, 2007 1 commit
  11. 29 Nov, 2006 1 commit
    • Leigh Stoller's avatar
      A bunch of changes attempting to deal with testbed networks that are · baab5fc2
      Leigh Stoller authored
      bigger then a /24 network, as in Utah's network. Mostly the changes
      are how we deal with the reverse zone file creation and what gets
      stuck into the named.conf file. Prior to this commit, we assumed a
      single /24 network, cause thats how it looks in an elabinelab
      experiment (which is where its critical to have the named config files
      generated automatically).
      
      But with the changes to support a single control network, the named
      setup inside elabinelab is bigger then a /24 and the reverse files
      have to be created and populated correctly.
      baab5fc2
  12. 18 Aug, 2005 1 commit
  13. 24 May, 2005 1 commit
  14. 06 May, 2005 1 commit
  15. 14 Feb, 2005 1 commit
  16. 01 Feb, 2005 1 commit
  17. 07 Jan, 2005 2 commits
    • Mike Hibler's avatar
      Just can't resist pissing on things... · 2f27d203
      Mike Hibler authored
      Try my hand at modifying named config creation.  Allows for "fs" to be
      different than ops/users.  Also tried to eliminate some redundant output.
      We still generate multiple A records for some IPs (e.g., "ops" and "users")
      and don't (I think) generate MX records consistently.
      2f27d203
    • Leigh Stoller's avatar
      Named setup gets a serious collagen injection ... As per Mike/Rob · cff2421e
      Leigh Stoller authored
      request, beef up named setup so that sites like DETER are handled
      properly. I have added 4 new defs variables:
      
          #
          # If your boss/ops nodes are multihomed (and typically, one of the
          # networks is a public routable network, and the other is an internal
          # unroutable network), then define the the external addresses here (and
          # the internal addresses above).
          #
          EXTERNAL_BOSSNODE_IP=$BOSSNODE_IP
          EXTERNAL_USERNODE_IP=$USERNODE_IP
      
          #
          # As above, if you have internal and external networks, define the
          # external network here, and the internal network above.
          #
          EXTERNAL_TESTBED_NETWORK=$TESTBED_NETWORK
          EXTERNAL_TESTBED_NETMASK=$TESTBED_NETMASK
      
      which if not set default to the internal values. When the external and
      internal networks are different, generate two sets of reverse zone
      files and two forward files (one internal and one external).
      cff2421e
  18. 21 Dec, 2004 1 commit
  19. 27 Oct, 2004 2 commits
  20. 26 Oct, 2004 1 commit
  21. 07 Oct, 2004 1 commit