Disclaimer: This guide is only supported for OneFuse v1.0 and v1.0.1 only
This Migration Tool allows users who are currently leveraging the SovLabs vRealize Automation 7 Legacy Plugin to move existing module configurations from Legacy SovLabs into OneFuse.
Table of Contents
Migrating SovLabs vRA 7 Legacy Module Configurations
Automatically migrate your existing SovLabs vRA 7 Legacy Module Configurations to OneFuse as Policies. This utility is provided upon request only
Request access to the SovLabs Legacy OneFuse Migration Utility
To obtain a copy of the migration utility, please submit a support request at https://support.cloudbolt.io.
Import Package into vRealize Orchestrator
Import the SovLabs OneFuse Migration package using the VMware Supported Orchestrator package procedure located here
Using the Utility
Select the Workflows tab in the top right-hand corner of the vRealize Orchestrator client.
On the left of the screen navigate to the SovLabs>Migrate folder.
Select the workflow “Migrate to OneFuse"
Click the Start workflow… icon in the centered menu at the top of the vRealize Orchestrator Client.
Select the VMware vRealize Automation Endpoint connection relevant to this migration, and then click Next
In the “OneFuse Endpoint” section of the “Start Workflow : Migrate to OneFuse” dialog, click the blue box titled SovLabs OneFuse Endpoint to migrate content to, and select the VMware vRealize Automation Endpoint connection relevant to this migration
Fill out the field titled “Password for user username-from-connection used for connection to SovLabs OneFuse Endpoint”. Click Next
In the “Module to Migrate” section of the “Start Workflow : Migrate to OneFuse” dialog, select the Module that should be migrated. Click Next
Migrate all Policies
In the “Policies to Migrate” section of the “Start Workflow : Migrate to OneFuse” dialog, select whether or not to Migrate all Policies? and Overwrite Policies already existing in SovLabs OneFuse?
Then click Submit to execute the Workflow with the selected inputs
Migrate Individual Policies
In the “Policies to Migrate” section of the “Start Workflow: Migrate to OneFuse” dialog, click the blue box titled Select which Policies should be migrated.
In the “Array of string” dialog, use the New Value dropdown to select an existing Policy in VMware vRealize Automation.
Click Insert value to add it to the list of policies to be migrated. It is not possible to select the same Policy multiple times.
Once all relevant policies have been added to the list in the “Array of string” dialog, click Accept
Click Submit to execute the Workflow with the selected inputs.
A workflow output will display information about what has been migrated, and any potential issues. It will also provide information, if any, on if the migrated items require manual editing in SovLabs OneFuse to address missing passwords or incompatibilities with the new Template Engine language.
Once the workflow has been submitted and executed, select the Workflow Token underneath the “Migrate to OneFuse” workflow.
Switch to the Logs tab in the middle of the vRealize Orchestrator client
Notate any items listed as Errors in RED. These errors will notate which specific migration elements may need additional updates manually inside the OneFuse Platform
To view an audit log of the inputs selected and items migrated during a specific workflow execution, switch to the Resources tab in the top right-hand corner of the vRealize Orchestrator client.
Navigate to: Library>SovLabs>Migrate
Inside the Migrate folder will be a dated .txt file with the Migration records