The following steps need to be run on all nodes, which have the Trilio Datamover API & Workloadmanager services running. Those nodes can be identified by checking the roles_data.yaml
for the role that contains the below entries
Once the role that runs the Trilio Datamover API & Workloadmanager services has been identified will the following commands clean the nodes from the service.
Run all commands as root or user with sudo permissions.
Remove triliovault_datamover_api
container.
Clean Trilio Datamover API service conf directory.
Clean Trilio Datamover API service log directory.
Remove triliovault_wlm_api
container.
Clean Trilio Workloadmanager API service conf directory.
Clean Trilio Workloadmanager API service log directory.
Remove triliovault_wlm_workloads
container.
Clean Trilio Workloadmanager Workloads service conf directory.
Clean Trilio Workloadmanager Workloads service log directory.
Remove triliovault_wlm_scheduler
container.
Clean Trilio Workloadmanager Scheduler service conf directory.
Clean Trilio Workloadmanager Scheduler service log directory.
Remove triliovault-wlm-cron-podman-0
container from controller.
Clean Trilio Workloadmanager Cron service conf directory.
Clean Trilio Workloadmanager Cron service log directory.
The following steps need to be run on all nodes, which have the Trilio Datamover service running. Those nodes can be identified by checking the roles_data.yaml
for the role that contains the entry OS::TripleO::Services::TrilioDatamover
.
Once the role that runs the Trilio Datamover service has been identified will the following commands clean the nodes from the service.
Run all commands as root or user with sudo permissions.
Remove triliovault_datamover
container.
Unmount the Trilio Backup Target on the compute host.
Clean Trilio Datamover service conf directory.
Clean log directory of Trilio Datamover service.
Remove wlm cron resource from pcs cluster on the controller node.
The following steps need to be run on all nodes, which have the HAproxy service running. Those nodes can be identified by checking the roles_data.yaml
for the role that contains the entry OS::TripleO::Services::HAproxy
.
Once the role that runs the HAproxy service has been identified will the following commands clean the nodes from all the Trilio resources.
Run all commands as root or user with sudo permissions.
Edit the following file inside the HAproxy container and remove all Trilio entries.
/var/lib/config-data/puppet-generated/haproxy/etc/haproxy/haproxy.cfg
An example of these entries is given below.
Restart the HAproxy container once all edits have been done.
Trilio registers services and users in Keystone. Those need to be unregistered and deleted.
Trilio creates databases for dmapi and workloadmgr services. These databases need to be cleaned.
Login into the database cluster
Run the following SQL statements to clean the database.
Remove the following entries from roles_data.yaml
used in the overcloud deploy command.
OS::TripleO::Services::TrilioDatamoverApi
OS::TripleO::Services::TrilioWlmApi
OS::TripleO::Services::TrilioWlmWorkloads
OS::TripleO::Services::TrilioWlmScheduler
OS::TripleO::Services::TrilioWlmCron
OS::TripleO::Services::TrilioDatamover
In the case that the overcloud deploy command used prior to the deployment of Trilio is still available, it can directly be used.
Follow these steps to clean the overcloud deploy command from all Trilio entries.
Remove trilio_env.yaml entry
Remove trilio endpoint map file Replace with original map file if existing
Run the cleaned overcloud deploy command.