1.4 PlateSpin Discovery

In a PlateSpin Discovery environment, PlateSpin Transformation Manager works with the PlateSpin Migrate Connector to provide automated discovery of details about source workloads and target platforms.

Source Workload Discovery

Import with automated discovery simplifies and standardizes the setup of workloads for planning. You provide minimal connection information and logon credentials. The discovery process retrieves details about the workload, populates properties for the related object in the planning database, and creates a proposed workload with the same configuration. Workload discovery is required before you can submit a workload for automated migration.

Transformation Manager provides the following methods of import and automated discovery of workloads:

  • Single IPv4 address or FQDN

  • Range of IPv4 addresses (0 to 255)

  • Spreadsheet with any number of workloads, providing the IPv4 address or FQDN for each

  • REST API by using your custom script

You can retry failed discoveries for one or multiple items at a time. You can also rediscover modified workloads if needed.

Target Platform Discovery

Target platform discovery standardizes information collected for the platform and helps set boundaries for target workloads that will be created there. You provide minimal connection information and logon credentials. The discovery process retrieves details about available resources for the platform. Platform discovery is required before you can configure automated migrations for a workload.

Transformation Manager provides automated discovery for supported target platforms, such as VMware vCenter clusters and Microsoft Azure global and sovereign clouds. The platform resources are rediscovered automatically about every 6 hours or on demand.

The resource information is specific to the target account and platform type:

  • VMware vCenter Server

    • Clusters

    • Hosts

    • Networks

    • Datastores

    • Resource Pools

  • Microsoft Azure Cloud

    • Associated locations based on the target cloud environment

    • Networks

    • Subnetworks

    • Datastores (storage accounts)

    • Resource groups