Problem:
In our environment, ESXi can be installed to 2 boot targets - SD Card or M.2. A system can have both devices. The user has to specify the target. To solve this we have created 2 separate provisioning templates - ESXi on SD and ESXi on BOSS. Then we create boot target specific OS entries for each ESXi build, set the appropriate template as default and associate that entry with the host:
ESXi 6.0 Build 01 on SD
ESXI6.0 Build 01 on BOSS
ESXI6.0 Build 02 on SD
ESXI6.0 Build 02 on BOSS
ESXI6.5 Build 01 on SD
ESXI6.5 Build 02 on BOSS
… and so on
This has resulted in over 200 OS entries already!
Expected outcome:
The kickstart file location for ESXi is specifed as a kernel parameter (or through boot.cfg) like this:
kernelopt=ks=http://${foreman_server_ip}/unattended/provision
Is it possible to directly link to the provisioning template here. For e.g, if the boot target is SD Card, I would like to pass something like:
kernelopt=ks=http://${foreman_server_ip}/unattended/provision/ESXi_on_SD
Is this possible at all or is there a better way to do it?