1. 23 Jul, 2014 1 commit
  2. 27 May, 2014 1 commit
  3. 25 May, 2014 1 commit
  4. 22 May, 2014 2 commits
    • Gary Wong's avatar
      791a2d49
    • Gary Wong's avatar
      Add GPO ops-monitoring support. · e9a21edc
      Gary Wong authored
      The pieces are:
      
       * A monitoring daemon (clientside/protogeni/shared-node-monitor), which
         runs in each Xen shared node dom0, and gathers node and interface
         statistics.  It communicates these over the event system with...
      
       * A listening daemon (event/monitoring/shared-node-listener), running
         on the local boss node, and inserts everything it hears into the
         MySQL database "monitoring".  This database is also used by...
      
       * A site-wide monitoring daemon (protogeni/scripts/mondbd), periodically
         polling the normal testbed database (nodes and interfaces tables) and
         copying snapshots of the important pieces into the monitoring database.
      
       * The monitoring database is also read by a WWW front end invoked as a
         WSGI process by Apache.  This front end is developed by the GPO and
         modified to work with ProtoGENI, and is maintained in an independent
         repository.
      e9a21edc
  5. 29 Aug, 2013 2 commits
  6. 30 Nov, 2012 1 commit
    • Mike Hibler's avatar
      Plumb through an fs-install makefile target and fixes to ops-install. · 3cd66d51
      Mike Hibler authored
      This officially drops the pretense that fs nodes can operate with minimal
      Emulab software. If you have a seperate fs node, it had better be dedicated
      to Emulab!
      
      However, it still doesn't do everything. In particular, accounts are not
      installed. This has never been needed for serving NFS, but is needed for
      the samba stuff to work correctly.
      
      Also, you cannot do an fs node software install from boss yet as we do not
      mount fs filesystems on boss. You really cannot do a full ops install from
      boss either since we don't mount ops' /usr/local/etc/emulab directory.
      3cd66d51
  7. 30 Oct, 2012 1 commit
  8. 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
  9. 13 Sep, 2012 1 commit
  10. 28 Jul, 2011 1 commit
  11. 27 Jul, 2011 1 commit
  12. 24 Jul, 2011 1 commit
  13. 19 Jul, 2011 5 commits
  14. 22 Sep, 2004 1 commit
  15. 20 Apr, 2004 1 commit
    • Mike Hibler's avatar
      Improve the client-install. You can now do a "make client-install" from · 361ee691
      Mike Hibler authored
      the top level.  This will build all the necessary binaries and then install
      them.  This works on FBSD4 and RHL7.3.  It still doesn't work on FBSD5
      (newer compiler that no longer supports a style of use of _FUNCTION_ in the
      event lib) or RHL9 (event lib needs SSL lib which has a bad dependency
      on Kerberos).  Notes:
      
      - requires that elvin libraries be installed on nodes (they are) to build
        event agents, requires linuxthreads be installed on FBSD (it is now) to
        build imagezip (which is installed, but is not strictly necessary)
      
      - installed event-agents and other binaries are stripped
      
      - added a few missing files to the source tree for bsd (healthd.conf)
        and linux (healthd.conf, rc.local)
      
      - the only thing that doesn't get rebuilt in /usr/local/etc/emulab is
        healthd, I couldn't quickly find how it gets built
      
      - uses a scaled down version of libtb with no DB functions (since mysql
        isn't installed on nodes).  N.B. DO NOT DO A CLIENT INSTALL FROM YOUR
        REGULAR OBJ TREE OR ELSE YOU MAY WIND UP WITH A NEUTERED VERSION OF
        libtb.a!
      
      The build-as-well-as-install semantics are counter to the regular install
      targets, but this is what we gotta do for now.  Once the TB source builds
      under Linux and newer BSDs, we could undo this and just require that people
      do a regular "make" followed by "make client-install"  OTOH, there should
      be no reason to require installation of mysql and other server-side packages
      just to build clients (or make them sit through the compilation of assign),
      so maybe we will keep the client build special.
      361ee691
  16. 07 Jul, 2002 1 commit
  17. 24 Feb, 2002 1 commit
  18. 10 Jan, 2001 1 commit
  19. 03 Jan, 2001 1 commit
  20. 02 Jan, 2001 1 commit
  21. 01 Dec, 2000 1 commit
  22. 21 Jul, 2000 1 commit