Resource pool automatic deployment method and device, electronic equipment and readable medium

Abstract

The embodiment of the invention provides an automatic deployment method and device for a resource pool, electronic equipment and a readable medium, and relates to the technical field of data processing, and the method comprises the steps: abstracting a resource pool deployment step into standardized steps of three types of tasks, works and steps; writing the standardization step into a configuration file; storing standardization steps in the configuration file into a database; analyzing a dependency relationship among the standardization steps; performing dynamic resource pool deployment and arrangement based on the dependency relationship among the standardization steps; when the dependency condition is met, automatically triggering the next deployment step; and recording the execution result, the execution end timestamp and the execution time of each standardized step. According to the invention, automatic resource pool deployment can be carried out, manual operation steps are reduced, and the resource pool deployment efficiency, the deployment resource distribution uniformity and the deployment accuracy are improved.

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, and in particular to a resource pool automatic deployment method, a resource pool automatic deployment device, an electronic device and a computer-readable medium. Background Art

[0002] With the vigorous development of cloud computing business, the workload of resource pool deployment is increasing, and the importance of delivery efficiency is gradually highlighted. How to effectively improve the efficiency of resource pool deployment has become a bottleneck that urgently needs to be broken through in business development.

[0003] The existing deployment process is that the deployment engineer obtains the collaborative document, determines the deployment components based on the deployment information in the collaborative document, and starts preparing for the deployment work by referring to the full-process deployment manual. The deployment work is divided into the following steps: (1) Basic environment preparation, including yum virtual machine configuration, harbor configuration, ntp configuration, physical server host name modification, virtual machine creation, server and virtual machine optimization and reinforcement, post-optimization cleanup, virtual machine system disk expansion, server virtual machine restart, control virtual machine configuration network element external network interface ipv6 address, vnet type server network card rename, tenant side service deployment, jumpserver add route, jumpserver management to 4A system and other operations; (2) Storage deployment, including block (eds-hdd), flash memory (eds-ssd), file block engine (sfs-hdd), file flash memory engine (sfs-ssd) , object engine (zos), file gateway, object gateway; (3) container base deployment; (4) computing middleware deployment; (5) computing component deployment (tenant-side image upload, computing HA, flavor creation, etc.); (6) monitoring deployment, including base monitoring, storage monitoring, computing monitoring; (7) vnet deployment, including control plane deployment, computing node service deployment, epos miniaturized network element deployment, network element virtual machine cmdb entry, dpos standardized network element deployment, epos / dpos mixed deployment, eip management, smoke test, netprobe deployment, etc.; (8) bare metal component deployment; (9) cloud dedicated line component deployment; (10) vcpe component deployment; (11) private cloud management component deployment.

[0004] However, there are a lot of manual operation steps in current manual deployment, which not only relies on professional judgment but also relies on the deployment engineer's understanding of the business, which makes it difficult to balance speed and accuracy when facing a large amount of resource pool deployment workload. Even experienced deployment engineers are prone to human errors under high workload, so current manual deployment has disadvantages in deployment efficiency and accuracy, resulting in low manual deployment efficiency, uneven deployment resource allocation, and low deployment accuracy. Summary of the invention

[0005] The embodiment of the present invention provides a resource pool automatic deployment method, a resource pool automatic deployment device, an electronic device and a computer-readable storage medium to solve the current problems of low manual deployment efficiency, uneven deployment resource allocation and low deployment accuracy.

[0006] An embodiment of the present invention discloses a resource pool automatic deployment method, comprising:

[0007] S1: Abstract the resource pool deployment steps into three standardized steps: tasks, work, and steps;

[0008] S2: writing the standardization steps into a configuration file;

[0009] S3: storing the standardized steps in the configuration file into a database;

[0010] S4: Analyze the dependencies between the various standardization steps;

[0011] S5: Perform dynamic resource pool deployment and orchestration based on the dependency relationship between each of the standardized steps;

[0012] S6: When the dependency conditions are met, the next deployment step is automatically triggered;

[0013] S7: Record the execution result, execution end timestamp and execution time of each of the standardization steps.

[0014] The embodiment of the present invention discloses a resource pool automatic deployment device, comprising:

[0015] Abstraction module, which is used to abstract deployment steps into three standardized steps: tasks, work, and steps;

[0016] A writing module, used for writing the standardization steps into a configuration file;

[0017] A storage module, used for storing the standardized steps in the configuration file into a database;

[0018] An analysis module, used for analyzing the dependencies between the various standardization steps;

[0019] An orchestration module, used to perform dynamic resource pool deployment orchestration based on the dependency relationship between each of the standardized steps;

[0020] The trigger module is used to automatically trigger the next deployment step when the dependency conditions are met;

[0021] The recording module is used to record the execution result, execution end timestamp and execution time of each of the standardization steps.

[0022] The embodiment of the present invention further discloses an electronic device, comprising a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus;

[0023] The memory is used to store computer programs;

[0024] The processor is used to implement the resource pool automatic deployment method as described in the embodiment of the present invention when executing the program stored in the memory.

[0025] The embodiment of the present invention further discloses one or more computer-readable media on which instructions are stored. When executed by one or more processors, the processors execute the resource pool automatic deployment method as described in the embodiment of the present invention.

[0026] The embodiments of the present invention include the following advantages:

[0027] The present invention abstracts the resource pool deployment steps into three categories of standardized steps: tasks, work, and steps, and performs dynamic resource pool deployment orchestration based on the dependencies between the standardized steps. It can automate resource pool deployment, reduce manual operation steps, and improve resource pool deployment efficiency, deployment resource allocation uniformity, and deployment accuracy. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] Figure 1 It is a flowchart of the steps of a resource pool automatic deployment method provided in an embodiment of the present invention;

[0029] Figure 2 is a schematic diagram of the structure of an automation engine provided in an embodiment of the present invention;

[0030] Figure 3 is a hierarchical schematic diagram of a standardized step provided in an embodiment of the present invention;

[0031] Figure 4 It is a schematic diagram of a front-end and back-end separation architecture provided in an embodiment of the present invention;

[0032] Figure 5 is a block diagram of a resource pool automatic deployment device provided in an embodiment of the present invention;

[0033] Figure 6 is a block diagram of an electronic device provided in an embodiment of the present invention;

[0034] Figure 7 is a schematic diagram of a computer-readable medium provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0035] In order to make the above-mentioned objects, features and advantages of the present invention more obvious and easy to understand, the present invention is further described in detail below with reference to the accompanying drawings and specific embodiments.

[0036] Reference Figure 1 , showing a step flow chart of a resource pool automatic deployment method provided in an embodiment of the present invention.

[0037] The present invention proposes a resource pool automatic deployment method, which can be specifically run in an automation engine, referring to Figure 2 , showing a structural schematic diagram of an automation engine provided in an embodiment of the present invention.

[0038] like Figure 2 As shown in the figure, the schematic diagram of the automation engine structure contains three core functional modules: process definition, process instantiation and process monitoring. In the process definition module, the design of task nodes and decision nodes is supported to clarify the logical flow of task execution. The process instantiation module is responsible for converting the defined process into an executable instance and running it in the actual environment to ensure that the task is executed in the expected order and dependency relationship. The process monitoring module monitors the process operation throughout the process through real-time status tracking and log recording, which is convenient for locating problems and auditing the execution process. The overall architecture realizes flexible orchestration, dynamic execution and efficient monitoring of the process, and improves the reliability and operability of the automation engine. In turn, the automation engine can realize parallel execution and dependency management of tasks.

[0039] The resource pool automatic deployment method may specifically include the following steps:

[0040] S1: Abstract the resource pool deployment steps into three standardized categories: tasks, work, and steps.

[0041] Reference Figure 3 , showing a hierarchical schematic diagram of a standardization step provided in an embodiment of the present invention.

[0042] It should be noted that through hierarchical management, the entire process is divided into macro tasks, meso jobs, and micro steps, making the responsibilities of each level clearer. Task: describes the overall deployment stage. Job: describes specific subtasks, such as virtual machine deployment or storage configuration. Step: refines to specific operation steps, such as generating a virtual machine list or executing a command.

[0043] Among them, the standardized steps of the task category include: basic environment preparation and storage deployment. Basic environment preparation can build the infrastructure environment required for deployment, laying the foundation for the deployment of the entire resource pool, including key operations such as network configuration, host optimization, and virtual machine creation, to ensure a stable basic environment for subsequent deployment steps. Storage deployment can configure and deploy different types of storage systems (block storage, object storage, file storage, etc.) to provide efficient and reliable data storage support for computing components, containerized platforms, etc.

[0044] Among them, the standardized steps of the work category include: physical server renaming and virtual machine deployment. Physical server renaming can standardize the naming of physical servers, facilitate resource pool management and identification, and avoid subsequent deployment and operation and maintenance problems caused by naming conflicts or non-standard naming. Virtual machine deployment can deploy the required virtual machines in the resource pool, including virtual machine creation, optimized configuration, etc., which is the carrier for the subsequent application and service operation.

[0045] Among them, the standardized steps of the step category include: generating a virtual machine list file according to the collaborative document excel file and executing virtual machine deployment. Generating a virtual machine list file according to the collaborative document excel file can extract the key parameters of virtual machine deployment (such as name, configuration, network information) from the collaborative document, generate a virtual machine list for deployment, and ensure that the virtual machine configuration information is accurate and consistent. Execute virtual machine deployment according to the generated virtual machine list file to automatically complete the creation, configuration and initialization of the virtual machine, including network connection, storage mounting and other operations.

[0046] It should be noted that the standardized steps of a step category are the smallest atoms of the entire automation engine operation.

[0047] Furthermore, the step attributes of the standardized step of the step category include: name name, description description, pre-dependency dependency dependency, execution command cmd, post-action post_action and return status.

[0048] The name defines the unique identifier of each step, which is usually concise and meaningful. It is used to identify the step, facilitate reference in configuration files, logging, and dependencies, and improve the readability and maintainability of the step.

[0049] The description defines a detailed description of the function or purpose of the step. It is used to help developers, operation and maintenance engineers, and other users quickly understand the purpose of the step and is displayed in the log for easy auditing and troubleshooting.

[0050] Among them, the pre-dependency defines the pre-dependency, other steps that need to be completed before the current step is executed, which can be a single dependent step or a collection of multiple steps. In other words, the current standardized step will be executed only when the pre-dependency status is SUCCESS. Based on the introduction of dependency, the asynchronous processing of the automation engine is realized. The dependency of the standardized step in the automation deployment engine can be one or more, so as to facilitate the flexible arrangement of the deployment workflow.

[0051] The execution command (cmd) defines the specific operation command or script that needs to be executed in the current step. It is used to define the actual operation content of the step.

[0052] Among them, the post-action (post_action) calls the function name in the python script to verify the corresponding log of the current step to see if it meets the expected result. If not, it returns the FAILED status. Cmd and post_action are also a reflection of the high scalability of the tool. By changing cmd and post_action, some deployment sequences can be quickly arranged and adapted to achieve hot loading without changing the Java code. (Since the technology stack of other members of the development team is python, the function in the python script is also called here).

[0053] The return status includes wait and success. Only when the step returns success, the subsequent steps that depend on this step will be triggered. If it returns wait, the subsequent steps that depend on this step will not be triggered and will keep waiting. The application scenarios of this function can be roughly divided into three categories: 1. It is used for some additional work that needs to be done manually outside the automated deployment process, and it plays a prompting role, reminding the deployment engineer to do the next process flow action in time to avoid the overall deployment time being extended due to untimely process flow; 2. After generating the configuration file, wait for the deployment engineer to manually confirm it again; 3. Data that cannot be obtained manually in the early stage of deployment work, wait here, obtain the data and manually fill in the configuration file to carry out the next deployment task.

[0054] In the present invention, the resource pool deployment steps are divided into three categories: task, job, and step, and the pre-dependency is introduced, which not only improves the clarity and flexibility of deployment, but also realizes efficient management of automation, parallelization, and modularization. This method can significantly improve deployment efficiency and quality, while reducing human errors, and is particularly suitable for complex distributed system deployment scenarios.

[0055] S2: Write the standardization steps into the configuration file.

[0056] Specifically, before writing the configuration file, you need to clarify the properties and purpose of each standardized step. Then choose a file format such as YAML or JSON. Define the hierarchical structure of the configuration file, and then write the steps of the configuration file. Through the structured writing of standardized steps, the configuration file clearly defines the logic and dependencies between tasks, work, and steps. Combined with automation tools, it can efficiently support the dynamic deployment of resource pools, reduce human intervention, and improve the reliability and efficiency of the overall deployment.

[0057] Optionally, the configuration file is specifically a task.yml configuration file.

[0058] Among them, the task.yml configuration file is a configuration file used to define standardized steps in the automatic deployment of the resource pool. It is usually in YAML format, with a clear structure and easy to read. In the present invention, it is mainly used to describe the execution process, dependencies and parameter settings of tasks, jobs and steps. task.yml is an important configuration file for the automatic deployment of the resource pool.

[0059] Furthermore, the core functions of the task.yml configuration file are: (1) Defining the task flow: clearly describing the tasks, work, and steps to be deployed. (2) Dynamic orchestration: supporting complex dependencies and asynchronous execution. (3) Standardization: providing a unified format to improve maintainability and reusability. (4) Flexibility: configuration is logic, supporting rapid process adjustment.

[0060] In the present invention, by writing standardized steps into the configuration file, the configuration and code are separated, providing flexibility, reusability and efficient management capabilities. The structuring and maintainability of the configuration file make the system more adaptable to dynamic demand adjustments, while supporting rapid deployment and version management. This approach greatly improves the automation level and adaptability of resource pool deployment.

[0061] S3: Stores the standardized steps in the configuration file in a database.

[0062] Optionally, the database is specifically an in-memory H2 database.

[0063] Among them, H2 database is an open source relational database written in Java. It is compact, powerful, and supports embedded and server modes. H2 database is often used for temporary storage, fast query, or embedded in lightweight applications. It is an ideal choice for automated deployment scenarios.

[0064] In the present invention, the standardized steps in the configuration file are stored in the memory-type H2 database, which can significantly improve the execution efficiency, flexibility and maintainability of the system. It is not only suitable for dynamic loading and real-time configuration update, but also simplifies management and supports complex queries and concurrent operations. For scenarios that require fast response in resource pool automated deployment, the H2 database is an efficient, lightweight and flexible solution.

[0065] S4: Analyze the dependencies between various standardization steps.

[0066] Among them, dependencies include sequence dependency, resource dependency and state dependency.

[0067] Sequential dependency means that a step can only start after another step is completed.

[0068] Among them, resource dependency means that a step requires data or resources generated by the previous step.

[0069] Among them, state dependency means that the execution state (such as success or failure) of the previous step determines the execution of the current step.

[0070] Specifically, the following key attributes of each step (especially dependency and post_action) can be extracted from the configuration file. By analyzing the dependency field and post_action field, a Directed Acyclic Graph (DAG) between steps can be established. Standardized steps are represented by nodes, and dependencies are represented by edges, that is, the output of a step is the input of another step.

[0071] In the present invention, by analyzing the sequence dependency, resource dependency and state dependency, a clear, flexible and efficient deployment process can be constructed. It not only ensures the correctness of the task, but also significantly improves the automation level, execution efficiency and maintainability of the process, providing a solid guarantee for the automated deployment of the resource pool. This method is suitable for deployment scenarios of various scales and complexities, especially in high-concurrency, large-scale distributed environments.

[0072] S5: Perform dynamic resource pool deployment orchestration based on the dependencies between various standardized steps.

[0073] Specifically, find the steps without pre-dependencies in the dependency graph as the initial executable task. Create a task queue and put the initial step into the queue for execution. Check whether the task meets the completion conditions of all its dependent steps. When all dependent conditions are met, move the task from the waiting queue to the execution queue. Tasks without dependencies can be scheduled in parallel to improve execution efficiency. Dynamically parse the configuration file of the task and execute the command according to the step attributes. After the execution is completed, trigger the post-action according to the result. Monitor the execution status of each task in real time (such as SUCCESS, FAILED). If the task fails, adjust the subsequent tasks according to the status dependency (such as skip or retry). If a step fails and is marked as a critical task, suspend the subsequent steps and issue an alarm. If the failed step is not a critical task, the system can automatically skip or retry according to the logic. Whenever a step is completed, dynamically update the status of its dependent steps and add the affected tasks to the executable queue. According to the dependency graph, identify task groups without direct dependencies, which can be executed in parallel to make full use of resources.

[0074] Optionally, use workflow scheduling tools (such as Apache Airflow, Prefect) to dynamically resolve dependencies and schedule tasks. Of course, you can also use custom scripts and event triggers to manage task dependencies.

[0075] In the present invention, dynamic resource pool deployment and orchestration are performed based on the dependencies between various standardized steps, which can ensure the correct task execution order and reasonable resource scheduling, lay the foundation for dynamic orchestration, and at the same time improve efficiency, flexibility and fault tolerance, while reducing manual intervention and achieving efficient resource pool deployment.

[0076] S6: When the dependency conditions are met, the next deployment step is automatically triggered.

[0077] It should be noted that for sequential dependencies, the current step cannot start until a previous step is completed. For resource dependencies, the current step requires the resources or data generated by the previous step. For state dependencies, the execution of the current step depends on the execution result (such as success or failure) of the previous step.

[0078] Furthermore, if the status of all the dependent pre-steps is SUCCESS (or other conditions are met), the current step is automatically started. No human intervention is required, and it is dynamically scheduled by the deployment engine.

[0079] Specifically, the deployment engine continuously tracks the execution status of the task and records the completion status of each step. Dependency states usually include PENDING, RUNNING, SUCCESS, and FAILED. When the status of all dependent steps of a step changes to SUCCESS, the deployment engine moves the step into the execution queue and starts its corresponding command. If there is no direct dependency between multiple steps, the system can trigger these steps in parallel to improve deployment efficiency. After each triggered step is executed, the status table or dependency graph is updated to ensure dynamic control of the entire process.

[0080] In the present invention, dynamic dependency monitoring and scheduling are used to ensure process correctness and efficiency while reducing manual intervention. This mechanism is suitable for complex resource pool deployment scenarios and can significantly improve deployment efficiency and quality.

[0081] S7: Record the execution result, execution end timestamp, and execution time of each standardized step.

[0082] The execution result indicates the final status of each standardized step, usually used to describe whether the task was completed successfully or an error occurred. For example, SUCCESS: The step was completed successfully. FAILED: The step failed to execute. SKIPPED: From the business side, this step does not need to be executed. RUNNING: The step is being executed. PENDING: The step is waiting to be executed (dependencies are not met).

[0083] The execution end timestamp is a specific time stamp when each standardized step is completed, usually accurate to seconds or milliseconds.

[0084] The execution time indicates the time it takes for each step to complete from start to finish, usually in seconds or milliseconds.

[0085] Optionally, the execution result, execution end timestamp and execution time of each standardized step are automatically recorded in the form of a log.

[0086] The log is a record file generated by the system during operation, which is used to record the system status, events, operation results and related information. It is an important feedback tool for the system operation status and is widely used in debugging, monitoring, performance optimization and troubleshooting.

[0087] In the present invention, the execution result, execution end timestamp and execution time of each standardized step are recorded, which can provide transparency of the deployment process, quickly locate faults, optimize process performance, and enhance the fault tolerance and dynamic adjustment capabilities of the process. At the same time, it supports process visualization and auditing, reduces human intervention, improves the reliability and efficiency of automated deployment, and provides key data support for subsequent analysis and optimization.

[0088] In a possible implementation, the method further includes: building an intelligent interface for the database, and performing inspection operations and operation and maintenance operations through the intelligent interface.

[0089] Among them, the intelligent interface can query the execution status, dependencies, and history of deployment tasks in real time. It supports quick checking of the completion of key steps in deployment to ensure that tasks are executed as expected. Furthermore, the intelligent interface provides the ability to modify and adjust the deployment process, such as dynamically updating task parameters and adjusting dependencies. When problems occur in deployment, it supports rapid problem location and repair operations. All data in the resource pool deployment process are managed uniformly to ensure data consistency and integrity. The data comes from the automation engine and is structured and easy to use through the interface.

[0090] For the technical implementation of the smart interface, data is generated during the deployment process and stored in an in-memory H2 database. The smart interface provides data access and management capabilities for tasks, jobs, and steps based on the database. The interface access capability is provided using RESTful API, which is suitable for a variety of usage scenarios. The backend is developed using SpringBoot, which supports flexible expansion and efficient operation. Through the smart interface, users can automatically complete tedious inspection and data operation tasks. Combined with the built-in workflow engine, it supports asynchronous execution of tasks and dependency management.

[0091] It should be noted that the automation engine manages all data during the resource pool deployment, and develops an intelligent interface based on this data to facilitate inspection operations and operation and maintenance operations during deployment.

[0092] In the present invention, the smart interface in the document is an important part of the Smart-Deploy engine, which greatly reduces manual intervention and repetitive work by providing a unified operation portal and automated data management capabilities. The smart interface enhances the transparency and flexibility of the deployment process, while supporting dynamic adjustment and rapid fault diagnosis, and is an indispensable technical component for the automated deployment of resource pools.

[0093] In a possible implementation, it also includes: building a front-end and back-end separation architecture, where the front-end provides a user interaction interface and the back-end controls the triggering and stopping of tasks.

[0094] Reference Figure 4 , showing a schematic diagram of a front-end and back-end separation architecture provided in an embodiment of the present invention.

[0095] like Figure 4As shown in the figure, the front-end and back-end separation architecture consists of the front-end (TUI interface) and the back-end (Java back-end module). The back-end is responsible for parsing the input collaborative documents, basic environment data, and application data files (such as .xlsx) through the automated deployment engine, and structures these data into the orchestration information of tasks, jobs, and steps. The back-end implements dynamic scheduling, dependency management, and result output of tasks by calling logic modules, while the front-end obtains deployment information, real-time status, and results from the back-end through the RESTful API, and presents them in a visual way, while supporting user input operations and configurations. The overall architecture realizes the automation of task orchestration, intuitive interaction, and decoupling of front-end and back-end logic, improving deployment efficiency and system flexibility.

[0096] Optionally, the backend is developed using Springboot and provides a RESTful API interface. All steps defined in task.yml will have corresponding logic classes during the development process. The development model of the strategy pattern is adopted to achieve the correspondence between the annotation name and step_name. The Java backend module runs on the deployment virtual machine, and forms the database required for the deployment of the entire resource pool through data input and reading from the program environment. At the same time, the corresponding orchestration content is executed according to the workflow of the deployment orchestration information.

[0097] Furthermore, deployment orchestration can be executed according to dependencies, that is, once the dependent steps of a certain step are completed, this step can be started. Compared with manual sequential execution, the advantage of this type of orchestration is that some deployment components can be run concurrently, improving deployment efficiency.

[0098] In the present invention, the way of building a front-end and back-end separation architecture not only improves the flexibility of the system and user experience, but also realizes efficient task management and code reuse through dynamic workflow orchestration and strategy mode. The back-end is developed based on SpringBoot, combined with RESTful API, which provides a stable, secure and scalable technical foundation for resource pool deployment, greatly improving deployment efficiency and system maintainability. This architectural design is particularly suitable for complex and changeable automated deployment scenarios.

[0099] It should be noted that by adopting the resource pool automatic deployment method provided by the present invention, 95% of the manual operation steps can be managed in the tool engine, thereby improving the deployment work efficiency, reducing the manual deployment of a resource pool from 7 days to 3 days, while also eliminating human error operations and improving the efficiency and quality of deployment.

[0100] The embodiments of the present invention include the following advantages:

[0101] The present invention abstracts the resource pool deployment steps into three categories of standardized steps: tasks, work, and steps. Based on the dependencies between the standardized steps, dynamic resource pool deployment orchestration is performed, which can automate resource pool deployment, reduce manual operation steps, and improve resource pool deployment efficiency, deployment resource allocation uniformity, and deployment accuracy.

[0102] It should be noted that, for the sake of simplicity, the method embodiments are described as a series of action combinations, but those skilled in the art should be aware that the embodiments of the present invention are not limited by the order of the actions described, because according to the embodiments of the present invention, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions involved are not necessarily required by the embodiments of the present invention.

[0103] In addition, refer to Figure 5 , showing a block diagram of a resource pool automatic deployment device provided in an embodiment of the present invention.

[0104] The embodiment of the present invention discloses a resource pool automatic deployment device 20, comprising:

[0105] The abstraction module 201 is used to abstract the deployment steps into three types of standardized steps: tasks, work and steps.

[0106] The writing module 202 is used to write the standardized steps into the configuration file.

[0107] The storage module 203 is used to store the standardized steps in the configuration file into a database.

[0108] The analysis module 204 is used to analyze the dependencies between various standardization steps.

[0109] The orchestration module 205 is used to perform dynamic resource pool deployment orchestration based on the dependency relationship between various standardized steps.

[0110] The trigger module 206 is used to automatically trigger the next deployment step when the dependency condition is met.

[0111] The recording module 207 is used to record the execution result, execution end timestamp and execution time of each standardization step.

[0112] In a possible implementation, the standardized steps of the task category include: basic environment preparation and storage deployment. The standardized steps of the work category include: physical server renaming and virtual machine deployment. The standardized steps of the step category include: generating a virtual machine list file based on a collaborative document excel file and executing virtual machine deployment.

[0113] In a possible implementation, the step attributes of the standardized step of the step category include: name name, description description, pre-dependency dependency dependency, execution command cmd, post-action post_action and return status.

[0114] In a possible implementation, the resource pool automatic deployment method further includes:

[0115] Build an intelligent interface for the database and perform inspection and maintenance operations through the intelligent interface.

[0116] In a possible implementation, the resource pool automatic deployment method further includes:

[0117] Build a front-end and back-end separation architecture, with the front-end providing a user interaction interface and the back-end controlling the triggering and stopping of tasks.

[0118] As for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0119] The embodiments of the present invention include the following advantages:

[0120] The present invention abstracts the resource pool deployment steps into three categories of standardized steps: tasks, work, and steps. Based on the dependencies between the standardized steps, dynamic resource pool deployment orchestration is performed, which can automate resource pool deployment, reduce manual operation steps, and improve resource pool deployment efficiency, deployment resource allocation uniformity, and deployment accuracy.

[0121] In addition, refer to Figure 6 , shows a block diagram of an electronic device provided in an embodiment of the present invention. The embodiment of the present invention also provides an electronic device, including a processor 1301, a communication interface 1302, a memory 1303 and a communication bus 1304, wherein the processor 1301, the communication interface 1302, and the memory 1303 communicate with each other through the communication bus 1304,

[0122] The memory 1303 is used to store computer programs.

[0123] The processor 1301 is used to implement the following steps when executing the program stored in the memory 1303:

[0124] S1: Abstract the resource pool deployment steps into three standardized categories: tasks, work, and steps.

[0125] S2: Write the standardization steps into the configuration file.

[0126] S3: Stores the standardized steps in the configuration file in a database.

[0127] S4: Analyze the dependencies between various standardization steps.

[0128] S5: Perform dynamic resource pool deployment orchestration based on the dependencies between various standardized steps.

[0129] S6: When the dependency conditions are met, the next deployment step is automatically triggered.

[0130] S7: Record the execution result, execution end timestamp, and execution time of each standardized step.

[0131] The communication bus mentioned in the above terminal can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The communication bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus.

[0132] The communication interface is used for communication between the above terminal and other devices.

[0133] The memory may include a random access memory (RAM) or a non-volatile memory, such as at least one disk memory. Optionally, the memory may also be at least one storage device located away from the aforementioned processor.

[0134] The above-mentioned processor may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc. It may also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0135] Reference Figure 7, showing a schematic diagram of a computer-readable medium provided in an embodiment of the present invention. In another embodiment provided by the present invention, a computer-readable storage medium 1401 is also provided, in which instructions are stored, and when the instructions are run on a computer, the computer executes the resource pool automatic deployment method in the above embodiment.

[0136] In another embodiment of the present invention, a computer program product including instructions is provided. When the computer program product is run on a computer, the computer executes the automatic resource pool deployment method in the above embodiment.

[0137] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function according to the embodiment of the present invention is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website site, a computer, a server or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or a data center that includes one or more available media integration. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state hard disk Solid State Disk (SSD)), etc.

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

[0139] Each embodiment in this specification is described in a related manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0140] The above are only preferred embodiments of the present invention and are not intended to limit the protection scope of the present invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention are included in the protection scope of the present invention.

Claims

1. A resource pool automatic deployment method, characterized in that: include: S1: Abstract the resource pool deployment steps into three standardized steps: tasks, work, and steps; S2: writing the standardization steps into a configuration file; S3: storing the standardized steps in the configuration file into a database; S4: Analyze the dependencies between the various standardization steps; S5: Perform dynamic resource pool deployment and orchestration based on the dependency relationship between each of the standardized steps; S6: When the dependency conditions are met, the next deployment step is automatically triggered; S7: Record the execution result, execution end timestamp and execution time of each of the standardization steps.

2. The resource pool automatic deployment method according to claim 1, characterized in that: The standardized steps of the task category include: basic environment preparation and storage deployment; the standardized steps of the work category include: physical server renaming and virtual machine deployment; the standardized steps of the step category include: generating a virtual machine list file based on a collaborative document excel file and executing virtual machine deployment.

3. The resource pool automatic deployment method according to claim 1, characterized in that: The step attributes of the standardized steps of the step category include: name, description, pre-dependency, execution command, post-action and return status.

4. The resource pool automatic deployment method according to claim 1, characterized in that: Also includes: An intelligent interface is constructed for the database, and inspection operations and operation and maintenance operations are performed through the intelligent interface.

5. The resource pool automatic deployment method according to claim 1, characterized in that: Also includes: Build a front-end and back-end separation architecture, with the front-end providing a user interaction interface and the back-end controlling the triggering and stopping of tasks.

6. A resource pool automatic deployment device, characterized in that: include: Abstraction module, which is used to abstract deployment steps into three standardized steps: tasks, work, and steps; A writing module, used for writing the standardization steps into a configuration file; A storage module, used for storing the standardized steps in the configuration file into a database; An analysis module, used for analyzing the dependencies between the various standardization steps; An orchestration module, used to perform dynamic resource pool deployment orchestration based on the dependency relationship between each of the standardized steps; The trigger module is used to automatically trigger the next deployment step when the dependency conditions are met; The recording module is used to record the execution result, execution end timestamp and execution time of each of the standardization steps.

7. The resource pool automatic deployment device according to claim 6, characterized in that: The standardized steps of the task category include: basic environment preparation and storage deployment; the standardized steps of the work category include: physical server renaming and virtual machine deployment; the standardized steps of the step category include: generating a virtual machine list file based on a collaborative document excel file and executing virtual machine deployment.

8. The resource pool automatic deployment device according to claim 6, characterized in that: The step attributes of the standardized steps of the step category include: name, description, pre-dependency, execution command, post-action and return status.

9. An electronic device, characterized in that: It includes a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other through the communication bus; The memory is used to store computer programs; The processor is used to implement the resource pool automatic deployment method as described in any one of claims 1-5 when executing the program stored in the memory.

10. A computer-readable medium, characterized in that Instructions are stored thereon, and when executed by one or more processors, the processors are caused to execute the resource pool automatic deployment method as described in any one of claims 1-5.

Images