In this article, we will demonstrate how to migrate Property Groups from VMware’s vRealize Automation 7 to OneFuse Property Sets.
Features
- Migrate vRA 7 Property Groups from user’s desired vRA tenant to OneFuse as (Static) Property Set(s).
- Ability to migrate all or a selected/filtered set of vRA Property Groups.
- Ability to create a Property Set per vRA Property Group with optional user specified prefix and/or suffix to the name.
- If the vRA Property Group Name has any spaces, dashes (-), periods (.) or slashes, it will be replaced by an underscore (_).
- Ability to create 1 Property Set for all selected vRA Property Group(s) with user specified name and optional description.
- Ability to flatten all properties from selected vRA Property Group(s).
- If the user chooses to flatten all properties, any duplicated properties will be overwritten with the latest vRA Property Group’s value.
- If the user chooses not to flatten all properties, then the properties will get nested inside an object with the key name as the vRA Property Group’s name.
- Ability to flatten all properties from selected vRA Property Group(s).
- Ability to migrate vRA 7 specific properties, nested inside the “OneFuse_VRA7_Props” object.
- *Note: Any vRA 7 specific properties (listed via: https://docs.vmware.com/en/vRealize-Automation/7.6/vrealize-automation-76-custom-properties.pdf) needs to be reviewed if the user decides to migrate them.
- Ability to migrate in SovLabs Heritage specific properties, nested inside the “OneFuse_VRA7_Props” object.
- *Note: Any SovLabs Heritage specific properties (listed via: http://docs.sovlabs.com/latest/vmware-vra7x-plugin/modules/intro/vra-properties/) needs to be reviewed if the user decides to migrate them.
- Any encrypted properties in the vRA Property Group will have blank values for the key in the Property Set.
- Ability for user to see/get a list of Property Set(s) that contain incompatible OneFuse Templating Language (via Workflow Token variable: incompatiblePropertySets) after the workflow run completes.
Prerequisites
- OneFuse installed and setup (instructions).
- OneFuse vRO 7 Package imported (instructions).
- OneFuse Endpoint created via vRO 7 (instructions).
- OneFuse Migration package downloaded and imported into vRO 7 (instructions).
- vRO Java Client to run the migration workflow
Run the vRO Workflow
- Login to vRO 7 Java Client
- Click the Workflows tab
- Navigate to OneFuse > Migration Tools > Properties > vRA7 > Migrate Properties – vRA7 workflow
- Run the Migrate Properties – vRA7 workflow
- Right-click on the workflow and click Start Workflow -OR- Click the green play icon
- Follow instructions based on the desired outcome from the two migration options presented below:
- Creating a Static Property Set per vRA Property Group
- Creating one Static Property Set that merges the selected vRA Property Group(s)
- Once the workflow is submitted, the workflow should complete successfully and create the appropriate Static Property Set(s) in OneFuse.
- Login to the OneFuse UI in order to visually verify.
Incompatible Static Property Sets that were created as part of the migration are listed for review
A courtesy check will be performed during the migration since the SovLabs Heritage Template Engine differs from the OneFuse Template Engine.
Any incompatible Static Property Sets will be listed in the logs for it to be verified and manually resolved by the user.
The list of incompatible Static Property Sets also gets saved in the Workflow Token Variable incompatiblePropertySets for future reference.
Edit the Static Property Set via the OneFuse UI to remediate issues. Refer to the OneFuse Template Engine documentation.
Visual Example of Possible Outcomes
Let’s say we want two vRA Property Groups to be migrated to OneFuse:
- SVL_App_Win2K12
- SVL_App_WindowsApp
For visual purposes, the vRA Property Groups are represented in JSON format.
Scenario 1: Creating a Static Property Set per vRA Property Group
Results in the creation of two Static Property Sets in OneFuse:
- SVL_App_Win2K12
- SVL_App_WindowsApp
Scenario 2: Opting for one Static Property Set for the vRA Property Groups selected and NOT flattening properties
Results in the following:
- 1 Static Property Set with specified name. In our example: “test”
- Any vRA or SovLabs properties nested in the “OneFuse_VRA7_Props” object
- Each vRA Property Group as it’s own object
Scenario 3: Opting for one Static Property Set for the vRA Property Groups selected AND flattening properties
Results in the following:
- 1 Static Property Set with specified name. In our example: “test”
- Any vRA or SovLabs properties nested in the “OneFuse_VRA7_Props” object
- All properties from vRA Property Groups merged. For any duplicate keys, the last vRA Property Group, wins. In our example, the property values defined in SVL_App_WindowsApp will override the values specified in SVL_App_Win2K12 for duplicate keys. The properties that were overridden are highlighted below.
Create a Static Property Set per vRA Property Group
The instructions below will create a corresponding Static Property Set per vRA Property Group selected for migration.
You will be presented with the following options when running the Migrate Properties – vRA7 workflow.
| Section Name | Question | Notes/Comments |
|---|---|---|
| 1 vRA Property Group(s) | ||
| 1a vRealize Automation | Tenant | Select the desired vRA tenant from the dropdown list. Click Next |
| 1b vRA Property Group(s) | Get all Property Groups? | Select Yes to get all existing vRA Property Groups for that tenant. Select No to specify which vRA Property Group(s) to migrate. |
| Name Filter – Optional | Optional field to input letters that will match on name of the vRA Property Groups and result in a filtered list. | |
| Page Size | *Only shown when Get all Property Groups is No Defaulted to 100. Change this field value to a greater number if the vRA tenant has long list of vRA Property Groups | |
| Property Group Names | *Only shown when Get all Property Groups is No Will show the list of vRA Property Groups. Click on Not Set In the dropdown for New value: select the desired vRA Property Group name and click the Insert Value button Repeat until all desired vRA Property Group Names are listed Once satisfied, click Accept Click Next | |
| 2 OneFuse Property Set(s) | ||
| 2a OneFuse Endpoint | OneFuse Endpoint | Select the desired OneFuse Endpoint from the dropdown list Assumes a OneFuse Endpoint was created via vRO 7 (instructions). Click Next |
| 2b Property Set(s) | Create a Property Set per vRA Property Group? | Select Yes |
| Property Set Name Prefix – Optional | Optional. The Static Property Set Name will be the same name as the vRA Property Group Name. If this field is filled out, there will be a prefix added to all the Static Property Sets that get created from this migration run. *If the vRA Property Group Name has any spaces, dashes (-) or periods (.), it will be replaced by an underscore (_). | |
| Property Set Name Suffix – Optional | Optional. The Static Property Set Name will be the same name as the vRA Property Group Name. If this field is filled out, there will be a suffix added to all the Static Property Sets that get created from this migration run. *If the vRA Property Group Name has any spaces, dashes (-) or periods (.), it will be replaced by an underscore (_). | |
| Template Properties – Optional | Optional. Input in a JSON format of properties with key:value pairs that will be used to evaluate any templated fields during the migration. Example: { "Environment": "dev", "OS": "linux", "Application": "web" }Click Next | |
| 2c Advanced | Migrate vRA 7 Properties? | Select Yes to migrate vRA 7 specific properties. They will be nested inside the “OneFuse_VRA7_Props” object. Any vRA 7 specific properties (listed via: https://docs.vmware.com/en/vRealize-Automation/7.6/vrealize-automation-76-custom-properties.pdf) needs to be reviewed if the user decides to migrate them. |
| Migrate SovLabs Properties? | Select Yes to migrate SovLabs Heritage specific properties. They will be nested inside the “OneFuse_VRA7_Props” object. Any SovLabs Heritage specific properties (listed via: http://docs.sovlabs.com/latest/vmware-vra7x-plugin/modules/intro/vra-properties/) needs to be reviewed if the user decides to migrate them. Click Submit |
Create a Static Property Set that contains multiple vRA Property Groups
The instructions below will create one Static Property Set that “merges” the vRA Property Groups selected for migration.
| Section Name | Question | Notes/Comments |
|---|---|---|
| 1 vRA Property Group(s) | ||
| 1a vRealize Automation | Tenant | Select the desired vRA tenant from the dropdown list Click Next |
| 1b vRA Property Group(s) | Get all Property Groups? | Select Yes to get all existing vRA Property Groups for that tenant Select No to specify which vRA Property Group(s) to migrate. |
| Name Filter – Optional | Optional field to input letters that will match on name of the vRA Property Groups and result in a filtered list. | |
| Page Size | *Only shown when Get all Property Groups is No Defaulted to 100. Change this field value to a greater number if the vRA tenant has long list of vRA Property Groups. | |
| Property Group Names | *Only shown when Get all Property Groups is No Will show the list of vRA Property Groups. Click on Not Set In the dropdown for New value: select the desired vRA Property Group name and click the Insert Value button Repeat until all desired vRA Property Group Names are listed Once satisfied, click Accept Click Next | |
| 2 OneFuse Property Set(s) | ||
| 2a OneFuse Endpoint | OneFuse Endpoint | Select the desired OneFuse Endpoint from the dropdown list *Assumes a OneFuse Endpoint was created via vRO 7 (instructions) Click Next |
| 2b Property Set(s) | Create a Property Set per vRA Property Group? | Select No |
| Property Set Name | Type in the Property Set Name *Only Letters, Numbers and underscores (_) allowed | |
| Property Set Description – Optional | Optional. Type in the Property Set Description | |
| Flatten all Properties? | Select Yes to flatten/merge all properties If the user chooses to flatten all properties, any duplicated properties will be overwritten with the latest vRA Property Group’s value. Select No to migrate the properties as children properties nested inside an object with the key name as the vRA Property Group’s name. | |
| Template Properties – Optional | Optional. Input in a JSON format of properties with key:value pairs that will be used to evaluate any templated fields during the migration. Example: { "Environment": "dev", "OS": "linux", "Application": "web" }Click Next | |
| 2c Advanced | Migrate vRA 7 Properties? | Select Yes to migrate vRA 7 specific properties. They will be nested inside the “OneFuse_VRA7_Props” object. Any vRA 7 specific properties (listed via: https://docs.vmware.com/en/vRealize-Automation/7.6/vrealize-automation-76-custom-properties.pdf) needs to be reviewed if the user decides to migrate them. |
| Migrate SovLabs Properties? | Select Yes to migrateSovLabs Heritage specific properties. They will be nested inside the “OneFuse_VRA7_Props” object. Any SovLabs Heritage specific properties (listed via: http://docs.sovlabs.com/latest/vmware-vra7x-plugin/modules/intro/vra-properties/) needs to be reviewed if the user decides to migrate them. Click Submit | |
