Migrate from Aria Automation to Aria Automation with OneFuse
Migration tools for OneFuse managed objects from VMware Aria Automation to VMware Aria Automation with OneFuse
34 minute read
The OneFuse Migration Tools vRealize Orchestrator Package provides examples for the user to “create” OneFuse Managed Objects via Brownfield ingest from Aria Automation VMs and apply necessary OneFuse vRA Properties on these VMs (to enable future deprovisioning from Aria Automation+OneFuse).
Once migrated, OneFuse Managed Objects will exist and the user has the flexibility to do the following:
- Destroy via API without deprovisioning.
- Destroy normally within the deployment in Aria Automation/Cloud, which then calls OneFuse to destroy and deprovision the resource.
The following table depicts sample workflows for OneFuse Modules in the Migration Tools vRO Package:
| OneFuse Module / Feature | Migration Tools vRO Package Minimum Version |
|---|---|
| Ansible Tower | 2023.0.0 Build 20555874 |
| DNS Module | 2023.0.0 Build 20555874 |
| IPAM Module | 2023.0.0 Build 20555874 |
| Microsoft Active Directory Module | 2023.0.0 Build 20555874 |
| Naming Module | 2023.0.0 Build 20555874 |
| ServiceNow CMDB Module | 2023.0.0 Build 20555874 |
| Properties | 2023.0.0 Build 22506664 |
Prerequisites
-
OneFuse configured:
- DNS requires necessary Credentials, Endpoints and DNS Policies
- IPAM requires necessary Credentials, Endpoints and IPAM Policies
- Naming requires Sequences and Naming Policies
-
VMware Aria Automation 8.2+/Cloud installed and set up with OneFuse:
VMware’s Aria Automation 8.2+ started support for injecting custom properties on vRA8 VMs outside of the normal lifecycle.
- Getting started
- Installation and setup
- Note the OneFuse Endpoint name and configurations for the migration workflows below.
Download the migration tool vRealize Orchestrator workflow package
Access CloudBolt’s Download Article for CMP/OneFuse 2023.5.
The article will always contain the latest vRO Migration Package Download Link.
- Go to https://support.cloudbolt.io/cloudbolt/s/article/cloudbolt-2023-5--1983840286--1.
- Download the OneFuse VMware vRO Migration Package.
Import the migration tool vRealize Orchestrator workflow package
For a new install and upgrades, perform the following to import the latest migration tool vRealize Orchestrator workflow package.
- Log in to Aria Orchestrator.
- Open up the Navigation tab on the left hand side of the screen and select Assets > Packages.
- Select Import.
-
Select the migration tool vRealize Orchestrator workflow package (
.package) to upload. -
Select Open.
-
Review the imported package information.
You might be prompted to indicate that you trust the publisher certificate of the source vRealize Orchestrator instance before you can import the file.
-
Select Import.
-
- Verify the OneFuse vRealize Orchestrator workflow package successfully imported:
io.cloudbolt.onefuse.migrationis listed in the list of Packages under Assets > Packages.- The Build Number is found in the Description field of the vRO Package.
Migrate existing resources to OneFuse Managed Objects
Ansible Tower
Migrate Aria Automation VMs to create OneFuse Managed Ansible Tower Deployments. In addition, apply necessary OneFuse vRA Properties to the Aria Automation VMs so that when the deployment is destroyed from Aria Automation, OneFuse will destroy the Ansible Tower Deployments.
Optionally, if there are any vRA Properties that identify and/or filter the VMs to be migrated, it will be helpful to have a list to reference when running the workflow below.
- Log in to Aria Orchestrator.
- Open up the Navigation tab on the left hand side of the screen and select Assets > Workflows.
- Switch to Tree-View in the top right hand corner of the screen.
- Go to the following workflow via tree view: Workflows > OneFuse > Migration Tools > Ansible Tower > From vRA8 > To vRA8.
- Select the Workflow: Migrate Ansible Tower from vRA8 to vRA8+OneFuse > select Run.
- Fill out the form fields.
- Select the Run button.
- Verify the Workflow completed successfully.
Migrate Ansible Tower from vRA8 to vRA8+OneFuse
| Field Label | Description |
|---|---|
| OneFuse Endpoint and Policy | |
| OneFuse Endpoint | Select the OneFuse Endpoint (created in prerequisite step 3, Installation and Setup). |
| OneFuse Policy Name to migrate to | Select the OneFuse Policy Name to migrate the Deployments to from the dropdown. |
| Name | |
| Limit scope on Name (vRA8 Resource Name) | Boolean checkbox to enable/disable the “Limit scope on Name” function. |
| Name search string | Provide a search string that will be used to limit the scope based on the vRA8 Resource Name. |
| Name search match type | Select from the dropdown - startswith (The name of the vRA8 Resource must start with search string) - endswith (The name of the vRA8 Resource must end with search string) - substring (The name of the vRA8 Resource must contain the search string) - equal (The name of the vRA8 Resource must exactly match the search string) |
| Primary IP Address | |
| Limit scope on Primary IP Address | Boolean checkbox to enable/disable the “Limit scope on Primary IP Address” function. |
| Primary IP Address search string | Provide a search string that will be used to limit the scope based on the Primary IP Address. |
| Primary IP Address search match type | Select from the dropdown - startswith (The Primary IP Address of the vRA8 Resource must start with search string) - endswith (The Primary IP Address of the vRA8 Resource must end with search string) - substring (The Primary IP Address of the vRA8 Resource must contain the search string) - equal (The Primary IP Address of the vRA8 Resource must exactly match the search string) |
| Owner | |
| Limit scope on Owner | Boolean checkbox to enable/disable the “Limit scope on Owner” function. |
| Owner (exact match) | Provide the owner string that will be used to limit the scope. |
| Project | |
| Limit scope on Project | Boolean checkbox to enable/disable the “Limit scope on Project” function. |
| Project | Select Project from populated dropdown. |
| Match All Properties | |
| Limit scope based on ALL vRA8 Custom Properties - Number of Properties | Filter VMs based on ALL specified number of vRA8 Properties. Select from the dropdown: - 0 - Do not Limit scope based on ALL - 1 - Limit scope based on 1 vRA Property - 2 - Limit scope based on 2 vRA Properties - 3 - Limit scope based on all 3 vRA Properties For each selected number of Properties provide the below information - Property Key - Property Value (Optional) - Property Value - Match Type (Select from the dropdown) - equal (The Property Value must exactly match the search string) - startswith (The Property Value must start with search string) - endswith (The Property Value must end with search string) - substring (The Property Value must contain the search string) |
| Match Any Properties | |
| Limit scope based on ANY vRA8 Custom Properties - Number of Properties | Filter VMs based on ANY specified number of vRA8 Properties. Select from the dropdown: - 0 - Do not Limit scope based on ANY - 2 - Limit scope based on matching at least one of the 2 vRA Properties - 3 - Limit scope based on matching at least one of the 3 vRA Properties For each selected number of Properties provide the below information - Property Key - Property Value (Optional) - Property Value - Match Type (Select from the dropdown) - equal (The Property Value must exactly match the search string) - startswith (The Property Value must start with search string) - endswith (The Property Value must end with search string) - substring (The Property Value must contain the search string) |
| vRA Tags | |
| Limit scope based on vRA Tags - Number of Tags | Filter VMs based on ANY specified number of vRA8 Tags. Select from the dropdown: - 0 - Do not Limit scope based on vRA Tags - 1 - Limit scope based on 1 vRA Tag - 2 - Limit scope based on 2 vRA Tags - 3 - Limit scope based on 3 vRA Tags (If 2 or 3 are selected, select in the dropdown whether machines should match ALL tags or ANY of the tags) For each selected number of vRA Tags provide the below information - vRA Tag - Key - vRA Tag - Value (Optional) |
| Settings | |
| Allow Ingest of duplicates | Recommended to select No. In the event this workflow runs multiple times and this is Yes, it will create the OneFuse Managed Object (regardless if another with the same values exist) and overwrite the vRA Property with the latest Managed Object reference. |
| Dry run? | If Yes, this will not perform an actual migration. It will only provide logs for the actions this workflow would have performed. Select No to perform a migration. |
| Error handling | Select from the dropdown: - Roll back: Completely roll back all migration creation/vRA Properties injection - Skip failures and report: Will log the failure, continue with the migration and at the end, provide a summarized report via vRO Logs. (The following variables for a particular Workflow run captures the outputs: managedObjectsPropString, ingestedManagedObjectsPropString, customPropertiesPropString, trackingIdPropString, vmPropertiesPropString and statusPropString. Please note that more output properties may exist.) |
DNS
Migrate Aria Automation VMs to create OneFuse Managed DNS Reservations. In addition, apply necessary OneFuse vRA Properties to the Aria Automation VMs so that when the deployment is destroyed from Aria Automation, OneFuse will destroy the DNS Reservations.
Optionally, if there are any vRA Properties that identify and/or filter the VMs for particular Domains, it will be helpful to have a list to reference when running the workflow below.
- Log in to Aria Orchestrator.
- Open up the Navigation tab on the left hand side of the screen and select Assets > Workflows.
- Switch to Tree-View in the top right hand corner of the screen.
- Go to the following workflow via tree view: Workflows > OneFuse > Migration Tools > DNS > From vRA8 > To vRA8.
- Select the Workflow: Migrate DNS Reservations from vRA8 to vRA8+OneFuse > select Run.
- Fill out the form fields.
- Select the Run button.
- Verify the Workflow completed successfully.
Migrate DNS Reservations from vRA8 to vRA8+OneFuse
| Field Label | Description |
|---|---|
| OneFuse Endpoint and Policy | |
| OneFuse Endpoint | Select the OneFuse Endpoint (created in prerequisite step 3, Installation and Setup). |
| OneFuse Policy Name to migrate to | Select the OneFuse Policy Name to migrate the Deployments to from the dropdown. |
| Domains for the Policy to register against | Provide an array of Domain names for the DNS Policy to register against. |
| Validate NIC DNS Suffix against provided Domains | Boolean checkbox to control whether or not the workflow should validate the DNS Suffix of each nic matches the provided Domains. |
| Name | |
| Limit scope on Name (vRA8 Resource Name) | Boolean checkbox to enable/disable the “Limit scope on Name” function. |
| Name search string | Provide a search string that will be used to limit the scope based on the vRA8 Resource Name. |
| Name search match type | Select from the dropdown - startswith (The name of the vRA8 Resource must start with search string) - endswith (The name of the vRA8 Resource must end with search string) - substring (The name of the vRA8 Resource must contain the search string) - equal (The name of the vRA8 Resource must exactly match the search string) |
| Primary IP Address | |
| Limit scope on Primary IP Address | Boolean checkbox to enable/disable the “Limit scope on Primary IP Address” function. |
| Primary IP Address search string | Provide a search string that will be used to limit the scope based on the Primary IP Address. |
| Primary IP Address search match type | Select from the dropdown - startswith (The Primary IP Address of the vRA8 Resource must start with search string) - endswith (The Primary IP Address of the vRA8 Resource must end with search string) - substring (The Primary IP Address of the vRA8 Resource must contain the search string) - equal (The Primary IP Address of the vRA8 Resource must exactly match the search string) |
| Owner | |
| Limit scope on Owner | Boolean checkbox to enable/disable the “Limit scope on Owner” function. |
| Owner (exact match) | Provide the owner string that will be used to limit the scope. |
| Project | |
| Limit scope on Project | Boolean checkbox to enable/disable the “Limit scope on Project” function. |
| Project | Select Project from populated dropdown. |
| Match All Properties | |
| Limit scope based on ALL vRA8 Custom Properties - Number of Properties | Filter VMs based on ALL specified number of vRA8 Properties. Select from the dropdown: - 0 - Do not Limit scope based on ALL - 1 - Limit scope based on 1 vRA Property - 2 - Limit scope based on 2 vRA Properties - 3 - Limit scope based on all 3 vRA Properties For each selected number of Properties provide the below information - Property Key - Property Value (Optional) - Property Value - Match Type (Select from the dropdown) - equal (The Property Value must exactly match the search string) - startswith (The Property Value must start with search string) - endswith (The Property Value must end with search string) - substring (The Property Value must contain the search string) |
| Match Any Properties | |
| Limit scope based on ANY vRA8 Custom Properties - Number of Properties | Filter VMs based on ANY specified number of vRA8 Properties. Select from the dropdown: - 0 - Do not Limit scope based on ANY - 2 - Limit scope based on matching at least one of the 2 vRA Properties - 3 - Limit scope based on matching at least one of the 3 vRA Properties For each selected number of Properties provide the below information - Property Key - Property Value (Optional) - Property Value - Match Type (Select from the dropdown) - equal (The Property Value must exactly match the search string) - startswith (The Property Value must start with search string) - endswith (The Property Value must end with search string) - substring (The Property Value must contain the search string) |
| vRA Tags | |
| Limit scope based on vRA Tags - Number of Tags | Filter VMs based on ANY specified number of vRA8 Tags. Select from the dropdown: - 0 - Do not Limit scope based on vRA Tags - 1 - Limit scope based on 1 vRA Tag - 2 - Limit scope based on 2 vRA Tags - 3 - Limit scope based on 3 vRA Tags (If 2 or 3 are selected, select in the dropdown whether machines should match ALL tags or ANY of the tags) For each selected number of vRA Tags provide the below information - vRA Tag - Key - vRA Tag - Value (Optional) |
| Settings | |
| Allow Ingest of duplicates | Recommended to select No. In the event this workflow runs multiple times and this is Yes, it will create the OneFuse Managed Object (regardless if another with the same values exist) and overwrite the vRA Property with the latest Managed Object reference. |
| Dry run? | If Yes, this will not perform an actual migration. It will only provide logs for the actions this workflow would have performed. Select No to perform a migration. |
| Error handling | Select from the dropdown: - Roll back: Completely roll back all migration creation/vRA Properties injection - Skip failures and report: Will log the failure, continue with the migration and at the end, provide a summarized report via vRO Logs. (The following variables for a particular Workflow run captures the outputs: managedObjectsPropString, ingestedManagedObjectsPropString, customPropertiesPropString, trackingIdPropString, vmPropertiesPropString and statusPropString. Please note that more output properties may exist.) |
IPAM
Migrate Aria Automation VMs to create OneFuse Managed IPAM Reservations. In addition, apply necessary OneFuse vRA Properties to the Aria Automation VMs so that when the deployment is destroyed from Aria Automation, OneFuse will destroy the IPAM Reservations.
Optionally, if there are any vRA Properties that identify and/or filter the VMs for particular Subnets, it will be helpful to have a list to reference when running the workflow below.
- Log in to Aria Orchestrator.
- Open up the Navigation tab on the left hand side of the screen and select Assets > Workflows.
- Switch to Tree-View in the top right hand corner of the screen.
- Go to the following workflow via tree view: Workflows > OneFuse > Migration Tools > IPAM > From vRA8 > To vRA8.
- Select the Workflow: Migrate IPAM Reservations from vRA8 to vRA8+OneFuse > select Run.
- Fill out the form fields.
- Select the Run button.
- Verify the Workflow completed successfully.
Migrate IPAM Reservations from vRA8 to vRA8+OneFuse
| Field Label | Description |
|---|---|
| OneFuse Endpoint and Policy | |
| OneFuse Endpoint | Select the OneFuse Endpoint (created in prerequisite step 3, Installation and Setup). |
| OneFuse Policy Name to migrate to | Select the OneFuse Policy Name to migrate the Deployments to from the dropdown. |
| Migrate any IP from found VMs | Boolean checkbox to control whether or not the workflow should migrate any IP found on the VM or only IPs matching certain IP prefixes. |
| Only migrate IPs that start with | Provide an array of IP prefix strings that an IP should match. For example, “192.168.0.” will only migrate IPs on found VMs, that starts with that string. |
| Name | |
| Limit scope on Name (vRA8 Resource Name) | Boolean checkbox to enable/disable the “Limit scope on Name” function. |
| Name search string | Provide a search string that will be used to limit the scope based on the vRA8 Resource Name. |
| Name search match type | Select from the dropdown - startswith (The name of the vRA8 Resource must start with search string) - endswith (The name of the vRA8 Resource must end with search string) - substring (The name of the vRA8 Resource must contain the search string) - equal (The name of the vRA8 Resource must exactly match the search string) |
| Primary IP Address | |
| Limit scope on Primary IP Address | Boolean checkbox to enable/disable the “Limit scope on Primary IP Address” function. |
| Primary IP Address search string | Provide a search string that will be used to limit the scope based on the Primary IP Address. |
| Primary IP Address search match type | Select from the dropdown - startswith (The Primary IP Address of the vRA8 Resource must start with search string) - endswith (The Primary IP Address of the vRA8 Resource must end with search string) - substring (The Primary IP Address of the vRA8 Resource must contain the search string) - equal (The Primary IP Address of the vRA8 Resource must exactly match the search string) |
| Owner | |
| Limit scope on Owner | Boolean checkbox to enable/disable the “Limit scope on Owner” function. |
| Owner (exact match) | Provide the owner string that will be used to limit the scope. |
| Project | |
| Limit scope on Project | Boolean checkbox to enable/disable the “Limit scope on Project” function. |
| Project | Select Project from populated dropdown. |
| Match All Properties | |
| Limit scope based on ALL vRA8 Custom Properties - Number of Properties | Filter VMs based on ALL specified number of vRA8 Properties. Select from the dropdown: - 0 - Do not Limit scope based on ALL - 1 - Limit scope based on 1 vRA Property - 2 - Limit scope based on 2 vRA Properties - 3 - Limit scope based on all 3 vRA Properties For each selected number of Properties provide the below information - Property Key - Property Value (Optional) - Property Value - Match Type (Select from the dropdown) - equal (The Property Value must exactly match the search string) - startswith (The Property Value must start with search string) - endswith (The Property Value must end with search string) - substring (The Property Value must contain the search string) |
| Match Any Properties | |
| Limit scope based on ANY vRA8 Custom Properties - Number of Properties | Filter VMs based on ANY specified number of vRA8 Properties. Select from the dropdown: - 0 - Do not Limit scope based on ANY - 2 - Limit scope based on matching at least one of the 2 vRA Properties - 3 - Limit scope based on matching at least one of the 3 vRA Properties For each selected number of Properties provide the below information - Property Key - Property Value (Optional) - Property Value - Match Type (Select from the dropdown) - equal (The Property Value must exactly match the search string) - startswith (The Property Value must start with search string) - endswith (The Property Value must end with search string) - substring (The Property Value must contain the search string) |
| vRA Tags | |
| Limit scope based on vRA Tags - Number of Tags | Filter VMs based on ANY specified number of vRA8 Tags. Select from the dropdown: - 0 - Do not Limit scope based on vRA Tags - 1 - Limit scope based on 1 vRA Tag - 2 - Limit scope based on 2 vRA Tags - 3 - Limit scope based on 3 vRA Tags (If 2 or 3 are selected, select in the dropdown whether machines should match ALL tags or ANY of the tags) For each selected number of vRA Tags provide the below information - vRA Tag - Key - vRA Tag - Value (Optional) |
| Settings | |
| Allow Ingest of duplicates | Recommended to select No. In the event this workflow runs multiple times and this is Yes, it will create the OneFuse Managed Object (regardless if another with the same values exist) and overwrite the vRA Property with the latest Managed Object reference. |
| Dry run? | If Yes, this will not perform an actual migration. It will only provide logs for the actions this workflow would have performed. Select No to perform a migration. |
| Error handling | Select from the dropdown: - Roll back: Completely roll back all migration creation/vRA Properties injection - Skip failures and report: Will log the failure, continue with the migration and at the end, provide a summarized report via vRO Logs. (The following variables for a particular Workflow run captures the outputs: managedObjectsPropString, ingestedManagedObjectsPropString, customPropertiesPropString, trackingIdPropString, vmPropertiesPropString and statusPropString. Please note that more output properties may exist.) |
Microsoft Active Directory computer accounts
Migrate Aria Automation VMs to create OneFuse Managed Microsoft Active Directory Computer Accounts. In addition, apply necessary OneFuse vRA Properties to the Aria Automation VMs so that when the deployment is destroyed from Aria Automation, OneFuse will destroy the Microsoft Active Directory Computer Accounts.
Optionally, if there are any vRA Properties that identify and/or filter the VMs to be migrated, it will be helpful to have a list to reference when running the workflow below.
- Log in to Aria Orchestrator.
- Open up the Navigation tab on the left hand side of the screen and select Assets > Workflows.
- Switch to Tree-View in the top right hand corner of the screen.
- Go to the following workflow via tree view: Workflows > OneFuse > Migration Tools > AD > From vRA8 > To vRA8.
- Select the Workflow: Migrate AD from vRA8 to vRA8+OneFuse > select Run.
- Fill out the form fields.
- Select the Run button.
- Verify the Workflow completed successfully.
Migrate AD from vRA8 to vRA8+OneFuse
| Field Label | Description |
|---|---|
| OneFuse Endpoint and Policy | |
| OneFuse Endpoint | Select the OneFuse Endpoint (created in prerequisite step 3, Installation and Setup). |
| OneFuse Policy Name to migrate to | Select the OneFuse Policy Name to migrate the Deployments to from the dropdown. |
| Name | |
| Limit scope on Name (vRA8 Resource Name) | Boolean checkbox to enable/disable the “Limit scope on Name” function. |
| Name search string | Provide a search string that will be used to limit the scope based on the vRA8 Resource Name. |
| Name search match type | Select from the dropdown - startswith (The name of the vRA8 Resource must start with search string) - endswith (The name of the vRA8 Resource must end with search string) - substring (The name of the vRA8 Resource must contain the search string) - equal (The name of the vRA8 Resource must exactly match the search string) |
| Primary IP Address | |
| Limit scope on Primary IP Address | Boolean checkbox to enable/disable the “Limit scope on Primary IP Address” function. |
| Primary IP Address search string | Provide a search string that will be used to limit the scope based on the Primary IP Address. |
| Primary IP Address search match type | Select from the dropdown - startswith (The Primary IP Address of the vRA8 Resource must start with search string) - endswith (The Primary IP Address of the vRA8 Resource must end with search string) - substring (The Primary IP Address of the vRA8 Resource must contain the search string) - equal (The Primary IP Address of the vRA8 Resource must exactly match the search string) |
| Owner | |
| Limit scope on Owner | Boolean checkbox to enable/disable the “Limit scope on Owner” function. |
| Owner (exact match) | Provide the owner string that will be used to limit the scope. |
| Project | |
| Limit scope on Project | Boolean checkbox to enable/disable the “Limit scope on Project” function. |
| Project | Select Project from populated dropdown. |
| Match All Properties | |
| Limit scope based on ALL vRA8 Custom Properties - Number of Properties | Filter VMs based on ALL specified number of vRA8 Properties. Select from the dropdown: - 0 - Do not Limit scope based on ALL - 1 - Limit scope based on 1 vRA Property - 2 - Limit scope based on 2 vRA Properties - 3 - Limit scope based on all 3 vRA Properties For each selected number of Properties provide the below information - Property Key - Property Value (Optional) - Property Value - Match Type (Select from the dropdown) - equal (The Property Value must exactly match the search string) - startswith (The Property Value must start with search string) - endswith (The Property Value must end with search string) - substring (The Property Value must contain the search string) |
| Match Any Properties | |
| Limit scope based on ANY vRA8 Custom Properties - Number of Properties | Filter VMs based on ANY specified number of vRA8 Properties. Select from the dropdown: - 0 - Do not Limit scope based on ANY - 2 - Limit scope based on matching at least one of the 2 vRA Properties - 3 - Limit scope based on matching at least one of the 3 vRA Properties For each selected number of Properties provide the below information - Property Key - Property Value (Optional) - Property Value - Match Type (Select from the dropdown) - equal (The Property Value must exactly match the search string) - startswith (The Property Value must start with search string) - endswith (The Property Value must end with search string) - substring (The Property Value must contain the search string) |
| vRA Tags | |
| Limit scope based on vRA Tags - Number of Tags | Filter VMs based on ANY specified number of vRA8 Tags. Select from the dropdown: - 0 - Do not Limit scope based on vRA Tags - 1 - Limit scope based on 1 vRA Tag - 2 - Limit scope based on 2 vRA Tags - 3 - Limit scope based on 3 vRA Tags (If 2 or 3 are selected, select in the dropdown whether machines should match ALL tags or ANY of the tags) For each selected number of vRA Tags provide the below information - vRA Tag - Key - vRA Tag - Value (Optional) |
| Settings | |
| Allow Ingest of duplicates | Recommended to select No. In the event this workflow runs multiple times and this is Yes, it will create the OneFuse Managed Object (regardless if another with the same values exist) and overwrite the vRA Property with the latest Managed Object reference. |
| Dry run? | If Yes, this will not perform an actual migration. It will only provide logs for the actions this workflow would have performed. Select No to perform a migration. |
| Error handling | Select from the dropdown: - Roll back: Completely roll back all migration creation/vRA Properties injection - Skip failures and report: Will log the failure, continue with the migration and at the end, provide a summarized report via vRO Logs. (The following variables for a particular Workflow run captures the outputs: managedObjectsPropString, ingestedManagedObjectsPropString, customPropertiesPropString, trackingIdPropString, vmPropertiesPropString and statusPropString. Please note that more output properties may exist.) |
Names
Migrate Aria Automation VMs to create OneFuse Managed Names. In addition, apply necessary OneFuse vRA Properties to the Aria Automation VMs so that when the deployment is destroyed from Aria Automation, OneFuse will destroy the Names.
Optionally, if there are any vRA Properties that identify and/or filter the VMs to be migrated, it will be helpful to have a list to reference when running the workflow below.
- Log in to Aria Orchestrator.
- Open up the Navigation tab on the left hand side of the screen and select Assets > Workflows.
- Switch to Tree-View in the top right hand corner of the screen.
- Go to the following workflow via tree view: Workflows > OneFuse > Migration Tools > Naming > From vRA8 > To vRA8.
- Select the Workflow: Migrate VM Names from vRA8 to vRA8+OneFuse > select Run.
- Fill out the form fields.
- Select the Run button.
- Verify the Workflow completed successfully.
Migrate VM Names from vRA8 to vRA8+OneFuse
| Field Label | Description |
|---|---|
| OneFuse Endpoint and Policy | |
| OneFuse Endpoint | Select the OneFuse Endpoint (created in prerequisite step 3, Installation and Setup). |
| OneFuse Policy Name to migrate to | Select the OneFuse Policy Name to migrate the Deployments to from the dropdown. |
| Name | |
| Limit scope on Name (vRA8 Resource Name) | Boolean checkbox to enable/disable the “Limit scope on Name” function. |
| Name search string | Provide a search string that will be used to limit the scope based on the vRA8 Resource Name. |
| Name search match type | Select from the dropdown - startswith (The name of the vRA8 Resource must start with search string) - endswith (The name of the vRA8 Resource must end with search string) - substring (The name of the vRA8 Resource must contain the search string) - equal (The name of the vRA8 Resource must exactly match the search string) |
| Primary IP Address | |
| Limit scope on Primary IP Address | Boolean checkbox to enable/disable the “Limit scope on Primary IP Address” function. |
| Primary IP Address search string | Provide a search string that will be used to limit the scope based on the Primary IP Address. |
| Primary IP Address search match type | Select from the dropdown - startswith (The Primary IP Address of the vRA8 Resource must start with search string) - endswith (The Primary IP Address of the vRA8 Resource must end with search string) - substring (The Primary IP Address of the vRA8 Resource must contain the search string) - equal (The Primary IP Address of the vRA8 Resource must exactly match the search string) |
| Owner | |
| Limit scope on Owner | Boolean checkbox to enable/disable the “Limit scope on Owner” function. |
| Owner (exact match) | Provide the owner string that will be used to limit the scope. |
| Project | |
| Limit scope on Project | Boolean checkbox to enable/disable the “Limit scope on Project” function. |
| Project | Select Project from populated dropdown. |
| Match All Properties | |
| Limit scope based on ALL vRA8 Custom Properties - Number of Properties | Filter VMs based on ALL specified number of vRA8 Properties. Select from the dropdown: - 0 - Do not Limit scope based on ALL - 1 - Limit scope based on 1 vRA Property - 2 - Limit scope based on 2 vRA Properties - 3 - Limit scope based on all 3 vRA Properties For each selected number of Properties provide the below information - Property Key - Property Value (Optional) - Property Value - Match Type (Select from the dropdown) - equal (The Property Value must exactly match the search string) - startswith (The Property Value must start with search string) - endswith (The Property Value must end with search string) - substring (The Property Value must contain the search string) |
| Match Any Properties | |
| Limit scope based on ANY vRA8 Custom Properties - Number of Properties | Filter VMs based on ANY specified number of vRA8 Properties. Select from the dropdown: - 0 - Do not Limit scope based on ANY - 2 - Limit scope based on matching at least one of the 2 vRA Properties - 3 - Limit scope based on matching at least one of the 3 vRA Properties For each selected number of Properties provide the below information - Property Key - Property Value (Optional) - Property Value - Match Type (Select from the dropdown) - equal (The Property Value must exactly match the search string) - startswith (The Property Value must start with search string) - endswith (The Property Value must end with search string) - substring (The Property Value must contain the search string) |
| vRA Tags | |
| Limit scope based on vRA Tags - Number of Tags | Filter VMs based on ANY specified number of vRA8 Tags. Select from the dropdown: - 0 - Do not Limit scope based on vRA Tags - 1 - Limit scope based on 1 vRA Tag - 2 - Limit scope based on 2 vRA Tags - 3 - Limit scope based on 3 vRA Tags (If 2 or 3 are selected, select in the dropdown whether machines should match ALL tags or ANY of the tags) For each selected number of vRA Tags provide the below information - vRA Tag - Key - vRA Tag - Value (Optional) |
| Settings | |
| Allow Ingest of duplicates | Recommended to select No. In the event this workflow runs multiple times and this is Yes, it will create the OneFuse Managed Object (regardless if another with the same values exist) and overwrite the vRA Property with the latest Managed Object reference. |
| Dry run? | If Yes, this will not perform an actual migration. It will only provide logs for the actions this workflow would have performed. Select No to perform a migration. |
| Error handling | Select from the dropdown: - Roll back: Completely roll back all migration creation/vRA Properties injection - Skip failures and report: Will log the failure, continue with the migration and at the end, provide a summarized report via vRO Logs. (The following variables for a particular Workflow run captures the outputs: managedObjectsPropString, ingestedManagedObjectsPropString, customPropertiesPropString, trackingIdPropString, vmPropertiesPropString and statusPropString. Please note that more output properties may exist.) |
ServiceNow CMDB deployments
Migrate Aria Automation VMs to create OneFuse Managed ServiceNow CMDB Deployments. In addition, apply necessary OneFuse vRA Properties to the Aria Automation VMs so that when the deployment is destroyed from Aria Automation, OneFuse will destroy the ServiceNow CMDB Deployments.
Optionally, if there are any vRA Properties that identify and/or filter the VMs to be migrated, it will be helpful to have a list to reference when running the workflow below.
- Log in to Aria Orchestrator.
- Open up the Navigation tab on the left hand side of the screen and select Assets > Workflows.
- Switch to Tree-View in the top right hand corner of the screen.
- Go to the following workflow via tree view: Workflows > OneFuse > Migration Tools > ServiceNow CMDB > From vRA8 > To vRA8.
- Select the Workflow: Migrate ServiceNow CMDB from vRA8 to vRA8+OneFuse > select Run.
- Fill out the form fields.
- Select the Run button.
- Verify the Workflow completed successfully.
Migrate ServiceNow CMDB from vRA8 to vRA8+OneFuse
| Field Label | Description |
|---|---|
| OneFuse Endpoint and Policy | |
| OneFuse Endpoint | Select the OneFuse Endpoint (created in prerequisite step 3, Installation and Setup). |
| OneFuse Policy Name to migrate to | Select the OneFuse Policy Name to migrate the Deployments to from the dropdown. |
| ServiceNow CMDB Class Name | Select the ServiceNow CMDB Class Name from the dropdown that is populated based on the OneFuse Policy selected above. |
| Name | |
| Limit scope on Name (vRA8 Resource Name) | Boolean checkbox to enable/disable the “Limit scope on Name” function. |
| Name search string | Provide a search string that will be used to limit the scope based on the vRA8 Resource Name. |
| Name search match type | Select from the dropdown - startswith (The name of the vRA8 Resource must start with search string) - endswith (The name of the vRA8 Resource must end with search string) - substring (The name of the vRA8 Resource must contain the search string) - equal (The name of the vRA8 Resource must exactly match the search string) |
| Primary IP Address | |
| Limit scope on Primary IP Address | Boolean checkbox to enable/disable the “Limit scope on Primary IP Address” function. |
| Primary IP Address search string | Provide a search string that will be used to limit the scope based on the Primary IP Address. |
| Primary IP Address search match type | Select from the dropdown - startswith (The Primary IP Address of the vRA8 Resource must start with search string) - endswith (The Primary IP Address of the vRA8 Resource must end with search string) - substring (The Primary IP Address of the vRA8 Resource must contain the search string) - equal (The Primary IP Address of the vRA8 Resource must exactly match the search string) |
| Owner | |
| Limit scope on Owner | Boolean checkbox to enable/disable the “Limit scope on Owner” function. |
| Owner (exact match) | Provide the owner string that will be used to limit the scope. |
| Project | |
| Limit scope on Project | Boolean checkbox to enable/disable the “Limit scope on Project” function. |
| Project | Select Project from populated dropdown. |
| Match All Properties | |
| Limit scope based on ALL vRA8 Custom Properties - Number of Properties | Filter VMs based on ALL specified number of vRA8 Properties. Select from the dropdown: - 0 - Do not Limit scope based on ALL - 1 - Limit scope based on 1 vRA Property - 2 - Limit scope based on 2 vRA Properties - 3 - Limit scope based on all 3 vRA Properties For each selected number of Properties provide the below information - Property Key - Property Value (Optional) - Property Value - Match Type (Select from the dropdown) - equal (The Property Value must exactly match the search string) - startswith (The Property Value must start with search string) - endswith (The Property Value must end with search string) - substring (The Property Value must contain the search string) |
| Match Any Properties | |
| Limit scope based on ANY vRA8 Custom Properties - Number of Properties | Filter VMs based on ANY specified number of vRA8 Properties. Select from the dropdown: - 0 - Do not Limit scope based on ANY - 2 - Limit scope based on matching at least one of the 2 vRA Properties - 3 - Limit scope based on matching at least one of the 3 vRA Properties For each selected number of Properties provide the below information - Property Key - Property Value (Optional) - Property Value - Match Type (Select from the dropdown) - equal (The Property Value must exactly match the search string) - startswith (The Property Value must start with search string) - endswith (The Property Value must end with search string) - substring (The Property Value must contain the search string) |
| vRA Tags | |
| Limit scope based on vRA Tags - Number of Tags | Filter VMs based on ANY specified number of vRA8 Tags. Select from the dropdown: - 0 - Do not Limit scope based on vRA Tags - 1 - Limit scope based on 1 vRA Tag - 2 - Limit scope based on 2 vRA Tags - 3 - Limit scope based on 3 vRA Tags (If 2 or 3 are selected, select in the dropdown whether machines should match ALL tags or ANY of the tags) For each selected number of vRA Tags provide the below information - vRA Tag - Key - vRA Tag - Value (Optional) |
| Settings | |
| Allow Ingest of duplicates | Recommended to select No. In the event this workflow runs multiple times and this is Yes, it will create the OneFuse Managed Object (regardless if another with the same values exist) and overwrite the vRA Property with the latest Managed Object reference. |
| Dry run? | If Yes, this will not perform an actual migration. It will only provide logs for the actions this workflow would have performed. Select No to perform a migration. |
| Error handling | Select from the dropdown: - Roll back: Completely roll back all migration creation/vRA Properties injection - Skip failures and report: Will log the failure, continue with the migration and at the end, provide a summarized report via vRO Logs. (The following variables for a particular Workflow run captures the outputs: managedObjectsPropString, ingestedManagedObjectsPropString, customPropertiesPropString, trackingIdPropString, vmPropertiesPropString and statusPropString. Please note that more output properties may exist.) |
Properties
Migrate Aria Automation VMs to move Custom Properties from a vRA8 VM marked as Missing, to a new onboarded vRA8 VM. This is useful in case VMs are moved to a new underlying vCenter, as re-onboarding the VMs is then required in vRA8.
Have a list of VM Names (either vRA8 Resource Names or Host Names) ready, as this is the main input for the workflow to be able to execute.
- Log in to Aria Orchestrator.
- Open up the Navigation tab on the left hand side of the screen and select Assets > Workflows.
- Switch to Tree-View in the top right hand corner of the screen.
- Go to the following workflow via tree view: Workflows > OneFuse > Migration Tools > Properties > From vRA8 > To vRA8.
- Select the Workflow: Migrate VM Properties from vRA8 to vRA8 - Using inclusion and exclusion rules > select Run.
- Fill out the form fields.
- Select the Run button.
- Verify the Workflow completed successfully.
Migrate VM Properties from vRA8 to vRA8 - Using inclusion and exclusion rules
| Field Label | Description |
|---|---|
| Endpoints and Accounts | |
| Use the “vRA Migration” Endpoint as the destination, instead of the primary “vRA” Endpoint | Boolean checkbox to enable/disable using the “vRA Migration” Endpoint as the destination. |
| Source vRA8 Cloud Account | Select the Source vRA8 Cloud Account from the dropdown, that is populated with the names for the Cloud Accounts in the Source vRA8. |
| Destination vRA8 Cloud Account | Select the Destination vRA8 Cloud Account from the dropdown, that is populated with the names for the Cloud Accounts in the Destination vRA8. |
| VMs to Process | |
| Names of VMs to be found | Multi-line text field, where the names of the VMs to be migrated should be pasted into. |
| Type of names provided | Select from the dropdown - vRA8 Resource Names (Names provided are the names that the Resources have in vRA8) - Host Names (Names provided are the Host Names as seen in the Hostname field for each VM in vRA8) |
| Separator used in list of Names | Select from the dropdown - Comma (The list of names is separated by commas) - Semicolon (The list of names is separated by semicolons) - Space (The list of names is separated by spaces) - New Line (The list of names is separated by a new line) |
| Limit scope on Project | Boolean checkbox to enable/disable if only VMs should be included if they are part of the below selected Project. |
| Project | Select the Source vRA8 Project. (Only visible if “Limit scope on Project” is enabled) |
| Properties to migrate | |
| Overwrite existing vRA8 Properties | Boolean checkbox to enable/disable if existing Properties on the Destination VM should be overwritten. |
| Only migrate properties with specified prefixes | Boolean checkbox to enable/disable if only properties with provided prefixes should be migrated. |
| Array of prefixes for properties to be migrated | Provide an array of property prefixes. (Only visible if “Only migrate properties with specified prefixes” is enabled) |
| Ignore properties with specific prefixes | Boolean checkbox to enable/disable if properties with provided prefixes should be ignored. (Only visible if “Only migrate properties with specified prefixes” is disabled) |
| Array of prefixes for properties to be ignored | Provide an array of property prefixes. (Only visible if “Only migrate properties with specified prefixes” is disabled and “Ignore properties with specific prefixes” is enabled.) |
| Settings | |
| Dry run? | If Yes, this will not perform an actual migration. It will only provide logs for the actions this workflow would have performed. Select No to perform a migration. |
| Error handling | Select from the dropdown: - Roll back: Completely roll back all migration creation/vRA Properties injection - Skip failures and report: Will log the failure, continue with the migration and at the end, provide a summarized report via vRO Logs. (The following variables for a particular Workflow run captures the outputs: resourceObjectsPropString, templatePropertiesPropString, customPropertiesPropString, vmPropertiesPropString and statusPropString. Please note that more output properties may exist.) |