1. 13 Aug, 2015 3 commits
  2. 13 Jul, 2015 1 commit
    • David Johnson's avatar
      Add geni-lib script parameter warnings/errors, groups, helpdocs. · c201620c
      David Johnson authored
      (The bulk of the code is in the parameter form formatter/decorator JS
      code; I only applied it to the wizard for now... but it's
      straightforward to copy it into the old parameter code ;))
      
      The portal can now render the parameter form in much more complex ways.
      It supports a notion of advanced parameter groups, a panel containing
      parameters that is closed by default but expandable; generic parameter
      groups; per-parameter detailed helpdocs in an expandable subpanel (and
      an expand-all-help link that will also expand all the parameter group
      panels), and error messages and warnings.  A summary of both errors and
      warnings is displayed at the top of the form, and specific error message
      details are displayed near parameters.  The error message display is
      flexible to generic user messages -- basically if the error is a proper
      geni-lib portal error/warning, but not a parameter error/warning, it
      will be displayed at the top of the parameter form (along with any
      others).  If it's an "improper" one, we'll still do our best to display
      it.  If you warn a user, you can provide a set of parameter values that
      "fix" the warning, and the Portal UI will change the form values and
      tell the user it did so.  You can't do this on error; the assumption is
      the user has to fix the error.
      
      Finally, the portal now tries to rungenilib in warnings-are-fatal mode
      the first time parameter bind (to generate rspec) is attempted.  If they
      go backwards to re-parameterize, warnings should be fatal again.  It's
      too hard to figure out when we should stop warnings-fatal mode; we can't
      block the user's progress if they really want to proceed in the face of
      warnings.
      c201620c
  3. 03 Jan, 2015 1 commit
  4. 12 Nov, 2014 1 commit
  5. 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
  6. 29 Sep, 2010 1 commit
    • Kevin Atkinson's avatar
      Detect when the NS parser crashed via the signal in parse.proxy and · 44d56444
      Kevin Atkinson authored
      send back an exit code with the signal embedded (128 + signal) so that
      the boss end can detect that the parser failed.  If the signal is due
      to to crash (other than SIGABRT, as that is likely due due to running
      out of memory) than email testbed-ops.
      
      Also remove the email to testbed-ops when the parser exceeded the CPU
      Limit.
      44d56444
  7. 04 May, 2010 1 commit
    • Kevin Atkinson's avatar
      BUG FIX: Make parse errors "User" errors again. · 7a148ab4
      Kevin Atkinson authored
      The problem is that comit f6d81289
      (Changes from Pat Gunn at CMU: allow "at swapout"...) changed the exit
      status of parse.proxy with this line:
        -    exec("nice -15 $parser @ARGV $nsfile");
        +    exec("nice -15 $parser @ARGV $nsfile|tee $tempdir/output.txt");
      so parse-ns was not detecting that it failed.  It then processed to
      run xmlconvert which detected that the ns parse failed.
      
      The causes two problems, 1) my error handling code depends on the fact
      that parse.proxy failed in order to determine it was a user error and
      2) it causes the "Syntax Check" option to always report correct syntax
      even when it shouldn't.
      7a148ab4
  8. 15 Apr, 2010 1 commit
  9. 11 May, 2009 2 commits
  10. 23 Jan, 2006 1 commit
    • Timothy Stack's avatar
      · add602df
      Timothy Stack authored
      Parse the NS file with the real NS parser so we can make sure linktest is
      doing the "right" thing.
      
      	* configure, configure.in: Add tbsetup/nsverify files.
      
      	* tbsetup/GNUmakefile.in: Add nsverify subdir.
      
      	* tbsetup/tbprerun.in: Run verify-ns on the experiments NS file.
      
      	* tbsetup/ns2ir/nstb_compat.tcl: Bring up-to-date with the current
      	world.
      
      	* tbsetup/nsverify/GNUmakefile.in: Makefile.
      
      	* tbsetup/nsverify/ns-2.27.patch: Patch file for NS version 2.27.
      
      	* tbsetup/nsverify/nstbparse.in: Wrapper for the NS parser.
      
      	* tbsetup/nsverify/tb_compat.tcl: Different version of
      	tb_compat.tcl that is used to verify linktest parameters.
      
      	* tbsetup/nsverify/verify-ns.in: Script that runs on boss and
      	verifies that the testbed parser worked correctly.
      
      	* tbsetup/ns2ir/parse-ns.in, tbsetup/ns2ir/parse.proxy.in: Tweaked
      	a bit so parse.proxy can be used to run the regular NS parser in
      	addition to the testbed one.
      add602df
  11. 02 Feb, 2004 1 commit
  12. 01 Aug, 2003 1 commit
  13. 02 Jul, 2003 1 commit
  14. 30 Jun, 2003 1 commit
    • Leigh Stoller's avatar
      Make the new parser live on mini. New parser ssh'es over to ops to · 2202fc5a
      Leigh Stoller authored
      do the actual parse. The parser now spits out XML instead of DB
      queries, and the wrapper on boss converts that to DB insertions after
      verification. There are some makefile changes as well to install the
      new parser on ops via NFS, since otherwise the parser could
      intolerably out of date on ops!
      2202fc5a