Help Center/ Migration Center/ User Guide/ Application Discovery/ Discovering Resources – Simple Project/ Discovering Resources over the Internet
Updated on 2024-11-01 GMT+08:00
View PDF
Share

Discovering Resources over the Internet

Before migrating, you need to discover your resources and collect their details. This section describes how to discover resources provisioned on cloud platforms such as Alibaba Cloud, Huawei Cloud, AWS, Tencent Cloud, Google Cloud, Azure, Qiniu Cloud, and Kingsoft Cloud over the Internet. The resource types MgC can discover depends on the cloud platform.

  • Alibaba Cloud and Huawei Cloud: servers, containers, middleware, databases, networks, and storage
  • Tencent Cloud: servers, databases, and storage
  • AWS , Google Cloud, and Azure: servers, containers, middleware, databases, storage, and networks
  • Qiniu Cloud and Kingsoft Cloud: object storage

Creating a Discovery Task

  1. Sign in to the MgC console.
  2. In the navigation pane on the left, choose Research > Application Discovery. Select a migration project in the upper left corner of the page.
  3. If this is your first time to create a discovery task, click Discover Over Internet in the Cloud Discovery area.

    If this is not your first time to create a discovery task, choose Discover > Over Internet in the Discovery Task card.

  4. Configure a discovery task based on Table 1.

    Table 1 Parameters for creating an Internet-based discovery task

    Area

    Parameter

    Description

    Mandatory

    Basic Settings

    Task Name

    Specify a name for the task.

    Yes

    Task Description

    Describe the task.

    No

    Task Settings

    Source Platform

    Select the source cloud platform. Currently, Alibaba Cloud, Huawei Cloud, AWS, Tencent Cloud, Google Cloud, Azure, Qiniu Cloud, and Kingsoft Cloud are supported.

    Yes

    Credential

    Select the credential for accessing the source cloud platform. If no credential is available, choose Create to add one. For details, see Managing Credentials.

    • If the source cloud platform is Alibaba Cloud, Huawei Cloud, AWS, Tencent Cloud, Qiniu Cloud, or Kingsoft Cloud, select AK/SK for Authentication and enter the AK/SK pair of your source cloud account.
    • If the source cloud platform is Google Cloud, select Configuration File for Authentication and upload the configuration file that contains your Google Cloud service account credentials. The file must be in JSON format and cannot exceed 4 KB.
    • If the source cloud platform is Azure, Select ID/Secret for Authentication. To learn how to obtain Azure credentials, see How Do I Obtain Azure Credentials?

    Yes

    Region

    Select the region where your source environment is located. Multiple regions can be selected.

    Yes

  5. Choose the resource types (collection items) to be collected from the Resource Type drop-down list. For resource types supported for each cloud platform, see Table 2.

    Table 2 Supported resource types

    Cloud Platform

    Resource Type

    Subtype

    Alibaba Cloud
    • Servers
    • Containers
    • Databases

    -

    Middleware
    • Redis
    • Kafka

    Storage
    • Object storage
    • File storage

    Networks
    • Cloud connections
    • Load balancers (ALB and CLB)
    • Private lines
    • Public domain names
    • Private domain names
    • EIPs
    • Public NAT gateways
    • Route tables
    • Security groups
    • VPCs
    • VPN gateways

    Huawei Cloud
    • Servers
    • Containers
    • Databases

    -

    Middleware
    • Redis
    • Kafka

    Storage
    • Object storage
    • File storage

    Networks
    • Load balancers (ELB)
    • Public domain names
    • Private domain names
    • EIPs
    • Public NAT gateways
    • Route tables
    • Security groups
    • VPCs

    AWS
    • Servers
    • Containers
    • Databases

    -

    Storage
    • Object storage
    • File storage

    Networks
    • Load balancers (ELB) (Currently, only CLB balancers are supported.)
    • Public domain names
    • Private domain names
    • EIPs
    • Public NAT gateways
    • Route tables
    • Security groups
    • VPCs

    Storage
    • Object storage
    • File storage

    Tencent Cloud
    • Servers
    • Databases

    -

    Storage
    • Object storage
    • File storage

    Google Cloud
    • Servers
    • Containers
    • Databases

    -

    Middleware

    Redis

    Storage
    • Object storage
    • File storage

    Networks
    • EIPs
    • Route tables
    • Security groups
    • VPCs

    Azure
    • Servers
    • Containers
    • Databases

    -

    Storage
    • Object storage
    • File storage

    Middleware
    • Redis
    • Kafka

    Networks
    • EIPs
    • Route tables
    • Security groups
    • Public NAT gateways
    • VPCs
    • Load balancers

    Qiniu Cloud

    Storage

    Object storage

    Kingsoft Cloud

    Storage

    Object storage

  6. (Optional) Group the servers to be discovered as an application.

    • If an application is available, select the application from the Application drop-down list.
    • If no applications are available, click Create Application. In the displayed dialog box, enter an application name and description, select the business scenario, environment, and region, and click OK.

  7. Click Confirm. After this Internet-based discovery task is created, MgC starts discovering details about resources and applications.

    • You can view the list and details of discovered resources on the Application Discovery page.
    • You can view the task status and view the task details on the task list page. If the task status is Failed, click View in the Operation column to view the data source that failed to be collected. You can move the cursor to the collection status of the data source to view the failure cause.

  8. Wait until the task status changes to Succeeded. Then perform subsequent operations for different types of resources.

Performing a Migration Pre-check

Perform the following steps to check whether your source servers meet the migration requirements:
  1. Ensure that Edge has been installed in the source intranet environment and has been registered with MgC.
  2. On the Application Discovery page, click the Resources tab and click the number in the Server row.
  3. On the top of the server list, choose Migration Scenario > Server migration above the list.
  4. Click Configure in the Migration Readiness column.
  5. Configure the parameters listed in Table 3.
    Table 3 Parameters for configuring migration readiness

    Parameter

    Configuration

    Type

    Set this parameter based on the source server OS type.

    Edge Device

    Select the Edge device in the source environment.

    IP Address

    Select the IP address for accessing the source server. It can be a public or private IP address. After the migration pre-check is passed, the IP address you select here will be used for migration.

    Port

    Enter the port on the source server that allows access from the Edge device.

    • By default, port 5985 on Windows source servers must be opened to the Edge device. The port cannot be changed.
    • By default, port 22 on Linux source servers must be opened to the Edge device. You can specify a different port if needed.

    Credential

    Select the server credential. If the credential has not been added to MgC, go to the Edge console and add the server credential to Edge and synchronize it to MgC.
  6. Click Confirm. The system checks whether the source server can be accessed using the information you specify and whether the server can be migrated. If Ready shows up in the Migration Readiness column, the source server can be migrated. Then you can design a migration solution to migrate the server.

Performing a Deep Collection for Servers or Containers

Perform the following steps to perform a deep collection for your source servers or containers:
  1. Ensure that Edge has been installed in the source intranet environment and has been registered with MgC.
  2. On the Application Discovery page, click the Resources tab and click the number in the Server or Container row.
  3. Locate the server or container that a deep collection is to be performed for, click Configure in the Edge Device column.

    To associate multiple resources with one Edge device, select them and choose Manage Device Association in the upper right corner of the page.

  4. Select your Edge device. For Access Setting, if the selected resource is in the same VPC as the Edge device, select Private access. Otherwise, select Public access. Then click OK. Wait until Associated appears in the Edge Device column.
  5. In the Credential column, click Associate to associate the credential for accessing the resource.
  6. Select the resource credential. If the credential has not been added to MgC, go to the Edge console, add the credential to Edge, and synchronize it to MgC.

    To perform a deep collection for your source servers to collect as much as details, provide server credentials that meet the following requirements:

    • Linux: root account and password
    • Windows: Administrator account and password
  7. Click OK. Then MgC checks whether the server can be accessed using the associated credential. When Ready appears in the Deep Collection column, click Collect to perform a deep collection. After the first deep collection is complete, you can click Collect Again in the Deep Collection column to perform a second deep collection if needed. After the deep collection is complete, you can proceed to the next phase: Designing a Migration Solution.

Performing a Deep Collection for Object Storage Resources

Follow the steps below to perform a deep collection for your object storage resources, so the system can use the collected details to recommend appropriately sized migration clusters.
  1. Ensure that Edge has been installed in the source intranet environment and has been registered with MgC.
  2. On the Application Discovery page, click the Resources tab and click the number in the Storage row.
  3. In the object storage resource list, click Configure in the Deep Collection column.
  4. Select the Edge device in the source environment and the credential used for accessing the resource, and click Confirm. If the credential has not been added to MgC, go to the Edge console and add the resource credential to Edge and synchronize it to MgC.

    To perform a deep collection for your Azure object storage resources, you need to provide your storage account and access key. For details about how to obtain the credentials, see How Do I Obtain the Required Credentials Before Using MgC to Perform a Deep Collection for My Azure Object Storage Resources?

  5. Click Add Prefix in the Operation column.
  6. Enter a prefix to filter the objects whose details need to be collected. If this parameter is not specified, all objects in the bucket are collected by default. Click OK to save the prefix settings.
  7. Click Deep Collection in the Operation column. The system starts collecting path details. You can perform a deep collection on a resource for multiple times. When Collection Status changes to Completed, click the resource name to view the collected information.

Performing a Deep Collection for Databases

Deep collection is available for AWS RDS (for MySQL, MariaDB, Aurora, PostgreSQL, SQL Server, and Oracle) and AWS DocumentDB databases. The data collected includes database version, engine, server character set, average transactions per second (TPS), and queries per second (QPS), and other key performance metrics (KPIs). The collected data depends on the database type.

  1. Ensure that Edge has been installed in the source intranet environment, can access source databases, and has been registered with MgC.
  1. On the Application Discovery page, click the Resources tab and click the number in the Database row.
  2. In the database list, filter all discovered AWS databases by applying the Vendor filter. In the Edge Device column of each database for which deep collection is supported, click Associate.

    To associate multiple databases with one Edge device, select them and choose Manage Device Association in the upper right corner of the page.

  3. Select your Edge device. For Access Setting, if the selected resource is in the same VPC as the Edge device, select Private access. Otherwise, select Public access. Then click OK. Wait until Associated appears in the Edge Device column.
  4. In the Credential column, click Associate to associate the credential for accessing the resource.
  5. Select the database credential. If the credential has not been added to MgC, go to the Edge console, add the credential to Edge, and synchronize it to MgC.
  6. Click OK. Then MgC checks whether the server can be accessed using the associated credential. When Ready appears in the Deep Collection column, click Collect to perform a deep collection. If the first deep collection completes or fails, you can click Collect Again in the Deep Collection column to perform a deep collection again if needed.
  7. Wait for the deep collection to complete. Then click the database name to go to the database details page. In the Database Information area, you can view the collected details.

Viewing the List and Details of Discovered Source Resources

A discovery task can collect only basic information about source resources. More detailed information needs to be collected through a deep collection.
  1. On the Application Discovery page, click the Resources tab to view the number of discovered resources by type and the number of resources that are not associated with applications.

  2. Click a resource type or number to view the resource list.
  3. Click a resource name to view its details.

Viewing Task Details

  1. On the Application Discovery page, click View next to Total tasks to go to the task list.
  2. Locate a discovery task, and click View in the Operation column.
  3. Click before a collection item to view the data sources contained in the collection item and the collection result of each resource type.

    Figure 1 Viewing collection results

  4. In the Collection Result column, you can click the number next to a resource type to view the corresponding resource list.