1. 31 Mar, 2015 1 commit
  2. 06 Jan, 2015 1 commit
  3. 12 Jul, 2014 1 commit
  4. 22 Apr, 2014 1 commit
  5. 16 Apr, 2014 1 commit
  6. 14 Apr, 2014 1 commit
    • Leigh B Stoller's avatar
      Various changes, see below. · 0b320234
      Leigh B Stoller authored
      1. Add warning 1 hour before expiration, even for "short lived"
         slivers.
      
      2. Auto-delete orphaned cartificates.
      
      3. Try to destroy locked/expired slices before send email about them.
      0b320234
  7. 30 Aug, 2013 1 commit
  8. 15 Aug, 2013 3 commits
    • Leigh B Stoller's avatar
      Minor debugging change. · b3c13417
      Leigh B Stoller authored
      b3c13417
    • Leigh B Stoller's avatar
      Turn off actual norenew until the 30th. · fc0b3ae9
      Leigh B Stoller authored
      fc0b3ae9
    • Leigh B Stoller's avatar
      Changes to idle handling in ProtoGeni slivers · ec076c05
      Leigh B Stoller authored
      When a new sliver is created, they are given a relatively short
      lifetime. This is the value of protogeni/initial_sliver_lifetime and
      defaults to six hours.
      
      A user may renew a sliver for up to the number of days in
      protogeni/max_sliver_lifetime (defaults to 90 days), except in Utah
      where it is 5 days (Emulab, Utah Rack, Utah DDC Rack).
      
      The CM daemon idle code looks for idle slivers. An idle sliver is one
      in which 50% of the physical nodes have been idle for three hours.
      (protogeni/idlecheck_threshold). At this point an email message is
      sent to the sliver creator.
      
      If the sitevar protogeni/idlecheck_norenew is set, then the email
      threatens to mark the sliver as unrenewable if it stays idle. Then, at
      2 * protogeni/idlecheck_threshold, if the sliver is still idle, the
      sliver is marked as unrenewable. No matter what the user does at this
      point, he will not be able to renew the sliver and it will expire out
      normally.
      
      If protogeni/idlecheck_norenew is no set, behaviour remains as it is
      now; a followup message is sent every 24 hours.
      
      There is a new backend script called "setexpiration" that allows an
      aggregate admin person to override the settings on a per-slice basis
      so that users who have a need for a long running sliver do not have to
      continually renew and/or bypas the max_sliver_lifetime setting. For
      example:
      
      boss> wap setexpiration -e YYYY-MM-DD mysliceurn
      
      will extend the termination date to the given date. To restore the
      default behavour:
      
      boss> wap setexpiration -E mysliceurn
      
      Note that idle checks are still made. To turn off idle checks for
      a slice:
      
      boss> wap setexpiration -i mysliceurn
      
      To turn then back on:
      
      boss> wap setexpiration -I mysliceurn
      ec076c05
  9. 22 Jul, 2013 1 commit
  10. 17 Jul, 2013 1 commit
  11. 24 Jun, 2013 1 commit
  12. 18 Jun, 2013 1 commit
  13. 12 Feb, 2013 2 commits
  14. 31 Jan, 2013 1 commit
  15. 24 Jan, 2013 1 commit
  16. 23 Jan, 2013 1 commit
    • Leigh B Stoller's avatar
      Add idle checking, similar to how idlemail/idleswap functions for · 7f494949
      Leigh B Stoller authored
      normal experiments. I could have rolled this into the existing code,
      but that would have been very unpleasant.
      
      Currently, checks every 15 minutes, using the same idle threshold as
      idlemail, but sends email only once every 24 hours. There are two
      site variables:
      
        protogeni/idlecheck		- enable/disable PG idle checks.
        protogeni/idlecheck_terminate - enable/disable termination on idle.
      
      Both start as zero when the site variables are added.
      7f494949
  17. 19 Oct, 2012 1 commit
    • Leigh B Stoller's avatar
      Knock down another shared vlan bug; this one was caused by the cached · b45ad18a
      Leigh B Stoller authored
      DB objects we use in the libraries. We hang onto those objects forever
      in the expire daemon, but they are stale in the case of shared vlans
      which are being messed with elsewhere.
      
      Rather then track down all the caching bugs, I changed the expire
      daemon to call the existing cleanupslice script, avoiding all cache
      problems.
      b45ad18a
  18. 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
  19. 24 Apr, 2012 1 commit
  20. 11 Apr, 2012 1 commit
  21. 05 Apr, 2012 2 commits
  22. 07 Nov, 2011 1 commit
  23. 13 Jun, 2011 1 commit
  24. 02 Jun, 2011 1 commit
  25. 14 Feb, 2011 1 commit
  26. 26 Oct, 2010 1 commit
  27. 20 Oct, 2010 1 commit
  28. 11 Oct, 2010 1 commit
    • Leigh B Stoller's avatar
      Work on an optimization to the perl code. Maybe you have noticed, but · 92f83e48
      Leigh B Stoller authored
      starting any one of our scripts can take a second or two. That time is
      spent including and compiling 10000s of thousands of lines of perl
      code, both from our libraries and from the perl libraries.
      
      Mostly this is just a maintenance thing; we just never thought about
      it much and we have a lot more code these days.
      
      So I have done two things.
      
      1) I have used SelfLoader() on some of our biggest perl modules.
         SelfLoader delays compilation until code is used. This is not as
         good as AutoLoader() though, and so I did it with just a few 
         modules (the biggest ones).
      
      2) Mostly I reorganized things:
      
        a) Split libdb into an EmulabConstants module and all the rest of
           the code, which is slowly getting phased out.
      
        b) Move little things around to avoid including libdb or Experiment
           (the biggest files).
      
        c) Change "use foo" in many places to a "require foo" in the
           function that actually uses that module. This was really a big
           win cause we have dozens of cases where we would include a
           module, but use it in only one place and typically not all.
      
      Most things are now starting up in 1/3 the time. I am hoping this will
      help to reduce the load spiking we see on boss, and also help with the
      upcoming Geni tutorial (which kill boss last time).
      92f83e48
  29. 30 Sep, 2010 1 commit
  30. 16 Jul, 2010 1 commit
  31. 15 Jul, 2010 1 commit
  32. 14 Jul, 2010 1 commit
  33. 10 May, 2010 1 commit
  34. 26 Apr, 2010 1 commit
  35. 02 Dec, 2009 1 commit
  36. 22 Oct, 2009 1 commit