Discovering Resources over the Internet

Creating a Discovery Task

1. Log 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 you are a first-time user of MgC, click Discover Over Internet in the Cloud Discovery area.

   If you are not a first-time user of MgC, 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
   Task Basics	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 create a credential by referring to Adding a Credential. 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 your 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 regions where your source services are running.	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 Types of supported resources

   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) 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) Associate the servers to be discovered with 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 based on the resource type.
   • Perform a migration readiness check or deeper discovery on the discovered servers, and design migration solutions.
   • Perform a deeper discovery on the discovered containers, and design migration solutions.
   • Design migration solutions for middleware, database, and storage resources. Deep collection can be performed for AWS RDS for MySQL, MariaDB, and Aurora databases to obtain detailed database information.
   • Perform deep collection and design migration plans for object storage resources. For details, see Creating a Migration Plan.

Performing a Migration Readiness Check

Performing a Deep Collection for Servers or 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, and Aurora 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 collected 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 resource to be discovered deeply is in the same VPC as the Edge device, select Private access. Otherwise, select Public access. Then click OK. Wait until the device association status changes to Associated.
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 and add the credential to the Edge device and synchronize it to MgC.
6. Click OK. Then MgC checks the credential association status. When Ready is displayed in the Deep Collection column, click Collect to start collecting database details.. You can click Collect 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

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.

Rediscovering Resource Details

Rediscovery can only be executed for collection items whose collection status is Succeeded and collection mode is API and for data sources whose collection status is Succeeded. You need to delete the data sources that fail to be collected and click Add Data Source to collect data again.

1. On the task list page, locate a discovery task, and click View in the Operation column.
2. Locate the required data source, click Re-collect in the Operation column, and click OK.

   Locate the required collection item, choose More > Re-collect in the Operation column, and click OK.