1. 07 Jul, 2018 4 commits
  2. 29 Jun, 2018 1 commit
  3. 21 Jun, 2018 1 commit
  4. 20 Jun, 2018 1 commit
    • David Johnson's avatar
      Bring iperf-2.0.2 up to speed for gccs up through 8.x. · 8bd8d4c7
      David Johnson authored
      Unfortunately, I didn't notice the first time, but the include causing
      all the problems was an apparently unnecessary math.h.  Simply removing
      it fixed all the odd libstdc++ errors; trying to fix them all up and
      leaving it in was much more complicated.  This works on gccs 4, 6, 7, 8.
      This is a good outcome because the iperf-2.0.10 patch is still subtly
      wrong in some important way; bandwidths are inconsistent or sometimes
      consistently asymmetric (with no good reason).  So some parameter must
      still not be being exchanged between client and server.
  5. 15 Jun, 2018 1 commit
    • David Johnson's avatar
      Fix doubly-run ntp on Ubuntu 14. · a2c69a18
      David Johnson authored
      /etc/init.d/ntp was being run twice on Ubuntu14 (and was failing slowly
      the first time) because of the presence of
      /etc/network/if-up.d/ntpdate... which would run ntpdate then
      /etc/init.d/ntp via invoke-rc.d... so we would see a double start with
      lots of delay.
      So now we overwrite that hook script!  Ugh.
  6. 12 Jun, 2018 5 commits
  7. 07 Jun, 2018 2 commits
  8. 06 Jun, 2018 1 commit
  9. 05 Jun, 2018 3 commits
  10. 01 Jun, 2018 1 commit
    • David Johnson's avatar
      Add more docker clientside tools. · b0f17e8e
      David Johnson authored
      Especially libvnode_docker::analyzeImageWithBusyboxCommand, which runs
      the busybox-static binary from the root context in the container with
      the given command (and extra container run API configuration).
  11. 31 May, 2018 1 commit
  12. 30 May, 2018 4 commits
    • Leigh Stoller's avatar
      Change to run DHCP on a specific set of interfaces. When XENVIFROUTING · 3c3918cb
      Leigh Stoller authored
      is off, this is just the control net interface (xenbr0). But when
      XENVIFROUTING is on, we want to listen on the control net bridge plus
      all of the container vifs. Since these are not created until the
      container is started, we have to call restartDHCP from emulab-cnet (we
      were already doing that), and now we also call reconfigDHCP() when the
      contain is destroyed so that interface list is correct (note that DHCPD
      does not seem to care if an interface dissappears, or even if an
      interface does not exist when starting.
      The main point here, is that on shared nodes we have to restrict the
      number of interfaces that DHCPd listens on (or even looks at) since it
      can be 100s, and dhcpd was taking well over a minute to start up each
      Aside; minor change to not look at the IP config for bridges, just the
      mac. Takes to long when there are 100s of bridges.
    • Leigh Stoller's avatar
      When XENVIFROUTING is on, and going offline (call new function to · d045249f
      Leigh Stoller authored
      rewrite the interface list in /etc/defaults/isc-dhcp-server. We do
      not need to restart DHCP, it does not mind that the vif is gone.
    • Leigh Stoller's avatar
      With XENVIFROUTING on, no point in restarting DHCP when adding an entry, · 04ebcf11
      Leigh Stoller authored
      since the vif foes not exist yet, and we call restartDHCP() again in
      emulab-cnet after the container and vif exist. In fact, no point in
      restarting DHCP when removing an entry, since by that time the vif is
      gone and dhcpd does not seem to mind that anyway.
    • David Johnson's avatar
      Docker ubuntu18 support. · bee80dcf
      David Johnson authored
  13. 25 May, 2018 10 commits
  14. 24 May, 2018 5 commits
    • Mike Hibler's avatar
      Argh! Typo (Think-o). · 584cc3d4
      Mike Hibler authored
    • Mike Hibler's avatar
      More 4.9 fixin' · e1761131
      Mike Hibler authored
    • David Johnson's avatar
      Fix minor bug in ubuntu18 udev rules. · 0613cd75
      David Johnson authored
    • David Johnson's avatar
    • David Johnson's avatar
      Force systemd-networkd to wait for udev to really finish processing. · 564f821e
      David Johnson authored
      Sometimes there seemed to be a race where systemd-networkd would start
      trying to find .network config files before the emulab control net udev
      rules (the shell script the rule launches, rather) could actually write
      them.  This race would sometimes manifest, but mostly not.
      By default, systemd-networkd does not wait for udev to finish
      processing its device events.  This seems odd, but I guess it is not
      expecting dynamic configuration in /run/systemd/network like we use
      (although its docs explicitly allow for this case).  Oh well.  `udevadm
      settle` is supposed to indicate that udev is done processing all device
      events; but it must not mean that it is finished processing all the
      rules!  So not only do we wait for it to settle; we wait for the
      appearance of at least one .network file (that we wrote, hopefully) in
      /run/systemd/network .  No one else would ever write them there,