1. 12 Sep, 2017 1 commit
  2. 10 Sep, 2017 1 commit
  3. 07 Sep, 2017 1 commit
  4. 01 Sep, 2017 2 commits
  5. 23 Aug, 2017 1 commit
    • Leigh B Stoller's avatar
      Several changes: · a6cd8ee2
      Leigh B Stoller authored
      1. Get rid of direct queries to wires and interfaces, use library.
      2. Allow node:iface on the command line for ports.
      3. Add -i option to print out results in node:iface. Eventually we want
         to flush card.port output, but lets wait on that for a while.
      4. Switch from card,port to iface lookups.
      5. The DB change adds iface to the port_counters table, no longer using
         card,port. Eventually flush them.
  6. 18 Aug, 2017 1 commit
  7. 17 Aug, 2017 1 commit
  8. 14 Aug, 2017 2 commits
  9. 11 Aug, 2017 1 commit
  10. 08 Aug, 2017 1 commit
  11. 27 Jul, 2017 2 commits
  12. 26 Jul, 2017 2 commits
    • Leigh B Stoller's avatar
      Changes to apt_announcements table: · 4408843a
      Leigh B Stoller authored
      1. Add a unique uuid for a shared lookup token with the web UI.
      2. Add pid_idx for targeting announcements to projects (issue #258).
    • Mike Hibler's avatar
      Support for per-experiment root keypairs (Round 1). See issue #302. · c6150425
      Mike Hibler authored
      Provide automated setup of an ssh keypair enabling root to login without
      a password between nodes. The biggest challenge here is to get the private
      key onto nodes in such a way that a non-root user on those nodes cannot
      obtain it. Otherwise that user would be able to ssh as root to any node.
      This precludes simple distribution of the private key using tmcd/tmcc as
      any user can do a tmcc (tmcd authentication is based on the node, not the
      This version does a post-imaging "push" of the private key from boss using
      ssh. The key is pushed from tbswap after nodes are imaged but before the
      event system, and thus any user startup scripts, are started. We actually
      use "pssh" (really "pscp") to scale a bit better, so YOU MUST HAVE THE
      PSSH PACKAGE INSTALLED. So be sure to do a:
          pkg install -r Emulab pssh
      on your boss node. See the new utils/pushrootkeys.in script for more.
      The public key is distributed via the "tmcc localization" comma...
  13. 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");
  14. 06 Jul, 2017 1 commit
  15. 20 Jun, 2017 1 commit
  16. 12 Jun, 2017 1 commit
  17. 06 Jun, 2017 2 commits
  18. 05 Jun, 2017 1 commit
  19. 04 Jun, 2017 1 commit
  20. 31 May, 2017 1 commit
  21. 30 May, 2017 4 commits
    • Leigh B Stoller's avatar
    • Leigh B Stoller's avatar
      Amend last commit. · 991986c5
      Leigh B Stoller authored
    • 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
    • Leigh B Stoller's avatar
      Possible fix for issue #296 · 60e65004
      Leigh B Stoller authored
  22. 16 May, 2017 1 commit
  23. 04 May, 2017 1 commit
  24. 02 May, 2017 2 commits
  25. 19 Apr, 2017 1 commit
  26. 17 Apr, 2017 2 commits
  27. 29 Mar, 2017 1 commit
  28. 24 Mar, 2017 1 commit
  29. 22 Mar, 2017 1 commit
  30. 17 Mar, 2017 1 commit