This topic describes how to take over DataPilot by using OAT. Taking over means bringing a DataPilot instance that is already running on the target server under OAT management, enabling management tasks such as status monitoring, upgrades, version rollback, and resource changes for DataPilot.
Prerequisites
Before you take over DataPilot, confirm the following information:
- You have installed OAT and logged in as a super administrator or an O&M engineer. For more information, see Install OAT.
- You have added the server where the DataPilot to be taken over resides. For more information, see Add a server.
- You have added the image used by DataPilot.
- You have taken over the components that DataPilot depends on (such as MetaDB, NLB, or OBDNS).
- The target DataPilot instance is deployed in the v2 single-image dual-tenant format and the version is not earlier than 0.30.1.
Note
OAT only supports taking over DataPilot in the v2 single-image dual-tenant format (deploy_schema = v2_single_image_dual_tenant) and the version must be 0.30.1 or later. The v1 dual-image single-tenant format is not supported for takeover. Please manually upgrade it to version 0.30.1 or later first.
Procedure
To take over DataPilot, perform the following steps:
In the left-side navigation pane, click Product Service > Product Management.
On the Product management page, click Take over the product in the upper-right corner and select Take Over DataPilot.
On the Take Over DataPilot page, configure the parameters.
The basic configuration parameters for DataPilot are as follows:
ParameterDescriptionDataPilot Image The Docker image of DataPilot. The version must be 0.30.1 or later. Product Name The product name, which must be unique. Server The IP address of the server where the DataPilot to be taken over resides. CPU The CPU available to DataPilot on the server. Automatically obtained via docker inspect.Memory The memory available to DataPilot on the server. Automatically obtained via docker inspect.The configuration parameters for the DataPilot MetaDB are as follows:
ParameterDescriptionMetaDB Type Select the type of MetaDB. Select Created MetaDB Select an existing MetaDB for DataPilot. (Optional) The load balancing configuration parameters are as follows:
ParameterDescriptionLoad balancing mode Select the load balancing mode. MetaDB TCP proxy IP The TCP address for connecting to MetaDB. MetaDB TCP proxy port The TCP port number. HTTP proxy domain name The HTTP address for accessing the DataPilot console. HTTP proxy port The HTTP port number. After configuring the takeover of DataPilot, click Submit.
If your configuration is incorrect, click Reset to restore the default configuration with one click.
Takeover validation rules
When OAT takes over DataPilot, it performs the following validations:
Verification Phase |
Verification content |
|---|---|
| Image Verification | The image type is DataPilot and the version is not earlier than 0.30.1. |
| Container Verification | The container exists and its name is standard. The image matches the form. The CPU, memory, mount path, and ports are consistent across all nodes. |
| Tenant Verification | Both the Meta tenant and Target tenant in MetaDB exist ininner_service, and use the root user. |
| Load balancing verification | The product L7 rule already exists in OBDNS or NLB.inner_service. |
| Server Verification | No other DataPilot or DataPilot sandbox containers are on the selected server. |
Note
- The
datapilot.credentialcredential file is not generated during takeover. - If DataPilot uses external S3 storage, only the S3 parameter format is validated during takeover; actual connectivity is not verified.
- After takeover, configurations such as CPU and memory are automatically obtained via
docker inspectand written into the product record.
What to do next
After taking over DataPilot, you can perform the following operations on DataPilot:
- Data refresh: When you change DataPilot's configuration outside of OAT, use the data refresh feature to synchronize the records in OAT. For more information, see Data refresh.
- Resource changes: Adjust DataPilot's CPU, memory, or node configurations. For more information, see Product and component resource changes.
- Upgrade: Upgrade the DataPilot version. The target version must be 0.30.1 or later.
- Version rollback: Roll back DataPilot to the previous version. Rollback is only allowed when the current version is 0.30.1 or later.
- Container operations: Perform operations such as rebuilding, starting, and stopping the DataPilot container. For more information, see Container operations.