Migrate from Aria Config to Tanzu Salt

Products

• VMware Aria Suite

Issue/Introduction

Aria Config is being rebranded to Tanzu Salt and is to be part of the Tanzu Platform product suite. Tanzu Platform being a 

Environment

Aria Config 8.16+

Tanzu Salt - all versions

Resolution

1. Login to Aria Config Postgres and export the database raas_* to /path/to/dir
2. Copy the raas encryption key from the Aria Config (/etc/raas/pki/.raas.key) to /path/to/dir
3. Login to Tanzusm Kubernetes cluster and ensure you are able to list pods with kubectl -n tanzusm get po|grep raas
4. Scale down the raas deployment with
   1. kubectl -n tanzuhub scale deploy raas --replicas=0
5. Login to Tanzusm UI. Note down the org id.
6. Login to TanzuSM postgres instance and locate the raas_<org_id_without_dashes>.
7. Drop the database in raas_<org_id_without_dashes>.
8. Create a new database called raas_<org_id_without_dashes> and import the data from the Aria Conifg into the  raas_<org_id_without_dashes>.
9. To map users from Aria Config to Tanzu SM auth,
   1. UPDATE USERS set username = '<tanzu_okta_user>', normalized_username =  '<tanzu_okta_user>' where username = '<aria_config_username>';
   2. Repeat this step for all users that need a mapping.
10. Edit the kubernetes secret "raas-db-encryption-key" to the base64 encoded value of contents of Aria Config raas encryption key /etc/raas/pki/.raas.key file copied in Step Use echo -n "contents_of_raas_key_file" | base64 for encoding
11. Run the db upgrade job in tanzusm. It would already run once when the raas deployment. So, something it needs to be re-run to upgrade the Aria Config DB to the current Tanzu Config SM release.
    1. kubectl create job --from=job/db-upgrade new-db-upgrade -n tanzusm
12. Scale up the raas deployment to enable it for usage.