Search…
Spinning up the TrilioVault VM
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.
1
[[email protected]]# cat meta-data
2
instance-id: triliovault
3
network-interfaces: |
4
auto eth0
5
iface ens3 inet static
6
address 158.69.170.20
7
netmask 255.255.255.0
8
gateway 158.69.170.30
9
10
dns-nameservers 11.11.0.51
11
local-hostname: tvault-controller
Copied!
The instance-id has to match the VM name in virsh
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.
1
[[email protected]]# cat user-data
2
#cloud-config
3
chpasswd:
4
list: |
5
root:password1
6
stack:password2
7
expire: False
Copied!

creating the image file

Both files meta-data and user-data are needed. Even when one is empty, is it needed to create a working cloud-init image.
The image is getting created using genisoimage follwing this general command:
genisoimage -output <name>.iso -volid cidata -joliet -rock </path/user-data> </path/meta-data>
An example of this command is shown below.
1
genisoimage -output tvault-firstboot-config.iso -volid cidata -joliet -rock user-data meta-data
Copied!

Spining up the TrilioVault appliance

After the cloud-init image has been created the TriloVault appliance can be spun up on the desired KVM server.
Extract the Triliovault QCOW2 tar file using the following command :
1
tar Jxvf TrilioVault_file.tar.xz
Copied!
See below an example command, how to spin up the TrilioVault appliance using virsh and the created iso image.
1
virt-install -n triliovault-vm --memory 24576 --vcpus 8 \
2
--os-type linux \
3
--disk tvault-appliance-os-3.0.154.qcow2,device=disk,bus=virtio,size=40 \
4
--network bridge=virbr0,model=virtio \
5
--network bridge=virbr1,model=virtio \
6
--graphics none \
7
--import \
8
--disk path=tvault-firstboot-config.iso,device=cdrom
Copied!
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:
Last modified 1mo ago