Installation method, device, equipment, medium and program product of cloud computing product

Abstract

The disclosure provides an installation method of a cloud computing product, which can be applied to the technical field of big data. The installation method of the cloud computing product comprises the following steps: generating an installation node corresponding to the cloud computing product in a preprocessing queue; storing the installation node in the preprocessing queue into an implementation queue; reading a system node of the installation node and an environment node of the installation node of the installation node in the implementation queue in parallel; and executing system implementation parameters corresponding to the system node and environment implementation parameters corresponding to the environment node, so as to complete the installation of the cloud computing product. The disclosure also provides an installation device, equipment, storage medium and program product of the cloud computing product.

Description

Technical Field

[0001] This disclosure relates to the field of computer technology, and more specifically to a method, apparatus, device, medium, and program product for installing a cloud computing product. Background Technology

[0002] With the rapid development of cloud computing, PaaS (Platform as a Service) has become an increasingly popular service model offered by cloud service providers. PaaS environment installation, as a crucial part of cloud platform PaaS resource provision, enables the installation of user-specified operating systems and middleware on the physical or virtual machines provided by the platform. Summary of the Invention

[0003] In view of at least one of the technical problems existing in the PaaS environment installation process, this disclosure provides a method, apparatus, device, media and program product for installing cloud computing products to achieve parallel installation and improve installation efficiency.

[0004] According to the first aspect of this disclosure, a method for installing a cloud computing product is provided, comprising: generating an installer node corresponding to the cloud computing product in a preprocessing queue; storing the installer node in the preprocessing queue into an implementation queue; reading the system component node and the environment component node of the installer node in the implementation queue in parallel; and executing the system component implementation parameters corresponding to the system component node and the environment component implementation parameters corresponding to the environment component node to complete the installation of the cloud computing product.

[0005] According to embodiments of this disclosure, before generating the installation component node corresponding to the cloud computing product in the preprocessing queue, the method further includes: parsing the user resource application form corresponding to the cloud computing product to determine the system component and the environment component; when the system component matches the installation component, determining the system component implementation parameters corresponding to the system component and the environment component implementation parameters corresponding to the environment component.

[0006] According to embodiments of this disclosure, the above-mentioned generation of the installation component node corresponding to the cloud computing product in the preprocessing queue includes: storing the system component cache identifier of the system component implementation parameters in the preprocessing queue to generate the system component node of the installation component node; storing the environment component cache identifier of the environment component implementation parameters in the preprocessing queue to generate the environment component node of the installation component node.

[0007] According to embodiments of this disclosure, before storing the environmental component cache identifier of the environmental component implementation parameters in the preprocessing queue and generating the environmental component node of the installer node, the method further includes: generating a verification node in the preprocessing queue based on the system component node; wherein the system component node and the environmental component node are arranged sequentially in the preprocessing queue with the verification node as the demarcation node.

[0008] According to embodiments of this disclosure, before storing the environment component cache identifier of the environment component implementation parameters in the preprocessing queue and generating the environment component node of the installer node, the method further includes: storing the environment component implementation parameters in the cache area according to the environment component type and generating the environment component cache identifier.

[0009] According to an embodiment of this disclosure, storing the installer node in the preprocessing queue into the implementation queue includes: reading the queue identifier of the implementation queue in the main implementation queue; when the implementation queue corresponding to the queue identifier and the preprocessing queue meet the node matching condition, storing the verification node in the preprocessing queue, as well as the system component node and environment component node of the installer node, into the implementation queue.

[0010] According to embodiments of this disclosure, the parallel reading of the system component node and environment component node of the installation component node in the implementation queue includes: reading the head element of the implementation queue according to the queue status of the implementation queue; when the head element of the read implementation queue is a system component node or an environment component node, retrieving the corresponding system component implementation parameters or environment component implementation parameters from the cache; when the head element of the read implementation queue is a verification node, repeatedly reading another implementation queue according to the reading completion degree of the system component node corresponding to the verification node.

[0011] According to embodiments of this disclosure, the execution of system component implementation parameters corresponding to system component nodes and environment component implementation parameters corresponding to environment component nodes includes: performing installation implementation in parallel based on system component implementation parameters and environment component implementation parameters; and completing the installation of the cloud computing product based on the implementation results of the installation implementation.

[0012] A second aspect of this disclosure provides an installation apparatus for a cloud computing product, comprising a node generation module, a node storage module, a node reading module, and a parameter execution module. The node generation module generates installation component nodes corresponding to the cloud computing product in a preprocessing queue; the node storage module stores the installation component nodes from the preprocessing queue into an implementation queue; the node reading module reads in parallel the system component nodes and environment component nodes of the installation component nodes in the implementation queue; and the parameter execution module executes in parallel the system component implementation parameters corresponding to the system component nodes and the environment component implementation parameters corresponding to the environment component nodes, thereby completing the installation of the cloud computing product.

[0013] A third aspect of this disclosure provides an electronic device comprising: one or more processors; and a memory for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors cause the one or more processors to perform the installation method of the cloud computing product described above.

[0014] A fourth aspect of this disclosure also provides a computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, cause the processor to perform the installation method of the aforementioned cloud computing product.

[0015] The fifth aspect of this disclosure also provides a computer program product, including a computer program that, when executed by a processor, implements the installation method of the aforementioned cloud computing product. Attached Figure Description

[0016] The foregoing contents, as well as other objects, features, and advantages of this disclosure, will become clearer from the following description of embodiments with reference to the accompanying drawings, in which:

[0017] Figure 1 The illustration schematically depicts an installation method, apparatus, device, medium, and application scenario diagram of a cloud computing product according to embodiments of the present disclosure;

[0018] Figure 2 A flowchart illustrating an installation method for a cloud computing product according to an embodiment of the present disclosure is shown schematically.

[0019] Figure 3 The diagram illustrates a process flow chart regarding the preprocessing queue in an installation method for a cloud computing product according to an embodiment of the present disclosure;

[0020] Figure 4 This schematically illustrates a flowchart of the process of storing installation component nodes in an implementation queue in an installation method for a cloud computing product according to an embodiment of the present disclosure;

[0021] Figure 5 The diagram illustrates a process flow chart of performing installation based on read installation component nodes in an installation method for a cloud computing product according to an embodiment of the present disclosure.

[0022] Figure 6 This schematically illustrates a structural block diagram of an installation apparatus for a cloud computing product according to embodiments of the present disclosure; and

[0023] Figure 7 A block diagram schematically illustrates an electronic device suitable for implementing an installation method for a cloud computing product according to an embodiment of the present disclosure. Detailed Implementation

[0024] The embodiments of the present disclosure will now be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the disclosure. In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the embodiments of the present disclosure for ease of explanation. However, it will be apparent that one or more embodiments may be practiced without these specific details. Furthermore, descriptions of well-known structures and techniques are omitted in the following description to avoid unnecessarily obscuring the concepts of the present disclosure.

[0025] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit this disclosure. The terms “comprising,” “including,” etc., as used herein indicate the presence of the stated features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.

[0026] All terms used herein (including technical and scientific terms) have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein are to be interpreted in a manner consistent with the context of this specification, and not in an idealized or overly rigid way.

[0027] When using expressions such as "at least one of A, B, and C", they should generally be interpreted in accordance with the meaning that is commonly understood by a person skilled in the art (e.g., "a system having at least one of A, B, and C" should include, but is not limited to, a system having A alone, a system having B alone, a system having C alone, a system having A and B, a system having A and C, a system having B and C, and / or a system having A, B, and C, etc.).

[0028] Existing cloud computing product installation methods are implemented sequentially, unit by unit. Specifically, the current installation process treats the OS system and middleware installation as a single, sequential process. Therefore, it's impossible to control the total number of installations currently in progress from the perspective of the installation server. Furthermore, when providing cluster-type cloud computing products, the OS system and middleware within the cluster must be installed sequentially, limiting the concurrency of the installation process. In other words, traditional sequential installation methods cannot achieve rate limiting and parallel processing at the underlying implementation level. During cluster installation, each machine in the cluster waits in a queue for the machine ahead to complete the installation process, and the performance of the installation server cannot be fully utilized. This results in significant pressure on the resource implementation layer during batch installations because the installation server cannot implement rate limiting.

[0029] It is evident that existing cloud computing product installation methods can only install the OS system and middleware for the same business service requirements as a whole. When the number of installations is huge, this process of sequentially installing the OS system and middleware according to each business service requirement will greatly limit installation efficiency, hinder the performance of the installation server, and waste installation resources.

[0030] In view of at least one of the technical problems existing in the PaaS environment installation process, this disclosure provides a method, apparatus, device, media and program product for installing cloud computing products to achieve parallel installation and improve installation efficiency.

[0031] It should be noted that the installation method and apparatus for the cloud computing products disclosed herein can be used in the fields of big data technology and artificial intelligence technology, as well as in the financial field and any other field outside the financial field. The application fields of the installation method and apparatus for the cloud computing products disclosed herein are not limited.

[0032] In the technical solution disclosed herein, the collection, storage, use, processing, transmission, provision, disclosure, and application of data, including user personal information, all comply with relevant laws and regulations, necessary confidentiality measures have been taken, and they do not violate public order and good morals. Furthermore, user authorization or consent has been obtained before acquiring or collecting user personal information.

[0033] The embodiments of this disclosure provide a method for installing a cloud computing product, including: generating an installer node corresponding to the cloud computing product in a preprocessing queue; storing the installer node in the preprocessing queue into an implementation queue; reading the system component node and the environment component node of the installer node in the implementation queue in parallel; and executing the system component implementation parameters corresponding to the system component node and the environment component implementation parameters corresponding to the environment component node in parallel to complete the installation of the cloud computing product.

[0034] Figure 1 The illustration schematically depicts an installation method, apparatus, device, medium, and application scenario diagram of a cloud computing product according to embodiments of the present disclosure.

[0035] like Figure 1 As shown, application scenario 100 according to this embodiment may include terminal devices 101, 102, and 103, network 104, and server 105. Network 104 is used as a medium to provide a communication link between terminal devices 101, 102, and 103 and server 105. Network 104 may include various connection types, such as wired or wireless communication links or fiber optic cables, etc.

[0036] Users can use terminal devices 101, 102, and 103 to interact with server 105 via network 104 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 101, 102, and 103, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social media platform software, etc. (for example only).

[0037] Terminal devices 101, 102, and 103 can be various electronic devices with displays and web browsing capabilities, including but not limited to smartphones, tablets, laptops, and desktop computers.

[0038] Server 105 can be a server that provides various services, such as a backend management server that supports websites browsed by users using terminal devices 101, 102, and 103 (for example only). The backend management server can analyze and process data such as received user requests, and feed back the processing results (such as web pages, information, or data obtained or generated according to user requests) to the terminal devices.

[0039] It should be noted that the installation method for the cloud computing product provided in this disclosure embodiment can generally be executed by server 105. Correspondingly, the installation device for the cloud computing product provided in this disclosure embodiment can generally be located in server 105. The installation method for the cloud computing product provided in this disclosure embodiment can also be executed by a server or server cluster that is different from server 105 and capable of communicating with terminal devices 101, 102, 103 and / or server 105. Correspondingly, the installation device for the cloud computing product provided in this disclosure embodiment can also be located in a server or server cluster that is different from server 105 and capable of communicating with terminal devices 101, 102, 103 and / or server 105.

[0040] It should be understood that Figure 1 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0041] The following will be based on Figure 1 The described scene, through Figures 2-7 The installation method of the cloud computing product according to the disclosed embodiments is described in detail.

[0042] Figure 2 A flowchart illustrating an installation method for a cloud computing product according to an embodiment of the present disclosure is shown.

[0043] like Figure 2 As shown, the installation method of the cloud computing product in this embodiment includes operations S201 to S204.

[0044] In operation S201, installer nodes corresponding to cloud computing products are generated in the preprocessing queue;

[0045] In operation S202, the installer nodes in the preprocessing queue are stored in the implementation queue;

[0046] In operation S203, the system component node and environment component node of the installation component node in the implementation queue are read in parallel.

[0047] In operation S204, the system component implementation parameters corresponding to the system component node and the environment component implementation parameters corresponding to the environment component node are executed to complete the installation of the cloud computing product.

[0048] In the embodiments of this disclosure, the cloud computing product can be a virtual machine or physical machine containing system components and environment components, which provides users with business services that meet their needs in a cloud computing manner. Specifically, the cloud computing product in the embodiments of this disclosure can be implemented based on PaaS, and can execute the installation process of the user-specified OS system and middleware programs on a specified physical machine or virtual machine to achieve the installation of the cloud computing product.

[0049] A preprocessing queue can be a linear list that generates installation component nodes corresponding to cloud computing products and stores these nodes. The nodes are then arranged sequentially as queue data. Each preprocessing queue can read the header element and write the tail element. An element occupying a specific position in this linear list can be understood as a node, and each element has a unique node identifier, such as a node ID. Each element can define a specific implementation process. Installation component nodes are the implementation process nodes corresponding to the element data of the aforementioned system components and environment components within this preprocessing queue.

[0050] The implementation queue is a doubly linked queue used to store specific implementation process nodes to be executed. It can also be represented as a linear list and used to read and write node element data. Installer nodes in the preprocessing queue can be executed sequentially, and all retrieved installer nodes are stored in the implementation queue. This allows for improved node processing speed through the implementation queue.

[0051] Installer nodes can include system node nodes and environment node nodes. System nodes can be computer programs, such as operating systems, used to manage and control computer hardware and software resources; system node nodes are the implementation process nodes for the system node's implementation parameters. Environment nodes can be system software or service programs, such as middleware corresponding to an operating system, used to implement the installation or usage environment of that operating system; environment node nodes are the implementation process nodes for the environment node's implementation parameters. The implementation queue can perform parallel reading operations on its installer nodes using different reading tools. That is, multiple reading tools can perform one-to-one parallel reading of each installer node at the same time. This can achieve node reading speeds several times, or even tens or hundreds of times, allowing for parallel reading of system node nodes and environment node nodes in the implementation queue. Furthermore, when there are multiple parallel implementation queues, the reading of corresponding nodes in each queue can be performed separately. Based on batch reading of multiple nodes in the implementation queue, batch parallel reading of multiple implementation queues can be achieved, further accelerating the parallel reading speed of node element data.

[0052] By reading the system component nodes, the corresponding system component implementation parameters can be retrieved; similarly, by reading the environment component nodes, the corresponding environment component implementation parameters can be retrieved. System component implementation parameters consist of the installation data, parameters, files, and scripts required for the system component installation process; environment component implementation parameters consist of the installation data, parameters, files, and scripts required for the environment component installation process. By executing the installation operation based on the system component implementation parameters, the system component can be installed; similarly, by executing the installation operation based on the environment component implementation parameters, the environment component can be installed. Therefore, when the installation process of the system component and its corresponding environment component is complete, it signifies that the installation of the corresponding cloud computing product is complete.

[0053] As can be seen, the above-described method of this disclosure provides a cloud computing product installation method based on an implementation queue. It can node the installation implementation parameters of the installer and store them in the implementation queue. By using execution reading tools such as execution threads, it can sequentially read the system component nodes and environment component nodes corresponding to the installation implementation parameters from the implementation queue and perform installation execution, thereby realizing the controllable batch installation of cloud computing products.

[0054] Therefore, compared to the traditional installation process that sequentially implements the originally integrated OS system and middleware, the method of the present disclosure embodiments can break down the unified implementation process into independent system component installation and environment component installation, thereby improving the concurrency granularity of product installation. Furthermore, by implementing parallel execution of installation component parameters, rate limiting of the installation implementation is achieved, ensuring high system availability. Clearly, the above-described installation method of the present disclosure embodiments can greatly improve product installation efficiency, maximize the installation performance of the installation server, save installation resources, and effectively improve product installation speed even with a large number of installations while ensuring product installation accuracy.

[0055] Figure 3 The diagram illustrates a process flow chart regarding the preprocessing queue in an installation method for a cloud computing product according to an embodiment of the present disclosure.

[0056] like Figures 2-3 As shown, according to an embodiment of this disclosure, before operation S201 generates the installation node corresponding to the cloud computing product in the preprocessing queue, the method further includes:

[0057] Analyze the user resource request form corresponding to the cloud computing product to determine the system components and environment components;

[0058] When system components are matched with installation components, determine the system component implementation parameters corresponding to the system component and the environmental component implementation parameters corresponding to the environmental component.

[0059] like Figure 3 As shown, the system retrieves the user resource request form provided by the user. This form is a resource data file provided by the user to fulfill their service requirements. It can be in the form of a data table or a data file, representing the installation resources corresponding to the user's service needs. Specifically, the system parses the user resource request form to obtain the installation resources matching it, such as OS, middleware, and other installation components, such as operation S301. These installation components include system components and environment components. The same user resource list can correspond to multiple business services, and each business service corresponds to a cloud computing product. In other words, to satisfy the installation of multiple business services in the user resource request form, multiple cloud computing products need to be installed in parallel.

[0060] After identifying the installation components that match the user's service requirements, confirm whether the database contains installation files and implementation parameters, such as those for the corresponding system components (e.g., OS image files) and environment components (e.g., middleware), as per operation S302. The installation parameters corresponding to the system components are called system component implementation parameters, and the installation parameters corresponding to the environment components are called environment component implementation parameters.

[0061] Furthermore, since there can be multiple suitable environment components for a system component, and similarly, there can be multiple suitable system components for a given environment component, it is necessary to match the determined system component and environment component to ensure they are compatible. Because the installation method in this embodiment allows for parallel installation of multiple cloud computing products, by retrieving a preset validity list of system component and environment component combinations, it can be confirmed that the system component selected by the user is suitable for the currently selected environment component, or vice versa, as in operation S303.

[0062] Based on the system components selected according to the user's service requirements from the preset database, obtain the corresponding system component implementation parameters, such as images, installation procedures, and implementation parameters. Similarly, based on the environment components selected according to the user's service requirements, obtain the corresponding environment component implementation parameters, such as images, installation procedures, and implementation parameters, as in operations S304, S309, and S311.

[0063] This allows for the determination of the corresponding system and environment component implementation parameters based on user service needs, thereby ensuring that the installed cloud computing products can accurately meet the user's service requirements when the implementation parameters are subsequently executed.

[0064] like Figures 2-3 As shown, according to an embodiment of this disclosure, in operation S201, generating the installation component node corresponding to the cloud computing product in the preprocessing queue, the following steps are included:

[0065] The system component cache identifier of the system component implementation parameters is stored in the preprocessing queue to generate the system component node of the installer node;

[0066] The environment component cache identifier of the environment component implementation parameters is stored in the preprocessing queue to generate the environment component node of the installer node.

[0067] The system component implementation parameters determined above are stored in a designated cache area, which can be a cache server, database, or data table. Simultaneously, the system component cache identifier (i.e., cache ID) used to identify the system component implementation parameters is stored as node element data in the preprocessing queue, and a system component node is generated in the preprocessing queue for this node element data, as in operation S305. When multiple system component cache identifiers corresponding to multiple system component implementation parameters for multiple user service requirements are stored as node element data in the preprocessing queue, batch generation of system component nodes can also be achieved, where each system component node corresponds to a node ID used to identify that node.

[0068] Similarly, the environmental component implementation parameters determined above are stored in a designated cache area, which can be a cache server, database, or data table. Simultaneously, the environmental component cache identifier used to identify the environmental component implementation parameters is stored as node element data in the cache area and stored in a preprocessing queue. At the same time, environmental component nodes are generated in the preprocessing queue for this node element data, as in operations S309 and S311. When multiple environmental component cache identifiers corresponding to multiple environmental component implementation parameters for multiple user service requirements are stored as node element data in the preprocessing queue, batch generation of environmental component nodes can also be achieved, where each environmental component node corresponds to a node ID used to identify the node.

[0069] Therefore, by preprocessing, user resource request forms are transformed into the installation process and related files, scripts, and other installation parameters required for resource implementation. These installation parameters are then stored in a cache, and their cache IDs are used as node IDs to be batch-stored into the preprocessing queue. This allows for the confirmation of the corresponding installation parameters and the storage of their corresponding identifiers as nodes in the preprocessing queue, thus achieving parameter tagging and facilitating accurate subsequent retrieval of real-time parameters.

[0070] like Figures 2-3 As shown, according to an embodiment of this disclosure, before storing the environment component cache identifier of the environment component implementation parameters in the preprocessing queue and generating the environment component node of the installer node, the method further includes:

[0071] Generate verification nodes in the preprocessing queue based on system component nodes;

[0072] In this process, system component nodes and environment component nodes are arranged sequentially in the preprocessing queue, with the verification node serving as the dividing node.

[0073] like Figure 3 As shown, for multiple system components corresponding to multiple business services in a user resource application form, return to operation S303 to continue determining whether all multiple system components have completed operations such as parameter determination and node storage. If all are completed, it means that there are no more system components to be installed in the current batch, such as OS, and further operation S306 needs to be executed.

[0074] The verification node is a set of system component nodes that have completed the aforementioned parameter determination, node storage, and other operations for subsequent verification. Each verification node includes multiple node IDs of all system component nodes in the preprocessing queue. At the same time, the verification node generates a fixed verification node ID for the set of multiple node IDs to uniquely identify the set of multiple node IDs.

[0075] Therefore, after all system component nodes (such as OS node IDs) in the current batch are stored, a verification node (such as a check node) is placed in the preprocessing queue. This verification node can store the node IDs of all system component nodes in this batch, which can be used to verify the execution status of the aforementioned system component nodes in subsequent processing.

[0076] After all system component nodes for the current batch are stored in the preprocessing queue, the verification node is stored sequentially in the preprocessing queue, followed by the storage of environment component nodes. This verification node serves as the boundary between system component nodes and environment component nodes. Therefore, when the verification node is encountered during the sequential reading process of the preprocessing queue, it signifies that the system component nodes have been read, and further reading operations on other nodes, such as environment component nodes, will proceed.

[0077] Therefore, by adding check nodes and other verification nodes as verification layers for the preprocessing queue and subsequent implementation queue, we can meet the requirement of different environmental components to make separate judgments on the type of environmental component relative to system components, which is more conducive to meeting the needs of clustered installation of environmental components.

[0078] Furthermore, if it is determined that there are no system components that need to be installed in the current batch (e.g., operation S303), then it can be further confirmed whether there are any environment components (e.g., middleware) that need to be installed in the current batch, as detailed in operation S307. Since there are cases where installing only system components is sufficient to complete the installation of a cloud computing product, it is necessary to assess whether the installation of environment components is required for that cloud computing product.

[0079] like Figures 2-3 As shown, according to an embodiment of this disclosure, before storing the environment component cache identifier of the environment component implementation parameters in the preprocessing queue and generating the environment component node of the installer node, the method further includes:

[0080] Based on the environment component type, the environment component implementation parameters are stored in the cache area, and an environment component cache identifier is generated.

[0081] Environment components are mainly categorized into two types: clustered installation environment components and non-clustered installation environment components. Non-clustered installation generally refers to the installation of a single environment component corresponding to a single system component, while clustered installation generally refers to the parallel installation of a group of environment components.

[0082] Therefore, based on the aforementioned determined environment components, processing is performed according to type. Specifically, when an environment component is installed in a cluster, the implementation information, such as the installation package, patch package, installation process, and implementation parameters corresponding to the environment component group requiring cluster installation, is obtained, as in operation S309. Then, this implementation information is stored in the cache area, and the cache ID is stored as a node ID in the preprocessing queue, as in operation S310. When an environment component (such as middleware) is installed in a non-cluster environment, the implementation information, such as the installation package, patch package, installation process, and implementation parameters corresponding to each middleware, is obtained sequentially, as in operation S311. Then, the implementation information is stored in the cache area, and the cache ID is stored as a node ID in the preprocessing queue, as in operation S312.

[0083] Therefore, the corresponding identification information of system component implementation parameters and environment component implementation parameters used for cloud computing products can be written into the preprocessing queue to complete the preprocessing of implementation parameters. Specifically, the preprocessing queue transforms the user's cloud computing resource application into the installation process and related files, scripts, and other implementation parameters required for resource implementation. The results of this preprocessing are stored in a cache, and the cache IDs of the preprocessing results generated from the current resource application are further stored in the preprocessing queue as nodes in an orderly manner. This facilitates the separation of the originally integrated installation and implementation process of system components such as the OS and environment components such as middleware into independent system component installation and environment component installation, further improving the concurrency granularity of installation and implementation. Furthermore, by adding verification layers such as checks, the needs of different environment components for clustered installation can be met.

[0084] Figure 4 The diagram illustrates a process flow chart for storing installation component nodes in an implementation queue in an installation method for a cloud computing product according to an embodiment of the present disclosure.

[0085] like Figures 2-4 As shown, according to an embodiment of this disclosure, in operation S202, storing the installer node in the preprocessing queue into the implementation queue includes:

[0086] Read the queue identifier of the implementation queue in the main implementation queue;

[0087] When the implementation queue corresponding to the queue identifier meets the node matching condition with the preprocessing queue, the verification node, system component node and environment component node of the installation component node in the preprocessing queue are stored into the implementation queue.

[0088] The main implementation queue is a component of the overall implementation queue, forming the overall implementation queue together with the implementation queue groups. The main implementation queue stores the IDs of all implementation queue groups, used for sequential polling of these groups. Each implementation queue group consists of multiple implementation queues. These implementation queues are bidirectional queues, capable of storing specific implementation process nodes to be executed. These implementation process nodes can be added to the implementation queue group in batches from the preprocessing queue according to the implementation process specified by the business service in the user resource application form.

[0089] First, the implementation queue ID currently at the tail of the implementation main queue is read from the implementation main queue and used as the queue identifier for that implementation queue, as in operation S401. This queue identifier can be the node ID of that implementation queue within the aforementioned implementation main queue.

[0090] Based on the implementation queue ID, the obtained implementation queue can be determined, such as operation S402.

[0091] The node matching condition is the matching rule for the number of nodes in the implementation queue and the preprocessing queue determined in the above operation S402. That is, during the installation of the cloud computing product, the number of nodes that need to be written from the preprocessing queue to the implementation queue needs to match the number of free nodes in the implementation queue, so as to prevent the necessary nodes in the preprocessing queue from not being written to the implementation queue.

[0092] Therefore, it is necessary to perform a verification operation on the implementation queue based on the current number of nodes in the preprocessing queue. Specifically, the verification method involves adding the number of occupied nodes in the implementation queue to the number of write nodes in the preprocessing queue and comparing this result with the length threshold of the implementation queue. The length threshold of the implementation queue is the threshold for the number of nodes it can store.

[0093] If the sum of the number of nodes in the implementation queue and the number of nodes in the preprocessing queue is greater than the implementation queue length threshold, wait for one polling cycle, read another implementation queue again, and repeat operations S401-S403, such as operation S431.

[0094] If the sum of the number of nodes in the implementation queue and the number of nodes in the preprocessing queue is less than or equal to the implementation queue length threshold, the current implementation queue can be locked, confirming that the implementation queue can store all the pre-write nodes in the preprocessing queue. Further, write permissions are obtained for the implementation queue to facilitate the sequential writing of the preprocessing queue's write nodes into the implementation queue, as described later in operation S404.

[0095] Furthermore, each node in the preprocessing queue is read sequentially, causing the nodes in the preprocessing queue (such as the corresponding cache IDs of system components and environment components) to be dequeued and written into the implementation queue, as in operation S405. This completes the writing of nodes to the implementation queue, writing all system component nodes and environment component nodes from the preprocessing queue into the implementation queue. Finally, the write permission for the current implementation queue is released, and the lock on the implementation queue is unlocked, as in operation S406.

[0096] The system establishes a main implementation queue and implementation queue groups to handle the transfer of implementation information from the preprocessing queue to the main implementation queue. The implementation queues within the implementation queue groups are bidirectional queues, storing the IDs of all nodes requiring installation, implementation, and verification. Simultaneously, the IDs of all queues within the implementation queue groups are ordered and stored in a main queue, forming the main implementation queue. The main implementation queue can be a unidirectional queue, where the head element is the currently readable (dequeued) implementation queue ID, and the tail element is stored in a separate node as the implementation queue ID currently being used for input. When implementation information from the preprocessing queue is written to the main implementation queue via the current implementation queue, the system retrieves and verifies the implementation queue corresponding to the tail element of the main implementation queue and writes relevant identifiers such as implementation parameters into it. Therefore, the system can create and monitor the main implementation queue and implementation queue groups, and simultaneously handle the input and output operations of installation nodes from the preprocessing queue to the main implementation queue. By implementing multiple write nodes in the overall queue, the parallelism of node reads can be further improved, thereby further increasing the node execution speed while ensuring the accuracy of node execution.

[0097] Figure 5 The diagram illustrates a process flow chart of performing installation based on read installation component nodes in an installation method for a cloud computing product according to an embodiment of the present disclosure.

[0098] like Figures 2-5 As shown, according to an embodiment of this disclosure, the system node and environment node of the installer node in the parallel reading implementation queue of operation S203 include:

[0099] Read the head element of the implemented queue based on the queue state;

[0100] When the head element of the read implementation queue is a system component node or an environment component node, retrieve the corresponding system component implementation parameters or environment component implementation parameters from the cache.

[0101] When the head element of the read implementation queue is a verification node, another implementation queue is read repeatedly based on the read completion rate of the system component node corresponding to the verification node.

[0102] The main queue is read using tools such as execution threads to obtain the head element, as in operation S501. This head element can be the ID of the implementation queue currently at the head of the main queue.

[0103] Based on the execution queue ID determined by the obtained head element, an execution queue A can be identified, such as operation S502.

[0104] The queue status of implementation queue A is determined (e.g., whether the queue status is empty), and different processing steps are performed based on its queue status, such as operation S503. The queue status refers to the node status of the corresponding implementation queue. Specifically, when no node is read from the implementation queue, the queue status can be empty; when a node is read from the implementation queue, the queue status can be non-empty. Non-empty queue statuses can be further differentiated; for example, when a verification node is read from the implementation queue, the queue status can be verification status; when an execution node is read from the implementation queue, the queue status can be execution status.

[0105] When the queue status of implementation queue A is empty, it indicates that there may be no executable nodes in the implementation queue. In this case, the tail element of the main implementation queue can be updated to the queue ID of implementation queue A, as in operation S531. Then, the queue ID of implementation queue A is added from the tail to the main implementation queue, as in operation S532. Finally, the current head element of the main implementation queue is read again to determine another implementation queue, and operations S501-S503 are repeated.

[0106] When the queue status of the current queue A is not empty, read and write permissions can be obtained for the current queue A, such as operation S504.

[0107] If the queue status of implementation queue A is not empty, and the head element of implementation queue A is a verification node (such as a check node), then implementation queue A is in a verification state. It can check whether all system component node IDs stored in the check node have been read, as in operation S506. If all checks are complete, it continues to read the next node of the verification node, such as an environment component node, and repeats operations S505-S506. Otherwise, if all system component node IDs have not been read, the check node is placed back at the head of implementation queue A, the tail element of the main implementation queue is updated to the queue ID of implementation queue A, and the queue ID of implementation queue A is written from the tail to the main implementation queue. Operations S501-S506 are restarted, and the next implementation queue of the main implementation queue is read, as in operations S561-S565.

[0108] When the head element of implementation queue A is a non-empty element and is another implementation node that is not a verification node, then the read and write permissions of the current implementation queue A are released, as in operation S507. A read operation is then performed on implementation queue A.

[0109] Read the head element m of the implementation queue A, where the head element m can be the node ID of the implementation process node. This implementation process node can be an environment node or a system node.

[0110] Update the tail element of the main queue A to the queue ID of the main queue A, and put the queue ID of the main queue A back into the main queue A from the tail, as in operations S508-S509.

[0111] Based on the node ID corresponding to the head element m of the implementation queue, the execution thread can retrieve the corresponding installation component implementation parameters, such as the image, installation process, and implementation parameters, from the cache, as in operation S510. Specifically, if the read node ID is a system component node ID, the system component implementation parameters are retrieved; if the read node ID is an environment component node ID, the environment component implementation parameters are retrieved.

[0112] Therefore, regardless of the size of the implementation queue storing installer nodes or the number of write nodes in the implementation queue, the execution threads described above can precisely and concurrently retrieve the corresponding system component implementation parameters or environment component implementation parameters. In other words, compared to the traditional integrated installation and execution method for system components and installers, this approach separates the previously integrated installation and execution processes for system components (such as the OS) and environment components (such as middleware) into independent system component installation and execution processes. This further improves the concurrency granularity of the installation and execution, increases node execution speed, and ensures the accuracy of node execution. Overall, this improves the installation and execution efficiency of cloud computing products, better leverages the overall performance of the installation server, and saves installation resources.

[0113] It should be noted that an execution thread is the smallest unit of execution capable of computational scheduling within the installation server. It can be used to execute implementation process nodes, such as system component nodes and environment component nodes. A significant number of execution threads can be pooled together to form an execution pool. Specifically, when the total implementation queue or the implementation queue itself is not empty, the execution threads in the execution pool retrieve the corresponding implementation parameter node from the total implementation queue and execute it. After completing the implementation of the implementation parameter node, the execution thread is released back into the execution pool. The number of execution threads in the execution pool is limited by a thread threshold.

[0114] By using an execution pool that allows control over the number of execution threads, rate limiting during installation is achieved, ensuring high system availability. Furthermore, by adding a check verification layer, the clustered installation requirements of different middleware are met.

[0115] like Figures 2-5 As shown, according to an embodiment of this disclosure, the system component implementation parameters corresponding to the system component node and the environment component implementation parameters corresponding to the environment component node executed in operation S204 include:

[0116] The installation process is executed in parallel based on the system component implementation parameters and the environment component implementation parameters.

[0117] Complete the installation of cloud computing products based on the implementation results.

[0118] Based on the retrieved system component implementation parameters and environment component implementation parameters, the installation process is executed via an execution thread. The execution results are then collected and placed into an implementation result set, as in operation S512. Specifically, files, scripts, images, and installation procedures corresponding to the specified implementation parameters can be executed to complete the installation of the corresponding components. Because it is a parallel installation operation, it can essentially achieve simultaneous installation of system components and environment components, thus completing the installation of cloud computing products. This allows users to quickly fulfill their service needs through cloud computing products, greatly improving the user experience.

[0119] Furthermore, after the installation and implementation of the corresponding parameters are completed, the corresponding execution threads are released back to the execution pool.

[0120] The installation process involves a significant number of execution threads performing the installation in parallel, along with the parallel reading of system component nodes and environment component nodes. This further enhances the parallel installation speed of system component implementation parameters and environment component implementation parameters. Consequently, it maximizes the installation server's performance and improves the utilization of installation resources.

[0121] Therefore, an execution pool is constructed, and the execution threads in the execution pool read and execute the implementation information from the overall implementation queue. Since the execution pool stores the execution threads capable of executing implementation process nodes together in a pooled manner, when the overall implementation queue is not empty, the execution threads in the execution pool retrieve implementation information from the queue and perform the implementation; after implementation, the execution threads are released back into the execution pool. Thus, according to the set parallel execution capability, implementation information in the overall implementation queue is retrieved concurrently and executed, and the corresponding results are recorded after execution. It is evident that by using an execution pool that allows control over the number of execution threads, rate limiting for the installation and implementation process is achieved, ensuring high availability of the system.

[0122] Therefore, the above-described method of this disclosure can split the original integrated OS system and middleware installation process into independent OS system installation and middleware installation, thereby improving the concurrency granularity of the installation process. In addition, by adding a check verification layer, the needs of different middleware for clustered installation can be met. Furthermore, by using an execution pool that can control the number of execution threads, rate limiting of the installation process is achieved, ensuring high availability of the system.

[0123] Furthermore, by using cloud computing resource application preprocessing, the installation process of cloud computing resources applied for by users is split into process queues that include OS system installation process and middleware installation process. By establishing an implementation master queue, read and write separation and overall control of the installation implementation process are achieved, and concurrent controllability of the installation implementation process is achieved through execution pool.

[0124] Based on the above-described installation method for cloud computing products, this disclosure also provides an installation apparatus for cloud computing products. The following will be combined with... Figure 6 The device is described in detail.

[0125] Figure 6 The diagram illustrates a structural block diagram of an installation apparatus for a cloud computing product according to an embodiment of the present disclosure.

[0126] like Figure 6 As shown, the installation device 600 for the cloud computing product in this embodiment includes a node generation module 610, a node storage module 620, a node reading module 630, and a parameter execution module 640.

[0127] The node generation module 610 is used to generate installation node corresponding to the cloud computing product in the preprocessing queue. In one embodiment, the node generation module 610 can be used to perform the operation S201 described above, which will not be repeated here.

[0128] The node storage module 620 is used to store the installation node in the preprocessing queue into the implementation queue. In one embodiment, the node storage module 620 can be used to perform the operation S202 described above, which will not be repeated here.

[0129] The node reading module 630 is used to read in parallel the system component nodes and environment component nodes of the installation component nodes in the implementation queue. In one embodiment, the node reading module 630 can be used to perform the operation S203 described above, which will not be repeated here.

[0130] The parameter execution module 640 is used to execute the system component implementation parameters corresponding to the system component node and the environment component implementation parameters corresponding to the environment component node in parallel to complete the installation of the cloud computing product. In one embodiment, the parameter execution module 640 can be used to execute the operation S204 described above, which will not be repeated here.

[0131] According to embodiments of this disclosure, any plurality of modules among the node generation module 610, node storage module 620, node reading module 630, and parameter execution module 640 may be combined into one module, or any one of these modules may be split into multiple modules. Alternatively, at least part of the functionality of one or more of these modules may be combined with at least part of the functionality of other modules and implemented in one module. According to embodiments of this disclosure, at least one of the node generation module 610, node storage module 620, node reading module 630, and parameter execution module 640 may be at least partially implemented as hardware circuitry, such as a field-programmable gate array (FPGA), a programmable logic array (PLA), a system-on-a-chip, a system-on-a-substrate, a system-on-package, an application-specific integrated circuit (ASIC), or implemented in hardware or firmware by any other reasonable means of integrating or packaging the circuitry, or implemented in any one of software, hardware, and firmware methods, or in a suitable combination of any of these methods. Alternatively, at least one of the node generation module 610, node storage module 620, node reading module 630, and parameter execution module 640 can be at least partially implemented as a computer program module, which can perform corresponding functions when the computer program module is run.

[0132] Figure 7 A block diagram schematically illustrates an electronic device suitable for implementing an installation method for a cloud computing product according to an embodiment of the present disclosure.

[0133] like Figure 7 As shown, an electronic device 700 according to an embodiment of the present disclosure includes a processor 701, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 702 or a program loaded from a storage portion 708 into a random access memory (RAM) 703. The processor 701 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or an associated chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 701 may also include onboard memory for caching purposes. The processor 701 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0134] RAM 703 stores various programs and data required for the operation of electronic device 700. Processor 701, ROM 702, and RAM 703 are interconnected via bus 704. Processor 701 performs various operations of the method flow according to embodiments of the present disclosure by executing programs in ROM 702 and / or RAM 703. It should be noted that the programs may also be stored in one or more memories other than ROM 702 and RAM 703. Processor 701 may also perform various operations of the method flow according to embodiments of the present disclosure by executing programs stored in said one or more memories.

[0135] According to embodiments of this disclosure, the electronic device 700 may further include an input / output (I / O) interface 705, which is also connected to a bus 704. The electronic device 700 may also include one or more of the following components connected to the I / O interface 705: an input section 706 including a keyboard, mouse, etc.; an output section 707 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 708 including a hard disk, etc.; and a communication section 709 including a network interface card such as a LAN card, modem, etc. The communication section 709 performs communication processing via a network such as the Internet. A drive 710 is also connected to the I / O interface 705 as needed. A removable medium 711, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 710 as needed so that computer programs read from it can be installed into the storage section 708 as needed.

[0136] This disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or it may exist independently and not assembled into the device / apparatus / system. The computer-readable storage medium carries one or more programs that, when executed, implement the method according to the embodiments of this disclosure.

[0137] According to embodiments of this disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, such as, but not limited to: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this disclosure, the computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. For example, according to embodiments of this disclosure, the computer-readable storage medium may include ROM 702 and / or RAM 703 and / or one or more memories other than ROM 702 and RAM 703 described above.

[0138] Embodiments of this disclosure also include a computer program product comprising a computer program containing program code for performing the methods shown in the flowchart. When the computer program product is run on a computer system, the program code is used to cause the computer system to implement the item recommendation method provided in the embodiments of this disclosure.

[0139] When the computer program is executed by the processor 701, it performs the functions defined in the system / apparatus of this disclosure embodiments. According to embodiments of this disclosure, the systems, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0140] In one embodiment, the computer program may rely on a tangible storage medium such as an optical storage device or a magnetic storage device. In another embodiment, the computer program may also be transmitted and distributed in the form of signals over a network medium, and may be downloaded and installed via the communication section 709, and / or installed from a removable medium 711. The program code contained in the computer program can be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination thereof.

[0141] In such an embodiment, the computer program can be downloaded and installed from a network via the communication section 709, and / or installed from the removable medium 711. When the computer program is executed by the processor 701, it performs the functions defined in the system of this disclosure embodiment. According to embodiments of this disclosure, the systems, devices, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0142] According to embodiments of this disclosure, program code for executing the computer programs provided in embodiments of this disclosure can be written in any combination of one or more programming languages. Specifically, these computational programs can be implemented using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, languages ​​such as Java, C++, Python, "C", or similar programming languages. The program code can execute entirely on the user's computing device, partially on the user's device, partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0143] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0144] Those skilled in the art will understand that the features described in the various embodiments and / or claims of this disclosure can be combined or combined in various ways, even if such combinations or combinations are not explicitly described in this disclosure. In particular, the features described in the various embodiments and / or claims of this disclosure can be combined or combined in various ways without departing from the spirit and teachings of this disclosure. All such combinations and / or combinations fall within the scope of this disclosure.

[0145] The embodiments of this disclosure have been described above. However, these embodiments are for illustrative purposes only and are not intended to limit the scope of this disclosure. Although various embodiments have been described above, this does not mean that the measures in the various embodiments cannot be used advantageously in combination. The scope of this disclosure is defined by the appended claims and their equivalents. Various substitutions and modifications can be made by those skilled in the art without departing from the scope of this disclosure, and all such substitutions and modifications should fall within the scope of this disclosure.

Claims

1. A method for installing a cloud computing product, wherein, include: Generate the installation node corresponding to the cloud computing product in the preprocessing queue; Store the installer nodes in the preprocessing queue into the implementation queue; The system component node and the environment component node of the installation component node in the implementation queue are read in parallel. as well as The installation of the cloud computing product is completed by executing the system component implementation parameters corresponding to the system component node and the environment component implementation parameters corresponding to the environment component node. The installation node is the implementation process node in the preprocessing queue corresponding to the element data of system component installation and environment component installation; Wherein, the system component node is the implementation process node of the system component implementation parameters corresponding to the system component; wherein, the environment component node is the implementation process node of the environment component implementation parameters corresponding to the environment component; Specifically, generating the installation node corresponding to the cloud computing product in the preprocessing queue includes: storing the system component cache identifier of the system component implementation parameters in the preprocessing queue to generate the system component node of the installation node; and storing the environment component cache identifier of the environment component implementation parameters in the preprocessing queue to generate the environment component node of the installation node. The step of storing the installer nodes in the preprocessing queue into the implementation queue includes: reading the queue identifier of the implementation queue in the main implementation queue; when the implementation queue corresponding to the queue identifier and the preprocessing queue meet the node matching condition, storing the verification node in the preprocessing queue, as well as the system component node and environment component node of the installer node, into the implementation queue. The process of reading the system component node and environment component node of the installation component node in the parallel reading of the implementation queue includes: reading the head element of the implementation queue according to the queue status of the implementation queue; when the head element of the implementation queue is the system component node or the environment component node, retrieving the corresponding system component implementation parameters or environment component implementation parameters from the cache; when the head element of the implementation queue is a verification node, repeatedly reading another implementation queue according to the reading completion degree of the system component node corresponding to the verification node.

2. The method according to claim 1, wherein, Before generating the installation node corresponding to the cloud computing product in the preprocessing queue, the method further includes: Analyze the user resource request form corresponding to the cloud computing product to determine the system components and environment components; When the system component is matched with the mounting component, the system component implementation parameters corresponding to the system component and the environmental component implementation parameters corresponding to the environmental component are determined.

3. The method according to claim 1, wherein, Before storing the environment component cache identifier of the environment component implementation parameters into the preprocessing queue and generating the environment component node of the installer node, the method further includes: The verification nodes in the preprocessing queue are generated based on the system component nodes; The system component node and the environment component node are arranged sequentially in the preprocessing queue with the verification node as the dividing node.

4. The method according to claim 1, wherein, Before storing the environment component cache identifier of the environment component implementation parameters into the preprocessing queue and generating the environment component node of the installer node, the method further includes: Based on the environment component type, the environment component implementation parameters are stored in the cache area, and the environment component cache identifier is generated.

5. The method according to claim 1, wherein, The execution of the system component implementation parameters corresponding to the system component node and the environment component implementation parameters corresponding to the environment component node includes: The installation process is performed in parallel based on the system component implementation parameters and the environmental component implementation parameters. The installation of the cloud computing product is completed based on the implementation results of the installation.

6. An installation device for a cloud computing product, wherein, include: The node generation module is used to generate installation component nodes corresponding to the cloud computing product in the preprocessing queue; The node storage module is used to store the installation component nodes in the preprocessing queue into the implementation queue. The node reading module is used to read in parallel the system component nodes and environment component nodes of the installation component nodes of the implementation queue; as well as The parameter execution module is used to execute the system component implementation parameters corresponding to the system component node and the environment component implementation parameters corresponding to the environment component node in parallel to complete the installation of the cloud computing product. The installation node is the implementation process node in the preprocessing queue corresponding to the element data of system component installation and environment component installation; Wherein, the system component node is the implementation process node of the system component implementation parameters corresponding to the system component; wherein, the environment component node is the implementation process node of the environment component implementation parameters corresponding to the environment component; Specifically, generating the installation node corresponding to the cloud computing product in the preprocessing queue includes: storing the system component cache identifier of the system component implementation parameters in the preprocessing queue to generate the system component node of the installation node; and storing the environment component cache identifier of the environment component implementation parameters in the preprocessing queue to generate the environment component node of the installation node. The step of storing the installer nodes in the preprocessing queue into the implementation queue includes: reading the queue identifier of the implementation queue in the main implementation queue; when the implementation queue corresponding to the queue identifier and the preprocessing queue meet the node matching condition, storing the verification node in the preprocessing queue, as well as the system component node and environment component node of the installer node, into the implementation queue. The process of reading the system component node and environment component node of the installation component node in the parallel reading of the implementation queue includes: reading the head element of the implementation queue according to the queue status of the implementation queue; when the head element of the implementation queue is the system component node or the environment component node, retrieving the corresponding system component implementation parameters or environment component implementation parameters from the cache; when the head element of the implementation queue is a verification node, repeatedly reading another implementation queue according to the reading completion degree of the system component node corresponding to the verification node.

7. An electronic device, comprising: One or more processors; Storage device for storing one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors perform the method according to any one of claims 1 to 5.

8. A computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, cause the processor to perform the method according to any one of claims 1 to 5.

9. A computer program product comprising a computer program that, when executed by a processor, implements the method according to any one of claims 1 to 5.

Images