LogoLogo
T4O-4.3
T4O-4.3
  • About Trilio for OpenStack
  • Trilio for OpenStack Architecture
  • Trilio 4.3 Release Notes
    • T4O 4.3.0 (GA)
    • T4O 4.3.1
    • T4O 4.3.2
  • Deployment Guide
    • Compatibility Matrix
    • Requirements
    • Trilio network considerations
    • Preparing the installation
    • Spinning up the Trilio VM
    • Installing Trilio Components
      • Installing on RHOSP
      • Installing on Canonical OpenStack
      • Installing on Kolla Openstack
      • Installing on Ansible Openstack
      • Installing on TripleO Train
    • Configuring Trilio
    • Apply the Trilio license
    • Advanced Ceph configurations
      • Additions for multiple CEPH configurations
      • Additions for multiple Ceph users
    • Post Installation Health-Check
    • Uninstall Trilio
      • Uninstalling from RHOSP
      • Uninstalling from Canonical OpenStack
      • Uninstalling from Kolla OpenStack
      • Uninstalling from Ansible OpenStack
    • Upgrade Trilio
      • Upgrading on RHOSP
      • Upgrading on Canonical OpenStack
      • Upgrading on Kolla OpenStack
      • Upgrading on Ansible OpenStack
      • Upgrading on TripleO Train [CentOS7]
      • Upgrade Trilio Appliance
    • Upgrade OpenStack
      • TrilioVault Upgrade Upon RHOSP cloud Upgrade
    • Workload Encryption with Barbican
    • Multi-IP NFS Backup target mapping file configuration
    • Enabling T4O 4.1 or older backups when using NFS backup target
    • Install workloadmgr CLI client
    • Switch Backup Target on Kolla-ansible
    • Switch NFS Backing file
  • Trilio Appliance Administration Guide
    • Set Trilio GUI login banner
    • Trilio Appliance Dashboard
    • Set network accessibility of Trilio GUI
    • Reconfigure the Trilio Cluster
    • Change the Trilio GUI password
    • Reset the Trilio GUI password
    • Reinitialize Trilio
    • Download Trilio logs
    • Change Certificates used by Trilio
    • Restart Trilio Services
    • Shutdown/Restart the Trilio cluster
    • Clean up Trilio database
  • User Guide
    • Workloads
    • Snapshots
    • Restores
    • File Search
    • Snapshot Mount
    • Schedulers
    • E-Mail Notifications
  • Admin Guide
    • Backups-Admin Area
    • Workload Policies
    • Workload Quotas
    • Managing Trusts
    • Workload Import & Migration
    • Disaster Recovery
      • Example runbook for Disaster Recovery using NFS
    • Migrating encrypted Workloads
    • Rebasing existing workloads
  • Troubleshooting
    • Frequently Asked Questions
    • General Troubleshooting Tips
    • Using the workloadmgr CLI tool on the Trilio Appliance
    • Healthcheck of Trilio
    • Important log files
  • API GUIDE
    • Workloads
    • Snapshots
    • Restores
    • File Search
    • Snapshot Mount
    • Schedulers
    • E-Mail Notification Settings
    • Workload Policies
    • Workload Quotas
    • Managing Trusts
    • Workload Import and Migration
Powered by GitBook
On this page
  • Clean triliovault_datamover_api container
  • Clean triliovault_datamover container
  • Clean haproxy of Trilio Datamover API
  • Clean Kolla Ansible deployment procedure
  • Revert to original Horizon container
  • Clean Keystone resources
  • Clean Trilio database resources
  • Destroy the Trilio VM Cluster

Was this helpful?

Export as PDF
  1. Deployment Guide
  2. Uninstall Trilio

Uninstalling from Kolla OpenStack

Clean triliovault_datamover_api container

The container needs to be cleaned on all nodes where the triliovault_datamover_api container is running. The Kolla Openstack inventory file helps to identify the nodes with the service.

Following steps need to be done to clean the triliovault_datamover_api container:

Stop the triliovault_datamover_api container.

docker stop triliovault_datamover_api

Remove the triliovault_datamover_api container.

docker rm triliovault_datamover_api

Clean /etc/kolla/triliovault-datamover-api directory.

rm -rf /etc/kolla/triliovault-datamover-api

Clean log directory of triliovault_datamover_api container.

rm -rf /var/log/kolla/triliovault-datamover-api/

Clean triliovault_datamover container

The container needs to be cleaned on all nodes where the triliovault_datamover container is running. The Kolla Openstack inventory file helps to identify the nodes with the service.

Following steps need to be done to clean the triliovault_datamover container:

Stop the triliovault_datamover container.

docker stop triliovault_datamover

Remove the triliovault_datamover container.

docker rm triliovault_datamover

Clean /etc/kolla/triliovault-datamover directory.

rm -rf /etc/kolla/triliovault-datamover

Clean log directory of triliovault_datamover container.

rm -rf /var/log/kolla/triliovault-datamover/

Clean haproxy of Trilio Datamover API

The Trilio Datamover API entries need to be cleaned on all haproxy nodes. The Kolla Openstack inventory file helps to identify the nodes with the service.

Following steps need to be done to clean the haproxy container:

rm /etc/kolla/haproxy/services.d/triliovault-datamover-api.cfg
docker restart haproxy

Clean Kolla Ansible deployment procedure

Delete all Trilio related entries from:

Trilio entries can be found in:

Revert to original Horizon container

Run deploy command to replace the Trilio Horizon container with original Kolla Ansible Horizon container.

kolla-ansible -i multinode deploy

Clean Keystone resources

Trilio created a dmapi service with dmapi user.

openstack service delete dmapi
openstack user delete dmapi

Clean Trilio database resources

Trilio Datamover API service has its own database in the Openstack database.

Login to Openstack database as root user or user with similar priviliges.

mysql -u root -p

Delete dmapi database and user.

DROP DATABASE dmapi;
DROP USER dmapi;

Destroy the Trilio VM Cluster

List all VMs running on the KVM node

virsh list

Destroy the Trilio VMs

virsh destroy <Trilio VM Name or ID>

Undefine the Trilio VMs

virsh undefine <Trilio VM name>

Delete the TrlioVault VM disk from KVM Host storage

PreviousUninstalling from Canonical OpenStackNextUninstalling from Ansible OpenStack

Last updated 1 year ago

Was this helpful?

To cross-verify the uninstallation undo all steps done in and .

/usr/local/share/kolla-ansible/ansible/roles/ There is a role triliovault

/etc/kolla/globals.yml Trilio entries had been appended at the end of the file

/etc/kolla/passwords.yml Trilio entries had been appended at the end of the file

/usr/local/share/kolla-ansible/ansible/site.yml Trilio entries had been appended at the end of the file

/root/multinode Trilio entries had been appended at the end of this example inventory file

➡️
➡️
➡️
➡️
➡️
append Kolla Ansible yml files
clone Trilio Ansible role