1. 16 Aug, 2013 2 commits
  2. 15 Aug, 2013 14 commits
    • Mike Hibler's avatar
    • Mike Hibler's avatar
      Change the semantics of "reset". · c30b122e
      Mike Hibler authored
      "reset" now just unmounts blockstores, it does not destroy them.
      Need this so that people can include a SYSVOL blockstore in a custom image
      (the only place where "reset" is used). Also, destroying blockstores would
      have come as an unpleasant surprise to anyone who created a custom image
      and then expected their data to still be around afterward!
      
      Also work around a bizzare bug in BSD sed that happens in the prepare script.
      That script does:
      
           sed -e '/# next line is swap device/,+1d' /etc/fstab
      
      which should remove the matched comment and the line after it (the swapdev
      entry). But if there are EXACTLY two additional lines after the matched line,
      it would remove both of them (effectively "+2")! So if there was a mount for
      a blockstore device after the swap device, prepare would remove that line too.
      
      So in the finest tradition of "if it hurts, don't do it", the blockstore code
      makes sure that it adds at least two additional lines.
      c30b122e
    • Mike Hibler's avatar
      Fixed check vs. max offset, it was wrong. · f730b322
      Mike Hibler authored
      If number was positive, was converting to "(N)" for some reason.
      Parens don't compare well with integers...
      
      Also don't need "bc" just to compute abs(), just use "tr" to remove '-'.
      
      Also adjust the max offset a smidge to 5ms, 1ms is a bit tight.
      f730b322
    • Gary Wong's avatar
      Add tmcd support for the proposed "geni-get" GENI client side. · f1120a88
      Gary Wong authored
      This allows nodes in GENI slices to retrieve information about their
      sliver and slice via tmcc (or equivalent client-side support).  The
      set of queries available and their names were agreed upon in GEC 17
      sessions and subsequent discussions.
      f1120a88
    • Leigh Stoller's avatar
      f3078723
    • Leigh Stoller's avatar
      7bb1a7fd
    • Leigh Stoller's avatar
      Update last_report in the node_activity table, at the same time · fafb25b8
      Leigh Stoller authored
      we update last_ext_act, since this is how idle determines staleness.
      Not sure this is the best approach though.
      fafb25b8
    • Leigh Stoller's avatar
      Minor debugging change. · b3c13417
      Leigh Stoller authored
      b3c13417
    • Leigh Stoller's avatar
      Turn off actual norenew until the 30th. · fc0b3ae9
      Leigh Stoller authored
      fc0b3ae9
    • Leigh Stoller's avatar
      Add state transitions for updating users. · 57a83f9e
      Leigh Stoller authored
      57a83f9e
    • Leigh Stoller's avatar
      Change threshold to 3 instead of 4. · 5e791679
      Leigh Stoller authored
      5e791679
    • Leigh Stoller's avatar
      Minor bug fix. · 5b15bc8b
      Leigh Stoller authored
      5b15bc8b
    • Leigh Stoller's avatar
      Changes to idle handling in ProtoGeni slivers · ec076c05
      Leigh 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
    • Leigh Stoller's avatar
      7c4ca686
  3. 13 Aug, 2013 4 commits
  4. 12 Aug, 2013 1 commit
  5. 09 Aug, 2013 17 commits
  6. 08 Aug, 2013 2 commits