welcome: please sign in

Diff for "InstallationProcedure/VirtualMachine"

Differences between revisions 1 and 2
Revision 1 as of 2012-12-30 23:47:22
Size: 1845
Editor: ClintonEbadi
Comment: initial install steps
Revision 2 as of 2013-07-14 02:50:27
Size: 2017
Editor: ClintonEbadi
Comment: note that macvtap is the way to go in the future for networking
Deletions are marked like this. Additions are marked like this.
Line 10: Line 10:

It does appear that there is a better way than bridged networking: [[http://virt.kernelnewbies.org/MacVTap|MacVTap]] in bridged mode works without manual configuration.

This 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.

1. Update postinst

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.

2. Provision Resources

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.

3. Debian Install

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

InstallationProcedure/VirtualMachine (last edited 2013-07-14 02:50:27 by ClintonEbadi)