Online Discovery
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. Then you can organize the associations between resources and applications. The resource types supported by MgC depend on the source 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 an Online Discovery Task
- Sign in to the MgC console. In the navigation pane, under Project, select an application migration project from the drop-down list.
- In the navigation pane, choose Discover > Source Resources.
- Under Online Discovery, click Cloud Discovery.
Figure 1 Cloud platform discovery
- Configure the parameters listed in Table 1 to create a discovery task.
Table 1 Parameters for creating a cloud 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
Resource Type
Choose the types of source resources (collection items) to be collected from the drop-down list. For resource types supported for each cloud platform, see Table 2.
Yes
Application
Select the application that you want to group the discovered resources into. If no applications are available, perform the following steps to create one:
- Click Create Application, enter an application name and description, select a business scenario and running environment, and select the region where the application resources will be deployed on the target cloud.
- Click OK.
No
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
-
Middleware
- Redis
- Kafka
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
- Click Confirm. After the Internet-based discovery task is created, MgC starts discovering source resources.
- If the task succeeds, return to the Source Resources page and view the list of discovered source resources and resource details.
- If the task fails, click the task name to view the data source that fails to be collected. Move the cursor to the collection status of the data source to view the failure cause.
Figure 2 Viewing the failure cause
- 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 collection and design a migration solution.
- For discovered middleware, databases, and storage resources, design migration solutions. Deep collection is available for AWS RDS (for MySQL, MariaDB, Aurora, PostgreSQL, SQL Server, and Oracle) and AWS DocumentDB databases.
- For discovered object storage resources, perform a deep collection and configure a migration plan.
Check Migration Readiness for Servers
- Install the MgC Agent in the source intranet environment and connect the MgC Agent to MgC.
- Go to the Source Resources page, in the server list, select the servers to be migrated and click Group as Application above the list. If you have specified an application in the Internet-based discovery task for discovering these source servers, skip this step.
- If you have created an application, select the application from the drop-down list and click OK.
- If you have not created an application, click Create Application in the displayed dialog box. Then enter an application name and description, select a business scenario, environment, and target region, and click Create. Then click OK.
- On the top of the server list, choose Migration Scenario > Server migration.
- For each source server, click Configure in the Migration Readiness column.
- 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.
MgC Agent
Select the MgC Agent installed in the source environment.
Access IP Address
Select the IP address for accessing the source server. It can be a public or private IP address. After the pre-migration 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 MgC Agent.
- By default, port 5985 on Windows source servers must be opened to the MgC Agent. The port cannot be changed.
- By default, port 22 on Linux source servers must be opened to the MgC Agent. 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 MgC Agent console, add the server credential to the MgC Agent, and synchronize it to MgC.
NOTICE:The account provided in the credential must have sufficient permissions, so the MgC Agent can collect necessary server details. To perform a deep collection for the server to collect as much as details, the credential you provided must meet the following requirements:
- Linux: root and its password
- Windows: administrator and its password
- Click Confirm. The system checks whether the source server can be accessed using the information you provided 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 or design a migration plan to migrate the server.
Performing a Deep Collection for Servers
- Ensure that the MgC Agent has been installed in the source intranet environment and has been connected to MgC.
- On the Source Resources page, in the server list, locate the source server whose details you want to collect and click Configure in the MgC Agent column. Configure the parameters listed in Table 4.
Table 4 Parameters for configuring a deep collection Parameter
Configuration
Type
Set this parameter based on the source server OS type.
MgC Agent
Select the MgC Agent installed in the source environment.
Access IP Address
Select the IP address for accessing the source server. It can be a public or private IP address. After the pre-migration 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 MgC Agent.
- By default, port 5985 on Windows source servers must be opened to the MgC Agent. The port cannot be changed.
- By default, port 22 on Linux source servers must be opened to the MgC Agent. 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 MgC Agent console, add the server credential to the MgC Agent, and synchronize it to MgC.
NOTICE:The account provided in the credential must have sufficient permissions, so the MgC Agent can collect necessary server details. To perform a deep collection for the server to collect as much as details, the credential you provided must meet the following requirements:
- Linux: root and its password
- Windows: administrator and its password
- Click Confirm. Then the system automatically starts executing a deep collection. When Collected shows up in the Deep Collection column, the collection is complete. You can design a migration solution or design a migration plan to migrate your servers.
Performing a Deep Collection for Containers
- Ensure that the MgC Agent has been installed in the source intranet environment and has been connected to MgC.
- On the Source Resources page, click the Containers tab.
- For each container resource whose details need to be collected, click Associate in the MgC Agent column.
If you want to associate multiple resources with an MgC agent at a time, select them and click Manage MgC Agent above the list.
- Select the MgC Agent you installed in the source environment and click OK. Wait until Associated appears in the MgC Agent column.
- For each container resource, in the Credential column, click Associate to configure their credentials.
- Select the resource credential. If the credential is not displayed in the list, go to the MgC Agent console, add the credential to the MgC Agent, and synchronize it to MgC.
- 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 Again in the Deep Collection column to launch a deep collection again if needed. After the collection is complete, click the resource name to view the collected details.
Performing a Deep Collection for Object Storage Resources
- Ensure that the MgC Agent has been installed in the source intranet environment and has been connected to MgC.
- On the Source Resources page, click the Storage tab.
- Locate an object storage resource and click Configure in the Deep Collection column.
- Select the MgC Agent in the source environment and the credential for accessing the resource, and click Confirm. If the credential is not displayed in the drop-down list, go to the MgC Agent console and add the resource credential to the MgC Agent and synchronize it to MgC.
NOTICE:
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?
- Click Add Prefix in the Operation column.
- 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.
- 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.
- Ensure that the MgC Agent has been installed in the source intranet environment, can access source databases, and has been registered with MgC.
- On the Source Resources page, click the Databases tab.
- In the database list, filter all discovered AWS databases by applying the Vendor filter. Locate a supported database and in the MgC Agent column, click Associate.
If you want to associate multiple resources with an MgC agent at a time, select them and click Manage MgC Agent above the list.
- Select your MgC Agent. For Access Setting, if the selected resource is in the same VPC as your MgC Agent, select Private access. Otherwise, select Public access. Then click OK. Wait until Associated appears in the MgC Agent column.
- In the Credential column, click Associate to associate the credential for accessing the resource.
- Select the resource credential. If the credential is not displayed in the list, go to the MgC Agent console, add the credential to the MgC Agent, and synchronize it to MgC.
- 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 Again in the Deep Collection column to perform a deep collection again if needed.
- 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
- On the Source Resources page, you can view the list and number of discovered resources.
- Click each tab to view the list of resources for that category.
- Click a resource name to view its details.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot