After being an evangelist last week I’m now converting my Auto-Deploy ESXi hosts into Stateful installs and therefore ditching their wonderful ephemeralness!
Why? Well for the purpose of a small lab which I will have to rebuild at some point I don’t have the time to configure the supporting architecture which would mainly be the host profiles and dhcp/pxe environment.
Also it’s another option and part of using Auto-Deploy. You can choose to apply a host-profile, once the machine has first booted into ESXi which will then write the install to disk.
Presuming you did assign some storage to your ESXi host (be it virtual or physical) then it is quite simple to make your stateless install stateful in about 2 minutes.
- Ensure some storage is available to your host (as per the vSphere Docs this should be 5.2Gb minimum to host a 4GB scratch Partition on the boot device)
- If this is the first host then Right click the host in VI Client or Web client and select Host Profile>Create Profile from Host
- Give the profile a name then drill down into the following option in Profile/Policy on the left
System Image Cache Profile Settings
Set the dropdown to “Enable Stateful installs on the host”
Set Arguments for first disk to be “local” if you intend to use the first local disk found (There are other options detailed int he vSphere Documentation such as controller names)
Tick Check to overwrite any VMFS volumes on the selected disk if you want to overwrite your storage that ESXi finds
- Ok the profile and return to hosts/clusters view
- Right click the host you want to make “stateful” now and select Host Profile>Manage Profile
- Select the profile you just created and click OK
- Wait, not done yet!!! You’ve only attached it.
- Put your host into maintenance mode………………
- Then apply the profile via Host Profile>Apply Profile
- vCenter shows you the configuration changes it will make to get the host in what it believes will be a complaint state to match the profile.
This should just be listing the Disk to be used for stateful installs
and also VMFS volumes on that disk will be overwritten.
- Click Finish and go and get a brew whilst the Apply host configuration step completes. This took 15 minutes on my virtual ESXi host and then 5 minutes to reboot!
Just as a minor memory saver I’ve stopped Auto-Deploy on the vCenter Appliance too.
That will conclude my adventures in Auto Deploy land but it has led me nice and gently into host profiles and I’ll be working on them in the next blog (as you’ll find if you do the steps above..you won’t end up with a perfect ESXi host after the reboot step!)