Before you use OAT-CLI to deploy OCP, OMS, or ODC, you must upload the installation packages required for each product to the server where OAT-CLI is installed.
Run scp commands to upload local installation packages to the /root/t-oceanbase-antman/ directory on the server where OAT-CLI is installed.
Contact technical support to obtain the installation packages of your required versions.
For OCP deployment, you must upload the following installation packages to the server where OAT-CLI is installed: the installation package of OCP, installation package of OBProxy for OCP MetaDB, and installation package of OceanBase for OCP MetaDB.
In the following commands,
oat_serverindicates the IP address of the server where OAT-CLI is installed. NoteTo use the DNS mode in a three-node OCP deployment, you must also prepare the DNS installation package.
[root@hostname /]# scp ./ocp.tar <oat_server>:/root/t-oceanbase-antman/ocp.tar [root@hostname /]# scp ./obproxy.tar <oat_server>:/root/t-oceanbase-antman/obproxy.tar [root@hostname /]# scp ./observer.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 command,
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 command,
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