1. 13 Jul, 2017 1 commit
    • Leigh B Stoller's avatar
      Work on issue #302: · 92c8e4ba
      Leigh B Stoller authored
      Add new table experiment_keys to hold RSA priv/pub key pair and an SSH
      public key derived from the private key.
      
      Initialized when experiment is first created, I have not done anything
      to set the keys for existing experiments yet.
      
      But for testing, you can do this:
      
      	use lib "/usr/testbed/lib";
      	use Experiment;
      
      	my $experiment = Experiment->Lookup("testbed", "layers");
      	$experiment->GenerateKeys();
      92c8e4ba
  2. 06 Jul, 2017 1 commit
  3. 20 Jun, 2017 1 commit
  4. 12 Jun, 2017 1 commit
  5. 06 Jun, 2017 2 commits
  6. 05 Jun, 2017 1 commit
  7. 30 May, 2017 1 commit
    • Leigh B Stoller's avatar
      Rework how we store the sliver/slice status from the clusters: · e5d36e0d
      Leigh B Stoller authored
      In the beginning, the number and size of experiments was small, and so
      storing the entire slice/sliver status blob as json in the web task was
      fine, even though we had to lock tables to prevent races between the
      event updates and the local polling.
      
      But lately the size of those json blobs is getting huge and the lock is
      bogging things down, including not being able to keep up with the number
      of events coming from all the clusters, we get really far behind.
      
      So I have moved the status blobs out of the per-instance web task and
      into new tables, once per slice and one per node (sliver). This keeps
      the blobs very small and thus the lock time very small. So now we can
      keep up with the event stream.
      
      If we grow big enough that this problem comes big enough, we can switch
      to innodb for the per-sliver table and do row locking instead of table
      locking, but I do not think that will happen
      e5d36e0d
  8. 16 May, 2017 1 commit
  9. 04 May, 2017 1 commit
  10. 02 May, 2017 1 commit
    • Leigh B Stoller's avatar
      Speed up the instantiate page response time, it was taking forever! · af8cc34f
      Leigh B Stoller authored
      1. Okay, 10-15 seconds for me, which is the same as forever.
      
      2. Do not sort in PHP, sort in javascript, let the client burn those
         cycles instead of poor overworked boss.
      
      3. Store global lastused/usecount in the apt_profiles table so that we
         do not have to compute it every time for profile.
      
      4. Compute the user's lastused/usecount for each profile in a single
         query and create local array. Cuts out 100s of queries.
      af8cc34f
  11. 19 Apr, 2017 1 commit
  12. 17 Apr, 2017 1 commit
  13. 22 Mar, 2017 1 commit
  14. 17 Mar, 2017 1 commit
  15. 07 Mar, 2017 2 commits
  16. 03 Mar, 2017 1 commit
    • Leigh B Stoller's avatar
      Allow the gid in a group_policy to be '*', for example: · f61bab43
      Leigh B Stoller authored
      +---------+---------+---------+---------+--------+---------------+--------+
      | pid     | gid     | pid_idx | gid_idx | policy | auxdata       | count  |
      +---------+---------+---------+---------+--------+---------------+--------+
      | testbed | *       |   10345 |       0 | type   | d430          |     10 |
      
      which says to apply the policy to all subgroups, using the current
      count for the project.
      f61bab43
  17. 27 Feb, 2017 1 commit
  18. 22 Feb, 2017 1 commit
  19. 10 Feb, 2017 2 commits
  20. 06 Feb, 2017 1 commit
  21. 27 Jan, 2017 1 commit
  22. 19 Jan, 2017 2 commits
  23. 09 Jan, 2017 2 commits
  24. 06 Jan, 2017 2 commits
  25. 04 Jan, 2017 3 commits
  26. 27 Dec, 2016 1 commit
  27. 19 Dec, 2016 3 commits
  28. 15 Dec, 2016 1 commit
  29. 08 Dec, 2016 1 commit
  30. 07 Dec, 2016 1 commit