Archive for March 2013

Install the Auto Deploy Server

robot

What is Auto Deploy?

vSphere Auto Deploy can provision hundreds of physical hosts with ESXi software. You can specify the image to deploy and the hosts to provision with the image. Optionally, you can specify host profiles to apply to the hosts, and a vCenter Server folder or cluster for each host.

When a physical host set up for Auto Deploy is turned on, Auto Deploy uses a PXE boot infrastructure in conjunction with vSphere host profiles to provision and customize that host. No state is stored on the host itself. Instead, the Auto Deploy server manages state information for each host

Auto Deploy stores the information for the ESXi hosts to be provisioned in different locations. Information about the location of image profiles and host profiles is initially specified in the rules that map machines to image profiles and host profiles. When a host boots for the first time, the vCenter Server system creates a corresponding host object and stores the information in the database.

AutoDeploy Requirements

  • DHCP
  • DHCP Option 66: FQDN or IP Address of TFTP Server
  • DHCP Option 67: udionly.kpxe.vmw-hardwired – Name of GPXE Config file which we need the TFTP Server to direct the host to
  • Router Configuration – A setting to allow the DHCP
  • PXE
  • TFTP

Installation Instructions

  • Attach the vCenter ISO
  • Select AutoDeploy

Autodeploy1

  • Click Next

Autodeploy2

  • Click Next to the End User Patent Agreement

Autodeploy3

  • Click I accept to the Licensing agreement

Autodeploy4

  • Check Auto Deploy repository directory and repository maximum size

Autodeploy5

  • Put in vCenter Information

Autodeploy6

  • Trust the SSL Certificate

Autodeploy7

  • Check the ports

Autodeploy8

  • Check how your server is identified on the network

Autodeploy9

  • nn

Autodeploy10

  • Finish

Configure Advanced Boot Loader and Kernel Options

LogIcon

You can quickly deploy ESXi hosts using scripted, unattended installations or upgrades. Scripted installations, upgrades, or migrations provide an efficient way to deploy multiple hosts.
The installation or upgrade script contains the installation settings for ESXi. You can apply the script to all hosts that you want to have a similar configuration.

The installation or upgrade script can reside in one of the following locations:

  • FTP
  • HTTP/HTTPS
  • NFS
  • USB flash drive
  • CDROM

Enter Boot Options to Start an Installation or Upgrade Script

You can start an installation or upgrade script by typing boot command-line options at the boot command line.
At boot time you might need to specify options to access the kickstart file.

Procedure

  • You can enter boot options by pressing Shift+O in the boot loader.
  • For a PXE boot installation, you can pass options through the kernelopts line of the boot.cfg file.

KS

  • At the runweasel command prompt, type ks=location of installation script plus boot command line options
  • Example: ks=http://192.168.0.10/kickstart/ks_test.cfg nameserver=192.168.0.100 ip=192.168.0.210 netmask=255.255.255.0 gateway=192.168.0.254

The ESXi installer includes a default installation script that performs a standard installation to the first detected disk.

The default ks.cfg installation script is located in the initial RAM disk at /etc/vmware/weasel/ks.cfg. You can specify the location of the default ks.cfg file with the ks=file://etc/vmware/weasel/ks.cfg boot option

To get an idea how things work without writing installation script etc. Try installing a (virtual) ESXi host with the default ks.cfg installation script. At the weasel prompt, type:

ks=file://etc/vmware/weasel/ks.cfg

Kernel Options

The boot loader configuration file boot.cfg specifies

  • The kernel
  • The kernel options
  • The boot modules that the mboot.c32 boot loader uses in an ESXi installation.

The boot.cfg file is provided in the ESXi installer. You can modify the kernelopt line of the boot.cfg file to specify the location of an installation script or to pass other boot options.

This is useful while:

  • Creating an Installation .ISO with a custom installation or upgrade script;
  • Working with PXE booting the ESXi installer, using PXELINUX and a PXE or isolinux.cfg PXE configuration file.

Boot.cfg

The commands in boot.cfg configure the boot loader.

Capture