Linux Kickstart provisioning uses a configuration file to automate a Linux installation on a newly provisioned machine. To prepare for provisioning you must create a bootable ISO image and a Kickstart or autoYaST configuration file.
The following is a high-level overview of the steps required to prepare for Linux Kickstart provisioning:
- Verify that a DHCP server is available on the network. vRealize Automation cannot provision machines by using Linux Kickstart provisioning unless DHCP is available.
- Prepare the configuration file. In the configuration file, you must specify the locations of the vRealize Automation server and the Linux agent installation package. See Prepare the Linux Kickstart Configuration Sample File.
- Edit the isolinux/isolinux.cfg or loader/isolinux.cfg to specify the name and location of the configuration file and the appropriate Linux distribution source.
- Create the boot ISO image and save it to the location required by your virtualization platform. See the documentation provided by your hypervisor for information about the required location.
- (Optional) Add customization scripts.
- To specify post-installation customization scripts in the configuration file, see Specify Custom Scripts in a kickstart/autoYaST Configuration File.
- To call Visual Basic scripts in blueprint, see Checklist for Running Visual Basic Scripts During Provisioning.
- Gather the following information so that blueprint architects can include it in their blueprints:
Note: You can create a property group with the property set BootIsoProperties to include the required ISO information. This makes it easier to include this information correctly on blueprints.
- The name and location of the ISO image.
- For vCenter Server integrations, the vCenter Server guest operating system version with which vCenter Server is to create the machine.