This topic describes the resource requirements for deploying OCP. It is intended for quick start. To deploy OCP in test and production environments, refer to Deploy a database.
In Enterprise Edition OCP deployment, Docker containerization is typically used; Community Edition OCP is deployed as RPM packages. Both versions can deploy OCP-Server, MetaDB, and MonitorDB on the same physical host. MetaDB and MonitorDB can be configured as different tenants within the same OceanBase cluster.
The total host resource requirement is calculated as follows:
Total host resources = OCP-Server resources + MetaDB tenant resources + MonitorDB tenant resources + SYS tenant resources + System_Memory resources + Operating system kernel reserve (20% of total resources, recommended to be configured based on the actual host resources).
Hardware requirements
The minimum hardware requirements for an OCP-Server node are shown in the following table.
Hardware |
Minimum requirements |
|---|---|
| CPU |
|
| Memory | Available Memory: 64 GiB |
| NIC | 10 Gbit/s NIC |
Operating system requirements
Server Type |
Operating System |
Supported Versions |
|---|---|---|
| x86_64 | RHEL | 7.2 and later |
| x86_64 | CentOS | 7.2 and later |
| x86_64 | AliOS | 7.2 and later |
| x86_64 | openSUSE | 12 SP3 and later |
| ARM aarch64 | AliOS | 7.2 and later |
| ARM aarch64 | NeoKylin | 7.6 |
| ARM aarch64 | Huawei EulerOS | 2.0 SP8 |
Example
Using the resources required to manage 10 business OBServer nodes as an example, the required resources are as follows:
Container Classification |
Deployment Content |
CPU (Cores) |
Memory (GiB) |
|---|---|---|---|
| OCP Container | OCP-Server | 8 | 16 |
| OceanBase Container | MetaDB Tenant | 4 | 8 |
| OceanBase Container | MonitorDB Tenant | 4 | 16 |
| OceanBase Container | SYS Tenant | 5 | 28 |
| OceanBase Container | System_Memory | 0 | 0 |
Note
Open ports
Deployment Unit |
Listening Port |
Protocol type |
How to modify the listening port |
Remarks |
|---|---|---|---|---|
| OCP-Server | 8080 | http | Modify OCP system parametersserver.port. The restart takes effect. |
The OCP-Server web service listens on a specific port. Typically, other components access OCP-Server through the SLB/DNS address. |
| OceanBase cluster for OCP | 2881 | tcp | Modification not supported | SQL listening port of the OBServer node. |
| OBProxy | 2883 | tcp | Modification not supported | SQL listening port of OBProxy. |
