Kickstart scripts
After setting the options, add scripts to the kickstart file that will install the mandatory package group and cluster components:
Install the required packages
In the body of the %packages
script, specify the package group hci
to be installed on the server:
%packages
@^hci
%end
Install the required components on the primary node
To deploy the primary node, you need the admin panel and storage components. You can configure these components during the product installation. However, this will expose the superadmin password and storage token in the kickstart file. In this case, add the %addon com_vstorage
script to the kickstart file as follows:
%addon com_vstorage --management --internal-iface=<private_iface> --external-iface=<public_iface> --password=<password>
%end
where
<password>
is the password of the superadmin account for the admin panel.<private_iface>
is the name of the private network interface (the one you would select for the management network during attended installation).<public_iface>
is the name of the public network interface (the one you would select for the admin panel network during attended installation).
If you do not want to expose the sensitive information in the kickstart file, you can configure the components after the installation. In this case, add the %addon com_vstorage
script to the kickstart file as follows:
%addon com_vstorage --management --bare
%end
Install the required components on a secondary node
To deploy secondary nodes, you need only the storage component, which is installed by default. However, you will need the storage token and management node IP address to add the node to the infrastructure.
Obtain the token and management node address in the admin panel:
-
Log in to the admin panel on port 8888. The panel’s IP address is shown in the console after deploying the primary node. Use the default user name shown on the login screen and the primary node’s root password.
If prompted, add the security certificate to the browser’s exceptions.
- In the admin panel, open Infrastructure > Nodes, and then click Connect node to invoke a screen with the management node address and the token.
With the token and management node address, you can proceed to registering the node in the admin panel. You can do this during the product installation. However, this will expose the storage token in the kickstart file. In this case, add the %addon com_vstorage
script to the kickstart file as follows:
%addon com_vstorage --storage --token=<token> --mgmt-node-addr=<MN_IP_address>
%end
where:
<token>
is the obtained token.<MN_IP_address>
is the obtained management node address.
If you do not want to expose the sensitive information in the kickstart file, you can register the node after the installation.