Processing method for deploying cloud platform and product

Abstract

The embodiment of the invention provides a processing method and product for deploying a cloud platform, and the method comprises the steps: obtaining a target deployment script of a current cloud platform, the target deployment script comprising a target deployment component corresponding to any node and a deployment sequence of a plurality of target deployment components; executing a deployment process according to the target deployment script, and detecting whether the deployment state of any target deployment component is a deployment error state in real time; when it is detected that the deployment state of any target deployment component is a deployment error state, pausing a deployment process executed according to the target deployment script, and determining and executing an error repair strategy corresponding to the target deployment component; and after the execution of the error repair strategy corresponding to the target deployment component is completed, restarting the deployment process executed according to the target deployment script. The embodiment of the invention aims to improve the stability and reliability of the cloud platform application.

Description

Technical Field

[0001] The embodiments of the present application relate to the technical field of cloud platforms, and more specifically, to a processing method and product for deploying a cloud platform. Background Art

[0002] With the rapid development of cloud computing technology, more and more enterprises and organizations have begun to deploy their business applications on cloud platforms. Cloud platforms provide highly flexible computing resources, allowing users to quickly expand or reduce resources according to demand; applications on cloud platforms are usually composed of multiple nodes and multiple components, which need to collaborate with each other to provide complete services; therefore, how to efficiently deploy multiple nodes and multiple components in succession has become an important research direction.

[0003] The automated deployment tools of cloud platforms can define the deployment process by writing Playbooks, thereby achieving automated deployment. For large-scale cloud platform applications, the deployment process often requires high reliability and high availability. However, when errors occur during the deployment process, these deployment tools require human intervention to check and correct errors. This human intervention not only reduces deployment efficiency, but may also introduce new errors, thereby reducing the stability and reliability of cloud platform applications due to deployment tools. Summary of the invention

[0004] The embodiments of the present application provide a processing method and product for deploying a cloud platform, aiming to improve the stability and reliability of cloud platform applications.

[0005] In a first aspect, an embodiment of the present application provides a method for deploying a cloud platform, the method comprising: Obtain a target deployment script of the current cloud platform, wherein the target deployment script includes a target deployment component corresponding to any node and a deployment order of multiple target deployment components; Execute the deployment process according to the target deployment script, and detect in real time whether the deployment status of any target deployment component is a deployment error status; When it is detected that the deployment state of any target deployment component is a deployment error state, pausing the deployment process executed according to the target deployment script, and determining and executing the error repair strategy corresponding to the target deployment component; When the error repair strategy corresponding to the target deployment component is executed, the deployment process executed according to the target deployment script is restarted.

[0006] Optionally, before obtaining the target deployment script of the current cloud platform, the method further includes: In response to the deployment configuration operation, determining the deployment configuration strategy of the current cloud platform, wherein the deployment configuration strategy includes a target deployment component corresponding to any node, dependencies between the multiple target deployment components, and a deployment order of the multiple target deployment components; Compile the target deployment script of the current cloud platform according to the deployment configuration strategy.

[0007] Optionally, real-time detection of whether the deployment state of any target deployment component is a deployment error state includes: Real-time detection of whether any target deployment component starts to be installed within a first preset time period; If any target deployment component does not start to be installed within the first preset time period, the deployment state of the target deployment component is determined to be a non-deployed state in the deployment error state.

[0008] Optionally, real-time detection of whether the deployment state of any target deployment component is a deployment error state includes: Real-time detection of any interruption in the installation process of any target deployment component; If any target deployment component is interrupted during the installation process, the deployment state of the target deployment component is determined to be a deployment interruption state in the deployment error state.

[0009] Optionally, real-time detection of whether the deployment state of any target deployment component is a deployment error state includes: Verify after any target deployment component is installed; When any installed target deployment component is inconsistent with the corresponding target deployment component configured in the target deployment script, the deployment state of the target deployment component is determined to be a deployment error state in the deployment error state.

[0010] Optionally, the method further comprises: In response to the first repair operation, one or more error repair strategies corresponding to any target deployment component are added to the target deployment script, wherein the multiple error repair strategies include repair strategies corresponding to different error causes.

[0011] Optionally, the method further comprises: In response to the second repair operation, a repair rule base is created, wherein the repair rule base includes one or more error repair strategies corresponding to any target deployment component, and the multiple error repair strategies include repair strategies corresponding to different error causes.

[0012] Optionally, when it is detected that the deployment state of any target deployment component is a deployment error state, pausing the deployment process executed according to the target deployment script, and determining and executing an error repair strategy corresponding to the target deployment component, including: When it is detected that the deployment state of any target deployment component is a deployment error state, pausing the deployment process executed according to the target deployment script; Determine the error cause corresponding to the target deployment component according to the error cause range corresponding to the deployment error state of the target deployment component; According to the error cause corresponding to the target deployment component, an error repair strategy corresponding to the target deployment component is determined.

[0013] Optionally, determining an error repair strategy corresponding to the target deployment component according to the error cause corresponding to the target deployment component includes: According to the error cause corresponding to the target deployment component, searching in the target deployment script whether there is an error repair strategy corresponding to the error cause of the target deployment component; When the target deployment script contains an error repair strategy corresponding to the error cause of the target deployment component, the error repair strategy is executed.

[0014] Optionally, according to the error cause corresponding to the target deployment component, after searching in the target deployment script whether there is an error repair strategy corresponding to the error cause of the target deployment component, the method further includes: When the target deployment script does not contain an error repair strategy corresponding to the error cause of the target deployment component, searching the repair rule library for an error repair strategy corresponding to the error cause of the target deployment component; When the error repair strategy corresponding to the error cause of the target deployment component exists in the repair rule library, the error repair strategy is executed.

[0015] Optionally, after searching the repair rule base to see whether there is an error repair strategy corresponding to the error cause of the target deployment component, the method further includes: When the error repair strategy corresponding to the error cause of the target deployment component does not exist in the repair rule library, a pop-up window prompts the deployment error state and error cause of the target deployment component.

[0016] Optionally, after the error repair strategy corresponding to the target deployment component is executed, restarting the deployment process executed according to the target deployment script includes: After the deployment process executed according to the target deployment script is completed, each target deployment component is tested in turn according to the deployment order of the multiple target deployment components; When the deployment state of any target deployment component is a deployment error state, an error repair strategy corresponding to the target deployment component is determined and executed to repair the target deployment component.

[0017] In a second aspect, an embodiment of the present application provides a computer device, comprising: at least one processor, and a memory, wherein the memory stores a computer program that can be run on the processor, wherein when the processor executes the computer program, the processing method for deploying a cloud platform described in the first aspect of the embodiment is executed.

[0018] In a third aspect, an embodiment of the present application provides a non-volatile readable storage medium, wherein the non-volatile readable storage medium stores a computer program, wherein when the computer program is executed by a processor, the processing method for deploying a cloud platform described in the first aspect of the embodiment is executed.

[0019] In a fourth aspect, an embodiment of the present application provides a computer program product, including a computer program / instruction, which, when executed by a processor, implements the processing method for deploying a cloud platform described in the first aspect of the embodiment.

[0020] Beneficial effects: The method obtains the target deployment script of the current cloud platform, wherein the target deployment script includes the target deployment component corresponding to any node and the deployment order of multiple target deployment components; executes the deployment process according to the target deployment script, and detects in real time whether the deployment status of any target deployment component is a deployment error status.

[0021] When it is detected that the deployment status of any target deployment component is a deployment error status, the deployment process executed according to the target deployment script is suspended, and the error repair strategy corresponding to the target deployment component is determined and executed; when the error repair strategy corresponding to the target deployment component is executed, the deployment process executed according to the target deployment script is restarted.

[0022] By performing error detection on any target deployment component during the process of automated deployment on the cloud platform, when any target deployment component is in a deployment error state, the error of the erroneously deployed target deployment component can be automatically repaired. Compared with manual error checking and correction of component deployment, this improves deployment efficiency and the accuracy of deployed components, thereby improving the stability and reliability of cloud platform applications. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the following is a brief introduction to the drawings required for use in the embodiments or related technical descriptions.

[0024] Figure 1 A flowchart showing the steps of a processing method for deploying a cloud platform provided in an embodiment of the present application is shown; Figure 2 A functional module diagram of a processing device for deploying a cloud platform provided in an embodiment of the present application is shown; Figure 3 A schematic diagram of the structure of an error detection and repair module provided in an embodiment of the present application is shown; Figure 4 A functional module diagram of a processing system for deploying a cloud platform provided in an embodiment of the present application is shown; Figure 5 A schematic diagram of a computer device provided in an embodiment of the present application is shown; Figure 6 A schematic diagram of a non-volatile readable storage medium provided in an embodiment of the present application is shown; Figure 7 The computer program product provided by the embodiment of the present application is shown. DETAILED DESCRIPTION

[0025] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

[0026] To make the purpose, technical scheme and advantages of the embodiments of the present application clearer, each embodiment of the present application will be described in detail below in conjunction with the accompanying drawings. However, it will be appreciated by those skilled in the art that in each embodiment of the present application, many technical details are proposed in order to enable the reader to better understand the present application. However, even without these technical details and various changes and modifications based on the following embodiments, the technical scheme claimed in the present application can also be implemented. The division of the following embodiments is for the convenience of description, and the specific implementation of the present application should not constitute any limitation, and the various embodiments can be combined with each other and referenced to each other without contradiction.

[0027] Cloud platform: refers to a cloud computing platform that provides a range of services and resources, allowing users to access and use these resources through the Internet without having to directly manage the underlying hardware or software; Cloud management platform: a system designed to manage and monitor multi-cloud environments in a consistent manner. The platform allows users to monitor and manage resources from multiple cloud service providers in a single console. It usually provides automation, security, cost management, compliance, and optimization capabilities to help enterprises use cloud services effectively. Cloud platform deployment tools: for configuration management, application deployment, task automation, and service orchestration; Playbook: A Playbook is a configuration, deployment, and orchestration script for cloud platform deployment tools. It is written in YAML format (a highly readable format for expressing data serialization) and defines one or more "plays". Each Play defines a policy, including a set of roles, which is applied to a group of hosts. Role: A role is a predefined collection of tasks in a Playbook that is used to implement configurations that can be reused in multiple Playbooks. For example, a "webserver" role may contain all the tasks and handlers required to set up a web server. Task: A task is a single action performed in a Playbook, usually consisting of a module and the module's parameters; Jinja2 template: Jinja2 is a modern and design-friendly template engine that is widely used in Web development. In cloud platform deployment tools, Jinja2 templates are mainly used for configuration file management and dynamic content generation. IP address: Internet Protocol Address, Internet Protocol address; MySQL: A relational database management system.

[0028] With the rapid development of cloud computing technology, more and more enterprises and organizations have begun to deploy their business applications on cloud platforms. Cloud platforms provide highly flexible computing resources, allowing users to quickly expand or reduce resources according to demand; applications on cloud platforms are usually composed of multiple nodes and multiple components, which need to collaborate with each other to provide complete services; therefore, how to efficiently deploy multiple nodes and multiple components in succession has become an important research direction.

[0029] Cloud platform deployment tools can define deployment processes by writing Playbooks to achieve automated deployment. For large-scale cloud platform applications, the deployment process often requires high reliability and high availability. However, when errors occur during the deployment process, these deployment tools require human intervention to check and correct errors. This human intervention not only reduces deployment efficiency, but may also introduce new errors, thereby reducing the stability and reliability of cloud platform applications due to deployment tools.

[0030] Therefore, in order to improve the stability and reliability of cloud platform applications, an embodiment of the present application provides a processing method for deploying a cloud platform.

[0031] Reference Figure 1 , shows a flowchart of a method for deploying a cloud platform provided in an embodiment of the present application, the method may include the following steps: S101: Obtain a target deployment script of the current cloud platform, wherein the target deployment script includes a target deployment component corresponding to any node and a deployment order of multiple target deployment components.

[0032] Specifically, when deploying a cloud platform, in response to a deployment configuration operation of a user, a deployment configuration strategy of the current cloud platform may be determined, and then a target deployment script of the current cloud platform may be compiled according to the deployment configuration strategy.

[0033] When the cloud platform is deployed through the cloud platform deployment tool, in response to the user's deployment configuration operation, the nodes that need to be deployed included in the deployment configuration strategy corresponding to the cloud platform are determined, and the nodes are determined. The target deployment components that need to be deployed on any server node, as well as the dependencies and deployment order between multiple target deployment components are determined.

[0034] Components include applications deployed on server nodes or software modules that implement any function. For example, components include but are not limited to computing components, computing task creation components, computing data storage components, and network IP allocation components.

[0035] For example, according to the user's deployment configuration operation, it is determined to deploy a computing task creation component on node 1, a computing component on node 2, and a computing data storage component on node 3. There is a dependency relationship between the computing task creation component, the computing component, and the computing data storage component, and they have a sequential execution order in the actual application process. The deployment order of these three components is based on the sequential execution order.

[0036] In the cloud platform deployment tool, after the deployment configuration strategy is determined, a Playbook will be automatically written as the target deployment script. In the Playbook, one or more "plays" are written and defined in YAML format. Each Play defines a strategy, which includes a role set. In this method, a deployment component is a role.

[0037] Take the deployment of a cloud management platform based on the cloud platform deployment tool, which includes many components such as database server, message queue server, file storage server, cloud management platform server, cache server, etc. as an example. First, create a Playbook according to the user's deployment requirements. Each component is a role, and determine the node IP corresponding to each component.

[0038] For example, the structure of a Playbook is as follows: #playbok.yml --- name:Deploy Cloud Management Platform hosts: all become: yes vars: #Application environment variables, such as database password, application server port, etc. roles: -role:database vars: #Database role variables tags: database -role:message_queue vars: #Variables of message queue roles tags: message_ queue -role:file_storage vars: #File storage role variables tags:file_storage -role:cloud_management_platform vars: #Variables of the cloud management platform tags:cloud_management_platform -role:security vars: #Security role variables tags:security Among them, hosts:all means that the Playbook will be applied to all hosts defined in the inventory file, become:yes means that the task will be run with elevated permissions (usually root); each role has its own variables and tags, which allow only specific parts of the Playbook to be run, or certain roles to be skipped.

[0039] For example, the roles directory structure is as follows: roles / database -tasks -main.yml -handlers -main.yml -templates -files -vars -main.yml message_queue … file_storage … cloud_management_platform … Security … networking … That is, each role under the roles directory will contain tasks, handlers, templates, files, vars and other directories. Among them, the main.yml file under the tasks directory contains the Playbook code for executing the role's tasks; the main.yml file under the handlers directory is used to define handlers that can be triggered by notifications; the templates directory contains Jinja2 templates, which are mainly used for configuration file management and dynamic content generation; the files directory contains files that need to be copied to the target host; and the main.yml file under the vars directory contains the role's variable definition.

[0040] When creating a Playbook, you need to define the corresponding tasks for each role. Taking the definition of database tasks in the cloud platform deployment tool as an example, the following steps are involved: 1) Install database software: Use the package management module (such as apt or yum) of the cloud platform deployment tool to install the database software; 2) Configure the database: Use the template module to configure the database configuration file; for example, you can create a MySQL configuration file template my.cnf.j2 and use the template module of the cloud platform deployment tool to copy it to the correct location; 3) Start and enable the database service: Use the service module to ensure that the database service is started and automatically enabled when the system starts; 4) Set up database security: For MySQL, you can use the mysql_user and mysql_db modules to set up database users and databases, which usually include deleting anonymous users, not allowing root users to log in remotely, and other security measures; 5) Create database and user: Create the required database and user according to application requirements; 6) Handlers: Define handlers to handle tasks such as service restart.

[0041] S102: Execute a deployment process according to the target deployment script, and detect in real time whether the deployment state of any target deployment component is a deployment error state.

[0042] After the target deployment script, such as the Playbook of the cloud platform deployment tool, is written, the deployment process is automatically started according to the target deployment script. For example, during the deployment process according to the Playbook, one or more target deployment components corresponding to the node are deployed on any node in order from top to bottom.

[0043] In order to detect in real time whether any component in the deployment process has a deployment error, this method uses real-time detection to detect whether the deployment state of any target deployment component is a deployment error state.

[0044] In a feasible implementation manner, the deployment error state includes an undeployed state, a deployment interrupted state, and a deployment error state. When the deployment state of any target deployment component is detected in real time as a deployment error state, it specifically includes: Real-time detection is performed to determine whether any target deployment component starts to be installed within a first preset time period; if any target deployment component does not start to be installed within the first preset time period, the deployment state of the target deployment component is determined to be an undeployed state in a deployment error state.

[0045] In the actual implementation process, if when deploying any target deployment component corresponding to the node on any node, it is detected that the target deployment component has not started to be installed after the first preset time, then the target deployment component is characterized as being in an undeployed state. The length of the first preset time can be customized according to the needs of the actual application, and this embodiment does not impose any restrictions.

[0046] Real-time detection is performed to determine whether any target deployment component is interrupted during installation; if any target deployment component is interrupted during installation, the deployment state of the target deployment component is determined to be a deployment interruption state in a deployment error state.

[0047] After any target deployment component is installed, verification is performed; when any installed target deployment component is inconsistent with the corresponding target deployment component configured in the target deployment script, the deployment state of the target deployment component is determined to be a deployment error state in the deployment error state.

[0048] S103: When it is detected that the deployment state of any target deployment component is a deployment error state, the deployment process executed according to the target deployment script is suspended, and an error repair strategy corresponding to the target deployment component is determined and executed.

[0049] Specifically, when it is detected that the deployment state of any target deployment component is a deployment error state, the deployment process according to the target deployment script such as Playbook is paused at the location of the target deployment component, and then the target deployment component is repaired.

[0050] First, according to the error cause range corresponding to the deployment error state of the target deployment component, the error cause corresponding to the target deployment component is determined; according to the error cause corresponding to the target deployment component, the error repair strategy corresponding to the target deployment component is determined.

[0051] For example, if the deployment error state of any target deployment component is the undeployed state, the corresponding error cause may include an error in the component installation environment configuration; if the deployment error state of any target deployment component is the deployment interrupted state, the corresponding error cause includes an inability to receive the installation package of the target deployment component or an installation package parsing error; if the deployment error state of any target deployment component is the deployment error state, the corresponding error cause includes configuration parameters not taking effect and port number conflicts.

[0052] In the actual implementation process, the mapping relationship between the deployment error status and the error cause of different target deployment components can be preset, and the error repair strategies corresponding to the error causes of different target deployment components can be predefined, which is not limited in this embodiment.

[0053] In a feasible manner, a conditional error repair strategy for any target deployment component may be written in the Playbook of the cloud platform deployment tool, or a repair rule library may be created to store one or more error repair strategies corresponding to any target deployment component.

[0054] Specifically, in response to the first repair operation, one or more error repair strategies corresponding to any target deployment component are added to the target deployment script, and the multiple error repair strategies include repair strategies corresponding to different error causes.

[0055] In response to the second repair operation, a repair rule base is created, wherein the repair rule base includes one or more error repair strategies corresponding to any target deployment component, and the multiple error repair strategies include repair strategies corresponding to different error causes.

[0056] The repair strategies corresponding to different error causes can be customized according to the needs of actual applications. For example, the error repair strategies include but are not limited to reinstalling components, modifying configuration parameters, and restarting components. For example, when the error cause of a deployment error state caused by a target deployment component is a port number conflict, the error repair strategy of modifying the configuration parameters can be executed to modify the conflicting port number; or when the cause of a deployment interruption state caused by a target deployment component is an installation package parsing error, the error repair strategy is executed to obtain the installation package of the target deployment component for reinstallation.

[0057] When one or more error repair policies corresponding to any target deployment component are added to both the target deployment script and the repair rule base, the error repair policies written in the target deployment script, such as the Playbook of the cloud platform deployment tool, have a higher priority than the error repair policies in the repair rule base.

[0058] After determining the error cause corresponding to the target deployment component based on the error cause range corresponding to the deployment error state of the target deployment component, first search the target deployment script for an error repair strategy corresponding to the error cause of the target deployment component based on the error cause corresponding to the target deployment component.

[0059] When the target deployment script contains an error repair strategy corresponding to the error cause of the target deployment component, the error repair strategy is executed.

[0060] When the target deployment script does not contain an error repair policy corresponding to the error cause of the target deployment component, the repair rule base is searched to see whether there is an error repair policy corresponding to the error cause of the target deployment component. If the repair rule base contains an error repair policy corresponding to the error cause of the target deployment component, the error repair policy is executed. When the repair rule base does not contain an error repair policy corresponding to the error cause of the target deployment component, a pop-up window may be provided to prompt the user that an error has occurred in the deployment of the target deployment component and to provide the error cause, so that the user can respond in time to repair the error of the target deployment component.

[0061] S104: After the error repair strategy corresponding to the target deployment component is executed, restart the deployment process executed according to the target deployment script.

[0062] When the error repair strategy corresponding to the target deployment component is completed, the target deployment component is restarted from the location where the error occurs, and the subsequent deployment process continues to be executed according to the target deployment script.

[0063] In a feasible implementation, after the deployment process executed according to the target deployment script is completed, each target deployment component is tested in turn according to the deployment order of multiple target deployment components; when the deployment status of any target deployment component is a deployment error status, the error repair strategy corresponding to the target deployment component is determined and executed to repair the target deployment component.

[0064] Therefore, a comprehensive check can be performed on all target deployment components after the deployment is completed to ensure that all target deployment components can work normally and provide normal cloud platform services.

[0065] This method performs error detection on any target deployment component during the process of automated deployment on the cloud platform. When any target deployment component is in a deployment error state, the method can automatically repair the error of the erroneously deployed target deployment component. Compared with manual error checking and error correction for component deployment, the method can greatly improve the deployment efficiency and reliability of multi-node and multi-component applications on the cloud platform. Through the automated repair mechanism, the need for human intervention is reduced, and the error rate in the deployment process is reduced, thereby improving the stability and reliability of cloud platform applications.

[0066] Reference Figure 2 , shows a functional module diagram of a processing device for deploying a cloud platform provided in an embodiment of the present application, the device comprising: Install a deployment module, which is used to start deploying a target deployment component according to a target deployment script, such as a target deployment script of a cloud platform deployment tool; The error detection and repair module is used to detect the deployment status of any deployment component during the deployment process. When it is detected that the deployment status of any target deployment component is a deployment error state, the installation deployment module is instructed to suspend the deployment process and execute the corresponding error repair strategy of the target deployment component. After the repair is completed, the installation deployment module is notified to restart the deployment process from the error point.

[0067] When all target deployment components are deployed, the error detection and repair module is used to check all target deployment components to ensure that all target deployment components can work properly and the application can provide the expected services, and finally obtain the cloud platform instance that needs to be deployed.

[0068] Reference Figure 3 , shows a schematic diagram of the structure of the error detection and repair module provided in an embodiment of the present application. In a feasible implementation, the error detection and repair module includes a detection module, a repair module, and a repair rule base.

[0069] The detection module is used to monitor the deployment status of any target deployment component during the entire deployment process. When it is detected that the deployment status of any target deployment component is a deployment error state, the error cause of the target deployment component is analyzed and the error cause is sent to the repair module. The repair module first checks whether there is an error repair strategy for the error cause of the target deployment component in the target deployment script such as Playbook according to the error cause. If not, the error repair strategy for the error cause of the target deployment component predefined in the repair rule library is used to repair the error cause of the target deployment component.

[0070] Reference Figure 4 , shows a functional module diagram of a processing system for deploying a cloud platform provided in an embodiment of the present application, the system comprising: An acquisition module 100 is used to acquire a target deployment script of the current cloud platform, wherein the target deployment script includes a target deployment component corresponding to any node and a deployment order of multiple target deployment components; The deployment execution and detection module 200 is used to execute the deployment process according to the target deployment script and detect in real time whether the deployment state of any target deployment component is a deployment error state; The error repair module 300 is used to suspend the deployment process executed according to the target deployment script when it is detected that the deployment state of any target deployment component is a deployment error state, and determine and execute the error repair strategy corresponding to the target deployment component; The deployment restart module 400 is used to restart the deployment process executed according to the target deployment script after the error repair strategy corresponding to the target deployment component is executed.

[0071] Optionally, the system further comprises: A deployment configuration module is used to determine the deployment configuration strategy of the current cloud platform in response to a deployment configuration operation, wherein the deployment configuration strategy includes the target deployment component corresponding to any node, the dependencies between the multiple target deployment components, and the deployment order of the multiple target deployment components; and compile the target deployment script of the current cloud platform according to the deployment configuration strategy.

[0072] Optionally, the deployment execution and detection module includes a first detection unit, configured to: Real-time detection of whether any target deployment component starts to be installed within a first preset time period; If any target deployment component does not start to be installed within the first preset time period, the deployment state of the target deployment component is determined to be a non-deployed state in the deployment error state.

[0073] Optionally, the deployment execution and detection module includes a second detection unit, configured to: Real-time detection of any interruption in the installation process of any target deployment component; If any target deployment component is interrupted during the installation process, the deployment state of the target deployment component is determined to be a deployment interruption state in the deployment error state.

[0074] Optionally, the deployment execution and detection module includes a third detection unit, configured to: Verify after any target deployment component is installed; When any installed target deployment component is inconsistent with the corresponding target deployment component configured in the target deployment script, the deployment state of the target deployment component is determined to be a deployment error state in the deployment error state.

[0075] Optionally, the system further comprises: The first preset unit is used to add one or more error repair strategies corresponding to any target deployment component in the target deployment script in response to a first repair operation, wherein the multiple error repair strategies include repair strategies corresponding to different error causes.

[0076] Optionally, the system further comprises: The second preset unit is used to create a repair rule library in response to the second repair operation, wherein the repair rule library includes one or more error repair strategies corresponding to any target deployment component, and the multiple error repair strategies include repair strategies corresponding to different error causes.

[0077] Optionally, the error repair module includes: A pausing unit, configured to suspend the deployment process executed according to the target deployment script when detecting that the deployment state of any target deployment component is a deployment error state; A determination unit, configured to determine an error cause corresponding to the target deployment component according to an error cause range corresponding to the deployment error state of the target deployment component; The repair unit is used to determine an error repair strategy corresponding to the target deployment component according to the error cause corresponding to the target deployment component.

[0078] Optionally, the repair unit includes a first repair subunit, configured to: According to the error cause corresponding to the target deployment component, searching in the target deployment script whether there is an error repair strategy corresponding to the error cause of the target deployment component; When the target deployment script contains an error repair strategy corresponding to the error cause of the target deployment component, the error repair strategy is executed.

[0079] Optionally, the repair unit includes a second repair subunit, configured to: When the target deployment script does not contain an error repair strategy corresponding to the error cause of the target deployment component, searching the repair rule library for an error repair strategy corresponding to the error cause of the target deployment component; When the error repair strategy corresponding to the error cause of the target deployment component exists in the repair rule library, the error repair strategy is executed.

[0080] Optionally, the second repair subunit is further used to: When the error repair strategy corresponding to the error cause of the target deployment component does not exist in the repair rule library, a pop-up window prompts the deployment error state and error cause of the target deployment component.

[0081] Optionally, the deployment restart module includes a check and repair unit, which is used to: After the deployment process executed according to the target deployment script is completed, each target deployment component is tested in turn according to the deployment order of the multiple target deployment components; When the deployment state of any target deployment component is a deployment error state, an error repair strategy corresponding to the target deployment component is determined and executed to repair the target deployment component.

[0082] Reference Figure 5 , shows a schematic diagram of a computer device provided in an embodiment of the present application, including: at least one processor 501, and a memory 502, wherein the memory 502 stores a computer program that can be run on the processor 501, wherein the processor 501 executes the processing method for deploying the cloud platform described in the embodiment when executing the computer program.

[0083] Reference Figure 6 , showing a schematic diagram of a non-volatile readable storage medium provided in an embodiment of the present application, wherein the non-volatile readable storage medium 600 stores a computer program 601, wherein the computer program 601, when executed by a processor, executes the processing method for deploying a cloud platform described in the embodiment.

[0084] Reference Figure 7 , showing a computer program product provided in an embodiment of the present application, the computer program product 700 includes a computer program / instruction 701, and when the computer program / instruction 701 is executed by a processor, the processing method for deploying a cloud platform described in the embodiment is implemented.

[0085] The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referenced to each other.

[0086] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, devices, or computer program products. Therefore, the present application may be provided in the form of a complete hardware embodiment, a complete software embodiment, or a combination of software and hardware embodiments. Moreover, the present application may be provided in the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0087] The embodiments of the present application are described with reference to the flowcharts and / or block diagrams of the methods, terminal devices (systems) and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor or other programmable data processing terminal device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing terminal device generate instructions for implementing the processes in the flowchart. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0088] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing terminal device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0089] These computer program instructions can also be loaded onto a computer or other programmable data processing terminal device so that a series of operating steps are executed on the computer or other programmable terminal device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable terminal device to implement the process. Figure 1 A process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0090] Although the preferred embodiments of the present application have been described, those skilled in the art may make additional changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the embodiments of the present application.

[0091] Finally, it should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprises" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or terminal device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or terminal device. In the absence of further restrictions, the elements defined by the sentence "including one..." do not exclude the existence of other identical elements in the process, method, article or terminal device including the elements.

[0092] Specific examples are used herein to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea. At the same time, for those skilled in the art, according to the idea of ​​the present application, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.

Claims

1. A method for deploying a cloud platform, characterized in that: The method comprises: Obtain a target deployment script of the current cloud platform, wherein the target deployment script includes a target deployment component corresponding to any node and a deployment order of multiple target deployment components; Execute the deployment process according to the target deployment script, and detect in real time whether the deployment status of any target deployment component is a deployment error status; When it is detected that the deployment state of any target deployment component is a deployment error state, pausing the deployment process executed according to the target deployment script, and determining and executing the error repair strategy corresponding to the target deployment component; When the error repair strategy corresponding to the target deployment component is executed, the deployment process executed according to the target deployment script is restarted.

2. The method according to claim 1, characterized in that Before obtaining the target deployment script of the current cloud platform, the method further includes: In response to the deployment configuration operation, determining the deployment configuration strategy of the current cloud platform, wherein the deployment configuration strategy includes a target deployment component corresponding to any node, dependencies between the multiple target deployment components, and a deployment order of the multiple target deployment components; Compile the target deployment script of the current cloud platform according to the deployment configuration strategy.

3. The method according to claim 1, characterized in that: Real-time detection of whether the deployment status of any target deployment component is a deployment error status, including: Real-time detection of whether any target deployment component starts to be installed within a first preset time period; If any target deployment component does not start to be installed within the first preset time period, the deployment state of the target deployment component is determined to be a non-deployed state in the deployment error state.

4. The method according to claim 1, characterized in that: Real-time detection of whether the deployment status of any target deployment component is a deployment error status, including: Real-time detection of any interruption in the installation process of any target deployment component; If any target deployment component is interrupted during the installation process, the deployment state of the target deployment component is determined to be a deployment interruption state in the deployment error state.

5. The method according to claim 1, characterized in that Real-time detection of whether the deployment status of any target deployment component is a deployment error status, including: Verify after any target deployment component is installed; When any installed target deployment component is inconsistent with the corresponding target deployment component configured in the target deployment script, the deployment state of the target deployment component is determined to be a deployment error state in the deployment error state.

6. The method according to claim 1, characterized in that The method further comprises: In response to the first repair operation, one or more error repair strategies corresponding to any target deployment component are added to the target deployment script, wherein the multiple error repair strategies include repair strategies corresponding to different error causes.

7. The method according to claim 6, characterized in that The method further comprises: In response to the second repair operation, a repair rule base is created, wherein the repair rule base includes one or more error repair strategies corresponding to any target deployment component, and the multiple error repair strategies include repair strategies corresponding to different error causes.

8. The method according to claim 7, characterized in that When it is detected that the deployment state of any target deployment component is a deployment error state, the deployment process executed according to the target deployment script is suspended, and an error repair strategy corresponding to the target deployment component is determined and executed, including: When it is detected that the deployment state of any target deployment component is a deployment error state, pausing the deployment process executed according to the target deployment script; Determine the error cause corresponding to the target deployment component according to the error cause range corresponding to the deployment error state of the target deployment component; According to the error cause corresponding to the target deployment component, an error repair strategy corresponding to the target deployment component is determined.

9. The method according to claim 8, characterized in that According to the error cause corresponding to the target deployment component, an error repair strategy corresponding to the target deployment component is determined, including: According to the error cause corresponding to the target deployment component, searching in the target deployment script whether there is an error repair strategy corresponding to the error cause of the target deployment component; When the target deployment script contains an error repair strategy corresponding to the error cause of the target deployment component, the error repair strategy is executed.

10. The method according to claim 9, characterized in that According to the error cause corresponding to the target deployment component, after searching in the target deployment script whether there is an error repair strategy corresponding to the error cause of the target deployment component, the method further includes: When the target deployment script does not contain an error repair strategy corresponding to the error cause of the target deployment component, searching the repair rule library for an error repair strategy corresponding to the error cause of the target deployment component; When the error repair strategy corresponding to the error cause of the target deployment component exists in the repair rule library, the error repair strategy is executed.

11. The method according to claim 10, characterized in that After searching the repair rule base for an error repair strategy corresponding to the error cause of the target deployment component, the method further includes: When the error repair strategy corresponding to the error cause of the target deployment component does not exist in the repair rule library, a pop-up window prompts the deployment error state and error cause of the target deployment component.

12. The method according to claim 1, characterized in that When the error repair strategy corresponding to the target deployment component is executed, restarting the deployment process executed according to the target deployment script includes: After the deployment process executed according to the target deployment script is completed, each target deployment component is tested in turn according to the deployment order of the multiple target deployment components; When the deployment state of any target deployment component is a deployment error state, an error repair strategy corresponding to the target deployment component is determined and executed to repair the target deployment component.

13. A computer device, characterized in that: include: At least one processor, and a memory, wherein the memory stores a computer program that can be run on the processor, wherein when the processor executes the computer program, the processing method for deploying a cloud platform according to any one of claims 1-12 is executed.

14. A non-volatile readable storage medium, characterized in that: The non-volatile readable storage medium stores a computer program, wherein the computer program, when executed by a processor, executes the processing method for deploying a cloud platform according to any one of claims 1 to 12.

15. A computer program product comprising a computer program / instructions, characterized in that When the computer program / instruction is executed by a processor, the processing method for deploying a cloud platform as described in any one of claims 1 to 12 is implemented.

Images