1. 30 Dec, 2017 1 commit
  2. 29 Dec, 2017 2 commits
  3. 27 Dec, 2017 1 commit
  4. 26 Dec, 2017 4 commits
  5. 23 Dec, 2017 4 commits
  6. 20 Dec, 2017 1 commit
  7. 19 Dec, 2017 1 commit
    • Mike Hibler's avatar
      Revenge of the Delta Images. · a79af843
      Mike Hibler authored
      Can't live with em, can't kill em dead... When writing my hack
      routine to convert an image path into an imageid, I failed to
      consider the .ddz (delta image) suffix.
      a79af843
  8. 18 Dec, 2017 1 commit
  9. 16 Dec, 2017 2 commits
  10. 14 Dec, 2017 5 commits
  11. 13 Dec, 2017 10 commits
  12. 12 Dec, 2017 3 commits
    • Leigh B Stoller's avatar
      Another mysql 5.7 bug. · d52f35c6
      Leigh B Stoller authored
      d52f35c6
    • Leigh B Stoller's avatar
      Fix; change tbreport to tberror. · 90ab807b
      Leigh B Stoller authored
      90ab807b
    • David Johnson's avatar
      Add Linux exp firewall support for virt_node_public_addr addresses. · 798f9b6f
      David Johnson authored
      A new tmcd command, publicaddrinfo, just dumps the relevant bits of
      virt_node_public_addr to any node in an experiment that has addrs
      allocated (we don't want to restrict based on calling node_id or
      pool_id).
      
      Then the generic getfwconfig() function calls that, and sets some bits.
      I also extended this function to add some dynamic clientside vars
      (EMULAB_DOMAIN, EMULAB_EXPDOMAIN, EMULAB_PUBLICADDRS) so that user
      firewall rule writers can use them to refer to the control net IPs of
      nodes in their experiment (i.e., node-0.EMULAB_EXPDOMAIN); and so that
      rules can be written over EMULAB_PUBLICADDRS -- a command-delineated
      list of IP addrs).
      
      Finally, I extended the Linux firewalling code to allow any experiment
      node to answer ARPs for the public IP addresses; we can't know a priori
      which node should answer -- and it could change.
      
      This closes #353 .
      798f9b6f
  13. 11 Dec, 2017 5 commits