1. 30 Jul, 2018 1 commit
  2. 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
  3. 30 Nov, 2012 1 commit
  4. 17 Feb, 2012 1 commit
    • Leigh Stoller's avatar
      BIG reorganization of the install code. · 82e1d812
      Leigh Stoller authored
      * Split up boss/ops/fs install into indvidual modules; generally, what
        was a toplevel phase in the original files is not a file. This
        allowed for better code/variable reuse. No longer monolithic, which
        makes it easy to test and rerun parts.
      
      * Incorporate "update" into the install process. Certain phase file
        can be used in update mode, as when the IP/subnet/domain changes.
      
      * Moved the MFS setup from rc.mkelab into the normal install process.
        Users no longer have to do this themselves. Good thing.
      
      * installvars.pm is a new library that has the merged set of the
        zillion variables that were at the top of boss/fs/ops install.
      82e1d812