Migrate Aria Config from LCM Based Deployment
search cancel

Migrate Aria Config from LCM Based Deployment

book

Article ID: 375126

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

Support for Life Cycle Managed based deployments of Aria Config were recently deprecated and customers need guidance on how to migrate their existing data from the appliance.

Environment

Aria Config 8.12.2.8+ (LCM based deployments only)

Cause

Photon OS 3 is now end of life

Salt 3005.x that ships with Photon OS 3 is also now end of life

Resolution

This solution assumes that you are you managing less than 1,000 minions and intend to migrate to a single managed VM based on RHEL, or a compatible RHEL derivative such as Oracle Linux. However, this same basic process will also work for a multi-node deployment. You should download the same version of the installer as your current running version of RaaS on the LCM based appliance if possible. If this version is not available, then please contact support to see if a copy is available. This will help ensure that the migration goes as smoothly as possible.

 

  1. Backup data from the appliance including configs
    1. Instructions to backup your database
    2. Be sure to also back up a copy of the /etc/raas/pki/.raas.key file
      1. This file is essential for being able to decrypt certain items in the database 
  2. Stand up a new VM with RHEL based OS for Aria Config installer compatibility
  3. Download the Aria Config installer that best matches your target OS from https://support.broadcom.com/group/ecx/productfiles?displayGroup=VMware%20Aria%20Automation%20-%20VMware%20Aria%20Automation%20Config&release=8.16&os=&servicePk=202405&language=EN&groupId=203949
    1. Be sure to download the "Automated Installer", not the OVA or virtual appliance
  4. Extract the installer tarball on the new managed VM
  5. Find the DB packages under sse-installer/salt/sse/eapI_database/files and install the RPM's in a single command like rpm -Uvh ./*.rpm
    1. If the service started, go ahead and stop the postgresql service for now
  6. Copy the DB configuration from the LCM based appliance over to the DB server
    1. The default configuration is normally under /var/lib/postgresql/data, or /var/lib/postgresql/<VERSION>/data
    2. You will need to copy the postgresql.conf and the pg_hba.conf files over to the new host
  7. Start the DB service with a command like "systemctl start postgresql-<VERSION>"
  8. Restore the DB backup on the new server
    1. See the linked instructions above
  9. Install Redis on the new managed VM from the installer provided packages
    1. The installer provided package can be found under sse-installer/sse/salt/eapi_cache/files/
    2. Run a command like rpm -Uvh ./*.rpm to install the service
    3. Ensure that the Redis service is stopped with a command like "systemctl stop redis"
    4. Copy over the Redis configuration from the appliance
      1. This file is normally stored under /etc/redis.conf or /etc/redis/redis.conf
      2. You can also just tarball the entire directory and copy it over to the new managed VM
  10. Start the Redis service with a command like "systemctl start redis"
  11. Install RaaS from the installer provided packages
    1. The installer provided packages can be found under sse-installer/salt/sse/eapi_service/files
    2. Install the files with a series of commands like the following
      1. rpm -Uvh ./openssl*.rpm
      2. rpm -Uvh ./lib*.rpm
      3. rpm -Uvh ./xml*.rpm
      4. rpm -Uvh ./ssc-trans*.rpm
      5. rpm -Uvh ./singleton*.rpm
        1. If this command hangs at some point it is okay to use Ctrl-c to quit out of the package installation
        2. Confirm that the package is installed successfully with rpm -qa | grep -i singleton
        3. This package requires Java to also be installed
      6. rpm -Uvh ./raas*.rpm
    3. Ensure that the RaaS service is stopped with a command like "systemctl stop raas"
    4. Copy over the previously created tarball containing the RaaS configuration and unpack the tarball on the new managed VM
        1. Confirm that you see the /etc/raas/pki/.raas.key file in the expected location
  12. Start the RaaS service with a command like "systemctl start raas"
  13.  Check the RaaS service status with a command like "systemctl start raas"
    1. The service may take a minute to come up
  14. Resolve any errors that may arise

 

In the event that your Aria Config instance is integrated with Aria Automation (formerly vRA), then you will need to additionally follow these steps: 

  1. Snapshot LCM, Aria Automation, Aria Config
  2. In LCM, open the Aria Automation environment and remove the Aria Config product from the environment
    1. This will not delete the LCM deployed Config appliance
    2. This will attempt to remove the Aria Config integration from Aria Automation
    3. If there are existing deployments in Automation that depend on the integration this step will fail
    4. If this step fails it is save to retry the operation and skip it in the LCM request
  3. In the newly deployed Aria Config, connect to the postgres database with the command: su - postgres -c psql
  4. In the PostgreSQL prompt the vra_params table content needs to be deleted: delete from vra_params;
    1. Once this is run only local account access will be enabled for Aria Config. vIDM based auth provided by Aria Automation will no longer work. If you do not want to leverage local accounts you may configure LDAP integration directly on Config
    2. https://docs.vmware.com/en/VMware-Aria-Automation/8.16/Using-Automation-Config/GUID-54FE4409-718B-4BA9-ADD3-7CA1874865F5.html
  5. Update any DNS / IP configurations for Aria Config. If the integration in step 2 did not delete and was skipped then the new Aria Config appliance MUST use the same fqdn as the previous Config appliance in DNS
  6. If the integration in step 2 succeeded the Aria Config appliance can use any desired fqdn when the integration is recreated
  7. If you are deploying Windows machines using the Aria Automation integration ensure you have also completed the following:
    1. Ensure that "salt-cloud" is installed along with "salt-master"
    2. Unpack the desired minion version bundle into /etc/salt/cloud.deploy.d
    3. Install the dependencies outlined in the following document using `salt-pip install <package_name>`:
      1. https://docs.saltproject.io/en/latest/topics/cloud/windows.html

Please contact support in the event you have any questions regarding this process.

Powered by Wolken Software