1. 07 Nov, 2001 1 commit
  2. 06 Nov, 2001 1 commit
  3. 05 Nov, 2001 1 commit
  4. 23 Oct, 2001 1 commit
  5. 17 Oct, 2001 3 commits
  6. 30 Sep, 2001 1 commit
  7. 28 Sep, 2001 1 commit
  8. 26 Sep, 2001 1 commit
  9. 18 Sep, 2001 1 commit
  10. 17 Sep, 2001 1 commit
  11. 06 Sep, 2001 1 commit
    • Leigh B. Stoller's avatar
      Changes to nfree in how scheduled reloads are handled. Instead of · 2007505d
      Leigh B. Stoller authored
      firing off an os_load, just move the node from its current reservation
      to emulab-ops/reloadpending. This moves the operation out of band from
      the user's perspective (he gets more immediate response when an
      experiment ends, and besides we cannot handle mass reloads anyway, and
      so this approach is unusable until Frisbee.
      
      Change the reload_daemon to look for free nodes that need a reload (as
      before) *and* nodes in emulab-ops/reloadpending (as put there by nfree).
      In this case, the imageid comes from the reloads table instead of the
      node-types table. I also updated the reload_daemon to use libdb routines.
      
      Also change testbed/reloading to emulab-ops/reloading. Maybe someday
      I'll remove these hardwired strings.
      2007505d
  12. 23 Aug, 2001 1 commit
    • Mac Newbold's avatar
      Lots of small changes for turning our 'require lib*' lines into 'use lib*'... · e2ed8a1c
      Mac Newbold authored
      Lots of small changes for turning our 'require lib*' lines into 'use lib*' lines. Proper modules declare themselves as a package, and use Exporter to export the names of the subroutines that should be visible from the outside world. Many of ours didn't do that, it was just a file with a bunch of subs in it. So now I've fixed many of them to be proper, and removed the requires and 'push(@INC,...)' hacks and changed it to the proper 'use lib @prefix@/lib/;' and use lib*.
      e2ed8a1c
  13. 01 Aug, 2001 1 commit
  14. 21 Jul, 2001 1 commit
    • Mac Newbold's avatar
      Many changes and updates for handling new types. The db now has types like... · 78b4e4f5
      Mac Newbold authored
      Many changes and updates for handling new types. The db now has types like 'pc600', 'pc850', and 'dnard', and each type has a class like 'pc' or 'shark'. This updates scripts that use types to use classes where appropriate, and to handle the new types where there were hardcoded things that couldn't be eliminated right now.
      78b4e4f5
  15. 29 Jun, 2001 1 commit
  16. 10 May, 2001 1 commit
    • Leigh B. Stoller's avatar
      Lots of little changes for sending email to the right places, with · 3285bc3e
      Leigh B. Stoller authored
      proper headers. Split out some of the mail into testbed-logs,
      testbed-ops, and testbed-approval. Added a library for including from
      our perl scripts. Contains a couple of mail helper functions, but will
      hopefully contain more as time goes by.
      
      Fixed a bug in the web interface that was causing breakage for people
      with multiple accounts. Mac and Jay have noticed this, when logging
      out and trying to join or create a project under a new or different
      name.
      3285bc3e
  17. 03 May, 2001 1 commit
    • Leigh B. Stoller's avatar
      A slew of changes for new images/os_info tables. disk_images is gone, · 23a230e8
      Leigh B. Stoller authored
      replaced by the "images" table. New os_info table is added. New web
      pages to add and delete OSIDs to/from the os_info table, for use in
      the NS file. tb-create-os is gone. handle_os no longer operates on the
      tbcmds file, and no longer writes anything into the ir file. Moved the
      setting up of os state (nodes table) from os_setup to handle_os, where
      it should be. os_load and sched_reload now take a single argument, the
      name of the imageid from the images table.
      23a230e8
  18. 30 Mar, 2001 1 commit
    • Leigh B. Stoller's avatar
      Reloading daemon. Looks for free nodes that have not been reloaded · 74d21844
      Leigh B. Stoller authored
      since the last reservation (as determined by last_reservation table).
      Picks one (randomly) from that set of nodes, and calls sched_reload on
      it. Then waits until the node has finished reloading, as determined by
      the reserved table, which gets cleared by the tmcd when the node first
      reboots after a scheduled reload. Sleeps 30 seconds, and then goes
      around again. So at most one node is tied up in a reload at a time,
      which seems like a good balance between trying to keep the machines in
      a pristine state, and having nodes available for use.
      
      The advantage of this approach is that instead of calling sched_reload
      on 40 nodes (after generating a new image) and watching the network
      meltdown, we can let the nodes reload at a slower pace. We could call
      sched_reload on allocated nodes so that they will load when freed, but
      we run into the problem of big experiments ending and causing meltdown.
      
      The downside is that this approach is a little too aggressive. Nodes
      will end up reloading after just a single experiment. Need finer grain
      control over when to reload, but I will leave that as an exercise for
      later.
      74d21844