Installation

Pre-installation steps

1. Ensure that you can access the server console (HPE iLO, Dell iDRAC, or CISCO CIMI).

2. On a bare-metal server, create a RAID1 virtual drive (for the operating system, or for the operating system and metadata server).

Note: Optionally, you can create a RAID1 virtual drive in the Virtuozzo Infrastructure installer.

3. Download the latest Virtuozzo Infrastructure ISO (named vz-platform.iso) from the official repository and upload it to the server console (USB or HTML5 virtual console).

4. Load the Virtuozzo Infrastructure ISO in the server virtual media (HTML5/JAVA), reboot the node, and make sure the boot order is appropriately configured (for example, CD/DVD/USB as Boot Option #1).

Virtuozzo Infrastructure installation

License agreement

On Step 1, carefully read and accept the End-User License Agreement.

Network configuration

On Step 2, configure the network. In this guide, we’ll use the best practices for the Virtuozzo Infrastructure deployment by having the most standard network distribution for your cluster.

In Virtuozzo Infrastructure, we need to understand the two main set of networks:

Backend networks are used for constructing and operating software-defined storage (Virtuozzo Storage)
- Isolated network
- No connections to/from outside
- Low latency, high bandwidth
- Dedicated ports/cards where possible
Frontend networks are used for other traffic
- Management and API
- Internet connection(s)
- Virtual networks (VXLAN based)

Both networks are recommended to be created as a bonded connection (LAG) per server.

On the infrastructure level, we recommend distributing them on two physical bonds (each one is made out of two Ethernet ports) from the supported NICS.

Bond0
- Services network: an IP address is consumed by each server; routable; needs a default gateway; an (HA) IP address will be used for accessing the admin panel; can have RFC 1918 compliant IP address pool, but needs to be NATed at least one (HA) address.
- Private network: an IP address is consumed by each server; isolated, not routable; can have RFC 1918 compliant IP address pool.
- Compute network (no need to set up this network on this step): the Internet VLAN for all tenants (consumers); public IP address subnet; nodes do not consume IP address from that subnet.
Bond1
- Storage network: an IP address is consumed by each server; isolated, not routable; can have RFC 1918 compliant IP address pool.

1. Specify the first node’s hostname.

Important: You will be able to change the hostname later only by contacting the technical support.

2. Create the first bond (bond0) for the Services and Private networks.

3. Configure the bond’s subordinate interfaces (for example, p3p1 and p3p2) and set the MTU value for each interface up to 9000.

Important: The MTU value must be the same across the entire network.

If you are integrating Virtuozzo Infrastructure into an existing network, adjust the MTU value to that of the network.
If you are deploying Virtuozzo Infrastructure from scratch alongside a new network, set the MTU value to the recommended 9000.

4. For the bond, change the following options:

Mode: 802.3ad
MTU: 9000
LACP rate: Fast

The configured bonds will require additional configuration later, as described in the Infrastructure setup section.

5. On top of the bond bond0, create one VLAN for the Services network and another VLAN for the Private network.

6. Configure the Services and Private network VLANs:

6.1. For the Services network VLAN:

Note: The Services network will be an infrastructure network providing Internet access to the cluster itself for updates, connectivity to the licensing portal, and such services as billing, S3, NFS, Acronis Backup Storage, and other, which means that it needs a routable IP address (with a gateway) and DNS configured. To learn more, refer to the external access requirements in the Administrator Guide.

On the VLAN tab:
- Parent interface: bond0
- VLAN id: the ID you defined (for example, 3100)
- MTU: 1500
On the IPV4 Settings tab:
- Method: Manual
- Address/Netmask: the IP address from VLAN 3100 (172.16.XX.X/24)
- Gateway: 172.16.XX.1
- DNS servers: the DNS IP address (1.1.1.1)

6.2. For the Private network VLAN:

On the VLAN tab:
- Parent interface: bond0
- VLAN id: the ID you defined (for example, 3101)
- MTU: 9000
On the IPV4 Settings tab:
- Method: Manual
- Address/Netmask: the IP address from VLAN 3101 (192.160.0.x/24)
- Gateway: none

7. Create the second bond (bond1) and configure it the same way as bond0 (including MTU 9000).

8. On top of the bond bond1, create one VLAN for the Storage network.

9. Configure the Storage network VLAN:

On the VLAN tab:
- Parent interface: bond1
- VLAN id: the ID you defined (for example, 3102)
- MTU: 9000
On the IPV4 Settings tab:
- Method: Manual
- Address/Netmask: the IP address from VLAN 3102 (10.0.0.x/24)
- Gateway: none

VLAN 3102 will look as follows:

Connectivity tests

After the network configuration, press Alt+F2 to enter the command-line interface and test connectivity by running the following Linux commands to check if there are TX and RX packets:

1
2
3
# ifconfig bond0.3100
# ifconfig bond0.3101
# ifconfig bond1.3102

Run an ICMP request to your neighbor’s node IP on each interface to ensure that you have connectivity. Otherwise, you need to troubleshoot why there is no connectivity on your network side (VLAN propagation, network permissions, MTU configuration, 802.3ad - LACP setup, or other).

1
2
# ping 192.168.0.x -I bond0.3101 -s 9000
# ping 10.0.0.x -I bond0.3100 -s 9000

Check the VLAN 3102 gateway at 172.16.XX.1 and public sites (testing that DNS is working):

1
2
3
4
# ping 172.16.XX.1
# ping virtuozzo.com
# ping 8.8.8.8
# ping google.com

Once all of the tests are successful, return to the graphical user interface by pressing Alt+F6.

Time and date

On Step 3, ensure that the Network Time toggle switch is turned on, and then select your time zone:

Region: Etc
City: Coordinated Universal Time

Important: We only support the UTC time zone. Changing the time zone for nodes is not supported and may lead to system unavailability.

Cluster configuration

On Step 4, specify what type of node you are installing.

Primary node

1. If this is the first node, select Yes, create a new cluster.

2. For the internal management network, select the IP address of the Private network VLAN (192.168.0.x).

3. For the admin panel network, select the IP address of the Services network VLAN (172.16.0.X)

4. Specify the password for the admin panel access.

Note: You can use the same password for both the admin panel and SSH access. If you want to change them later, you can follow these recommendations:

Non-primary nodes

1. If this is not the first node, select No, add it to an existing cluster.

2. Obtain the token:

In the admin panel, go to the Infrastructure > Nodes page, click Connect node, and copy the displayed token.

In the command-line interface, run the following command (requires the admin panel password):

1
# vinfra node token show

3. Specify the management node IP address and the token, and then wait until the node is connected to the management node (it may take a few minutes).

Installation destination

On Step 5, select the drive for the OS installation from the drives available on the node. Select the one you want to use as the OS drive. No specific configuration or partitioning is needed.

Note: If you are not using a RAID1 virtual drive made on the IPMI, iDRAC, iLO console and you have two phyisical identical SSDs, you can select them both, and then select Combine disks in a software RAID mirror.

Once you select the drive, you need to click Reclaim the space to use the entire drive for the operating system.

Root password

Specify the password for the root user, and then start the installation. Depending on network conditions, it may take from 1 to 2 hours.

Post-installation steps

Once the installation is complete, the node will reboot automatically. You will be able to access the admin panel using the management node IP address on port 8888 (for example, https://172.16.0.x:8888) and the password you specified on Step 4.

Repeat the installation process for all other nodes.

In the admin panel, all of the registered nodes will appear as Unassigned.