Installing in the unattended mode

If you plan to perform an unattended installation of Virtuozzo Hybrid Infrastructure, you can use a kickstart file. It will automatically supply the installer with the options you would normally choose by hand.

Prerequisites

A PXE server is prepared, as outlined in Setting up a PXE server.
A kickstart file is created by using the options and scripts described in Creating a kickstart file.

To install in the unattended mode

Make the kickstart file accessible over the network:
1. Copy the kickstart file to the same directory on the HTTP server where the Virtuozzo Hybrid Infrastructure installation files are stored (for example, to /var/www/html/stor).
2. Add the following string to the /tftpboot/pxelinux.cfg/default file on the PXE server:
```
inst.ks=<HTTP_server_address>/<path_to_kickstart_file>
```
  For EFI-based systems, the file you need to edit has the name of /tftpboot/pxelinux.cfg/efidefault or /tftpboot/pxelinux.cfg/<PXE_server_IP_address>.
  
  Assuming that the HTTP server has the IP address of 198.123.123.198, the DocumentRoot directory is set to /var/www/html, and the full path to your kickstart file on this server is /var/www/html/stor/ks.cfg, your default file may look like the following:
```
default menu.c32
prompt 0
timeout 100
ontimeout ASTOR
menu title Boot Menu
label ASTOR
        menu label Install
        kernel vmlinuz
        append initrd=initrd.img ip=dhcp inst.repo=http://198.123.123.198/stor inst.ks=http://198.123.123.198/stor/ks.cfg
```
Configure the server to boot from the chosen media.
Boot the server and wait for the Welcome screen.
On the Welcome screen, select Install Virtuozzo Hybrid Infrastructure and press E to edit the menu entry.
Append the kickstart file location to the linux /images/pxeboot/vmlinuz line, and press Ctrl+X. For example:
```
linux /images/pxeboot/vmlinuz inst.stage2=hd:LABEL=<ISO_img> quiet ip=dhcp logo.nologo=1 inst.ks=<URL>
```

The installation will proceed automatically. Once it is complete, the node will reboot automatically. The admin panel IP address will be shown in the welcome prompt.

What's next

After installation on the primary node
If you installed the admin panel and storage components without exposing the superadmin password and storage token in the kickstart file, do the following:
1. On the node, run the following command as the root user to configure the admin panel component:
```
echo <password> | /usr/libexec/vstorage-ui-backend/bin/configure-backend.sh -i <private_iface> -x <public_iface>
```
  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)
2. Start the admin panel service on the node:
```
# systemctl start vstorage-ui-backend
```
3. Register the node in the admin panel:
```
# /usr/libexec/vstorage-ui-agent/bin/register-storage-node.sh -m <MN_IP_address> -x <public_iface>
```
  where
  - <MN_IP_address> is the IP address of the node's private network interface
  - <public_iface> is the name of the public network interface
Now you can proceed to deploying secondary nodes.
After installation on a secondary node
If you installed the storage component without exposing the storage token in the kickstart file, run the following script on the node, to register it in the admin panel:
```
# /usr/libexec/vstorage-ui-agent/bin/register-storage-node.sh -m <MN_IP_address> -t <token>
```
where
- <MN_IP_address> is the IP address of the private network interface on the node with the admin panel
- <token> is the token obtained in the admin panel or from the vinfra node token show output
When all the required nodes are displayed in the admin panel on the Infrastructure > Nodes screen as Unassigned, proceed to create the storage cluster, as outlined in Deployment and configuration.