Migration tools on CloudBolt Documentation

Migrate from vRA 7 to Aria Automation with OneFuse

Mon, 01 Jan 0001 00:00:00 +0000

Once migrated, OneFuse Managed Objects will exist and the user has the flexibility to

Destroy via API without deprovisioning

or
Destroy normally within the deployment in vRA8.2+/Cloud, which then calls OneFuse to destroy and deprovision the resource.

Migrate from Aria Automation to Aria Automation with OneFuse

Mon, 01 Jan 0001 00:00:00 +0000

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:

Migrate from vRA 7 to CMP with OneFuse

Mon, 01 Jan 0001 00:00:00 +0000

The OneFuse Migration Tools vRealize Orchestrator Package provides examples for the user to “create” OneFuse Managed Objects via Brownfield ingest from vRealize Automation 7x VMs and apply necessary OneFuse Properties on CloudBolt’s VMs (to enable future deprovisioning from CMP+OneFuse). Once migrated, OneFuse Managed Objects will exist and the user has the option to flexibility to 1) destroy via API without deprovisioning or 2) destroy normally within the deployment in CloudBolt CMP, which then calls OneFuse to destroy and deprovision the resource.

Migrate from Aria Automation to CMP with OneFuse

Mon, 01 Jan 0001 00:00:00 +0000

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 Properties on CloudBolt’s VMs (to enable future deprovisioning from CMP+OneFuse).

Once migrated, OneFuse Managed Objects will exist and the user has the option to flexibility to

Destroy via API without deprovisioning

Destroy normally within the deployment in CloudBolt CMP, which then calls OneFuse to destroy and deprovision the resource.

The Migration Tools vRO Package contains sample workflows that can be used out-of-the-box or copied then modified to fulfill requirements. Check back here for updates to the Migration Tools vRO Package.