After the installation and configuration of TrilioVault for RHV did succeed the following steps can be done to verify that the TrilioVault installation is healthy.
Verify the TrilioVault Appliance services are up
TrilioVault is using 3 main services on the TrilioVault Appliance:
wlm-api
wlm-scheduler
wlm-workloads
Those can be verified to be up and running using the systemctl status command.
The second component to check the TrilioVault Appliance's health is the nginx and pacemaker cluster.
pcsstatus######Clustername:triliovaultWARNINGS:Corosyncandpacemakernodenamesdonotmatch (IPs usedinsetup?)Stack:corosyncCurrentDC:om_tvm (version 1.1.19-8.el7_6.1-c3c624ea3d) -partitionwithquorumLastupdated:WedDec512:25:022018Lastchange:WedDec509:20:082018byrootviacibadminonom_tvm1nodeconfigured4resourcesconfiguredOnline: [ om_tvm]Fulllistofresources:virtual_ip (ocf::'heartbeat:IPaddr2): Started om_tvmwlm-api (systemd:wlm-api): Started om_tvmwlm-scheduler (systemd:wlm-scheduler): Started om_tvmClone Set: lb_nginx-clone [lb_nginx]Started: [ om_tvm ]Daemon Status:corosync: active/enabledpacemaker: active/enabledpcsd: active/enabled
Verify API connectivity from the RHV-Manager
The RHV-Manager is doing all API calls towards the TrilioVault Appliance.
Therefore it is helpful to do a quick API connectivity check using curl.
The following curl command lists the available workload-types and verfifies that the connection is available and working:
curl-k-XGEThttps://30.30.1.11:8780/v1/admin/workload_types/detail-H"Content-Type: application/json"-H"X-OvirtAuth-User: admin@internal"-H"X-OvirtAuth-Password: password"######{"workload_types": [{"status": "available", "user_id": "admin@internal", "name": "Parallel", "links": [{"href": "https://myapp/v1/admin/workloadtypes/2ddd528d-c9b4-4d7e-8722-cc395140255a", "rel": "self"}, {"href": "https://myapp/admin/workloadtypes/2ddd528d-c9b4-4d7e-8722-cc395140255a", "rel": "bookmark"}], "created_at": "2020-04-02T15:38:51.000000", "updated_at": "2020-04-02T15:38:51.000000", "metadata": [], "is_public": true, "project_id": "admin", "id": "2ddd528d-c9b4-4d7e-8722-cc395140255a", "description": "Parallel workload that snapshots VM in the specified order"}, {"status": "available", "user_id": "admin@internal", "name": "Serial", "links": [{"href": "https://myapp/v1/admin/workloadtypes/f82ce76f-17fe-438b-aa37-7a023058e50d", "rel": "self"}, {"href": "https://myapp/admin/workloadtypes/f82ce76f-17fe-438b-aa37-7a023058e50d", "rel": "bookmark"}], "created_at": "2020-04-02T15:38:47.000000", "updated_at": "2020-04-02T15:38:47.000000", "metadata": [], "is_public": true, "project_id": "admin", "id": "f82ce76f-17fe-438b-aa37-7a023058e50d", "description": "Serial workload that snapshots VM in the specified order"}]}
Verify the ovirt-imageio services are up and running
TrilioVault is extending the already exiting ovirt-imageio services.
The installation of these extensions does check if the ovirt-services come up.
Still it is a good call to verify again afterwards:
On the RHV-Manager check the ovirt-imageio-proxy service: