This topic describes how to add a server to the resource pool of OceanBase Admin Toolkit (OAT).
Note
This topic uses OAT V4.2.0 as an example. The GUI may vary with the OAT version.
Prerequisites
You have installed OAT. For more information, see Deploy OAT.
Procedure
Log in to the OAT console.
In the left-side navigation pane, click Server to open the Server Management page. In the upper-right corner, click Add Server.
In the Add Server page, enter the basic information.
Parameter descriptions:
Parameter Description Server IP The public IP address of the network interface of the server to be added. SSH Port The SSH access port of the server to be added. IDC The IDC where the server to be added is located. Credentials The access credentials of the server to be added. Username and password or key-based credentials are supported. Description (optional) The comment for the server to facilitate host management. In the Add Server page, configure the initialization settings.
Parameter descriptions:
Parameter Description Server Usage The purpose of the server to be added. OceanBase OS User The operating system user that installs and runs OBServer and OceanBase product services. This can be customized. Password The password of the OS owner user. UID:GID The UID and GID of the OS owner user. Docker root directory The data directory of Docker. Clock Synchronization: Disabled by default. To enable clock synchronization, specify the following information:
Notice
The clock sources must be synchronized between the server where the OceanBase cluster is deployed and the server where OCP is deployed.
Parameter Description Clock source IP address The IP address of the clock source. minpoll The minimum interval, in seconds, between time synchronization requests sent from the chrony client to the clock source. maxpoll The maximum interval, in seconds, between time synchronization requests sent from the chrony client to the clock source. maxslewrate The maximum slew rate for the chrony client clock, in PPM (parts per million). Use this server as a secondary clock source (optional) When enabled, the server can serve as a clock source before requests from clients on the allowlist are allowed and requests from clients on the blocklist are blocked. Automatically Synchronize to OCP: Disabled by default. When enabled, select an installed OCP. If no OCP is available, this option is disabled. After initialization is complete in OAT, OAT automatically calls the OCP API to add the server to the specified OCP for subsequent use.
Notice
- The installed OCPs refer to those available on the page that appears after you choose Product Services > Products > OCP in the OAT console. For more information about how to install OCP, see Deploy OCP.
- Before deploying an OceanBase cluster using OCP, it is necessary to add the nodes where the OceanBase cluster will be deployed to the OCP resource pool.
Disk initialization settings: To ensure the stability of OceanBase Database and related product services, we recommend that you configure the directories of the services on independent disks. When disk initialization is selected, the system automatically creates the corresponding VG by using LVM and mounts LVs of the corresponding size to the specified mount directories.
- Select a disk or partition: The system automatically identifies unmounted disks. You can select one or more disks to mount.
- Mounting Purpose: Select a mounting purpose. Valid values are Software Installation Path, Data Disk Path, Log Disk Path, and Docker Root Directory.
- Mounting Point: Select the mounting path based on the actual situation.
- Space (/GB): Specify the space size based on the actual situation, in GB.
Click Confirm.
If disk initialization is enabled, a dialog box that displays the check items appears. When no errors are reported in the check items, click OK to add the server.
If disk initialization is disabled, the configuration is submitted directly and initialization starts.
After the server is successfully added, you can see it in the server list. The server status is Initializing. On the Server Management page, find the added server and click View Tasks in the Actions column to view the task progress. You can search by IP at the top of the page when there are many servers.
If an error is returned for a subtask that does not affect business, you can view the logs and manually mark the subtask as success.
What to do next
After servers are successfully added, you can deploy OCP according to your requirements:
After OCP is deployed and servers are added, you can deploy an OceanBase cluster according to your requirements:
- Deploy a two-replica OceanBase cluster with the arbitration service by using OCP
- Deploy a single-replica OceanBase cluster by using OCP
- Deploy a three-replica OceanBase cluster by using OCP
References
- For more information about adding servers, see Add a server.
- After a server is initialized, you can perform O&M operations on it, including modifying server usage, clock synchronization configuration, and disk initialization. For more information about server O&M operations, see Perform O&M operations on a server.