Skip to main content
Version: v1.3

Frequently asked questions

Why did you choose to use the k8s deployment?​

K8s has the following advantages:

  • Scalability: nodes can be added or deleted at any time
  • Self healing: monitor your complete infrastructure regularly
  • Portable Management: single node and multi node only need to maintain one set of template

If the hardware requirements cannot be met, can they be deployed normally?​

At present, the configuration required by our pre check is basically the minimum configuration. Assuming that the amount of Task in your environment is extremely low, you can try to reduce some hardware resources (but this does not mean that your services are available). Then you can add --force Command to force installation.

What if the GPU server cannot be provided?​

Although our OCR supports CPU recognition, the recognition effect and recognition speed cannot be guaranteed, so we suggest you choose GPU.

Can I integrate the customer's Docker deployment?​

We support you to use your own docker. If there is a docker command in your server, we will not install docker. vice versa. You do not need to do additional operations. We will automatically determine whether there is a docker service in your server. Please note, however, that we will restart your Docker service for effective configuration.

The customer requires that the firewall must be enabled. Can it be supported?​

We have script Firewalld is supported, but this may cause unnecessary trouble.

Does it support localization system?​

At present, the systematic compatibility of automation code in ARM architecture is not very good. If manual deployment is required in ARM architecture

What should I do if an error occurs during deployment and cannot be resolved?​

You can view the troubleshooting document according to the current running error stage FAQ If you encounter problems during deployment and cannot solve them, you can submit Work order Give it to us. We will assign a technical support engineer to help you solve the problem.

What is the difference between single node deployment and multi node deployment?​

Single node deployment: all services run on this node. When the node is down, the service is unavailable.

Multi node deployment: generally, there are three nodes, and one is allowed to be down. The downtime will not affect the business.

Where are the passwords of MySQL, Redis and other middleware stored?​

By default, we will save all the middleware accounts and passwords in the/usr/local/laipvt/middleware/directory on the machine where the pre check was performed. For example, you can view the MySQL password in/usr/local/laipvt/middleware/mysql Yaml

How to delete a deployed service?​

Whether it is a single node deployment or a multi node deployment, we all support one click unloading of the environment by reading the configuration file (/usr/local/laipvt/check_result. yaml) reserved by pre check. Before uninstalling, make sure that the Docker container and the K8S environment are not running services that are unrelated to the future. This operation will clean up the docker and k8s directories and delete the deployment directory. Therefore, significant and irrecoverable losses are caused.

Whether it is a single node or multiple nodes, this command only needs to be executed on the machine that performs the pre check, and errors will be reported when executed on other machines .

/usr/local/python-3.7.6/bin/laipvt delete --all