Deployment Modes
Table 1 describes the two OmniOperator deployment modes. Choose either based on your requirements.
Deployment Mode |
Description |
Difference |
|---|---|---|
Using SmartKit |
Using SmartKit for service deployment implements batch task distribution without directly performing operations on all background servers. The prerequisite is that you have a Windows environment that can access all servers. SmartKit supports only Windows. |
Compared with local deployment, deployment using SmartKit is much more simple. Specifically, in the local deployment mode, to upload a package to multiple nodes and decompress and copy the package, you need to perform the operations on each node, whereas SmartKit allows you to perform these operations on multiple nodes in a batch. The SmartKit-based deployment mode is recommended. |
Local deployment |
If you want to directly deploy a service on your server, select local deployment. If there are a large number of nodes in the cluster, you are advised to generate scripts by referring to the local deployment procedure to implement batch installation. |
Before configuring environment variables, check whether environment variables such as LIBRARY_PATH and LD_LIBRARY_PATH exist in your environment. If the environment variables do not exist, you do not need to add $LD_LIBRARY_PATH and $LIBRARY_PATH during configuration, so as to prevent irrelevant content from being introduced to the current path. Otherwise, security problems may occur. All environment variable export operations in this document comply with this principle. Take LD_LIBRARY_PATH as an example. If LD_LIBRARY_PATH already exists in your environment, use export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/xxx. Otherwise, use export LD_LIBRARY_PATH=/xxx.