A method, apparatus, device and medium for generating a production scheme

Abstract

This application provides a method, apparatus, device, and medium for generating deployment schemes, relating to the application of large-scale models in the fintech field. The method for generating deployment schemes includes: obtaining installation packages for various versions of a target application; parsing each installation package to obtain an operation queue corresponding to each installation package; the operation queue representing the execution order of multiple installation operations involved in the installation of the target application; determining at least one first installation package from the installation packages of various historical versions based on the operation queues corresponding to each installation package; generating a deployment scheme for the current version's installation package based on the deployment scheme of at least one first installation package; wherein, when the deployment scheme of the current version's installation package is executed, at least some of the installation operations in the operation queue corresponding to the first installation package are executed.

Description

Technical Field

[0001] This application relates to the application of large models in the field of financial technology, and more specifically to a method, apparatus, equipment and medium for generating production plans. Background Technology

[0002] A production deployment plan refers to a systematic plan that formally deploys completed software programs or systems to a production environment and ensures their stable operation and maintainability. In the fintech field, the increasingly rapid iteration of business and functional requirements places higher demands on the speed of product version delivery.

[0003] The delivery of business product versions typically involves three stages: submitting version media, customizing deployment strategies, and writing deployment plans. In the stage of writing deployment plans, manual writing is often relied upon, which is time-consuming and labor-intensive, and may also delay the normal delivery of business products.

[0004] Therefore, there is an urgent need for a method, apparatus, equipment, and medium for generating production plans to address the deficiencies in related technologies. Summary of the Invention

[0005] In view of the above problems, this application provides a method, apparatus, equipment and medium for generating a production scheme.

[0006] The first aspect of this application provides a method for generating a deployment scheme, the method comprising: obtaining installation packages for various versions of a target application; parsing each installation package to obtain an operation queue corresponding to each installation package; the operation queue representing the execution order of multiple installation operations involved when the target application is installed; determining at least one first installation package from the installation packages of various historical versions based on the operation queues corresponding to each installation package; generating a deployment scheme for the current version of the installation package based on the deployment scheme of at least one first installation package; wherein, when the deployment scheme for the current version of the installation package is executed, at least some of the installation operations in the operation queue corresponding to the first installation package are executed.

[0007] According to an embodiment of this application, each installation package is parsed to obtain an operation queue corresponding to each installation package, including: parsing each installation package according to its format to obtain an installation strategy file for each installation package, wherein the installation strategy file represents multiple installation operations involved when the target application is installed; and processing the installation strategy file using a decision tree classification algorithm to obtain an operation queue for multiple installation operations.

[0008] According to the embodiments of this application, each installation package is parsed to obtain an installation strategy file for each installation package, including: when the installation package is an image package in a preset format, the installation package is parsed based on an abstract syntax tree to obtain an installation strategy file for the installation package; when the installation package is a compressed package in a preset format, the installation package is parsed based on the directories at each level of the installation package to obtain an installation strategy file for the installation package.

[0009] According to an embodiment of this application, determining at least one first installation package from the installation packages of each historical version based on the operation queue corresponding to each installation package includes: determining the similarity between the current version installation package and the installation packages of each historical version based on the operation queue corresponding to each installation package; determining at least one first installation package from the installation packages of each historical version, wherein the similarity between the first installation package and the current version installation package satisfies a preset similarity range.

[0010] According to an embodiment of this application, determining the similarity between the current version of the installation package and the installation packages of each historical version based on the operation queue corresponding to each installation package includes: obtaining at least one feature value of the operation queue corresponding to each installation package; determining the feature vector corresponding to each installation package based on the at least one feature value; and obtaining the similarity between the current version of the installation package and the installation packages of each historical version based on the cosine similarity between the feature vectors of each installation package.

[0011] According to an embodiment of this application, the method further includes: discretizing each similarity and outputting one of a first similarity, a second similarity, and a third similarity; wherein, the first similarity indicates that the deployment scheme of the current version of the installation package is the same as that of the historical version of the installation package; the second similarity indicates that the deployment scheme of the current version of the installation package is partially the same as that of the historical version of the installation package; and the third similarity indicates that the deployment scheme of the current version of the installation package is different from that of the historical version of the installation package.

[0012] According to an embodiment of this application, generating a deployment plan for the current version of the installation package based on a deployment plan for at least one first installation package includes: if the similarity between the current version of the installation package and the first installation package satisfies a first similarity, directly generating a deployment plan for the current version of the installation package based on the deployment plan for the first installation package; if the similarity between the current version of the installation package and the first installation package satisfies a second similarity, generating a deployment plan for the current version of the installation package based on a portion of the installation operations in the operation queue of the first installation package.

[0013] According to embodiments of this application, the characteristic values ​​of the operation queue include at least one of the following: the operation strategy of multiple installation operations in the operation queue; the operation order of multiple installation operations in the operation queue; the rollback operation corresponding to each installation operation in the operation queue, wherein the rollback operation represents the next operation to be executed if the corresponding installation operation fails; and the execution environment of the operation queue.

[0014] A second aspect of this application provides an apparatus for generating a deployment scheme. The apparatus includes: an installation package parsing module, configured to obtain installation packages for various versions of a target application; parse each installation package to obtain an operation queue corresponding to each installation package; the operation queue represents the execution order of multiple installation operations involved when the target application is installed; an installation package filtering module, configured to determine at least one first installation package from the installation packages of various historical versions based on the operation queues corresponding to each installation package; and a scheme generation module, configured to generate a deployment scheme for the current version of the installation package based on the deployment scheme of at least one first installation package; wherein, when the deployment scheme of the current version of the installation package is executed, at least some of the installation operations in the operation queue corresponding to the first installation package are executed.

[0015] A third aspect of this application provides an electronic device comprising: one or more processors; and a memory for storing one or more computer programs, wherein the one or more processors execute the one or more computer programs to implement the steps of the method described above.

[0016] A fourth aspect of this application also provides a computer-readable storage medium having a computer program or instructions stored thereon, which, when executed by a processor, implement the steps of the above-described method.

[0017] The fifth aspect of this application also provides a computer program product, including a computer program or instructions that, when executed by a processor, implement the steps of the above-described method. Attached Figure Description

[0018] The above-mentioned contents, other objects, features and advantages of this application will become clearer from the following description of embodiments with reference to the accompanying drawings, in which:

[0019] Figure 1 The illustration schematically depicts an application scenario of the production scheme generation method, apparatus, equipment, and medium according to embodiments of this application;

[0020] Figure 2 One of the flowcharts illustrating a method for generating a production plan according to an embodiment of this application is shown schematically;

[0021] Figure 3 The flowchart illustrating the method for generating a production plan according to an embodiment of this application is shown in the second example.

[0022] Figure 4 The third flowchart illustrating the method for generating a production plan according to an embodiment of this application is shown schematically.

[0023] Figure 5 This schematic diagram illustrates a structural block diagram of a production apparatus according to an embodiment of the present application;

[0024] Figure 6 A block diagram schematically illustrates an electronic device suitable for implementing a production plan according to an embodiment of this application. Detailed Implementation

[0025] The embodiments of this application 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 this application. In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the embodiments of this application for ease of explanation. However, it will be apparent that one or more embodiments may be implemented without these specific details. Furthermore, descriptions of well-known structures and technologies are omitted in the following description to avoid unnecessarily obscuring the concepts of this application.

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

[0027] 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.

[0028] 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 those 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.).

[0029] In the technical solution of this application, the user information (including but not limited to user personal information, user image information, user device information, such as location information) and data (including but not limited to data used for analysis, stored data, and displayed data) involved are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, storage, use, processing, transmission, provision, application, and application of related data all comply with relevant laws, regulations, and standards, take necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation entry points for users to choose to authorize or refuse.

[0030] In scenarios involving automated decision-making using personal information, the methods, devices, and systems provided in this application all offer users corresponding entry points for choosing to agree to or reject the automated decision-making results. If the user chooses to reject, the process proceeds to the expert decision-making stage. Here, "automated decision-making" refers to the activity of automatically analyzing and evaluating an individual's behavioral habits, interests, or economic, health, and credit status through computer programs, and then making a decision. Here, "expert decision-making" refers to the activity of making decisions by personnel who specialize in a particular field, possess specialized experience, knowledge, and skills, and have reached a certain level of professional expertise.

[0031] Figure 1 The illustration schematically depicts an application scenario diagram of a production scheme generation method, apparatus, equipment, medium, and program product according to an embodiment of this application.

[0032] like Figure 1 As shown, application scenario 100 according to this embodiment may include a first terminal device 101, a second terminal device 102, a third terminal device 103, a network 104, and a server 105. The network 104 serves as a medium for providing communication links between the first terminal device 101, the second terminal device 102, the third terminal device 103, and the server 105. The network 104 may include various connection types, such as wired or wireless communication links, or fiber optic cables, etc.

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

[0034] The first terminal device 101, the second terminal device 102, and the third terminal device 103 can be various electronic devices with displays and support web browsing, including but not limited to smartphones, tablets, laptops, and desktop computers.

[0035] Server 105 can be a server that provides various services, such as a backend management server that supports websites browsed by users using the first terminal device 101, the second terminal device 102, and the third terminal device 103 (this is just an example). 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.

[0036] It should be noted that the production scheme generation method provided in this application embodiment can generally be executed by server 105. Correspondingly, the production scheme generation apparatus provided in this application embodiment can generally be located in server 105. The production scheme generation method provided in this application embodiment can also be executed by a server or server cluster that is different from server 105 and capable of communicating with the first terminal device 101, the second terminal device 102, the third terminal device 103, and / or server 105. Correspondingly, the production scheme generation apparatus provided in this application embodiment can also be located in a server or server cluster that is different from server 105 and capable of communicating with the first terminal device 101, the second terminal device 102, the third terminal device 103, and / or server 105.

[0037] 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.

[0038] The following will be based on Figure 1 The described scene, through Figures 2-5 The method for generating a production plan according to the embodiments of this application will be described in detail.

[0039] Figure 2 One of the flowcharts illustrating a production scheme generation method according to an embodiment of this application is shown schematically.

[0040] like Figure 2 As shown, the production scheme generation method according to the embodiment of this application includes: operations S201 to S203.

[0041] Operation S201 retrieves the installation packages for each version of the target application; each installation package is parsed to obtain the corresponding operation queue; the operation queue represents the execution order of multiple installation operations involved in the installation of the target application.

[0042] Specifically, the process involves acquiring all installation packages of the target application from its initial version to the current version. Each version's installation package contains deployment files and related configuration information for different stages of the software installation. By parsing the installation files of each package, multiple installation operations involved in the installation process are extracted, and the execution order of these operations is determined, forming an operation queue. This operation queue clearly defines the sequence of tasks during software installation.

[0043] Operation S202 determines at least one first installation package from the installation packages of each historical version based on the operation queue corresponding to each installation package.

[0044] Specifically, the operation queue of the current version installation package is compared with the operation queue of the historical version installation packages. According to the preset comparison rules, at least one installation package with high similarity to the current version is found from the historical versions and used as the reference basis for generating the production plan, thus obtaining the first installation package.

[0045] Operation S203: Based on the deployment plan of at least one first installation package, generate a deployment plan for the current version of the installation package; wherein, when the deployment plan for the current version of the installation package is executed, at least some of the installation operations in the operation queue corresponding to the first installation package are executed.

[0046] Specifically, based on the deployment plan of the first installation package, a deployment plan suitable for the current version is generated, taking into account the characteristics and requirements of the current version's installation package. When executing the current version's deployment plan, at least some of the installation operations from the first installation package's operation queue will be included, thus reusing historical experience and reducing repetitive work.

[0047] For example, the target application is a bank's financial transaction software, currently preparing to release version V3.0. First, the installation packages for each version of the application from V1.0 to V3.0 are obtained. After parsing the V1.0 installation package, it is found that its operation queue is as follows: first, the database driver is installed; then, the database is initialized; next, the business logic layer components are installed; and finally, the front-end interface is deployed. Similar parsing is performed on the installation packages for other versions to obtain their respective operation queues.

[0048] By comparing the V3.0 installation package with the operation queues of previous versions, it was found that the V2.0 operation queue was quite similar to V3.0 in terms of database-related operations and the installation order of business logic layer components. Therefore, the V2.0 installation package was determined to be the first installation package. Based on the production plan for the V2.0 version, and considering that V3.0 adds new reporting functionality, the production plan for the V3.0 installation package was generated by retaining the database and business logic layer-related operations while writing corresponding installation operations for the new reporting functionality.

[0049] By adopting the above method, compared with manually writing production plans, we can quickly generate the current version's production plan by utilizing historical version information, reducing the workload of manual writing, improving the speed of version delivery, ensuring that business products can be delivered on time, and meeting the business needs of rapid iteration in the fintech field.

[0050] Figure 3 The second flowchart illustrating a method for generating a production plan according to an embodiment of this application is shown schematically.

[0051] like Figure 3 As shown, according to an embodiment of this application, in operation S201, each installation package is parsed to obtain the operation queue corresponding to each installation package, including: operation S301 to operation S302.

[0052] Operation S301 parses each installation package according to its format to obtain the installation strategy file for each package. The installation strategy file represents the multiple installation operations involved when the target application is installed.

[0053] Operation S302 processes the installation strategy file using a decision tree classification algorithm to obtain an operation queue of multiple installation operations.

[0054] Specifically, the installation package format is identified, and appropriate parsing methods are used based on the characteristics of different formats to extract multiple specific installation operations during the installation process, which are recorded in the installation strategy file. A decision tree classification algorithm is then used to analyze and sort the installation operations in the installation strategy file. The decision tree determines the order of each operation based on factors such as logical relationships and dependencies between operations, thereby generating an ordered operation queue, making the installation process more logical and rational.

[0055] For example, for an installation package of financial trading software, if it's a V2.5 version image package, the installation strategy file is parsed according to a preset image package parsing method. This file records operations such as loading the base image, configuring the system environment, and installing each functional module. If it's a V2.2 version compressed package, the installation strategy file is formed by parsing its directory structure and determining the installation operations corresponding to the files in each directory. Taking the V2.5 version installation strategy file as an example, through decision tree classification algorithm analysis, considering that system environment configuration must be completed before functional module installation, and that some functional modules have sequential dependencies, the operation queue is finally determined. For example, the base image is loaded first, followed by system environment configuration, and then each functional module is installed sequentially according to dependency order.

[0056] By adopting the above method, specific parsing methods are used to obtain installation operation information for different format installation packages. Then, a decision tree classification algorithm is used to sort these operations reasonably to form an operation queue. This ensures that the installation logic can be accurately sorted out regardless of the installation package format, providing a reliable basis for the subsequent generation of production plans.

[0057] According to the embodiments of this application, each installation package is parsed to obtain the installation strategy file for each installation package, including steps A and B.

[0058] Step A: If the installation package is an image package in a preset format, the installation package is parsed based on the abstract syntax tree to obtain the installation strategy file of the installation package.

[0059] Specifically, when the installation package is a preset format image package, an abstract syntax tree is used to transform the file structure, instructions, etc. within the image package into a tree structure for analysis. By traversing the tree structure, the installation operation corresponding to each node is determined, as well as the hierarchical relationship and sequence between operations. Finally, an installation strategy file is compiled, which records in detail all the operations required for the installation of the image package and their logical relationships.

[0060] Step B: If the installation package is a compressed package in a preset format, the installation package is parsed based on the directories at each level to obtain the installation strategy file.

[0061] Specifically, for compressed packages with preset formats, such as the first or second compression format, the process starts from the root directory of the compressed package and analyzes each directory and its contained files layer by layer. Based on the file type, name, and directory location, the corresponding operation for each file during the installation process is determined, such as the program installation operation for executable files, the parameter setting operation for configuration files, etc., thereby forming an installation strategy file that records the specific operation process of the compressed package installation.

[0062] For example, for a compressed package in the first compression format, the installation operation of the business system startup program corresponding to the executable file is determined from the "bin" directory under the root directory, and the system parameter configuration operation is determined from the configuration file in the "config" directory. The installation strategy file is sorted out according to the directory hierarchy, and the operation process is recorded, such as first decompressing the file to the specified directory, then executing the installer in the "bin" directory, and finally performing the parameter configuration in the "config" directory.

[0063] By adopting the above method, and considering the different structural characteristics of image packages and compressed packages, we can fully extract installation operation information from different format installation packages by using abstract syntax tree parsing for image packages and directory-based parsing for compressed packages, respectively. This allows us to accurately generate installation strategy files and provide accurate data for the generation of subsequent operation queues and the formulation of production plans.

[0064] According to an embodiment of this application, in operation S202, based on the operation queue corresponding to each installation package, at least one first installation package is determined from the installation packages of each historical version, including:

[0065] Based on the operation queue corresponding to each installation package, determine the similarity between the current version of the installation package and the installation packages of each historical version; determine at least one first installation package from the installation packages of each historical version, and the similarity between the first installation package and the current version of the installation package meets the preset similarity range.

[0066] Specifically, the operation queue of the current version installation package is compared with the operation queues of each historical version installation package. The similarity between the operation queues is analyzed from multiple dimensions, including operation content, order, and dependencies. The similarity is quantified numerically for comparison and selection. Based on a preset similarity range, at least one installation package whose similarity to the current version installation package falls within this range is selected from all historical version installation packages as a reference for generating the subsequent production plan, i.e., the first installation package. In the embodiments of this application, the setting of the preset range needs to comprehensively consider the actual situation of software version iteration and the feasibility of reusing the production plan.

[0067] By using the above method, the similarity between the current version and the historical version installation package operation queue is quantified, and the first installation package is selected according to a preset range. This allows for the accurate identification of versions similar to the current version that have reusable production solutions from among numerous historical versions.

[0068] Figure 4 The flowchart illustrating the third method for generating a production plan according to an embodiment of this application is shown schematically.

[0069] like Figure 4 As shown, according to an embodiment of this application, the similarity between the current version of the installation package and the installation packages of each historical version is determined based on the operation queue corresponding to each installation package, including: operations S401 to S403.

[0070] Operation S401 retrieves at least one feature value from the operation queue corresponding to each installation package.

[0071] Operation S402 determines the feature vector corresponding to each installation package based on at least one feature value.

[0072] Operation S403 calculates the similarity between the current version of the installation package and the installation packages of each historical version based on the cosine similarity between the feature vectors of each installation package.

[0073] Specifically, key information that represents the characteristics of the operation queue is extracted from the operation queue as feature values. For example, feature values ​​can be selected from multiple aspects such as operation strategy, operation order, rollback operation, and execution environment to characterize the operation queue and provide a data foundation for subsequent similarity calculation.

[0074] Furthermore, the obtained feature values ​​are quantized and combined into a vector in a certain order to reflect the characteristics of the installation package operation queue, so that the operation queues of different installation packages can be compared in vector form.

[0075] Finally, the cosine similarity algorithm is used to calculate the cosine value of the angle between the feature vector of the current version of the installation package and the feature vectors of each historical version of the installation package, as a quantitative indicator of similarity. The closer the value of the cosine value is to 1, the more similar the operation queues of the two installation packages are. This method accurately measures the degree of similarity between installation packages.

[0076] For example, consider the installation package operation queues for versions V3.0 and V2.4. Obtain the feature values ​​of the V3.0 operation queue, such as the operation strategy adopting a new distributed deployment strategy (quantized to 0.8), the operation sequence prioritizing front-end interface preloading (quantized to 0.6), the rollback operation for a critical installation operation being deleting temporary configuration and re-downloading the configuration file (quantized to 0.7), and the execution environment supporting the latest cloud server platform (quantized to 0.9), forming the feature vector [0.8, 0.6, 0.7, 0.9]. Similarly, obtain the feature vector for version V2.4, assuming it is [0.4, 0.5, 0.3, 0.6]. Calculate the similarity between the two feature vectors using the cosine similarity algorithm. Assuming the result is 0.65, this indicates that the similarity between the V3.0 and V2.4 installation package operation queues is 0.65.

[0077] By adopting the above method, the key characteristics of the operation queue are transformed into feature values ​​and formed into feature vectors. The cosine similarity algorithm is used to quantify the similarity between installation packages, and the similarity between the operation queues of each installation package is comprehensively and objectively measured from multiple dimensions.

[0078] According to an embodiment of this application, after operation S403, operation S404 is also included.

[0079] Operation S404 discretizes each similarity and outputs one of the first similarity, second similarity, and third similarity; wherein, the first similarity indicates that the deployment plan of the current version of the installation package is the same as that of the historical version of the installation package; the second similarity indicates that the deployment plan of the current version of the installation package is partially the same as that of the historical version of the installation package; and the third similarity indicates that the deployment plan of the current version of the installation package is different from that of the historical version of the installation package.

[0080] Specifically, the continuous similarity values ​​obtained through the cosine similarity algorithm are divided into different discrete categories according to certain rules, thereby making the similarity results more intuitive, easier to understand and apply, and used in the generation strategy of subsequent production plans.

[0081] For example, the discretization rules are configured as follows: a similarity greater than or equal to 0.9 is the first similarity, 0.7-0.89 is the second similarity, and less than 0.7 is the third similarity. For the core banking business system, the similarity calculation result of the operation queue of the installation package of version V3.0 and version V2.3 is 0.92. After discretization, the first similarity is output, indicating that the production schemes of versions V3.0 and V2.3 are the same; the similarity between versions V3.0 and V2.5 is 0.8, and the second similarity is output, indicating that the production schemes are partially the same; the similarity between versions V3.0 and V1.5 is 0.6, and the third similarity is output, indicating that the production schemes are different.

[0082] According to an embodiment of this application, in operation S203, a production plan for the current version of the installation package is generated based on at least one production plan for the first installation package.

[0083] For example, if the similarity between the current version of the installation package and the first installation package meets the first similarity requirement, the deployment plan for the current version of the installation package is directly generated based on the deployment plan for the first installation package.

[0084] Specifically, when the similarity between the current version installation package and the first installation package indicates that their deployment plans are the same, the deployment plan of the first installation package can be used as a template. Only a small amount of version-related information (such as version number, software name, etc.) needs to be modified to generate the deployment plan for the current version. This can maximize the reuse of historical experience and save time and manpower.

[0085] For example, if the similarity between the current version of the installation package and the first installation package meets the second similarity requirement, a production deployment plan for the current version of the installation package is generated based on some installation operations in the operation queue of the first installation package.

[0086] Specifically, if the current version and the first installation package show the same production plan, the installation operations that are similar to the current version are selected from the operation queue of the first installation package. Then, for the new or modified functions in the current version, the corresponding installation operations are called. Finally, they are integrated to form the production plan of the current version, which not only utilizes the experience of the previous version, but also takes into account the characteristics of the current version.

[0087] By employing the above method, different deployment scheme generation strategies are adopted based on the different similarity categories between the current version and the first installation package. When the similarity is high, the scheme is directly reused; when there is partial similarity, some operations are reused and new operations are added. This approach not only efficiently utilizes the content of deployment schemes from previous versions but also flexibly adapts to changes in the current version, quickly and accurately generating deployment schemes that meet the requirements.

[0088] According to embodiments of this application, the characteristic values ​​of the operation queue include at least one of the following:

[0089] Operation strategy for multiple installation operations in the operation queue;

[0090] The order of operations for multiple installation operations in the operation queue;

[0091] Each installation operation in the operation queue corresponds to a rollback operation. A rollback operation represents the next operation to be executed if the corresponding installation operation fails.

[0092] The execution environment for operating the queue.

[0093] Operational strategies refer to the specific methods and approaches used for each operation during the installation process. Different operational strategies affect the efficiency, stability, and final performance of the target application. For example, operational strategies may include: Platform as a Service (PaaS) deployment strategies, database execution strategies, load balancing strategies, and batch processing strategies. PaaS deployment strategies are used for containerized deployment scenarios, database execution strategies are used for executing table creation statements and data migration scenarios, load balancing strategies are used for configuring forwarding rules, and batch processing strategies are used for adding or changing batches of programs.

[0094] The operation sequence specifies the order in which each installation operation is performed, ensuring the correct installation and operation of the target application. For example, the database driver must be installed before database connection and data import operations; otherwise, the installation will fail.

[0095] Rollback refers to the process of reverting an application to its previous state and exploring alternative solutions when an installation operation fails. For example, if a file copying operation fails during software module installation, a rollback operation might delete the incomplete copied file and record the error message for later troubleshooting.

[0096] The execution environment includes the hardware environment (such as server configuration and storage devices) and software environment (such as operating system version and middleware version) required for application installation and operation. Different execution environment requirements may limit the compatibility and scalability of the software; for example, some new features may require support from specific versions of the operating system or database management system.

[0097] By employing the above methods, operation strategies, operation sequences, rollback operations, and execution environments are used as feature values ​​for the operation queue, comprehensively covering the key factors affecting software deployment and operation during the installation process. Characterizing the operation queue from different perspectives provides targeted information for accurately calculating the similarity between installation packages, thereby helping to select suitable historical version installation packages.

[0098] Figure 5 A schematic block diagram of a production apparatus according to an embodiment of this application is shown.

[0099] Based on the above-mentioned method for generating a production plan, this application provides an apparatus for generating a production plan, which will be described below in conjunction with... Figure 5 The device is described in detail.

[0100] like Figure 5 As shown, the production scheme generation device 400 of this embodiment includes an installation package parsing module 510, an installation package filtering module 520, and a scheme generation module 530.

[0101] The installation package parsing module 510 is used to obtain the installation packages for each version of the target application; parse each installation package to obtain the operation queue corresponding to each installation package; the operation queue represents the execution order of multiple installation operations involved in the installation of the target application.

[0102] The installation package filtering module 520 is used to determine at least one first installation package from the installation packages of each historical version based on the operation queue corresponding to each installation package.

[0103] The scheme generation module 530 is used to generate a production scheme for the current version of the installation package based on the production scheme of at least one first installation package; wherein, when the production scheme of the current version of the installation package is executed, at least some of the installation operations in the operation queue corresponding to the first installation package are executed.

[0104] According to embodiments of this disclosure, the installation package parsing module 510 is further configured to:

[0105] Based on the format of the installation package, each installation package is parsed to obtain the installation strategy file for each package. The installation strategy file represents the multiple installation operations involved when the target application is installed. The installation strategy file is processed by a decision tree classification algorithm to obtain the operation queue of multiple installation operations.

[0106] According to embodiments of this disclosure, the installation package parsing module 510 is further configured to:

[0107] When the installation package is a pre-defined image package, the installation package is parsed based on an abstract syntax tree to obtain the installation strategy file. When the installation package is a pre-defined compressed package, the installation package is parsed based on the directories at each level to obtain the installation strategy file.

[0108] According to embodiments of this disclosure, the installation package filtering module 520 is further configured to:

[0109] Based on the operation queue corresponding to each installation package, determine the similarity between the current version of the installation package and the installation packages of each historical version; determine at least one first installation package from the installation packages of each historical version, and the similarity between the first installation package and the current version of the installation package meets the preset similarity range.

[0110] According to embodiments of this disclosure, the installation package filtering module 520 is further configured to:

[0111] Obtain at least one feature value of the operation queue corresponding to each installation package; determine the feature vector corresponding to each installation package based on the at least one feature value; obtain the similarity between the current version of the installation package and the installation packages of each historical version based on the cosine similarity between the feature vectors of each installation package.

[0112] According to embodiments of this disclosure, the installation package filtering module 520 is further configured to:

[0113] Each similarity is discretized, and one of the first, second, and third similarities is output. The first similarity indicates that the deployment plan of the current version of the installation package is the same as that of the historical version of the installation package; the second similarity indicates that the deployment plan of the current version of the installation package is partially the same as that of the historical version of the installation package; and the third similarity indicates that the deployment plan of the current version of the installation package is different from that of the historical version of the installation package.

[0114] According to embodiments of this disclosure, the installation package filtering module 520 is further configured to:

[0115] If the similarity between the current version of the installation package and the first installation package meets the first similarity requirement, the deployment plan for the current version of the installation package is directly generated based on the deployment plan for the first installation package; if the similarity between the current version of the installation package and the first installation package meets the second similarity requirement, the deployment plan for the current version of the installation package is generated based on some installation operations in the operation queue of the first installation package.

[0116] According to embodiments of this disclosure, the characteristic values ​​of the operation queue include at least one of the following:

[0117] Operation strategy for multiple installation operations in the operation queue;

[0118] The order of operations for multiple installation operations in the operation queue;

[0119] Each installation operation in the operation queue corresponds to a rollback operation. A rollback operation represents the next operation to be executed if the corresponding installation operation fails.

[0120] The execution environment for operating the queue.

[0121] According to embodiments of this application, any multiple modules among the parsing module 510, the installation package filtering module 520, and the scheme generation module 530 can be merged into one module, or any one of these modules can be split into multiple modules. Alternatively, at least some of the functions of one or more of these modules can be combined with at least some of the functions of other modules and implemented in one module. According to embodiments of this application, at least one of the parsing module 510, the installation package filtering module 520, and the scheme generation module 530 can 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 any other reasonable means of integrating or packaging circuitry, or implemented in software, hardware, or firmware, or in any appropriate combination of any of these three implementation methods. Alternatively, at least one of the parsing module 510, the installation package filtering module 520, and the scheme generation module 530 can be at least partially implemented as a computer program module, which can perform corresponding functions when the computer program module is run.

[0122] Figure 6 A block diagram schematically illustrates an electronic device suitable for implementing a production plan according to an embodiment of this application.

[0123] like Figure 6 As shown, an electronic device 600 according to an embodiment of this application includes a processor 601, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 602 or a program loaded from a storage portion 608 into a random access memory (RAM) 603. The processor 601 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 601 may also include onboard memory for caching purposes. The processor 601 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of this application.

[0124] RAM 603 stores various programs and data required for the operation of electronic device 600. Processor 601, ROM 602, and RAM 603 are interconnected via bus 604. Processor 601 executes various operations of the method flow according to embodiments of this application by executing programs in ROM 602 and / or RAM 603. It should be noted that programs may also be stored in one or more memories other than ROM 602 and RAM 603. Processor 601 may also execute various operations of the method flow according to embodiments of this application by executing programs stored in one or more memories.

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

[0126] This application 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, which, when executed, implement the watermark generation method according to the embodiments of this application.

[0127] According to embodiments of this application, the computer-readable storage medium can be a non-volatile computer-readable storage medium, such as including 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 application, the computer-readable storage medium can be any tangible medium containing or storing 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 application, the computer-readable storage medium may include ROM 602 and / or RAM 603 and / or one or more memories other than ROM 602 and RAM 603 described above.

[0128] Embodiments of this application 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 enables the computer system to implement the watermark generation method provided in the embodiments of this application.

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

[0130] 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 downloaded and installed via the communication section 609, and / or installed from the removable medium 611. 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.

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

[0132] According to embodiments of this application, program code for executing the computer programs provided in the embodiments of this application 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 be executed 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).

[0133] 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 application. 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.

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

Claims

1. A method for generating a production plan, characterized in that, The method includes: Obtain the installation packages for each version of the target application; parse each installation package to obtain the operation queue corresponding to each installation package; the operation queue represents the execution order of multiple installation operations involved in the installation of the target application; Based on the operation queue corresponding to each installation package, at least one first installation package is determined from the installation packages of each historical version; Based on at least one deployment plan for the first installation package, a deployment plan for the current version of the installation package is generated; wherein, when the deployment plan for the current version of the installation package is executed, at least a portion of the installation operations in the operation queue corresponding to the first installation package are executed.

2. The method according to claim 1, characterized in that, The process of parsing each installation package to obtain the corresponding operation queue includes: According to the format of the installation package, each installation package is parsed to obtain the installation strategy file of each installation package. The installation strategy file represents multiple installation operations involved when the target application is installed. The installation strategy file is processed by a decision tree classification algorithm to obtain the operation queue of the multiple installation operations.

3. The method according to claim 2, characterized in that, Each of the installation packages is parsed to obtain the installation strategy file for each of the installation packages, including: If the installation package is an image package in a preset format, the installation package is parsed based on an abstract syntax tree to obtain the installation strategy file of the installation package; If the installation package is a compressed package in a preset format, the installation package is parsed based on the directories at each level of the installation package to obtain the installation strategy file of the installation package.

4. The method according to claim 1, characterized in that, The step of determining at least one first installation package from the installation packages of each historical version based on the operation queue corresponding to each installation package includes: Based on the operation queue corresponding to each installation package, determine the similarity between the current version of the installation package and the installation packages of each historical version; At least one first installation package is determined from the installation packages of various historical versions, and the similarity between the first installation package and the installation package of the current version meets a preset similarity range.

5. The method according to claim 4, characterized in that, The step of determining the similarity between the current version of the installation package and the installation packages of each historical version based on the operation queue corresponding to each installation package includes: Obtain at least one feature value from the operation queue corresponding to each installation package; Based on at least one feature value, determine the feature vector corresponding to each installation package; Based on the cosine similarity between the feature vectors of each installation package, the similarity between the current version of the installation package and the installation packages of each historical version is obtained.

6. The method according to claim 5, characterized in that, The method further includes: Discretize each similarity score and output one of the first, second, and third similarity scores; The first similarity indicates that the deployment scheme of the current version of the installation package is the same as that of the historical version of the installation package; the second similarity indicates that the deployment scheme of the current version of the installation package is partially the same as that of the historical version of the installation package; and the third similarity indicates that the deployment scheme of the current version of the installation package is different from that of the historical version of the installation package.

7. The method according to claim 6, characterized in that, The step of generating a deployment plan for the current version of the installation package based on at least one deployment plan for the first installation package includes: If the similarity between the current version of the installation package and the first installation package meets the first similarity requirement, the production plan for the current version of the installation package is directly generated based on the production plan of the first installation package. If the similarity between the current version of the installation package and the first installation package meets the second similarity requirement, a production deployment plan for the current version of the installation package is generated based on a portion of the installation operations in the operation queue of the first installation package.

8. The method according to claim 5, wherein the characteristic values ​​of the operation queue include at least one of the following: The operation strategy for multiple installation operations in the operation queue; The order of operations for multiple installation operations in the operation queue; The rollback operation corresponding to each installation operation in the operation queue represents the next operation to be executed if the corresponding installation operation fails. The execution environment of the operation queue.

9. A device for generating a production plan, characterized in that, The device includes: The installation package parsing module is used to obtain the installation packages for various versions of the target application; parse each installation package to obtain the operation queue corresponding to each installation package; the operation queue represents the execution order of multiple installation operations involved in the installation of the target application; The installation package filtering module is used to determine at least one first installation package from the installation packages of each historical version based on the operation queue corresponding to each installation package. The scheme generation module is used to generate a production scheme for the current version of the installation package based on at least one production scheme for the first installation package; wherein, when the production scheme for the current version of the installation package is executed, at least a portion of the installation operations in the operation queue corresponding to the first installation package are executed.

10. An electronic device, comprising: One or more processors; Memory, used to store one or more computer programs. The characteristic feature is that the one or more processors execute the one or more computer programs to implement the steps of the method according to any one of claims 1 to 8.

11. A computer-readable storage medium having a computer program or instructions stored thereon, characterized in that, When the computer program or instructions are executed by a processor, they implement the steps of the method according to any one of claims 1 to 8.

12. A computer program product, comprising a computer program or instructions, characterized in that, When the computer program or instructions are executed by a processor, they implement the steps of the method according to any one of claims 1 to 8.

Images