1. 02 Dec, 2014 1 commit
  2. 12 May, 2014 1 commit
  3. 12 Feb, 2014 1 commit
    • Mike Hibler's avatar
      Add frisbee master server mechanisms for turning on dynamic rate tuning. · d9ee4a67
      Mike Hibler authored
      For the Emulab configuration, we add the new site variable
      "images/frisbee/maxrate_dyn" which should be set non-zero to enable
      dynamic adjustment. If maxrate_dyn is enabled, then the maxrate_{std,usr}
      values are used as both the initial and maximum values for the BW of any
      instance. Really, if maxrate_dyn is on, then both of those should be set
      to the same value so that all servers are operating the same and the value
      should be just above the link BW.
      
      For the "null" configuration (aka, the subboss configuration),
      this is set by adding command line options:
          -O dynamicbw=1,bandwidth=1100000000
      which would enable it and start/cap the BW at 1.1Gb/sec.
      d9ee4a67
  4. 08 Jan, 2014 1 commit
  5. 06 Jan, 2014 1 commit
  6. 17 Oct, 2013 1 commit
  7. 09 Aug, 2013 1 commit
  8. 17 Jun, 2013 1 commit
  9. 18 Jan, 2013 1 commit
  10. 06 Dec, 2012 1 commit
  11. 30 Oct, 2012 1 commit
  12. 26 Oct, 2012 1 commit
  13. 15 Mar, 2012 1 commit
  14. 10 Feb, 2012 1 commit
  15. 02 Feb, 2012 1 commit
    • Leigh Stoller's avatar
      Add a couple of changes for the GPO. · cfbcf2c4
      Leigh Stoller authored
      1. Change default slice expiration to a new site variable called
         protogeni/default_slice_lifetime, defaults to six hours.
      
      2. Add a site variable (protogeni/warn_short_slices) to tell the
         sa_daemon if it should send email to war about short lived slices
         expiring, defaults to off.
      cfbcf2c4
  16. 02 Dec, 2011 1 commit
    • Leigh Stoller's avatar
      Changes to allow new users to request their encrypted SSL certificate · 8def7e94
      Leigh Stoller authored
      on the join/start project pages. At the moment this is conditional
      under the PROTOGENI flag, since users on non-protogeni sites rarely
      need an encrypted SSL certificate. The initial passphrase has to be
      store someplace since we cannot built the certificate until the user
      is approved, so put it into the users table, and delete when the first
      certificate is built (at approval).
      8def7e94
  17. 04 Oct, 2011 1 commit
  18. 28 Jul, 2011 1 commit
    • Leigh Stoller's avatar
      Power "saving" additions from Barry Trent, who got them from Kevin · 03478fb9
      Leigh Stoller authored
      Lahey.
      
      Power saving turns off nodes that have been sitting in PXEWAIT (and
      are thus free) for more then a set amount of time (see sitevar
      general/idlepower_idletime, which defaults to 3600 seconds).
      
      The driver script is tbsetup/idlepower.in and needs to be added to
      /etc/crontab at sites that want to do this. Even so, operation is
      enabled by the sitevar general/idlepower_enable. Each time it runs, it
      checks for nodes that need to be turned off, and then calls power.
      Note: This should be a daemon not a cron job.
      
      To be considered for power saving, you must add an attribute to the
      node_type_attributes table called 'idlepower_enable', set to 1.
      
      Locally, I hacked up stated and power to make the state transitions
      legal so that stated does not whine. I added POWEROFF as a valid
      transition from any state, to opmodes NORMAL, NORMALv1, and NORMALv2.
      Barry's original patch already had a state transition for PXEKERNEL.
      In power, I added code to look at the actual operation, and in the
      case of "on", do not send an event if the node is not in POWEROFF,
      since a user can foolishly say power on anytime, and the node is on
      nothing is every going to change, and the state transition would be
      wrong.
      
      node_reboot takes of powering nodes on, when they are in POWEROFF.
      
      Barry on copyright issues:
       "I'm not sure those rights are mine to grant! Remember that this code
       came originally from Kevin Lahey (kml@patheticgeek.net) and
       originated at DETER (although he's apparently not there anymore). I
       don't foresee a problem from our point of view (but I'll double
       check, of course). Shall I try to contact Kevin try to sort this mess
       out, or do you think it's better to coordinate from your end?"
      03478fb9
  19. 02 Jun, 2011 1 commit
  20. 18 May, 2011 1 commit
    • Mike Hibler's avatar
      Support image PUT (aka, "upload") and assorted minor changes. · 77dbad39
      Mike Hibler authored
      1. Support for PUT.
      
      The big change is support for uploading via the master server, based heavily
      on the prototype that Grant did. Currently only host-based (IP-based)
      authentication is done as is the case with download. Grant's SSL-based
      authentication code is "integrated" but has not even been compiled in.
      
      The PUT protocol allows for assorted gewgaws, like specifying a maximum size,
      setting a timeout value, returning size and signature info, etc.
      
      There is a new, awkwardly-named client utility "frisupload" which, like the
      download client, takes an "image ID" as an argument and requests to upload
      (PUT) that image via the master server. As with download, the image ID can
      be either of the form "<pid>/<emulab-image-name>", to upload/update an actual
      Emulab image or it can start with a "/" in which case it is considered to
      be a pathname on the server.
      
      On the server side, the master server takes PUT requests, verifies permission
      to upload the image, fires up a separate instance of an upload daemon (with
      the even catchier moniker "frisuploadd"), and returns the unicast addr/port
      info to the client which then begins the upload. The master server also acts
      as a traffic cop to make sure that downloads and uploads (or uploads and
      uploads) don't overlap.
      
      This has been integrated into the Emulab "create image" process in a
      backward-compatible way (i.e., so old admin MFSes will continue to work).
      Boy, was that fun. One not-so-desirable effect of this integration is that
      images now traverse our network twice, once to upload from node to boss and
      once for boss to write out the image file across NFS to ops. This is not
      really something that should be "fixed" in frisbee, it is only "undesirable"
      because we have a crappy NFS server.
      
      What has NOT been done includes: support of hierarchical PUT operations
      (we don't need it for either the elabinelab or subboss case), support for
      uploading standard images stored on boss (we really want something better
      than host-based authentication here), and the aforementioned support of
      SSL-based authentication.
      
      2. Other tidbits that got mixed in with PUT support:
      
      Added two new site variables:
          images/frisbee/maxrate_std
          images/frisbee/maxrate_usr
      which replace the hardwired (in mfrisbeed and frisbeelauncher before that)
      bandwidth limits for image download. mfrisbeed reads these (and the
      images/create/* variables) when it starts up or receives a HUP signal.
      These could be read from the DB on every GET/PUT, but they really don't change
      much and I needed something to test the reread-the-config-on-a-HUP code!
      
      Fixed avoidance of "problematic multicast addresses" so it would actually
      work as intended.
      
      Lots of internal "refactoring" to make up for things I did wrong the first
      time and to give the general impression that "Wow, Mike did a LOT!"
      77dbad39
  21. 09 Nov, 2010 1 commit
    • Mike Hibler's avatar
      Clean up some update turds. · 1b7ca63a
      Mike Hibler authored
      Cody updated his year old elabinelab and uncovered some problems with the
      update process.  Note the updates to the install/updates scripts are just
      to add "MASTER_SITE_FREEBSD=1" to the make lines.  This doesn't change
      anything functionally, it just speeds up the builds for older FreeBSDs where
      some of the MASTER_SITEs no longer exist.
      1b7ca63a
  22. 21 Oct, 2010 1 commit
  23. 13 May, 2010 1 commit
    • Mike Hibler's avatar
      Add site variables to control image creation. · a3f42091
      Mike Hibler authored
      These variables were previously constants hardwired into create_image:
      
      images/create/maxwait:
          Max time (minutes) to allow for saving an image
      images/create/idlewait:
          Max time (minutes) to allow between periods of progress
          (image file getting larger) when saving an image (should be <= maxwait)
      images/create/maxsize:
          Max size (GB) of a created image
      a3f42091
  24. 16 Apr, 2010 1 commit
  25. 15 Apr, 2010 2 commits
  26. 14 Apr, 2010 1 commit
    • Mike Hibler's avatar
      Add some useful elabinelab sitevars. · 9bb38c10
      Mike Hibler authored
      New sitevars:
        elabinelab/singlenet     set the system-wide default for cnet implementation
        elabinelab/boss_osid     default OSID for boss node
        elabinelab/ops_osid      default OSID for ops node
        elabinelab/fs_osid       default OSID for fs node
      
      Also mark the various elabinelab/*pkg* sitevars as deprecated.  Package
      versions are just too dependent on the OS running and we almost always
      wind up overriding these sitevars in rc.mkelab anyway.
      9bb38c10
  27. 06 Apr, 2010 1 commit
  28. 31 Mar, 2010 1 commit
    • Srikanth Chikkulapelly's avatar
      Added 2 sitevar variables that help CM implement policies. · f87e07a3
      Srikanth Chikkulapelly authored
      1) max_ticket_lifetime : It determines how long a sliver can live. Default is set to 90 days.
      2) max_components : It limits the number of components that can be requested/allocated to a user. Default value -1 indicates that there is no limit. any number of components can be requested/allocated.
      f87e07a3
  29. 08 Feb, 2010 1 commit
  30. 02 Nov, 2009 1 commit
  31. 05 Aug, 2009 1 commit
  32. 04 Aug, 2009 2 commits
  33. 30 Jan, 2009 1 commit
  34. 07 Nov, 2008 1 commit
  35. 28 Jul, 2008 1 commit
    • Mike Hibler's avatar
      Update the sitevars. · d85eaf21
      Mike Hibler authored
      Build sitevars-create.sql with "insert ignore"
      
      NOTE: output of "gmake sitevars" must still be tweaked by hand!
      d85eaf21
  36. 17 Jul, 2008 1 commit
  37. 27 Apr, 2006 1 commit
    • Kirk Webb's avatar
      · 296da8ea
      Kirk Webb authored
      Switch around 'value' and 'defaultvalue' fields for "watchdog/rusage" and
      set value field to NULL.
      296da8ea
  38. 01 Mar, 2006 1 commit
    • Kirk Webb's avatar
      · 0314c0ef
      Kirk Webb authored
      Update description and defaults for the watchdog/rusage sitevar
      (now in terms of seconds instead of minutes).
      0314c0ef