1. 28 Nov, 2018 2 commits
    • Leigh Stoller's avatar
      Part of issue #472; move tip and client part of xmlrpc, into the · 33b207d3
      Leigh Stoller authored
      clientside subdir so they can be installed on nodes.
    • Mike Hibler's avatar
      Various Linux local blockstore changes: · 7bd23fb1
      Mike Hibler authored
      Most important: if a <2TB blockstore has an ext4 filesystem, make sure we
      create it without the 64bit and huge_file features. The former will make
      it impossible (currently) to take a snapshot since imagezip does not handle
      64-bit blocknumbers (working on it...)
      Don't stripe an LVM LV over more than 8 devices. Some of the Clemson nodes
      have 20+ disks and we won't buy much (and it might even be counterproductive)
      to try to stripe writes over all devices all the time.
      Still trying to get lvcreate to not prompt when one of the devices has an
      old metadata prompt. -Zy is supposed to prevent that, but it doesn't. Try
      adding -y as well.
      Not related: in the BEGIN block, don't cat $ETCDIR/genvmtype unless it
      actually exists. Not everything is a docker container ya know...
  2. 08 Nov, 2018 1 commit
  3. 06 Nov, 2018 3 commits
  4. 05 Nov, 2018 2 commits
    • Leigh Stoller's avatar
      Working Mellanox user alloc switch support (issue #445): · 95e7bded
      Leigh Stoller authored
      * The primary problem with the mellanox is that the install image does a
        kexec out of ONIE into Linux, spends 30+ minutes doing stuff, and then
        reboots. This throws the reload state machine out of whack cause we do
        not get a chance to send the RELOADDONE state. So ... some change to
        rc.testbed and rc.reload on the USB dongle: the ONIE MFS sends
        RELOADING and writes a flag file to the ONIE partition on the
        "disk" (not the usb). Then the kexec into MLNX, the install happens,
        and reboots. The next boot into ONIE sees the flag file, erases it and
        sends REDLOADDONE. Waits for a bit, and then continues on the normal
        path. This abuses stated in that there a whiny messages in the stated
        log file, but I am immune to stated whining.
      * Another item of note is that the switch DHCPs, but only to get the IP
        info, there is no ability to give it an initial config file like we
        can with the Dell switches. The main problem here is that the switch
        comes up with its default login/password which is obviously well known
        cause its in the manual. That means there is a window where the switch
        is vulnerable, but since we block the switches from the public side,
        this is not a serious problem. As soon as we can get in (sshd is
        running) we login and update the config with passwords, keys,
      * Other changes to the machine dependent osload library module, I had
        done some of this before switching to the Dells way back when, but it
        needed to be updated/completed.
    • Leigh Stoller's avatar
      Allow NTPSERVER override in the NS file. · 849432e1
      Leigh Stoller authored
  5. 30 Oct, 2018 2 commits
  6. 26 Oct, 2018 6 commits
  7. 25 Oct, 2018 3 commits
    • David Johnson's avatar
      Replace the Docker entrypoint/cmd/env implementation for augmented images. · a986a085
      David Johnson authored
      (Also, add support for user to change container entrypoint at runtime.
      Note also that the server side now stores the entrypoint/cmd/env
      attributes as base64url-encoded virt_node_attributes, so that we can
      just use the existing table_regex for those values.)
      We add a new runit service (/etc/service/dockerentrypoint) to
      clientside/tmcc/linux/docker/dockerfiles/common to handle the
      entrypoint/cmd/env/workingdir/user emulation.  From the comments:
        Docker's semantics for ENTRYPOINT/CMD vary depending on if those
        values are specified as arrays of string, or simple as single strings
        (which must be interpreted by /bin/sh -c).
        Handling all the quoting possibilities in the shell is a major pain.
        So, this script handles the basic stuff (in particular, sourcing env
        vars, because we want the shell to interpret them!) -- then execs our
        perl companion script (run.pl) to deal with the entrypoint/command
        files that libvnode_docker::emulabizeImage and
        libvnode_docker::vnodeCreate populated.
        libvnode_docker creates these single-line files in /etc/emulab/docker
        as either string:hexstr(<entrypoint-or-cmd-string>), or
        array:hexstr(a[0]),hexstr(a[1])... .  This allows us to preserve the
        original type of the image's entrypoint/cmd as well as the runtime
        entrypoint/cmd, and to preserve the exact bytes for the eventual final
        call to exec.
        The static files builtin to an emulabized image are
        /etc/emulab/docker/{entrypoint.image,cmd.image}, and those created
        dynamically at runtime if user changes the entrypoint or cmd are
        bind-mounted to /etc/emulab/docker{entrypoint.runtime,cmd.runtime}.
        Given the presence (or absence!) of those files, this script
        implements the emulation, based upon the content in those files.
    • David Johnson's avatar
    • David Johnson's avatar
  8. 02 Oct, 2018 1 commit
    • David Johnson's avatar
      Force a regeneration of /etc/machine-id in prepare for systemd-based OSes. · b639e7f1
      David Johnson authored
      (Also link the dbus machine-id file to the one systemd will generate on
      the next boot.  This seems safe and correct.)
      Certain things (like systemd's dhcp client) use the machine-id as a seed
      for derived values.  For instance, systemd's dhcp client offers a
      ClientIdentifier in the new client style, and some servers will return
      the same address to *all* requesting clients, instead of returning only
      based on source MAC.  Can't have any of that confusion.
  9. 26 Sep, 2018 1 commit
  10. 04 Sep, 2018 1 commit
  11. 29 Aug, 2018 3 commits
  12. 24 Aug, 2018 2 commits
  13. 22 Aug, 2018 1 commit
  14. 21 Aug, 2018 3 commits
  15. 17 Aug, 2018 1 commit
  16. 16 Aug, 2018 3 commits
  17. 15 Aug, 2018 3 commits
  18. 14 Aug, 2018 1 commit
  19. 10 Aug, 2018 1 commit