Continuing from part 1 of How to Persist Configuration Changes in ESXi 4.x/5.x Part 1, here is another method which I prefer when trying to persist configuration changes in ESXi. When ESXi boots up, it loads it’s filesystem into memory which the modules to be loaded up are determined by the configuration found in /bootbank/boot.cfg and /altbootbank/boot.cfg for the two respective partitions (primary / backup).
UPDATE: You can now persist configuration files such as firewall rules and others using the new VIB Author Fling, please take a look at this article for more details.
Here is an example of ESXi 4.x default boot.cfg:
~ # cat /bootbank/boot.cfg
modules=k.z — s.z — c.z — oem.tgz — license.tgz — m.z — state.tgz — vpxa.vgz
Here is an example of ESXi 5.x default boot.cfg:
~ # cat /bootbank/boot.cfg
title=Loading VMware ESXi
modules=b.b00 — useropts.gz — k.b00 — a.b00 — ata-pata.v00 — ata-pata.v01 — ata-pata.v02 — ata-pata.v03 — ata-pata.v04 — ata-pata.v05 — ata-pata.v06 — ata-pata.v07 — block-cc.v00 — ehci-ehc.v00 — s.v00 — ima-qla4.v00 — ipmi-ipm.v00 — ipmi-ipm.v01 — ipmi-ipm.v02 — misc-cni.v00 — misc-dri.v00 — net-be2n.v00 — net-bnx2.v00 — net-bnx2.v01 — net-cnic.v00 — net-e100.v00 — net-e100.v01 — net-enic.v00 — net-forc.v00 — net-igb.v00 — net-ixgb.v00 — net-nx-n.v00 — net-r816.v00 — net-r816.v01 — net-s2io.v00 — net-sky2.v00 — net-tg3.v00 — ohci-usb.v00 — sata-ahc.v00 — sata-ata.v00 — sata-sat.v00 — sata-sat.v01 — sata-sat.v02 — sata-sat.v03 — scsi-aac.v00 — scsi-adp.v00 — scsi-aic.v00 — scsi-bnx.v00 — scsi-fni.v00 — scsi-hps.v00 — scsi-ips.v00 — scsi-lpf.v00 — scsi-meg.v00 — scsi-meg.v01 — scsi-meg.v02 — scsi-mpt.v00 — scsi-mpt.v01 — scsi-mpt.v02 — scsi-qla.v00 — scsi-qla.v01 — uhci-usb.v00 — imgdb.tgz — state.tgz
As we learned from the previous article, the cron’d /sbin/auto-backup.sh generates a local.tgz which is then converted to state.tgz which contains all files automatically backed up by VMware. This file is loaded up along with other modules as part of the boot process. Understanding this, allows us to take advantage of this feature for persisting our own configuration files.
Here is an example use case for creating .ssh directory for SSH keys and persisting a script
(ghettoVCB.sh) in /bin for an ESXi 4.x host:
Step 1 – Re-create the modified directory structure and files in a temporary local path which will then be tarred and gzip. An example would be the following:
Temporary local directory structure of change:
Note: It is very important to ensure that the modified files get the stickybit permission set. As noted in the last article that upon a change, the visorFS will automatically create a special file to denote it for backup but also it allows the file to be writable at some later point for custom files being added.
Step 2 – You will use the tar utility to tar/gzip the contents in a file with extension .tgz. One thing to note, the file name including the extension must not exceed 12 characters. In our example, we made two changes and re-created the local structure under /tmp. We will need to change into /tmp directory and tar up the contents by using the following command:
/tmp # tar -czvf ghetto.tgz .ssh/ bin/
Now you should have the contents of .ssh and bin within your *.tgz file. To verify and view the contents, you can run the following command:
/tmp # tar -tzvf ghetto.tgz
drw——- 0/0 0 2011-08-10 04:10:11 .ssh/
-rw——T 0/0 399 2011-08-10 04:10:11 .ssh/authorized_keys
drwxr-xr-x 0/0 0 2011-08-10 04:10:24 bin/
-rwxr-xr-t 0/0 46973 2011-08-10 04:10:24 bin/ghettoVCB.sh
Step 3 – Next we need to copy the *.tgz file into /bootbank and modify the /bootbank/boot.cfg to ensure our new module is included in the boot up process
cp /tmp/ghetto.tgz /bootbank
Here is what the modified ESXi 4.x boot.cfg should look like after:
modules=k.z — s.z — c.z — oem.tgz — license.tgz — m.z — state.tgz — vpxa.vgz — ghetto.tgz
The next time you reboot the system, you will automatically have your .ssh directory containing your SSH keys and the ghettoVCB script under /bin directory.
Now this is great for an inline modification, but what about creating custom configuration files and including that as part of a default kickstart installation? What about something like custom firewall rules in ESXi 5? In the following example, we’ll include a custom firewall rule called “virtuallyGhetto.xml” which will be stored in /etc/vmware/firewall when the contents of the module is extracted.
Step 1 – We of course need to create the XML file containing the firewall rule and create the directory structure in which it will be unloaded to.
Step 2 – Next we’ll tar up the local contents
[root@air tmp]# tar -zcvf ghetto.tgz etc/
Step 3 – This new package will need to be stored on you installation server which will be reachable via http using wget and as part of the %firstboot stanza in your ESXi 5 kickstart. It will download the *.tgz file and append the entry in /bootbank/boot.cfg configuration file. Here are the entries that should go into your kickstart:
# Adding custom files to boot argument (e.g. custom firewall rules,etc)
wget http://air.primp-industries.com/esxi5/ghetto.tgz -O /bootbank/ghetto.tgz
sed -e ‘/modules=/s/$/ — ghetto.tgz/’ -i /bootbank/boot.cfg
Note: If you add custom files that are located under /etc and you have the stickybit enabled on your file, changes made will persist upon the next reboot by either manually running /sbin/auto-backup.sh or letting it run via cron. If you add custom files that are not located under /etc, any change you make must be periodically updated in your custom *.tgz file else the next reboot, the original file will be loaded.