We implemented support for XenServer, Citrix Hypervisor and the open source project XCP-ng. As with CentOS/RedHat Linux and ESXi, the basic installation is based on kickstart.
First, the manufacturer installation routine is performed (with the xml config).
The postinstall script (create-customize.sh) ensures that the fsi routines and function are started after the first reboot (customize.sh).
After that the customize.sh script controls all inst and sub routine. This is the structure of the fsi xenserver installation directory:
/opt/fsi/inst/xen710/ks ├── inst => installation scripts ├── log => server installation log files ├── pool => pool config and information files ├── post => post scripts after normal installation ├── rpm => additional rpm or other files ├── sub => main config and installation files ├── tools => tools, this files are copied to the server ├── upd => update list and packages └── yum => needed libs or tools e.g. mc
If you need information for the fsi portal support of XenServer installation, please look here.
For every config option an own script exist. Name shema is sub_<install nummber>_<description>.sh
The following config scripts already exist:
some screenshot during a xen server installation