1. 01 Nov, 2014 1 commit
    • Brecht Vermeulen's avatar
      Fix regexps in 'Attempt to parse the violations into something human readable' · ca0bac29
      Brecht Vermeulen authored
      e.G. the following assign violations gave just 'Not enough bandwdith' as the 0 always matched.
      Now we match with any number 1-9
      
         BEST SCORE:  50.5 in 0 iters and 0.008631 seconds
        unassigned:  0
        pnode_load:  26
        no_connect:  0
        link_users:  0
        bandwidth:   0
        desires:     0
        vclass:      0
        delay:       0
        trivial mix: 0
        subnodes:    0
        max_types:   0
        endpoints:   0
      ca0bac29
  2. 28 Oct, 2014 1 commit
  3. 22 Oct, 2014 1 commit
  4. 08 Oct, 2014 1 commit
  5. 07 Oct, 2014 1 commit
  6. 25 Sep, 2014 2 commits
  7. 27 Aug, 2014 1 commit
  8. 31 Jul, 2014 1 commit
  9. 11 Jul, 2014 1 commit
  10. 11 Jun, 2014 1 commit
  11. 18 May, 2014 1 commit
  12. 13 May, 2014 1 commit
  13. 25 Apr, 2014 1 commit
  14. 24 Apr, 2014 1 commit
  15. 21 Apr, 2014 1 commit
  16. 14 Apr, 2014 1 commit
  17. 07 Apr, 2014 1 commit
  18. 31 Mar, 2014 1 commit
  19. 27 Mar, 2014 1 commit
    • Leigh B Stoller's avatar
      Add firewall and linkdelay support. · cee38539
      Leigh B Stoller authored
      Firewall support is preliminary and is relevant to XEN containers
      only. A suitable rspec fragment for your node is:
      
          <emulab:firewall style=closed'>
            <emulab:exception port='80' direction='incoming' ip='myip'/>
          </emulab:firewall>
      
      won't bother to explain, its obvious and going to change pretty
      quickly. Well, I should mention that "myip" means to replace the
      ip with the ip address of the caller.
      
      Linkedelay support allows passing through basic Emulab traffic shaping
      parameters, in a linkdelay only configuration.
      cee38539
  20. 04 Mar, 2014 1 commit
  21. 27 Feb, 2014 1 commit
  22. 13 Feb, 2014 1 commit
  23. 05 Feb, 2014 1 commit
    • Leigh B Stoller's avatar
      Switch from XEN-STD to UBUNTU12-64-STD for default XEN container · 929a46f6
      Leigh B Stoller authored
      image. Been wanting to do this for a while since the dependency on
      copying the contents of the root disk to create an image, has always
      been a dubious approach, since there is no consistency over time,
      and because it is unclear if the resulting image will boot on a
      physical node later (cause of the XEN stuff that is on the disk).
      929a46f6
  24. 04 Feb, 2014 1 commit
  25. 31 Dec, 2013 1 commit
  26. 06 Dec, 2013 1 commit
  27. 07 Nov, 2013 1 commit
  28. 06 Nov, 2013 1 commit
  29. 31 Oct, 2013 2 commits
  30. 11 Oct, 2013 1 commit
  31. 09 Sep, 2013 1 commit
  32. 30 Aug, 2013 1 commit
  33. 29 Aug, 2013 1 commit
  34. 28 Aug, 2013 1 commit
  35. 15 Aug, 2013 1 commit
    • 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
  36. 08 Aug, 2013 1 commit
  37. 11 Jul, 2013 1 commit
    • Leigh B Stoller's avatar
      Implement speaksfor (non-abac) support. · 8d53b3fd
      Leigh B Stoller authored
      CM V2 (and thus the AM) now accept a type=speaksfor credential along
      with regular credentials. When supplied, the speaksfor caller must be
      equal to the owner of the speaksfor credential and the target must be
      equal to the owner of the regular credential(s). All operations take
      place in the context of the spokenfor user.
      
      Added speaksfor slots to geni_slices,geni_aggregates and geni_tickets.
      Also to the history table. But these are just the most recent data.
      Each transaction is logged as normal, and the metadata now includes
      the speaksfor data and the log always includes all of the credentials.
      
      For testing, there is a new script in the scripts directory to
      generate a speaksfor credential. Not installed since it is really
      a hack. But to create one:
      
        perl genspeaksfor urn:publicid:IDN+emulab.net+user+leebee \
      	urn:publicid:IDN+emulab.net+user+stoller
      
      which generates a speaksfor credential that says stoller is speaking
      for leebee.
      
      Given a slice credential issued to leebee, the test scripts can be
      invoked as follows (by stoller):
      
        createsliver.py -S speaksfor.cred -s slice.cred -c leebee.cred
      
      A copy of leebee's self credential is needed simply cause of the test
      script's desire to talk to the SA (which does not support speaksfor).
      Not otherwise needed.
      
      Oh, not tested on the AM interface yet.
      8d53b3fd
  38. 04 Jul, 2013 1 commit