...
Each time you run the installer, a kickstart file is generated. This file will be saved next to the manifest file that was used for installation. The filename is in the format qube-component_group-install_version-kickstart.qks, e.g qube-upgrade-6.4-4-kickstart.qks or qube-worker-6.4-4-kickstart.qks. The kickstart file can be used by the installer to replicate the install/upgrade on another computer. This is an OS independent file, so you can, for example, install or upgrade across Linux, OS XmacOS, and Windows using the same kickstart file on the command line of each OS.
The kickstart file contains the list of the components that were selected for installation, uninstallation, the component group selection, and the supervisor discovery parameters if they were provided. It follows, then, that a kickstart file could be used to manage the removal of Qube! components as well as it can be used for install or upgrade. For the component group options "Upgrade Installed" or "Uninstall Everything", the exact component selection saved in the kickstart file is ignored and will be replaced at run time. For all other component group selections, the exact selections for install and uninstall will be replicated each time the kickstart file is used. In either case, when running on the command line (without a GUI), any component that needs to be downloaded will be downloaded by the installer before it is installed. If the component has already been downloaded by one computer, it will not be downloaded again by subsequent computers (assuming the location of the manifest, and therefore individual component installation files, is on a shared file server).
To use the kickstart file, you must run the installer on the command line. In fact, the installer may only be run on the command line when used in conjunction with a kickstart file. Once the file is created, usage is quite simple:
/path/to/qubeInstaller.version.os.exe /path/to/qube-kickstart.qks
| Note | ||
|---|---|---|
| ||
On OS XmacOS, the installer is an application package. You must run the binary inside the application package in order to use command line options. The binary in the applicaiton package will be, for example, in qubeInstaller.MacOSX-x86_64.app/Contents/MacOS/qubeInstaller, in which case, an OS X macOS user would run the above command as:
|
...