1. 17 Jan, 2017 1 commit
  2. 12 Jan, 2017 1 commit
  3. 11 Jan, 2017 2 commits
  4. 08 Jan, 2017 1 commit
  5. 07 Jan, 2017 1 commit
    • Leigh B Stoller's avatar
      Two minor fixes: · edde5522
      Leigh B Stoller authored
      1. For multi-architecture, being fixed to a specific node is the same as
         being fixed to a specific type.
      
      2. Watch for return value from nalloc, where -1 becomes 255. Hate that.
      edde5522
  6. 05 Jan, 2017 1 commit
  7. 03 Jan, 2017 1 commit
  8. 29 Dec, 2016 1 commit
    • Mike Hibler's avatar
      Modernize elabinelab and Emulab install support a bit. · f7e53243
      Mike Hibler authored
      Support FreeBSD 10.3. We will need to be moving to this before long
      as 10.2 EOLs in two days.
      
      Support setup of "Emulab-aware" ZFS use in install scripts. Note that
      the core support code was already done (WITHZFS, WITHAMD). Mostly this
      involves changes to setup either amd (WITHAMD==1) or autofs (WITHAMD==0)
      on the boss node and to NOT add mounts of /{users,groups,proj} to
      /etc/fstab. We still need to add a section to the install documentation
      about setting up a zpool for Emulab to use. There was also a fix to the
      firstuser script which did not do the account setup correctly.
      
      Support setup of ZFS in elabinelab. The elabinelab attributes CONFIG_ZFS
      and CONFIG_AUTOFS are used to convey intent here. Currently they can only
      be used in an "ops+fs" config (e.g., the standard boss and ops config,
      NOT the seperate fs node config). It should work with either the physical
      or virtual node setups:
      
      * For the physical node setup, we actually use local blockstores in the
        ops node config: a SYSVOL blockstore for /usr/testbed and a tiny 1Mib
        NONSYSVOL blockstore. The latter blockstore is not actually used, we
        just make it to force setup of a ZFS zpool which we then use for the
        inner elab.
      
      * For the virtual node setup, we just identify the virtual EXTRADISK
        intended for "/q" and create a zpool on that device.
      
      I would like to change all physical elabinelab setups to use blockstors
      rather than the current hacky mkextrafs usage. But that is a task for
      another day.
      
      Finally, a couple of random changes in elabinelab code: change the
      CentOS image downloaded to CENTOS7-64-STD, increased the default sizes
      of the EXTRADISKS used in the VM config.
      f7e53243
  9. 21 Dec, 2016 1 commit
  10. 15 Dec, 2016 2 commits
  11. 14 Dec, 2016 1 commit
    • David Johnson's avatar
      Bring libosload_new back into synch with libosload. · 48da2bbf
      David Johnson authored
      There wasn't a ton to do here (thanks mostly to Mike and Leigh keeping
      this pretty up-to-date), but there were a few new cut and paste bugs,
      and a few places where bugfixes or new features from libosload hadn't
      quite made it across.
      
      Maybe libosload_new hadn't been tested with vnodes, and at any rate, the
      type/class-based loading mechanism couldn't find a libosload_new package
      for them.  But the core of the support was there (libosload_virtnode).
      So I added a libosload_pcvm class that sits atop libosload_virtnode.
      48da2bbf
  12. 08 Dec, 2016 1 commit
  13. 07 Dec, 2016 1 commit
  14. 30 Nov, 2016 1 commit
  15. 11 Nov, 2016 2 commits
  16. 07 Nov, 2016 1 commit
  17. 02 Nov, 2016 2 commits
  18. 31 Oct, 2016 3 commits
  19. 27 Oct, 2016 1 commit
  20. 24 Oct, 2016 1 commit
  21. 21 Oct, 2016 2 commits
  22. 20 Oct, 2016 1 commit
  23. 17 Oct, 2016 2 commits
  24. 14 Oct, 2016 2 commits
    • Leigh B Stoller's avatar
      Attempt to address the problem described in issue #166; that nodes fail · 5d7164b3
      Leigh B Stoller authored
      to go from PXEBOOTING (pxewakeup) to actually booting, but we do not
      know that for a really long time cause we send a BOOTING event from
      bootinfo right after PXEBOOTING, since that was the only place to hook
      it in. Well Mike discovered the "on commit" support in dhcpd, and so
      that is what we are going to use now. Note that uboot nodes have been
      using on commit, now all nodes will when BOOTINFO_EVENTS=0.
      
      Mike's reportboot program is now a daemon, renamed to report_daemon.
      The original reportboot program is a little script that writes the
      arguments from dhcpd to a unix socket to be picked up by the daemon,
      which does the original work of mapping the IP/Mac to a node id and
      sending an event. The code has also been modified to run on a subboss
      using the same node mapping given to to dhcpd, reconstituted as DBM
      file by subboss_dhcpd_makeconf.
      
      The reason for using a daemon this way is so that we do not hang up
      dhcpd in case we cannot get to the event system. The unix domain
      socket will give us some amount of buffering, but I suspect that any
      event problem will eat that space up quickly, and I will be back to
      revisit this (probably want reportboot to not block on its write
      to the socket).
      
      pxeboot changed to not send PXEBOOTING or BOOTING when
      BOOTINFO_EVENTS=0.
      5d7164b3
    • Leigh B Stoller's avatar
      Couple of tiny fixes that I made while stumbling around on a question · ae70d47f
      Leigh B Stoller authored
      about nobwshaping from Kirk.
      ae70d47f
  25. 12 Oct, 2016 1 commit
  26. 11 Oct, 2016 2 commits
  27. 10 Oct, 2016 1 commit
    • Leigh B Stoller's avatar
      Address linktest problems reported by Mike in issue #160: · e7422d49
      Leigh B Stoller authored
      1. Changes to gentopofile to not put in linktest info for links and lan
         with only one member.
      
      2. Fix to the CM for deletenode of a node that has tagged links.
      
      3. Fixes to the status web page for deletenode; we were installing the
         linktest event handlers multiple times.
      
      4. Pass through -N argument to linktest from the CM, when the experiment
         has NFS mounts turned off, so that we use loghole to gather the data
         files (instead of via NFS).
      
      This closes issues #160.
      e7422d49
  28. 06 Oct, 2016 1 commit
  29. 03 Oct, 2016 2 commits