Discovering Resources over the Internet

Creating a Discovery Task

1. Sign in to the MgC console.
2. In the navigation pane on the left, choose Research > Source Resources. Select a migration project in the upper left corner of the page.
3. In the Discovery Tasks card, choose Discover > Over Internet.
   Figure 1 Discovery over Internet
   

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.
   Figure 2 Selecting the categories of resources to be discovered
   

   Table 2 Supported resource types

   Cloud Platform	Resource Type	Subtype
   Alibaba Cloud	Servers Containers Big data clusters 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 Big data clusters 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 Resource Discovery page.
   • You can view the task status and details on the task list page.

8. Wait until the task status changes to Succeeded. Then perform subsequent operations for different types of resources.
   • For discovered servers, perform a deep collection or check their migration readiness and then design a migration solution or migration plan.
   • For discovered containers, perform a deep collectionand design a migration solution.
   • Design migration solutions for middleware, database, and storage resources. Deep collection is available for AWS RDS (for MySQL, MariaDB, Aurora, PostgreSQL, SQL Server, and Oracle) and AWS DocumentDB databases.
   • Perform a deep collection and design migration plans for object storage resources. For details, see Migration Plans.

Check Migration Readiness for Servers

Performing a Deep Collection for Servers

Performing a Deep Collection for Containers

Performing a Deep Collection for Object Storage Resources

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.
2. On the Resource Discovery page, in the Resources area, click Database in the Category column or the number in the Total Resources column.
3. In the database list, filter all discovered AWS databases by applying the Vendor filter. Locate a supported database and in the Edge Device column, click Associate.

   To associate multiple databases with one Edge device, select them and choose Manage Device Association above the list.

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 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.
7. Click OK. Then MgC checks whether the resource can be accessed using the associated credential. When Ready appears in the Deep Collection column, click Collect to perform a deep collection. You can click Collect in the Deep Collection column to perform a deep collection again if needed.
8. 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 Discovered Source Resources

Viewing Discovery Tasks

1. On the Resource Discovery page, click View next to Total tasks to go to the task list.
   Figure 4 Viewing 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 results.
   Figure 5 Viewing collection results
   

   If a data source fails to be collected, you can move the cursor to the collection status of the data source to view the failure cause.

   

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