The TrilioVault Appliance is delivered as qcow2 image and runs as VM on top of a KVM Hypervisor.
The TrilioVault VM qcow2 image must be an available disk on the RHV Storage before the creation of the TrilioVault Appliance is possible.
This guide shows the tested way to spin up the TrilioVault Appliance on a RHV Cluster. Please contact a RHV Administrator and Trilio Customer Success Agent in case of incompatibility with company standards.
Creation the TrilioVault VM
The creation of the TrilioVault VM works like for any other Virtual Machine inside RHV.
To create a new Virtual Machine, go to Compute
The button "New" opens the window to define the VM.
The following instructions show the tested configuration for the TrilioVault Appliance.
After configuration, use the OK button to create the TrilioVault Appliance.
It is required to activate the Advanced Options.
Fill out the following details as necessary on the General tab:
Cluster - Choose the RHV Cluster to host the TrilioVault VM
Template - Blank
Operating System - The TrilioVault VM runs CentOS 7. Red Hat Enterprise 7.x x64 is a valid option.
Instance Type - Custom
Optimized for - Server
Name - Provide a RHV internal name for the TrilioVault VM
Description - Provide a RHV internal description for the TrilioVault VM (optional)
Comment - Provide a RHV internal comment for the TrilioVault VM (Optional)
Activate Delete Protection
NICs - Choose the network the TrilioVault VM connects with. The plus and minus symbols add/delete NICs as necessary.
Before moving to the next tab, attach the TrilioVault qcow2 image to the VM definition.
Click Attach under Instance Images.
Choose the TrilioVault qcow2 image
Check the box for OS
Without checking the box for OS, will the TrilioVault Appliance not boot, as the RHV VM is not utilizing the disk as the boot disk.
Under the System tab set the following:
Memory size - 24576 MB / 24 GB
Maximum memory - 24576 MB / 24 GB (RHV automatically first sets four times the Memory size)
Physical Memory Guaranteed - 24576 MB / 24 GB (RHV automatically first sets the same value as Memory size)
It is possible to set the initial Memory size to 8GB. RHV is automatically setting the Maximum Memory to 4 times the Memory size value. The actual Memory size can be adjusted later as needed.
Note: Do not set the Physical Memory Guaranteed below 8GB.
Total virtual CPUs - 4
Nothing to set at the Advanced Parameters
Leave Hardware Clock Timer Offset at 0
Leave custom serial policy unchecked
Under the Initial Run tab set the following:
Check "Use Cloud-Init/Sysprep"
(Optional) Set VM Hostname
(Optional) Check and set "Configure Time Zone"
Set User Name to rhv_nw
Set Password or SSH authentication
Set "Cloud-Init Network Protocol" to "Openstack Metadata"
(optional) Set DNS Servers and DNS Search Domains
Check In-guest Network Interface Name against interfaces
eth0 for the first interface
eth1 for the second interface
eth2, eth3, etc for further interfaces
Set IPv4 configuration as necessary
There are no TrilioVault specific configurations necessary in any further tab.
Starting the TrilioVault Appliance
After the creation of TrilioVault Appliance, the VM will automatically be put in a shutdown state.
Go to the overview of VMs in the RHV Manager (Compute
Virtual Machines), identify the TrilioVault Appliance VM in the list, mark it, and click the Run button to start it.
Cloud-initwill be disabled after the first boot.
Configuring the TrilioVault network using the CLI service account
TrilioVault is providing a limited-service account for the TrilioVault Appliance. It is no longer necessary to have root access.
The default credentials of this account are:
When this documentation is followed from beginning to end, the account's password will have been changed when setting up the cloud-init configuration.
The rhv_nw account has permission to change the network interface files.
The network interface files are located under:
Use the vi editor to configure the network interface. TrilioVault's default interface is eth0, which is using the following file for its configuration:
Edit this file according to the attached network. A typical interface configuration looks as follows
A warning will appear that a read-only file is edited. This warning needs to be overwritten using wq!