Environment building processing method and device

Abstract

The invention discloses an environment building processing method and device, and relates to the technical field of operation and maintenance. A specific embodiment of the method comprises the following steps: acquiring an environment resource demand list to import the environment resource demand list into an application system hierarchical architecture model to obtain application system hierarchical architecture information; for selection of one or more pieces of application system information, generating a machine node creating instruction for each application system based on deployment unit information and machine node configuration information; sending the machine node creating instruction to the first building party, so that the first building party executes machine node creating operation under the deployment unit to obtain machine node information; and in response to completion of creation of the machine nodes under the deployment unit, generating a basic software installation instruction based on the machine node information and the basic software information, and sending the basic software installation instruction to the second building party, so that the second building party executes basic software installation operation under each machine node. According to the embodiment, full-process automatic management from resource requirements to environment building completion is realized.

Description

Technical Field

[0001] The present invention relates to the field of operation and maintenance technology, and in particular to an environment construction processing method and device. Background Art

[0002] With the rapid development and popularization of computer technology, the number of enterprise systems, the number of machine nodes, and the amount of basic software that needs to be installed are constantly increasing. In addition to the formal production environment, enterprises generally need to build multiple IT (Information Technology) environments for different business needs, such as integrated test environment, performance test environment, user test environment, disaster recovery environment, etc. This requires operation and maintenance personnel to build the environment according to the resource configuration requirements of each system, including creating machine nodes and installing basic software. After the environment is built, the team of each system will continue to install and deploy the application system.

[0003] Although with the rapid development of cloud-native technology, some systems have been converted to containerized deployment, and the system is responsible for the image itself, and there is no need to prepare a basic environment for it, there are still a considerable proportion of systems that are not suitable for containers and require the support of machine (physical machine, virtual machine) nodes and basic software. The importance of environment construction is very high, such as creating a new environment or rebuilding an existing environment, and generally the time is tight and the task is heavy. This requires certain methods to quickly complete the creation of machine nodes and the installation of basic software, but the existing methods generally have many manual links, are prone to errors, and have a large workload. Summary of the invention

[0004] In view of this, an embodiment of the present invention provides an environment construction processing method and device, which can solve the problems of reliance on manual labor, high error rate and heavy workload in the prior art, and realize the rapid completion of machine node creation and basic software installation.

[0005] To achieve the above-mentioned purpose, according to one aspect of an embodiment of the present invention, there is provided an environment construction processing method, comprising: obtaining an environmental resource requirement list to import into an application system hierarchical architecture model, and obtaining application system hierarchical architecture information; wherein the application system hierarchical architecture information comprises application system information, deployment unit information, machine node configuration information and basic software information; in response to a selection operation on one or more application system information, for each selected application system, generating a machine node creation instruction based on the deployment unit information and the machine node configuration information; sending the machine node creation instruction to a first builder, so that the first builder performs a machine node creation operation under the deployment unit and obtains machine node information; when the machine node is created under the deployment unit, generating a basic software installation instruction based on the machine node information and the basic software information and sending it to a second builder, so that the second builder performs a basic software installation operation under each machine node.

[0006] Optionally, the generating of the instruction to create a machine node based on the deployment unit information and the machine node configuration information includes: determining the deployment unit according to the deployment unit information, obtaining the deployment log of the deployment unit, and obtaining the deployment status from the deployment log; in response to the deployment status being undeployed, generating the instruction to create a machine node based on the deployment unit information and the machine node configuration information; in response to the deployment status being deploying, returning a reminder message for repeated deployment; in response to the deployment status being deployed, obtaining the historical deployment unit information closest to the current one from the deployment log, comparing the deployment unit information with the historical deployment unit information, and generating corresponding instructions according to the comparison result.

[0007] Optionally, generating corresponding instructions according to the comparison results includes: when the comparison results are the same, returning a duplicate deployment prompt message; when the comparison result is greater than, calculating the difference between the deployment unit information and the historical deployment unit information, and generating a create machine node instruction based on the difference and the machine node configuration information; when the comparison result is less than, determining the machine node to be deleted based on the historical deployment unit information and the deployment unit information, and generating a delete machine node instruction.

[0008] Optionally, the method further includes: receiving a request to delete a machine node, obtaining application system information, deployment unit information and an identifier of a machine node to be deleted, or application system information, deployment unit information and the number of machine nodes to be deleted from the request to delete a machine node; determining an application system according to the application system information, and determining a deployment unit under the application system according to the deployment unit information; deleting a machine node corresponding to the identifier of the machine node to be deleted from the deployment unit according to the identifier of the machine node to be deleted; or deleting a machine node corresponding to the number of machine nodes to be deleted from the deployment unit according to the number of machine nodes to be deleted.

[0009] Optionally, the deployment unit information includes the number of nodes, and generating the instructions for creating machine nodes based on the deployment unit information and the machine node configuration information includes the following methods: generating the instructions for creating machine nodes based on the number of nodes and the machine node configuration information; generating the same number of instructions for creating machine nodes as the number of nodes based on the machine node configuration information.

[0010] Optionally, the deployment unit information includes the deployment unit type. After obtaining the application system hierarchical architecture information, the method further includes: determining the configuration information model and software information model pre-created for the deployment unit type or deployment unit; storing the machine node configuration information in the configuration information model to obtain configuration information model data; storing the basic software information in the software information model to obtain software information model data.

[0011] Optionally, after obtaining the application system hierarchical architecture information, the method also includes: tracking the creation status of each machine node under the deployment unit, and recording the results in the database in response to the completion of the creation of each machine node; and tracking the installation status of the basic software under each machine node, and recording the results in the database in response to the completion of the installation of each basic software.

[0012] To achieve the above-mentioned purpose, according to another aspect of an embodiment of the present invention, there is provided an environment construction processing device, comprising: a system query module, used to obtain an environmental resource requirement list to import into an application system hierarchical architecture model, and obtain application system hierarchical architecture information; wherein the application system hierarchical architecture information includes application system information, deployment unit information, machine node configuration information and basic software information; an information determination module, used to respond to a selection operation on one or more application system information; an instruction module, used to generate a machine node creation instruction for each selected application system based on the deployment unit information and the machine node configuration information; the machine node creation instruction is sent to a first builder, so that the first builder performs a machine node creation operation under the deployment unit and obtains machine node information; in response to the completion of the machine node creation under the deployment unit, based on the machine node information and the basic software information, a basic software installation instruction is generated and sent to a second builder, so that the second builder performs a basic software installation operation under each machine node.

[0013] Optionally, the instruction module is used to: determine the deployment unit according to the deployment unit information, obtain the deployment log of the deployment unit, and obtain the deployment status from the deployment log; in response to the deployment status being undeployed, generate a create machine node instruction based on the deployment unit information and the machine node configuration information; in response to the deployment status being deploying, return a repeat deployment prompt message; in response to the deployment status being deployed, obtain the historical deployment unit information closest to the current one from the deployment log, compare the deployment unit information with the historical deployment unit information, and generate corresponding instructions according to the comparison result.

[0014] Optionally, the instruction module is used to: return a duplicate deployment prompt message when the comparison result is the same; calculate the difference between the deployment unit information and the historical deployment unit information when the comparison result is greater than, and generate a create machine node instruction based on the difference and the machine node configuration information; and determine the machine node to be deleted based on the historical deployment unit information and the deployment unit information when the comparison result is less than, and generate a delete machine node instruction.

[0015] Optionally, the device also includes a deletion module, which is used to: receive a request to delete a machine node, obtain application system information, deployment unit information and an identifier of a machine node to be deleted, or application system information, deployment unit information and the number of machine nodes to be deleted from the request to delete a machine node; determine the application system according to the application system information, and determine the deployment unit under the application system according to the deployment unit information; delete the machine node corresponding to the identifier of the machine node to be deleted from the deployment unit according to the identifier of the machine node to be deleted; or delete the machine nodes corresponding to the number of machine nodes to be deleted from the deployment unit according to the number of machine nodes to be deleted.

[0016] Optionally, the deployment unit information includes the number of nodes, and the instruction module includes the following methods: generating instructions for creating machine nodes based on the number of nodes and machine node configuration information; and generating instructions for creating machine nodes equal to the number of nodes based on the machine node configuration information.

[0017] Optionally, the deployment unit information includes the deployment unit type, and the system query module is further used to: determine the configuration information model and software information model created in advance for the deployment unit type or deployment unit; store the machine node configuration information in the configuration information model to obtain configuration information model data; store the basic software information in the software information model to obtain software information model data.

[0018] Optionally, the device also includes a tracking module, which is used to: track the creation status of each machine node under the deployment unit; track the installation status of the basic software under each machine node; and a storage module, which is used to: record the results to the database in response to the completion of the creation of each machine node; and record the results to the database in response to the completion of the installation of each basic software.

[0019] To achieve the above objective, according to another aspect of an embodiment of the present invention, an environment building processing electronic device is provided.

[0020] The electronic device of an embodiment of the present invention includes: one or more processors; a storage device for storing one or more programs, and when the one or more programs are executed by the one or more processors, the one or more processors implement any of the above-mentioned environment building processing methods.

[0021] To achieve the above objective, according to another aspect of an embodiment of the present invention, a computer-readable medium is provided, on which a computer program is stored, and when the program is executed by a processor, any of the above-mentioned environment building processing methods is implemented.

[0022] To achieve the above object, according to another aspect of an embodiment of the present invention, a computing program product is provided. A computing program product of an embodiment of the present invention includes a computer program, and when the program is executed by a processor, the environment building processing method provided by an embodiment of the present invention is implemented.

[0023] According to the solution provided by the present invention, one embodiment of the above invention has the following advantages or beneficial effects: batch construction can be realized, and the efficiency of environment construction is significantly improved by automatically generating and executing instructions for creating machine nodes and installing basic software instructions, reducing manual links and errors caused by manual work.

[0024] The further effects of the above-mentioned non-conventional optional manner will be described below in conjunction with the specific implementation manner. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] The accompanying drawings are used to better understand the present invention and do not constitute an improper limitation of the present invention.

[0026] Figure 1 This is a schematic diagram of the main process of an environment building processing method according to an embodiment of the present invention;

[0027] Figure 2 is a flow chart of an optional environment building processing method according to an embodiment of the present invention;

[0028] Figure 3 is a schematic diagram of the architecture of an application system, a deployment unit, a configuration information model, and a software information model according to an embodiment of the present invention;

[0029] Figure 4 is a flow chart of another optional environment construction processing method according to an embodiment of the present invention;

[0030] FIG5 (a) is a schematic diagram of a flow chart of a specific environment building processing method according to an embodiment of the present invention;

[0031] FIG5( b ) is a flow chart of another specific environment building processing method according to an embodiment of the present invention;

[0032] Figure 6 is a schematic diagram of main modules of an environment building processing device according to an embodiment of the present invention;

[0033] Figure 7 is an exemplary system architecture diagram to which embodiments of the present invention may be applied;

[0034] Figure 8 It is a schematic diagram of the structure of a computer system of a mobile device or a server suitable for implementing an embodiment of the present invention. DETAILED DESCRIPTION

[0035] The following is a description of exemplary embodiments of the present invention in conjunction with the accompanying drawings, including various details of the embodiments of the present invention to facilitate understanding, which should be considered as merely exemplary. Therefore, it should be recognized by those of ordinary skill in the art that various changes and modifications may be made to the embodiments described herein without departing from the scope and spirit of the present invention. Similarly, for clarity and conciseness, the description of well-known functions and structures is omitted in the following description.

[0036] It should be noted that in the embodiments of the present application, certain software, components, models and other existing solutions in the industry may be mentioned, and they should be regarded as exemplary. Their purpose is only to illustrate the feasibility of implementing the technical solution of the present application, but it does not mean that the applicant has or will necessarily use the solution.

[0037] In the absence of conflict, the embodiments and features of the embodiments of the present invention can be combined with each other. The acquisition, transmission, storage, use, and processing of data in the technical solution of the present invention are in compliance with the relevant provisions of national laws and regulations, and are used for legal and reasonable purposes, and are not shared, disclosed, or sold outside of these legal uses, and are subject to supervision and management by regulatory authorities.

[0038] For user information, necessary measures should be taken to prevent illegal access to such personal information data, ensure that persons who have access to personal information data comply with relevant laws and regulations, and ensure the security of user personal information. Once such user personal information data is no longer needed, risks should be minimized by limiting or even prohibiting data collection and / or deleting data. When applicable, including in certain relevant applications, protect user privacy by de-identifying data, such as by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of stored data (e.g., collecting location data at the city level rather than at the specific address level), controlling how data is stored, and / or other methods of de-identification.

[0039] The concepts of "machine node", "node" and "machine" may vary in different contexts, but generally speaking, in the field of computer networks or distributed systems, these terms have certain associations and distinctions: A machine refers to a physical computing device, such as a server, a personal computer, or other hardware device with computing capabilities. In a network or distributed system, a node usually refers to a connection point in the network. It can be any entity that can send, receive, or forward information. In a network diagram, a node is usually represented by a circle and connected to other nodes by edges (i.e., connecting lines). In a distributed computing environment, a node often refers to a host running a specific software instance that can perform specific tasks, such as data processing or storage. A machine node is sometimes used to specifically refer to a physical machine in a network or cluster that carries the function of a node. In other words, a machine node can be understood as both a physical machine and a logical network node.

[0040] To put it simply, environment construction includes creating machine (such as operating system) nodes and installing basic software (such as middleware required for application system operation). Basic software is software that provides basic functions. Common basic software includes middleware (Tomcat, WebLogic, etc.), programming language runtime environment software (JDK / JRE, Python, etc.), Web server software (Nginx, Httpd, etc.), database software, etc. Due to the complexity of the database field, there is also a classification method that classifies databases as an independent software category.

[0041] When the existing operation and maintenance personnel are setting up the environment, they input a resource requirement list, which lists the systems, node configurations, and basic software that need to be built in the environment. Enterprise-level application systems are large and complex. For ease of understanding, see Table 1, which takes the resource requirement lists of two application systems as examples:

[0042]

[0043] There are two ways to build the environment:

[0044] Method 1: After the machine node is created, the required basic software is installed on each machine node through the automation tool; among them, the automation tool is the most common and one of the most important tools in operation and maintenance work. The automation tool interacts with each machine node through the Agent on each machine node, and can remotely issue execution commands and scripts, and issue execution commands in batches. It is an important tool in operation and maintenance management and a bottom-level support component for achieving automation. In daily operation and maintenance management work, common usage scenarios include software installation, creating operating system users / user groups, etc.

[0045] Taking the resource requirement list as an example, the list involves two systems, where system A includes four deployment units and system B includes three deployment units; these seven different units require the installation of six different basic software.

[0046] 1) Create a task in the automation tool: select the six machine nodes under the first deployment unit of system A as the execution target, select the orchestration of the Redis Sentinel installation required by this deployment unit as the execution action, generate a task and execute it;

[0047] 2) Execute the above tasks and install the software on the target machine node;

[0048] 3) Repeat steps 1) and 2) to complete the basic software installation of all deployment units in the list. Optionally, if there are some deployment units that require the same basic software type, version, and installation method (such as #3 and #7 in the list), the basic software requirements of these deployment units can be combined into one automated task for execution. The target machine node is the machine node under the deployment unit, and the execution action is the basic software installation required by it.

[0049] The disadvantages of this method are as follows: Disadvantage 1: The workload of manual operation is large. The resource requirement list example only lists the requirements of 19 machine nodes of 2 systems. In actual situations, the number of systems, deployment units and machine nodes involved in the new environment will be 2 orders of magnitude larger, and the number of basic software installation tasks that need to be created in the automation tool will also increase by dozens or even hundreds of times. Disadvantage 2: There are many input links, it is difficult to improve efficiency and the probability of errors is high. The original input is the resource requirement list of each system. When creating machine nodes, it is necessary to manually create machine nodes according to the list, which is the first input link; when using automation tools to create basic software installation tasks, manually select the execution target (machine node) and select the execution action (the basic software to be installed), which is the second input link. Both links contain multiple information sub-items that need to be filled in or entered manually, and the efficiency is difficult to improve; and the amount of required data is large, and the probability of manual input errors also increases.

[0050] Method 2: Create the required basic software into the operating system image template. After creating a machine using the image template, you will get the installed basic software. Take the resource requirement list in the example, which involves 3 operating systems (OS) and 6 basic software.

[0051] 1) Confirm the image required for the first requirement in the list. Since the basic software is provided by the image, the image information should be: "SUSE11_ Redis(Sentinel)_5.0.4";

[0052] 2) Search the image library to confirm whether the required image exists. If it does not exist, you need to create an image and upload it to the image library;

[0053] 3) Select the "SUSE11_ Redis(Sentinel)_5.0.4" image, create the virtual machine required for the first deployment unit of system A, and create 6 machine nodes;

[0054] Repeat steps 1), 2), and 3) to complete the creation of machine nodes for all systems and deployment units in the list and the installation of basic software.

[0055] The disadvantages of this method are as follows: Disadvantage 1: It takes time to make an operating system image, which is inflexible and difficult to respond to needs quickly. When there is no image in the image library that meets the requirements, an image needs to be made. As the types of basic software are gradually increasing and basic software vendors are constantly iterating and updating versions, and the production and approval of images take a long time, the method of using images to provide basic software can only be used as a supplementary means within a specific scope, and it is difficult to quickly and comprehensively support the basic software installation requirements; Disadvantage 2: The number of images increases significantly (number of image templates = OS basic image * software type * software version), which takes up a large amount of additional storage space.

[0056] There are other methods, such as: 1) Collect information from existing devices, abstract modeling, and form data; 2) Learn based on data to form intelligent adaptation rules; 3) Based on the obtained rules, package the application system to form a container image and store it; 4) Based on the packaged image, it can be deployed more easily, eliminating the complicated process of various installation and configuration.

[0057] However, this method relies on existing devices rather than new devices, and therefore does not involve the process of creating machine nodes under the deployment unit, while one of the focuses of this application is to create machine nodes based on the configuration information model. In addition, this method requires the installation of an agent on the device to collect device information. Although this application also involves the configuration information and basic software information of the machine node, this information is used to build the environment, that is, the machine node has not been created and the basic software has not been installed at this time. It is a kind of planning information. Even if the deployment unit has not been built, these two pieces of information can exist, which is different from the collection after the device is created.

[0058] See also Figure 1 , which shows a main flow chart of an environment building processing method provided by an embodiment of the present invention, including the following steps:

[0059] S101: Obtain an environmental resource requirement list to import into an application system hierarchical architecture model, and obtain application system hierarchical architecture information; wherein the application system hierarchical architecture information includes application system information, deployment unit information, machine node configuration information, and basic software information;

[0060] S102: In response to a selection operation of one or more application system information, for each selected application system, generating a machine node creation instruction based on the deployment unit information and the machine node configuration information;

[0061] S103: Sending a machine node creation instruction to the first builder, so that the first builder performs a machine node creation operation under the deployment unit to obtain machine node information;

[0062] S104: In response to the completion of the creation of the machine node under the deployment unit, based on the machine node information and the basic software information, generate a basic software installation instruction and send it to the second builder, so that the second builder performs the basic software installation operation under each machine node.

[0063] In the above implementation, for step S101, the application system referred to in this solution is a system that can run independently and carry a certain business or a certain type of business in the usual sense, such as an OA system or an attendance system. A system can be called an "application system" regardless of whether it requires virtual machines or container technology. Below the system is a deployment unit, so it can be regarded as a combination of one or more deployment units. Deployment unit: A collection of one or more service nodes, their contents are exactly the same. For services that need to be deployed on machine nodes, all machine node configurations under the deployment unit are also exactly the same.

[0064] Application system hierarchical architecture: describes the architecture information of the application system in a logical layered manner. The application system hierarchical architecture consists of two to three layers: system group (optional), application system, and deployment unit. Each hierarchical object contains corresponding attributes. Among them, system group: a logical combination of multiple application systems. These application systems are interrelated in business fields, or have relatively close upstream and downstream relationships.

[0065] This solution sets up an application system hierarchical architecture model, which can be regarded as a table with specification requirements. After the input of the environment construction (i.e., the environmental resource requirement list) is imported, the data in the environmental resource requirement list is sorted out according to the specifications in the table. Some data may be missing. In this case, in order to ensure that only data that meets the specifications can be stored in the application system hierarchical architecture model, the missing data is marked and refused to be stored, so as to ensure the integrity and accuracy of the imported data.

[0066] Through the table import module, the environmental resource demand list is imported into the application system hierarchical architecture model in the model format to obtain the application system hierarchical architecture information for storage in the database. Among them, the table import module can be a table tool, which is a commonly used tool in work, used for information statistics, ledger records and other tasks. Various programming languages ​​provide or implement toolkits for reading table data content, which can realize the table data reading and import module more conveniently and quickly for use by other functional modules in the system.

[0067] The application system hierarchical architecture information includes application system information, deployment unit information, machine node configuration information and basic software information. Taking Table 1 as an example, the application system information includes environment, system number, system name, deployment unit information includes deployment unit name, deployment unit type, number of nodes, node type, machine node configuration information includes operating system, CPU, memory, storage, and basic software information includes basic software and software version.

[0068] For steps S102 and S103, the operation and maintenance personnel can select one or more from the application system information, specifically, select the application system name or system number, so as to construct the system range to be built. Taking Table 1 as an example, system A and system B are selected to achieve the purpose of batch building. For system A and system B, the application system hierarchical architecture information is determined one by one, including application system information, deployment unit information, machine node configuration information and basic software information.

[0069] The machine node configuration information and basic software information are used to reflect the planning state requirements of the machine node, and the machine nodes under the same deployment unit have completely consistent requirements. For system A (the same applies to system B, which will not be repeated here), first generate a machine node creation instruction based on the deployment unit information and machine node configuration information. Different deployment units under the same system may have different deployment requirements, as shown in Table 1. The machine node creation instruction is sent to the first builder, and the machine node creation operation is executed. The creation status is tracked until all machine nodes under the deployment unit are created.

[0070] The first builder can be a cloud base / cloud platform or other infrastructure, such as a data center or server hardware. Cloud base / cloud platform is preferred because they provide more flexible and scalable services. Among them, the cloud base / cloud platform is the basic technology platform in the field of cloud computing. It encapsulates the underlying physical infrastructure, making the underlying complex processing transparent, providing interfaces and consoles to the upper layer, making the infrastructure virtualized and the management digital. Based on the support of the cloud base / cloud platform, only a small amount of resource requirement information (such as: model / specification configuration, operating system, storage requirements, network requirements) is required to create a machine node.

[0071] For step S104, because the installation of some basic software has specific requirements, some can be installed independently, while others need to be installed as a whole. Therefore, for a deployment unit, the basic software can only be installed after all machine nodes under the unit are created. At this time, based on the machine node information and the basic software information, the basic software installation instruction is generated. For example, there are three machine nodes, numbered 1, 2, and 3, respectively, then the machine node information is machine nodes 1, 2, and 3, indicating that the basic software is installed under machine nodes 1, 2, and 3. Or distinguish according to the system, such as the aforementioned SUSE 11, Kylin V10, and RHEL 8.5. Send the basic software installation instruction to the second builder, such as an automated operation and maintenance tool, an integrated / continuous deployment system, preferably an automated operation and maintenance tool, to perform software installation operation tasks, and track the installation status of each basic software until all basic software are safely completed.

[0072] The method provided in the above embodiment significantly improves the efficiency of environment construction by automatically generating and executing instructions for creating machine nodes and installing basic software, reduces errors and inconsistencies caused by manual operations, and integrates application system hierarchical architecture information to achieve full-process automated management from resource requirements to completion of environment construction.

[0073] See also Figure 2 , shows a schematic flow chart of an optional environment building processing method according to an embodiment of the present invention, including the following steps:

[0074] S201: Determine a configuration information model and a software information model pre-created for a deployment unit type or a deployment unit;

[0075] S202: storing the machine node configuration information into the configuration information model to obtain configuration information model data;

[0076] S203: storing the basic software information in the software information model to obtain software information model data.

[0077] In the above implementation, the machine node configuration information and basic software information are used to reflect the planning state requirements of the machine node, and the machine nodes under the same deployment unit are required to be completely consistent. Therefore, the relationship between the configuration information model, the software information model and the deployment unit is as follows: Figure 3 In addition, different configuration information models and software information models can be set for different deployment unit types to achieve fast configuration. However, considering that the requirements may be different in actual operation, the former method is preferred, that is, creating different configuration information models and software information models for different deployment units.

[0078] 1. Establish a configuration information model: This model is an abstraction of the machine node configuration information. The model defines the attributes of the configuration information, including: node type, operating system version, number of CPU cores, memory size, and storage size. Optionally, the model attribute definition is configurable, and attributes can be increased or decreased according to actual needs, such as increasing the shared storage size, shared storage mount point, and shared range;

[0079] 2. Establish a software information model: This model is an abstraction of the basic software that needs to be installed on the machine node. The model defines the attributes of the software information, including: software type, software name, version, installation method, and other required information. Optionally, the model attribute definition is configurable, and attributes can be added or removed according to actual needs, such as adding the user to whom the software belongs.

[0080] The meaning of the configuration information model and software information model is similar to the aforementioned application system hierarchical architecture model. They both ensure that only data that meets the specifications can be stored in the model, and that missing data is marked and refused to be stored, thereby ensuring the integrity and accuracy of the imported data. For example, if the model is an Excel template, after storing the data in the template, the template with the added data needs to be stored in another location to distinguish it from the original template and avoid overwriting the original template.

[0081] 3. Store the machine node configuration information in the configuration information model to obtain configuration information model data; and store the basic software information in the software information model to obtain software information model data; establish an association relationship among the configuration information model data, the software information model data and the deployment unit.

[0082] The method provided in the above embodiment predefines the configuration model and software information model of the deployment unit in the application system hierarchical architecture, and stores the configuration information of the machine node and the basic software information in the corresponding models, thereby achieving structured management and standardized processing of information. This not only improves the maintainability and flexibility of the deployment, but also simplifies the subsequent automated deployment process.

[0083] See also Figure 4 , shows a schematic flow chart of another optional environment building processing method according to an embodiment of the present invention, including the following steps:

[0084] S401: Determine a deployment unit according to the deployment unit information, obtain a deployment log of the deployment unit, and obtain a deployment status from the deployment log;

[0085] S402: In response to the deployment status being undeployed, generating a machine node creation instruction based on the deployment unit information and the machine node configuration information;

[0086] S403: In response to the deployment status being in deployment, returning a repeated deployment prompt message;

[0087] S404: In response to the deployment status being deployed, obtaining historical deployment unit information closest to the current one from the deployment log, and comparing the deployment unit information with the historical deployment unit information;

[0088] S405: When the comparison results are the same, a duplicate deployment prompt message is returned;

[0089] S406: When the comparison result is greater than, the difference between the deployment unit information and the historical deployment unit information is calculated, and based on the difference and the machine node configuration information, a machine node creation instruction is generated;

[0090] S407: When the comparison result is less than, based on the historical deployment unit information and the deployment unit information, determine the machine node to be deleted, and generate a deletion machine node instruction.

[0091] In the above implementation, this solution establishes an environment building framework, including:

[0092] 1. System query module, used to query and obtain the hierarchical architecture information of the imported application system, including system name, number, and environment information;

[0093] 2. Information determination module, used to determine the application system information to be built, deployment unit information, and machine node configuration information and basic software information associated with the deployment unit;

[0094] 3. Instruction module, used to generate instructions for creating machine nodes and installing basic software; for a description of the instructions for installing basic software, see Figure 1~Figure 3 The description shown is not repeated here.

[0095] 4. Storage module, used to store data during the environment construction process, including the completion of machine node creation and basic software installation under each deployment unit. When creating a machine node or installing basic software, record the operation process data and results of each step. When all nodes under a deployment unit are created and the basic software is installed, update the status of the deployment unit to completed. The deployment status of the entire application system is summarized based on the status of all deployment units.

[0096] The system query module queries and lists all imported systems, such as a list of system names and related information. The operation and maintenance personnel select the range of systems to be built, with the minimum number of systems being 1 and the maximum being the number of all imported systems. The information determination module determines the system information within the range one by one, including detailed information on the application system, deployment unit, configuration information, and basic software. At the same time, the historical data that has been built and is currently being built is queried for deduplication to avoid repeated construction. For example, for each system, check whether there are duplicate deployment records and remove duplicates.

[0097] When the machine node is created, its status is Installing. If the machine node is created, the statistical number will be increased by 1. If the statistical number is equal to the number of nodes, it means that the deployment unit is created. Check the deployment unit or mark it in other ways to indicate that its deployment status is Completed. Therefore, the status of the deployment unit is determined by the deployment status of the machine node, and the status of the deployment unit will determine the deployment status of the application system. The deployment status of the application system can be changed to Deployed only when the deployment status of all deployment units is Deployed.

[0098] The deployment operations for the deployment unit are described here, specifically:

[0099] Step 1: Determine the deployment unit according to the deployment unit information, obtain the deployment log of the deployment unit, and obtain the deployment status from the deployment log;

[0100] Step 2: In response to the deployment status being undeployed, based on the deployment unit information and the machine node configuration information, generate a create machine node instruction according to the instruction module;

[0101] Step 3: In response to the deployment status being "deploying", a repeated deployment prompt message is returned. For example, in the afternoon, operation and maintenance personnel Q clicked to deploy the cache service under application system A, but the search found that the cache service had been deployed by operation and maintenance personnel P in the morning, but the deployment event took a long time and is still in the deployment status.

[0102] Step 4: In response to the deployment status being deployed, obtain historical deployment unit information from the deployment log, compare the deployment unit information with the historical deployment unit information, and generate corresponding instructions based on the comparison results. Assume that operation and maintenance personnel P deployed the cache service under application system A yesterday. Today, operation and maintenance personnel Q added a machine node in response to user needs, so the number of nodes in the deployment unit information was changed from 6 to 7. Compare yesterday's and today's deployment unit information, mainly comparing the number of nodes. If it is found that there is one more node today than yesterday, then based on the node number 1 and the machine node configuration information, generate a machine node creation instruction and send it to the first builder.

[0103] However, if the number of nodes yesterday and today is 6, it means that the deployment requirements yesterday and today have not changed, and it is a repeated deployment, and a friendly reminder message of repeated deployment will pop up. This solution also supports an additional function - deleting machine nodes. If the user informs today that less than 6 machine nodes are actually used, 5 have met the requirements, and requires to delete a machine node, such as deleting machine node 1, or the user does not specify a machine node, the operation and maintenance personnel need to select a machine node by themselves, such as machine node 2, as the deleted machine node. This is because the configurations of the machine nodes are the same. Based on the deleted machine nodes, the machine node deletion instruction is generated and sent to the first builder, or it is manually deleted by the operation and maintenance personnel.

[0104] Therefore, after setting up the environment, this solution can also receive a request to delete a machine node, obtain the application system information, deployment unit information and the machine node identifier to be deleted from the request to delete a machine node; determine the application system according to the application system information, determine the deployment unit under the application system according to the deployment unit information; and delete the machine node corresponding to the machine node identifier from the deployment unit according to the machine node identifier to be deleted. Or, if the request only includes the number of machine nodes, delete the machine nodes corresponding to the number of machine nodes from the deployment unit.

[0105] The storage module is used to store data during the environment construction process, including the completion of machine node creation under each deployment unit, basic software installation status, etc. After deleting the machine node as mentioned above, the records in the storage module can also be updated to reflect the latest deployment status. Through the design and improvement of the above four modules, a relatively complete automated environment construction framework can be built, which can not only support the creation of new environments, but also flexibly respond to the needs of environmental adjustments, such as adding or reducing machine nodes.

[0106] The method provided in the above embodiment realizes efficient management and automated processing of the environment construction process by establishing system query, information determination, instruction generation and storage modules, ensures dynamic monitoring and optimal configuration of deployment units and machine nodes, avoids repeated deployment and waste of resources, improves operation and maintenance efficiency and system flexibility, and supports subsequent machine node deletion requests, thereby meeting user needs and reducing operation and maintenance costs.

[0107] Referring to FIG. 5( a ), a schematic diagram of a specific environment building processing method according to an embodiment of the present invention is shown, which includes the following steps:

[0108] S501: Pre-create a configuration information model and a software information model for a deployment unit type or a deployment unit;

[0109] S502: Obtain an environmental resource requirement list to import into the application system hierarchical architecture model, and obtain application system hierarchical architecture information; wherein the application system hierarchical architecture information includes application system information, deployment unit information, machine node configuration information and basic software information;

[0110] S503: storing the machine node configuration information into the configuration information model to obtain configuration information model data; storing the basic software information into the software information model to obtain software information model data;

[0111] S504: In response to the selection operation of one or more application system information, for each selected application system, query the historical data of the completed and currently being built data to perform deduplication processing to avoid repeated construction;

[0112] S505: Generate instructions for creating machine nodes based on the deployment unit information and the configuration information model data; wherein the instructions for creating machine nodes are generated based on the number of nodes and the machine node configuration information; or the instructions for creating machine nodes equal to the number of nodes are generated based on the machine node configuration information;

[0113] S506: Sending a machine node creation instruction to the cloud base / cloud platform, so that the cloud base / cloud platform executes a machine node creation operation under the deployment unit to obtain machine node information;

[0114] S507: Track the creation status of each machine node under the deployment unit, and in response to the completion of the creation of each machine node, record the result in the database;

[0115] S508: In response to the completion of the creation of the machine node under the deployment unit, based on the machine node information and the software information model data, generate an installation basic software instruction and send it to the second builder, so that the second builder performs the installation basic software operation under each machine node;

[0116] S509: Track the installation status of the basic software under each machine node, and in response to the completion of the installation of each basic software, record the result in the database.

[0117] Refer to Figure 5 (b), which shows a flowchart of another specific environment building processing method according to an embodiment of the present invention. In this solution, whether the number of nodes is included in the machine node creation instruction depends on the business function of the first builder. Most of the existing cloud platforms support the number of nodes included in the instruction, that is, the initiated machine node creation instruction includes the number of machine nodes to be created x, and the cloud platform will create x machine nodes according to the information in the instruction. For cloud platforms that do not support the number, the number is small, generally very small, and the second method can be used to implement it, which is implemented by the aforementioned instruction module, and only based on the machine node configuration information, the machine node creation instruction is generated, and the issuance of x machine node creation instructions is determined according to the number of nodes.

[0118] In the prior art, the operation and maintenance personnel need to check the creation progress of the x machine nodes respectively. The cloud platform will not summarize the creation status of the x machine nodes and can only obtain it actively. In view of this situation, this solution also creates an instruction tracking module to track the execution status of instructions.

[0119] For the creation of machine nodes: 1) The instruction module generates a machine node creation instruction based on the deployment unit information and machine node configuration information, sends it to the cloud base / cloud platform for machine node creation, and notifies the instruction tracking module to track the creation of the machine node. 2) The instruction tracking module tracks the instructions for machine node creation one by one until the creation is completed. When a creation instruction is completed, the storage module stores the result record in the database, and uses the deployment unit as the dimension to count whether all the machine nodes to be created have been created. If not, continue to wait for the creation of the machine nodes to be created under the deployment unit to be completed. If so, proceed to the next step.

[0120] For the installation of basic software: 1) The instruction module generates the basic software installation instructions based on the machine node information and the basic software information to be installed, and sends them to the automated operation and maintenance tool to execute the software installation operation task, and notify the instruction tracking module to track the installation of the basic software. 2) The instruction tracking module tracks the software installation one by one until the installation task is completed. When an installation instruction is completed, the storage module stores the result record in the database, and uses the deployment unit as the dimension to count whether the basic software installation under the deployment unit has been completed. If not, continue to wait for the installation instruction under the unit to be completed.

[0121] After that, the environment building framework uses the application system as the dimension to count whether all deployment units under the system have completed the construction work. If not, continue to wait. If yes, proceed to the next step. Using the whole as the dimension, count whether all systems within the scope of this environment building have completed the construction work. If not, continue to wait. If yes, this environment building is over.

[0122] Compared with the existing technology that is too dependent on manual work, has a high error rate and a large workload, the method provided by the embodiment of the present invention has the following beneficial effects:

[0123] 1. Manual determination is only required when determining the scope of the system to be built. There are no complex input items, the manual workload is small, and the input links and manual operation links are greatly reduced, thereby reducing errors caused by human errors;

[0124] 2. By replacing manual work with automatically executable methods, steps and module devices, the environment required for multiple application systems can be quickly built from scratch, which greatly reduces the workload, improves the efficiency and speed of environment construction, and meets the needs of large-scale and high-demand resource management and daily operation and maintenance;

[0125] 3. Unlike basic software information that can only be viewed in configuration management after installation is completed, enterprise operation and maintenance personnel can use software models and basic software information to fully understand software requirements that have not yet been installed in the planning stage, which helps to manage in advance and improve the management level of software baselines and specifications.

[0126] See also Figure 6 , showing a schematic diagram of the main modules of an environment construction processing device 600 provided by an embodiment of the present invention, including: a system query module 601, used to obtain an environmental resource requirement list to import into an application system hierarchical architecture model, and obtain application system hierarchical architecture information; wherein, the application system hierarchical architecture information includes application system information, deployment unit information, machine node configuration information and basic software information; an information determination module 602, used to respond to a selection operation of one or more application system information; an instruction module 603, used to generate a machine node creation instruction for each selected application system based on the deployment unit information and the machine node configuration information; send the machine node creation instruction to the first builder, so that the first builder performs the machine node creation operation under the deployment unit and obtains the machine node information; in response to the completion of the machine node creation under the deployment unit, generate a basic software installation instruction based on the machine node information and the basic software information and send it to the second builder, so that the second builder performs the basic software installation operation under each machine node.

[0127] In the implementation device of the present invention, the instruction module 603 is used to: determine the deployment unit according to the deployment unit information, obtain the deployment log of the deployment unit, and obtain the deployment status from the deployment log; in response to the deployment status being undeployed, generate a machine node creation instruction based on the deployment unit information and the machine node configuration information; in response to the deployment status being deploying, return a repeat deployment prompt message; in response to the deployment status being deployed, obtain the historical deployment unit information closest to the current one from the deployment log, compare the deployment unit information with the historical deployment unit information, and generate a corresponding instruction according to the comparison result.

[0128] In the implementation device of the present invention, the instruction module 603 is used to: when the comparison result is the same, return a duplicate deployment prompt message; when the comparison result is greater than, calculate the difference between the deployment unit information and the historical deployment unit information, and generate a create machine node instruction based on the difference and the machine node configuration information; when the comparison result is less than, determine the machine node to be deleted based on the historical deployment unit information and the deployment unit information, and generate a delete machine node instruction.

[0129] The implementation device of the present invention also includes a deletion module, which is used to: receive a request to delete a machine node, obtain application system information, deployment unit information and the identification of the machine node to be deleted, or application system information, deployment unit information and the number of machine nodes to be deleted from the request to delete the machine node; determine the application system according to the application system information, and determine the deployment unit under the application system according to the deployment unit information; according to the identification of the machine node to be deleted, delete the machine node corresponding to the identification of the machine node to be deleted from the deployment unit; or according to the number of machine nodes to be deleted, delete the machine nodes corresponding to the number of machine nodes to be deleted from the deployment unit.

[0130] In the implementation device of the present invention, the deployment unit information includes the number of nodes, and the instruction module 603 includes the following methods: generating a creation machine node instruction based on the number of nodes and the machine node configuration information; generating a creation machine node instruction equal to the number of nodes based on the machine node configuration information.

[0131] In the implementation device of the present invention, the deployment unit information includes the deployment unit type, and the system query module 601 is also used to: determine the configuration information model and software information model created in advance for the deployment unit type or deployment unit; store the machine node configuration information in the configuration information model to obtain the configuration information model data; store the basic software information in the software information model to obtain the software information model data.

[0132] The implementation device of the present invention also includes a tracking module, which is used to: track the creation status of each machine node under the deployment unit; track the installation status of the basic software under each machine node;

[0133] The storage module is used to: record the result to the database in response to the completion of creation of each machine node; and record the result to the database in response to the completion of installation of each basic software.

[0134] In addition, the specific implementation content of the device described in the embodiment of the present invention has been described in detail in the method described above, so the repeated content will not be described again here.

[0135] Figure 7 An exemplary system architecture 700 to which embodiments of the present invention may be applied is shown, including terminal devices 701 , 702 , 703 , a network 704 and a server 705 (only an example).

[0136] Terminal devices 701, 702, 703 can be various electronic devices with display screens and supporting web browsing, and various communication client applications are installed. Users can use terminal devices 701, 702, 703 to interact with server 705 through network 704 to receive or send messages, etc.

[0137] The network 704 is used to provide a medium for communication links between the terminal devices 701, 702, 703 and the server 705. The network 704 may include various connection types, such as wired, wireless communication links or optical fiber cables.

[0138] The server 705 may be a server that provides various services, such as a backend management server that provides support for shopping websites browsed by users using the terminal devices 701, 702, and 703 (for example only). The backend management server may analyze and process the received data such as product information query requests, and feed back the processing results (such as target push information, product information - for example only) to the terminal device. It should be noted that the method provided in the embodiment of the present invention is generally executed by the server 705, and accordingly, the device is generally set in the server 705.

[0139] It should be understood that Figure 7 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to implementation requirements.

[0140] Reference below Figure 8 , which shows a schematic diagram of the structure of a computer system 800 of a terminal device suitable for implementing an embodiment of the present invention. Figure 8 The terminal device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.

[0141] like Figure 8 As shown, the computer system 800 includes a central processing unit (CPU) 801, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 802 or a program loaded from a storage part 808 to a random access memory (RAM) 803. In the RAM 803, various programs and data required for the operation of the system 800 are also stored. The CPU 801, the ROM 802, and the RAM 803 are connected to each other through a bus 804. An input / output (I / O) interface 805 is also connected to the bus 804.

[0142] The following components are connected to the I / O interface 805: an input section 806 including a keyboard, a mouse, etc.; an output section 807 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 808 including a hard disk, etc.; and a communication section 809 including a network interface card such as a LAN card, a modem, etc. The communication section 809 performs communication processing via a network such as the Internet. A drive 810 is also connected to the I / O interface 805 as needed. A removable medium 811, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 810 as needed, so that a computer program read therefrom is installed into the storage section 808 as needed.

[0143] In particular, according to the embodiments disclosed in the present invention, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present invention include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program contains program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 809, and / or installed from the removable medium 811. When the computer program is executed by the central processing unit (CPU) 801, the above-mentioned functions defined in the system of the present invention are executed.

[0144] It should be noted that the computer-readable medium shown in the present invention may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present invention, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In the present invention, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable program code. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, optical cable, RF, etc., or any suitable combination of the above.

[0145] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present invention. In this regard, each box in the flow chart or block diagram can represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0146] The modules involved in the embodiments of the present invention may be implemented by software or hardware. The modules described may also be set in a processor, for example, it may be described as: a processor includes a system query module, an information determination module, and an instruction module. The names of these modules do not constitute a limitation on the modules themselves in some cases, for example, the instruction module may also be described as an "instruction generation and execution module".

[0147] As another aspect, the present invention further provides a computer-readable medium, which may be included in the device described in the above embodiment; or may exist independently without being assembled into the device. The above computer-readable medium carries one or more programs, and when the above one or more programs are executed by a device, the device executes any of the above-described environment building processing methods.

[0148] The computer program product of the present invention includes a computer program, and when the computer program is executed by a processor, the computer program implements the environment building processing method in the embodiment of the present invention.

[0149] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may occur depending on design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A method for processing environment construction, characterized in that: include: Obtaining an environmental resource requirement list to import into the application system hierarchical architecture model, and obtaining application system hierarchical architecture information; wherein the application system hierarchical architecture information includes application system information, deployment unit information, machine node configuration information and basic software information; In response to a selection operation of one or more application system information, for each selected application system, generating a machine node creation instruction based on the deployment unit information and the machine node configuration information; Sending a machine node creation instruction to the first builder, so that the first builder performs a machine node creation operation under the deployment unit to obtain machine node information; In response to the completion of the creation of the machine node under the deployment unit, based on the machine node information and the basic software information, an installation basic software instruction is generated and sent to the second builder, so that the second builder performs the installation basic software operation under each machine node.

2. The method according to claim 1, characterized in that The generating a machine node creation instruction based on the deployment unit information and the machine node configuration information includes: Determine the deployment unit according to the deployment unit information, obtain the deployment log of the deployment unit, and obtain the deployment status from the deployment log; In response to the deployment state being undeployed, generating a create machine node instruction based on the deployment unit information and the machine node configuration information; In response to the deployment status being "deploying", a repeated deployment prompt message is returned; In response to the deployment status being deployed, the historical deployment unit information closest to the current one is obtained from the deployment log, the deployment unit information is compared with the historical deployment unit information, and a corresponding instruction is generated according to the comparison result.

3. The method according to claim 2, characterized in that The generating corresponding instructions according to the comparison result includes: If the comparison results are the same, a duplicate deployment prompt message is returned; If the comparison result is greater than, the difference between the deployment unit information and the historical deployment unit information is calculated, and based on the difference and the machine node configuration information, a machine node creation instruction is generated; When the comparison result is less than, the machine node to be deleted is determined based on the historical deployment unit information and the deployment unit information, and an instruction to delete the machine node is generated.

4. The method according to claim 1, characterized in that: The method further comprises: Receive a request to delete a machine node, and obtain application system information, deployment unit information, and an identifier of the machine node to be deleted, or application system information, deployment unit information, and the number of machine nodes to be deleted from the request to delete the machine node; Determine the application system according to the application system information, and determine the deployment unit under the application system according to the deployment unit information; According to the identifier of the machine node to be deleted, the machine node corresponding to the identifier of the machine node to be deleted is deleted from the deployment unit; or according to the number of machine nodes to be deleted, the machine nodes corresponding to the number of machine nodes to be deleted are deleted from the deployment unit.

5. The method according to any one of claims 1 to 4, characterized in that The deployment unit information includes the number of nodes. The generating of the instruction to create a machine node based on the deployment unit information and the machine node configuration information includes the following methods: Generate instructions for creating machine nodes based on the number of nodes and machine node configuration information; Based on the machine node configuration information, a number of instructions for creating machine nodes equal to the number of nodes is generated.

6. The method according to claim 5, characterized in that The deployment unit information includes the deployment unit type. After obtaining the application system hierarchical architecture information, the method further includes: Determine the configuration information model and software information model created in advance for the deployment unit type or deployment unit; The machine node configuration information is stored in the configuration information model to obtain the configuration information model data; The basic software information is stored in the software information model to obtain software information model data.

7. The method according to claim 1, characterized in that After obtaining the application system hierarchical architecture information, the method further includes: Tracking the creation of each machine node under the deployment unit, and in response to the completion of the creation of each machine node, recording the result to the database; and Track the installation status of the basic software under each machine node, and record the results to the database in response to the completion of each basic software installation.

8. An environment construction processing device, characterized in that: include: A system query module is used to obtain an environmental resource requirement list to import into the application system hierarchical architecture model to obtain application system hierarchical architecture information; wherein the application system hierarchical architecture information includes application system information, deployment unit information, machine node configuration information and basic software information; An information determination module, for responding to a selection operation of one or more application system information; An instruction module, for generating a machine node creation instruction for each selected application system based on the deployment unit information and the machine node configuration information; Sending a machine node creation instruction to the first builder, so that the first builder performs a machine node creation operation under the deployment unit to obtain machine node information; In response to the completion of the creation of the machine node under the deployment unit, based on the machine node information and the basic software information, an installation basic software instruction is generated and sent to the second builder, so that the second builder performs the installation basic software operation under each machine node.

9. An electronic device, characterized in that: include: one or more processors; a 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 implement the method according to any one of claims 1 to 7.

10. A computer readable medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

11. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

Images