# Steps-to-decomission-Vertica-used-by-Classic-FinOps_687151665
## Introduction

These steps should be used to decomission/remove Vertica used by Classic FinOps.

HCMX FinOps was using Vertica for storing cloud cost data and creating FinOps reports. From 24.4 version, FinOps started support of using Operations Platform (OP) and Vertica deployed as part of OP. After migrating all tenats from Classic FinOps to OP based FinOps, the Vertica used in Classic mode will remain unused. These are the steps to decomission that classic FinOps.

## Make sure all FinOps tenants are migrated to OP

Before decomissioning the Vertica, make sure all FinOps tenants (i.e tenants which are enabled with FinOps capability) are migrated from Classic to OP mode. Here are the steps:

1. Login to Suite Administration https://<ExternalURL>/bo
2. Navigate to TENANTS, select a tenant. Click on Capability Settings. Navigate to Cloud Management Platform FinOps.
3. ‘Switch to Operations Platform’ should be greyed out. It should have Vertica details like ‘Vertica Hostname’, ‘Vertica Schema name’ etc. If you make sure that these Vertica related information is present, then it means the tenant is configured with OP mode. If Vertica details is not present, then tenant is in Classic mode. If so, the follow the FinOps Classic to FinOps OP migration steps.
4. Follow step 2 & 3 for all tenants i.e Navigate to every FinOps enabled tenant and make sure it is configured with OP mode.

## Steps for Decomissioning

1. Shudown the Classic Vertica.
2. Clean up config map entries
	1. Export itsma helm values. *helm get values sma -n itsma-helm -o yaml > itsma-helm.yaml*
		2. Update vertica details from the exported helm-values.yaml. Make sure the keys are not delated, just values are replaced as below.
		3. ```
		vertica :
		    dbname : NO_DB
		    host : NO_HOST
		    port : 0
		    rwuser : NO_USER
		    tlsEnabled : false
		```
		4. Peform helm upgrade. *helm upgrade sma chart-file -n ns -f itsma-helm.yaml.*

## Validate

1. Showback pods should be running and logs should not show any errors
2. Login to one of the tenant, initiate a collection. Collection should be successful.
3. Export the itmsa values (refer step a) and make sure vertica details are having the updated values. If you have backed up values yaml in a common place, please replace the exported values yaml for future reference.
4. Review the config maps
	1. kubectl describe cm vertica-database-configmap -n itsma-helm
5. Make sure the Vertica details are not pointing to an active DB.
