For Canonical Openstack it is not necessary to spin up the TrilioVault VM.
The TrilioVault Appliance is delivered as qcow2 image and runs as VM on top of a KVM Hypervisor.
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.
Creating the cloud-init image
The TrilioVault appliance is utilizing cloud-init to provide the initial network and user configuration.
Cloud-init is reading it's information either from a metadata server or from a provided cd image. TrilioVault is utilizing the cd image.
Needed tools
To create the cloud-init image it is required to have genisoimage available.
1
#For RHEL and centos
2
yum install genisoimage
3
#For Ubuntu
4
apt-get install genisoimage
Copied!
Providing the Metadata
Cloud-init is using two files for it's metadata.
The first file is called meta-data and contains the information about the network configuration.
Below is an example of this file.
The second file is called user-data and contains little scripts and information to set up for example the user passwords.
Below is an example of this file.
It is of course possible to spin up the TrilioVault appliance without a cloud-init iso-image.
It will spin up with default values.
Uninstalling cloud-init after first boot
Once the TrilioVault appliance is up and running with it's initial configuration is it recommended to uninstall cloud-init.
If cloud-init is not installed it will rerun the network configuration upon every boot. Setting the network configuration back to DHCP, if no metadata is provided.
To uninstall cloud-init, follow the example below.
1
sudo yum remove cloud-init
Copied!
Updating the appliance to the latest minor version
It is recommended to directly update the TrilioVault appliance to the latest version.
To do so follow the minor update guide provided here: