1. 18 Jul, 2019 1 commit
  2. 20 Jun, 2019 1 commit
  3. 19 Jun, 2019 1 commit
    • Mike Hibler's avatar
      Further tweaks to jumbo frames code. · 571b4a14
      Mike Hibler authored
      Now use a sitevar, general/allowjumboframes, rather than MAINSITE
      to determine whether we should even attempt any jumbo frames magic.
      
      Use a per-link/lan setting rather than the hacky per-experiment
      setting to let the user decide if they want to use jumbos. In NS
      world, we already had a link/lan method (set-settings) to specify
      virt_lan_settings which is where it winds up now.
      
      Client-side fixes to make jumbos work with vnodes.
      571b4a14
  4. 11 Jun, 2019 1 commit
  5. 03 Jun, 2019 1 commit
  6. 28 May, 2019 1 commit
  7. 17 May, 2019 2 commits
  8. 13 May, 2019 1 commit
    • Mike Hibler's avatar
      Properly cleanup when exportSlice fails. · 638b8731
      Mike Hibler authored
      We were relying on the subsequent unexportSlice call to do the
      cleanup, but it lacks the necessary state to know what needs to
      be cleaned up. The result of left over targets/target groups/extents.
      638b8731
  9. 26 Apr, 2019 2 commits
  10. 19 Apr, 2019 1 commit
    • David Johnson's avatar
      Better handle systemd-networkd chattiness in control net search. · 126ef78e
      David Johnson authored
      systemd-networkd and friends have become very chatty.  This commit
      is about turning down the noise.  It also removes PreferredLiftime=forever
      because it is no longer valid where it used to be, and cannot be used
      apparently in the DHCP case.  Seems that the default is now "forever"
      anyway, so it's now irrelevant to us.  (Older systemd-networkds would
      set the address lifetime to the advertised lease.)
      
      We also only mark an iface with CriticalConnection=yes once that iface
      has been chosen as the control net.  We used to just mark them all
      in the udev helper so that we didn't have to modify the generated
      config after successful detection, but now systemd-networkd complains
      about bringing down a searched-but-not-control-net interface if
      it is critical.  So, avoid that.
      
      Finally, I added `-q` to our invocation of systemd-networkd-wait-online,
      and increased the timeout with which we call it.  Timeout increase is
      because we would get spurious event loop disconnect messages without it;
      and q to quiet it in other ways.  Ugh.
      126ef78e
  11. 15 Apr, 2019 3 commits
    • Mike Hibler's avatar
      Initial steps to enable jumbo frames on experiment interfaces. · 33beb373
      Mike Hibler authored
      This is just mods to the tmcd "ifconfig" command to include an MTU= arg.
      Right now we don't have anything in the DB for MTU, so tmcd is just returning
      "MTU=" which says to not explicitly set the MTU.
      
      It also includes the basic client-side support which I have tested on a
      physical interface with MTU=1500. Further changes will be needed to DTRT
      on virtual interfaces and their physical carrier interface.
      
      But the hope is to get the client-side part nailed down before the next
      set of images are rolled, so that we will be ready when support for the
      front-side (UI and DB state) get added.
      33beb373
    • David Johnson's avatar
      b1110139
    • David Johnson's avatar
      Fix breakage to raw xmlrpc mode in 13ee8406. · 535c8d7a
      David Johnson authored
      (The hack to get "raw" xml mode from xmlrpclib is quite different than
      for m2crypto.  Basically, the response is parsed in the Transport, so
      not only do we need a special raw input method on the ServerProxy, but
      also a custom "raw" transport that skips the parser.)
      535c8d7a
  12. 09 Apr, 2019 1 commit
    • Mike Hibler's avatar
      Hack-ish change to allow ixl0 as control net. · 2452ef19
      Mike Hibler authored
      Our old hack-ish heuristic would only consider 10Gb interfaces if there
      were no 1Gb interfaces. But the new Powder nodes have both and we want
      one of the 10Gb interfaces to be the control net.
      2452ef19
  13. 03 Apr, 2019 1 commit
    • Leigh Stoller's avatar
      Watch for a bogus handshake; I saw this happen on one of the FEs, we did · 58e1192e
      Leigh Stoller authored
      a handshake even though capserver was not running. But the uid/gid
      values were totally bogus. So sanity check them, and if they look
      whacky, abort the handshake until the next time we wake up, to do it
      again.
      
      I go no good theories as to how this happened. A bad theory is that
      maybe some transient startup process bound that socket for a while, but
      that seems incredibly unlikely.
      58e1192e
  14. 02 Apr, 2019 1 commit
  15. 26 Mar, 2019 2 commits
  16. 19 Mar, 2019 2 commits
  17. 14 Mar, 2019 1 commit
  18. 06 Mar, 2019 1 commit
  19. 25 Feb, 2019 1 commit
  20. 21 Feb, 2019 1 commit
  21. 15 Feb, 2019 1 commit
    • Mike Hibler's avatar
      Make sure iscsid picks up change of initiator name. · 1c2d994c
      Mike Hibler authored
      Otherwise you get a lot of this action:
      
      WARNING: 10.254.254.203 (iqn.1993-08.org.debian:01:5ad48b44316d): session reinstatement from different address 10.254.254.201
      
      The issue was that we would restart iscsid after changing the name, but if the
      iSCSI sessions were already open, the name change would not immediately take
      effect (til next reboot).
      
      This will happen if the open-iscsi and/or iscsid service is started at boot time
      prior to the Emulab blockstore config running. We explicitly turned these services
      off in Ubuntu 14, but not in 16 and above cuz that would involve interaction with
      systemd and some of us don't speak systemd. Anyway, this will work even if the
      services are enabled at boot.
      1c2d994c
  22. 29 Jan, 2019 6 commits
  23. 28 Jan, 2019 1 commit
  24. 11 Jan, 2019 1 commit
  25. 04 Jan, 2019 1 commit
  26. 03 Jan, 2019 1 commit
  27. 17 Dec, 2018 1 commit
  28. 11 Dec, 2018 2 commits
    • Leigh Stoller's avatar
    • Leigh Stoller's avatar
      Changes for building/installing capture/console on control nodes: · fabd07a7
      Leigh Stoller authored
      * Makefile changes to build and install nossl versions of capture and
        console on a rack control node (or more generally, a physical node
        hosting boss/ops VMs that are not built on our XEN49 image).
      
      * Add -I (insecure) option to capture, that listens on localhost only.
      
      * Add systemd startup files for capture on ops and boss, I tested these
        on Ubuntu18.
      
      Basic instructions:
      
      * Clone the emulab-devel repo to the control node.
      
        git clone https://gitlab.flux.utah.edu/emulab/emulab-devel.git
      
      * On the control node, install the libssl devel code:
      
        sudo apt-get update
        sudo apt-get install libssl-dev
      
      * configure and build capture. Note that the obj-clientside directory might
        already exist, you can just rm -rf the directory.
      
        control> cd ~elabman
        control> mkdir obj-clientside
        control> cd obj-clientside
        control> /path/to/emulab-devel/clientside/configure
        control> make rack-control
        control> sudo make rack-control-install
        control> (cd os/capture; sudo make rack-control-startup-install)
      
      * start capture.
      
        control> sudo systemctl daemon-reload
        control> sudo systemctl start capture-boss
        control> sudo systemctl start capture-ops
      fabd07a7