What's New

This topic describes the new features of OceanBase Admin Toolkit (OAT) V4.2.1.

OAT V4.2.1 provides flexible deployment and out-of-the-box O&M features for OceanBase ecosystem products. OAT allows you to deploy multiple similar products and introduces the concept of components to provide flexible deployment modes.

New features

• OAT V4.2.1 supports unified management of the sqlauditstore component. You can install and uninstall the component in OAT.

• OAT V4.2.1 supports Rocky Linux 9 (RHEL 9).

  • The OAT image contains two Docker binary versions. Docker 20.10.24 is installed for Rocky Linux 9 (RHEL 9), and Docker 18.09.9 is installed for other operating systems.
  • If podman-docker is installed in Rocky Linux 9, an error may occur when you add a server. In this case, we recommend that you uninstall the package first and then install Docker 20 by using OAT.

• You can customize the database when you install and take over OceanBase Cloud Platform (OCP) or OceanBase Developer Center (ODC) by using OAT.

• A system parameter is provided for specifying the remote working directory of OAT.

• OAT V4.2.1 performs a check for the installation, takeover, and upgrade of an unknown product version.

• The OBSharding feature is enhanced.

  • You can define the resource specifications and bind CPU cores with worker threads during the installation of OceanBase Database Proxy (ODP).
  • You can add, remove, replace, scale out, and scale in ODP servers, and modify the binding relationships of CPU cores during resource change operations.
  • Container operations on ODP servers are supported.

• Automatic synchronization of MetaDB resource changes to OCP is implemented.

  When you perform the following operations to change resources in the MetaDB, you can choose to automatically synchronize the changes to OCP:

  • Modify a CPU or memory node: The MetaDB container is rebuilt and the OCP API is called to reinstall the OCP Agent.
  • Remove an OBServer node: The OCP API is called to forcibly remove an OBServer node that is no longer needed in OCP. The OBServer node list is automatically updated. If the corresponding zone is also deleted, you need to manually update the zone list in OCP.
  • Add an OBServer node: If the OCP API is called to add an OBServer node, OCP automatically detects and synchronizes the change in OBServer nodes or zones.

• When you configure clock synchronization for an OBServer node, you can use the chrony service in pool mode. You can also use the server mode or both of them.

• The internationalization of OAT is enhanced, providing services in different languages.

• Prometheus is upgraded to implement comprehensive monitoring and alerting features. Related system parameters are added.

  • Prometheus: obtains monitoring data from /prometheus in OAT.

  • Alertmanager: views alert information from /alertmanager in OAT.

  • System parameters:

    • oat.alertmanager.webhook_config
    • oat.alertmanager.email_config
    • oat.alertmanager.receiver

  • New environment variables for container startup:

    • EXPORTER_ADDRESS="xx.xx.xx.xx:7010"
    • PROMETHEUS_ADDRESS="xx.xx.xx.xx:7011"
    • ALERTMANAGER_ADDRESS="xx.xx.xx.xx:7012"

Supported products and components

The following table lists the products supported by OAT.

The following table lists the components supported by OAT.