-
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