Before you use oat-cli to deploy OceanBase Cloud Platform (OCP), OceanBase Migration Service (OMS), or OceanBase Developer Center (ODC), you must upload the installation packages required for each product to the servers where oat-cli is installed.
Run scp commands to upload local installation packages to the /root/t-oceanbase-antman/ directory on the servers where oat-cli is installed.
To obtain installation packages of the required versions, contact OceanBase Technical Support.
To deploy OCP, you must upload the OCP image and OCP MetaDB image to the server where oat-cli is installed.
In the following commands,
oat_serverindicates the IP address of the server where oat-cli is installed.Note
To use the Domain Name System (DNS) mode in three-node OCP deployment, you must also obtain the DNS image.
[root@hostname /]# scp ./ocp.tar <oat_server>:/root/t-oceanbase-antman/ocp.tar [root@hostname /]# scp ./metadb.tar <oat_server>:/root/t-oceanbase-antman/observer.tar [root@hostname /]# scp ./dns.tar <oat_server>:/root/t-oceanbase-antman/dns.tarFor ODC deployment, you must upload an ODC image to the server where oat-cli is installed.
In the following commands,
oat_serverindicates the IP address of the server where oat-cli is installed.[root@hostname /]# scp ./odc.tar <oat_server>:/root/t-oceanbase-antman/odc.tarFor OMS deployment, you must upload an OMS image to the server where oat-cli is installed.
In the following commands,
oat_serverindicates the IP address of the server where oat-cli is installed.[root@hostname /]# scp ./oms.tar <oat_server>:/root/t-oceanbase-antman/oms.tar