32020-03-07 03:32:14ClintonEbadiupdate machine-template git repo link (moved to zz_old)22013-07-14 02:50:27ClintonEbadinote that macvtap is the way to go in the future for networking12012-12-30 23:47:22ClintonEbadiinitial install stepsThis document was written with using the GUI virt-manager to deploy a KernelVirtualMachine using our AutomatedSystemInstall. It's probably worth automating this with virsh/virtinst after solidifying things a bit more.

Create a post install script in the machine-template. A post install script should extract kerberos keys, install any additional hcoop config packages needed, bootstrap domtool, and install a reasonable set of base software depending on the intended use. This is the install step most in need of improvement.

Create a new VM named after the host, select a network install using the current Debian stable, and add the preseed options specified on AutomatedSystemInstall to the kernel command line. Allocate a reasonable number of maximum cores, RAM, and disk (less than 40G is not recommended, although we are using LVM and can resize disks if needed). Set network using a shared device, currently br0:$HOST (which may be the Wrong Way (tm)). It does appear that there is a better way than bridged networking: MacVTap in bridged mode works without manual configuration.

The installation is mostly automated. Set the keyboard/language settings (accept the default), and enter the static network information specified on IpAddresses. The preseed will then be fetched and take over. Create a root password (pwgen -cny with a length >= 9 is sufficient) when prompted, and store it in the password stash. Confirm that the partition table should be written After the first reboot, log in as an admin user and run the post install script to integrate it into our infrastructure. You may have to reboot the machine once more to fully complete the process. Afterward, the machine should be fully functional (in the world of the ideal at least). CategorySystemAdministration