Bare metal server deployment method based on configuration list

Abstract

The invention discloses a bare metal server deployment method based on a configuration list, and belongs to the technical field of cloud computers. The method comprises the steps that a received configuration list is responded, the configuration list is compared with a historical configuration list received before, all data entries with difference items in the configuration list are obtained, and the different data entries in the configuration list comprise configuration description information for different bare metal servers; for each data entry with difference items in the configuration list, acquiring configuration related data associated with the data entry from a preset database; and deploying the bare metal servers associated with the data entries with the difference items according to the acquired configuration related data.

Description

Technical Field

[0001] This application belongs to the field of cloud computing technology, specifically relating to a bare metal server deployment method based on a configuration list. Background Technology

[0002] Bare metal server deployment technology provides high-performance and low-latency computing resources for cloud computing. Unlike virtualization technology, bare metal servers run directly on physical hardware without a virtualization layer, making them suitable for high-performance computing, big data processing, and latency-sensitive application scenarios.

[0003] In related technologies, the main approach is to use configuration templates to deploy different types of bare metal servers in batches. However, with the continuous development of enterprise cloud services, the demand for bare metal servers has increased significantly, and the diversity of these demands has also increased dramatically. Furthermore, due to system updates or business adjustments, deployed bare metal servers need to be redeployed frequently. This means that enterprises may need to manage dozens of bare metal servers, each using a different configuration template. As a result, the current bare metal server deployment methods are characterized by high management difficulty, complex operation, and a high probability of errors. Summary of the Invention

[0004] The purpose of this application is to provide a bare metal server deployment method based on a configuration list, which can solve the problems of high management difficulty, complex operation and high error probability of current bare metal server deployment methods.

[0005] To solve the above-mentioned technical problems, this application is implemented as follows: In a first aspect, embodiments of this application provide a bare-metal server deployment method based on a configuration list, applied to a cloud computing platform, the method comprising: In response to receiving a configuration list, the configuration list is compared with a previously received historical configuration list to obtain each data entry in the configuration list that has differences. The different data entries in the configuration list contain configuration description information for different bare metal servers. For each data entry in the configuration list that has a difference, retrieve the configuration-related data associated with the data entry from the preset database; Based on the obtained configuration-related data, the bare metal servers associated with each data entry for which there are differences are deployed.

[0006] Secondly, embodiments of this application provide a bare-metal server deployment apparatus based on a configuration list, applied to a cloud computing platform, the apparatus comprising: The list processing module is used to compare the configuration list with the previously received historical configuration list in response to receiving the configuration list, and obtain each data entry in the configuration list that has differences. The different data entries in the configuration list contain configuration description information for different bare metal servers. The data acquisition module is used to acquire configuration-related data associated with each data entry in the configuration list that has differences from a preset database. The server deployment module is used to deploy the bare metal servers associated with each data entry that has differences, based on the obtained configuration-related data.

[0007] Thirdly, embodiments of this application provide an electronic device including a processor, a memory, and a program or instructions stored in the memory and executable on the processor. When the program or instructions are executed by the processor, they implement the steps of the bare metal server deployment method based on a configuration list as described in the first aspect.

[0008] Fourthly, embodiments of this application provide a readable storage medium storing a program or instructions that, when executed by a processor, implement the steps of the bare metal server deployment method based on a configuration list as described in the first aspect.

[0009] Fifthly, embodiments of this application provide a chip, the chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being used to run programs or instructions to implement the bare metal server deployment method based on a configuration list as described in the first aspect.

[0010] In this embodiment, the cloud computing platform analyzes the differences between the configuration list and previously received historical configuration lists to determine the bare metal server to be deployed and the associated configuration description information. The platform then retrieves the associated configuration-related data from a pre-set database based on this description information and deploys the bare metal server accordingly. Thus, based on this configuration list, the cloud computing platform can automatically deploy a large number of mixed-type bare metal servers with minimal effort, reducing operational complexity and the probability of errors. Furthermore, the user only needs to upload and maintain the configuration list, while the cloud computing platform maintains the configuration-related data, reducing management difficulty and further decreasing the probability of errors. Attached Figure Description

[0011] Figure 1 A flowchart illustrating an implementation method for deploying a bare metal server based on a configuration list, provided in this application embodiment; Figure 2 A schematic diagram illustrating the multi-terminal interaction process of a bare metal server deployment method based on a configuration list provided in this application embodiment; Figure 3 A schematic diagram illustrating the implementation process of a bare metal server deployment method based on a configuration list, provided in an embodiment of this application; Figure 4 A schematic diagram of a bare metal server deployment device based on a configuration list provided in this application embodiment; Figure 5 This is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0012] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0013] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such use of data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0014] First, to facilitate understanding of the technical solutions provided in this application, the main technical concepts involved in the embodiments of this application will be briefly explained below.

[0015] Bare metal servers (BMS) can directly provide physical resources to users in a cloud computing environment, combining the high performance of physical servers with the flexibility of cloud computing.

[0016] Preboot execution environment (PXE): also known as a pre-execution environment, it provides a mechanism for booting a computer using a network.

[0017] In cloud computing, bare metal servers typically use PXE technology for automated installation and deployment. The main steps are as follows: Step 1: Configure the Dynamic Host Configuration Protocol (DHCP) server to assign Internet Protocol (IP) addresses to newly started bare metal servers and specify the location of the Trivial File Transfer Protocol (TFTP) server.

[0018] Step 2: Store the PXE boot files (such as the bootloader) and necessary configuration files on the TFTP server.

[0019] Step 3: Configure the PXE boot file, which typically includes a lightweight Linux distribution and an initial random access memory (RAM) disk (such as initrd) to boot the server into a usable installation environment.

[0020] Step 4: Prepare the operating system installation image and automated installation script (such as Kickstart for RHEL / CentOS or Preseed for Debian / Ubuntu) and place them on a Hypertext Transfer Protocol (HTTP) or Network File System (NFS) server.

[0021] Step 5: The bare metal server boots via network, obtains an IP address assigned by the DHCP server, and downloads the PXE boot file.

[0022] Step 6: The bare metal server is booted into a temporary installation environment using a PXE boot file, which is usually a streamlined Linux operating system.

[0023] Step 7: In the installation environment, the automated installation script takes over, configuring hard drive partitions, installing the operating system, configuring the network, and other necessary system settings.

[0024] Step 8: After the operating system installation is complete, perform the final configuration steps, such as installing the required software packages and tools, and configuring user and security policies.

[0025] As the types of bare metal servers increase, the installation and deployment process becomes increasingly complex. To differentiate between different types of bare metal servers, the current main approach is to deploy them in batches using configuration templates.

[0026] With the continuous development of enterprise cloud services, the demand for bare metal servers has increased significantly, and the diversity of these demands has also increased dramatically. Furthermore, due to system updates or business adjustments, deployed bare metal servers often need to be redeployed frequently. This means that enterprises may need to manage dozens of bare metal servers, each using different configuration templates. Consequently, current bare metal server deployment methods suffer from significant management difficulties, operational complexity, and a high probability of errors. Based on the above analysis, and addressing the problems of high management difficulty, complex operation, and high error probability in current bare metal server deployment methods, this application provides a bare metal server deployment method based on a configuration list. This method can achieve automatic configuration and deployment of a large number of mixed-type bare metal servers in a cloud computing environment with a small workload, and reduce management difficulty, operational complexity, and the probability of configuration errors.

[0027] The following description, in conjunction with the accompanying drawings, details a bare metal server deployment method based on a configuration list provided in this application, through specific embodiments and application scenarios.

[0028] See Figure 1 The diagram shown is an implementation flowchart of a bare metal server deployment method based on a configuration list provided in this application embodiment. The bare metal server deployment method based on a configuration list is applied to a cloud computing platform and may include the following steps: Step S101: In response to receiving the configuration list, the configuration list is compared with the previously received historical configuration list to obtain each data entry in the configuration list that has differences. The different data entries in the configuration list contain configuration description information for different bare metal servers.

[0029] In this embodiment, the user can generate a configuration list containing one or more data entries locally. This configuration list includes configuration description information for one or more bare metal servers that the user needs to configure (or reconfigure). The user then sends the generated configuration list from the local machine to the cloud computing platform.

[0030] In some embodiments, the data entry may also include identification information of the bare metal server, so that the cloud computing platform can determine the bare metal server associated with the data entry based on the identification information.

[0031] In some embodiments, different rows or columns in the configuration list can be associated with different bare metal servers. Users can place the data entries associated with the bare metal servers to be configured in the row or column associated with the bare metal server in the configuration list, so that the cloud computing platform can determine the bare metal server associated with the data entry based on the row or column in the configuration list where the data entry is located.

[0032] After receiving the configuration list, the cloud computing platform compares it with its existing historical configuration lists (such as its own temporarily stored historical configuration lists) to identify data entries in the configuration list that have discrepancies. For example, if a bare metal server is associated with a different system version number in this configuration list compared to the historical configuration list, the cloud computing platform will identify the data entry associated with that bare metal server in the configuration list as a data entry with a discrepancy (i.e., a difference in system version number). In some embodiments, the cloud computing platform may create an activity list to record differences in the configuration list or data entries containing differences in the configuration list, so as to quickly retrieve the differences or data entries later.

[0033] Understandably, by building and transmitting configuration lists, manual operations can be greatly simplified, the risk of errors in the configuration process can be reduced, and thus the automated configuration and system deployment of large-scale bare metal servers in a cloud computing environment can be achieved efficiently.

[0034] Step S102: For each data entry in the configuration list that has differences, retrieve the configuration-related data associated with the data entry from the preset database.

[0035] In this embodiment, the cloud computing platform can obtain configuration-related data associated with each configuration description information in the data entry from a preset database. Alternatively, the cloud computing platform can obtain configuration-related data associated with each difference item in the data entry from a preset database, as well as configuration-related data associated with the configuration description information required to implement the configuration for the difference item, thereby ensuring that the cloud computing platform can normally complete the configuration for the difference item on the bare metal server.

[0036] Understandably, what users (such as the customer's IT department) need to upload and maintain is only a table, namely the configuration list of the bare metal server, while configuration-related data such as system images and configuration scripts can be maintained by the cloud computing platform (such as the maintainer of the cloud computing platform), thereby reducing the management difficulty for users and the risk of configuration errors.

[0037] Step S103: Based on the obtained configuration-related data, deploy the bare metal servers associated with each data entry that has differences.

[0038] In this embodiment of the application, after the cloud computing platform obtains the various configuration-related data required for deploying the bare metal server, it can deploy (or redeploy) the bare metal server according to the various configuration-related data.

[0039] For example, after obtaining the system images and configuration scripts (such as the automated installation script mentioned above) required for deploying each bare metal server, the cloud computing platform can deploy the system images to the corresponding bare metal servers one by one and execute the corresponding configuration scripts.

[0040] Understandably, cloud computing platforms can identify discrepancies by analyzing the configuration list, eliminating the need for manual verification. This allows for the automated configuration and deployment of a large number of mixed-type bare metal servers in a cloud computing environment with minimal workload. This improves deployment efficiency, reduces the risk of configuration errors, and better adapts to the deployment needs of bare metal servers of different scales and application scenarios, demonstrating strong scalability and flexibility.

[0041] As can be seen from the above technical solution, by analyzing the differences between the configuration list and previously received historical configuration lists, the cloud computing platform can determine the bare metal server to be deployed and the configuration description information associated with that bare metal server. The cloud computing platform can then retrieve the associated configuration-related data from a pre-set database based on this configuration description information and deploy the bare metal server accordingly. Therefore, based on this configuration list, the cloud computing platform can automatically deploy a large number of mixed-type bare metal servers with minimal workload, thereby reducing operational complexity and the probability of errors. Furthermore, the user only needs to upload and maintain the configuration list, while the cloud computing platform maintains the configuration-related data, reducing management difficulty and further decreasing the probability of errors.

[0042] In some embodiments, obtaining the configuration-related data associated with the data entry from a preset database includes: For each configuration description in the data entry, the configuration description is used as a search keyword to search the preset database; If no data matching the search keywords is found, the steps of adjusting the search keywords according to preset keyword transformation rules and re-searching the preset database according to the adjusted search keywords are performed iteratively until data matching the adjusted search keywords is found, at which point the search for the configuration description information ends; wherein, the preset keyword transformation rules include: replacing or deleting at least one character in the search keywords with similar characters; Retrieve data that matches the search keywords from the preset database.

[0043] In this embodiment of the application, the cloud computing platform can sequentially use the configuration description information in the data entries as search keywords (also known as original keywords) according to the order of configuration operations required when deploying bare metal servers.

[0044] The cloud computing platform can use regular expression matching and other methods to retrieve data that matches the original keywords in a preset database (i.e., retrieve configuration-related data associated with the relevant configuration description information, such as system version images that match the system version number).

[0045] If no matching results are found in the preset database for the original keyword (i.e., no data matching the original keyword is retrieved), the cloud computing platform will automatically adjust the original keyword according to preset keyword transformation rules. For example, it may replace or delete at least one character of the original keyword (such as letters or numbers) with similar characters and try searching again. If no matching results are found in the preset database, the cloud computing platform will continue to try searching again by adjusting the search keywords until data matching the adjusted search keywords is retrieved, at which point the search ends. This reduces the chances of not finding configuration-related data due to differences in terminology, input errors, etc., thereby improving the deployment success rate of bare metal servers.

[0046] In some embodiments, adjusting the search keywords according to preset keyword transformation rules includes: From a plurality of preset keyword transformation strategies, one preset keyword transformation strategy is randomly selected and executed to adjust the search keywords; this increases the randomness of keyword transformation, thereby improving the search success rate. The plurality of preset keyword transformation strategies include: Item A-1: ​​For the character to be replaced in the search keywords, replace the character to be replaced with the adjacent character on the keyboard; Item A-2: Swap the positions of two adjacent characters in the search keywords; Item A-3: Delete the first character of the specified side in the search keywords.

[0047] In this embodiment of the application, for item A-1, for the character to be replaced in the search keyword (such as the letter or number to be replaced), characters (such as letters or numbers) in positions adjacent to the character to be replaced can be selected according to the keyboard position distribution. For example, using the preset keyword transformation strategy described in item A-1, the search keyword "CentOS7.9" can be adjusted to "CemtOS7.9".

[0048] Regarding item A-2, the positions of two adjacent characters (such as letters or numbers) can be swapped according to their positions in the search keywords. For example, using the preset keyword transformation strategy described in item A-2, the search keyword "CentOS7.9" can be adjusted to "CentSO7.9".

[0049] Regarding item A-3, the rightmost or leftmost character of the keyword can be deleted to obtain the adjusted search keywords. For example, using the preset keyword transformation strategy described in item A-3, the search keyword "CentOS7.9" can be adjusted to "CentOS7.".

[0050] In some embodiments, if no data matching the search keywords is found, the method further includes: If the preset iteration termination condition is met, the retrieval of the configuration description information ends, the error information is recorded and the configuration description information is skipped, and the next configuration description information to be retrieved is used as the retrieval keyword to search the preset database. The preset iteration termination condition includes: the length of the retrieval keyword is lower than the preset length threshold.

[0051] In this embodiment, if a cloud computing node fails to find matching data after multiple rounds of keyword adjustment (or transformation) and detects that the length of the current search keyword is lower than a preset length threshold, the search will be terminated. The corresponding error information will be recorded for subsequent analysis, and the configuration description information will be skipped. The next item to be searched, the configuration description information, will then be used as the search keyword to search the preset database. This ensures the reliability of the search results and reduces the possibility of misconfiguration.

[0052] In some embodiments, the different data entries in the configuration list at least include system version information and configuration script information for different bare metal servers; for each data entry in the configuration list with differing items, retrieving the configuration-related data associated with the data entry from a preset database includes: For each data entry in the configuration list that has differences, the configuration-related data associated with the system version information and configuration script information in the data entry are obtained from the preset database.

[0053] In this embodiment, considering that for the bare metal server to be deployed normally, the cloud computing platform needs to obtain at least the configuration-related data (i.e., system image and configuration script) associated with the relevant system version information and configuration script information, respectively. Therefore, when the cloud computing platform finds a difference between the system version information (e.g., system version number) and the configuration script information (e.g., configuration script name) in the configuration list, it will retrieve the configuration-related data associated with the system version information and the configuration script information from a preset database to ensure that the bare metal server can be deployed normally.

[0054] For example, taking a cloud computing platform as the bare metal management console, and a preset database including a system image library and a configuration script library, the bare metal server deployment method based on a configuration list in this application embodiment will be described. See Figure 2 The diagram illustrates the multi-terminal interaction process of a bare metal server deployment method based on a configuration list. This multi-terminal interaction process mainly includes: 1. The user sends a configuration list to the bare metal management console.

[0055] 2. The bare metal management console matches and pulls the system image from the system image library.

[0056] 3. The bare metal management console matches and retrieves configuration scripts from the configuration script library.

[0057] 4. Initialize the bare metal server using the bare metal management console.

[0058] In some embodiments, for each data entry in the configuration list that has differences, retrieving the configuration-related data associated with the data entry from a preset database includes: For each configuration description information in each data entry of the aforementioned discrepancy item, if multiple configuration-related data matching the configuration description information are retrieved from the preset database, the latest uploaded configuration-related data among the multiple configuration-related data is obtained from the preset database.

[0059] In this embodiment of the application, when the cloud computing platform retrieves multiple configuration-related data that match the configuration description information from the preset database, it can sort these configuration-related data according to the timestamp of the database upload, and then select the latest uploaded configuration-related data for acquisition, so as to ensure the validity of the configuration-related data participating in the deployment of bare metal servers.

[0060] In some embodiments, the configuration list is constructed based on a spreadsheet file format associated with office software.

[0061] In this embodiment, the configuration list uses a spreadsheet file format similar to those used in office software, such as an Excel .xls file. It is understood that constructing the configuration list (also known as the bare metal server configuration list) using a common spreadsheet file format ensures that the data structure is intuitive and clear, facilitating manual editing and verification, thereby improving the user experience.

[0062] For example, taking a cloud computing platform as the bare metal management console, and a preset database including an image repository and a configuration script repository, the bare metal server deployment method based on a configuration list in this application embodiment will be described. See Figure 3 The diagram illustrates the implementation process of a bare metal server deployment method based on a configuration list. This implementation process mainly includes: (1) The user sends a configuration list to the bare metal management console.

[0063] Specifically, users generate a configuration list locally, including bare metal server identification information, system version information, and configuration script name, and then send it to the bare metal management console. Each data entry in the configuration list is uniquely identified by the bare metal server identification information.

[0064] (2) The bare metal management console performs difference identification.

[0065] Specifically, the bare metal management console performs difference identification, compares the configuration list it receives with the existing configuration list, marks the differences, and generates an activity list.

[0066] Optionally, if the bare metal management console detects a difference between the system version information and the configuration script name, it will mark the entire row of data containing the system version information and the configuration script name in the configuration list as the difference item.

[0067] Optionally, system version information can be represented as a string consisting of the system image name and version number, such as "CentOS7.9".

[0068] (3) The bare metal management console executes the configuration expansion, the image library returns the image list, and the configuration script library returns the configuration script list.

[0069] Specifically, the bare metal management console performs configuration expansion, retrieves the latest version of the system image from the image repository and the corresponding configuration script from the configuration script repository based on each difference item in the activity list.

[0070] Optionally, the bare metal management console performs a configuration rollout, which includes the following steps: Step S301: The bare metal management console first uses system version information as the search keyword and uses regular expression matching to query the image library.

[0071] In this step, the result obtained from the bare metal management console query is a list of images, which includes the image name, the storage address of the image file, and the upload timestamp of the image file.

[0072] Optionally, if a search using the original keywords (i.e., the search terms) yields no results in the mirror database, the bare metal management console needs to attempt the search again by changing the search terms to resemble similar ones. The rule for changing the search terms is to replace at least one character (including letters and numbers) in the original keywords with a similar character.

[0073] After multiple rounds of keyword transformation, if the length of the search keyword is lower than the preset minimum length, the search is stopped, the corresponding error message is recorded, and the difference is removed from the activity list, and the next difference is processed.

[0074] After the above search process is completed, the bare metal management console will obtain a list of system images.

[0075] Step S302: Sort by upload timestamp and select the latest uploaded (i.e., the most recently updated) valid image so that it can be loaded onto the corresponding bare metal server later.

[0076] Optionally, if the number of valid mirrors is zero, the search is aborted, the corresponding error message is logged, and this difference is removed from the active list, and the next difference is processed.

[0077] Step S303: Using the configuration script name as the search keyword, the configuration script library is queried using regular expression matching.

[0078] In this step, the bare metal management console retrieves a list of configuration scripts, including the script name, storage location, and upload timestamp.

[0079] Optionally, if a search based on the original keywords (i.e., the search terms) yields no results in the configuration script library, the bare metal management console needs to try searching again by changing the search terms. The keyword transformation rule is to replace at least one character (including letters and numbers) in the original keywords with a similar character.

[0080] After multiple rounds of keyword transformation, if the length of the search keyword is lower than the preset minimum length, the search is stopped, the corresponding error information is recorded, and the difference is removed from the activity list, and the next difference is processed.

[0081] After the above search process is completed, the bare metal management console will obtain a list of configuration scripts.

[0082] Step S304: Sort by upload timestamp and select the latest uploaded (i.e., the most recently updated) valid configuration script so that it can be loaded onto the corresponding bare metal server later.

[0083] Optionally, if the number of valid configuration scripts is zero, the search is stopped, the corresponding error message is logged, and this difference is removed from the activity list, and the next difference is processed.

[0084] (4) Perform configuration on the bare metal management console.

[0085] Specifically, the bare metal management console deploys the system images to the corresponding bare metal servers one by one and executes the corresponding configuration scripts.

[0086] (5) The bare metal server downloads the installation image required for deployment, and the image library returns the image accordingly.

[0087] (6) The bare metal server downloads the configuration scripts required for deployment, and the image library returns a list of configuration scripts accordingly.

[0088] It is understandable that, through the above steps of sending, receiving, and expanding the configuration list, this application can automatically configure and deploy a large number of bare metal servers with a small workload when handling the configuration and deployment of mixed types of bare metal servers. This reduces the operational threshold, decreases the amount of manual verification, facilitates operation, improves processing efficiency, and reduces the risk of configuration errors.

[0089] It should be noted that the bare metal server deployment method based on a configuration list provided in this application can be executed by a bare metal server deployment device based on a configuration list, or by a control module within that device for executing the bare metal server deployment method based on a configuration list. This application uses the execution of the bare metal server deployment method based on a configuration list by a bare metal server deployment device as an example to illustrate the bare metal server deployment method based on a configuration list provided in this application.

[0090] This application also provides a bare metal server deployment device based on a configuration list, which is applied to a cloud computing platform, such as... Figure 4 As shown, the device includes: The list processing module is used to compare the configuration list with the previously received historical configuration list in response to receiving the configuration list, and obtain each data entry in the configuration list that has differences. The different data entries in the configuration list contain configuration description information for different bare metal servers. The data acquisition module is used to acquire configuration-related data associated with each data entry in the configuration list that has differences from a preset database. The server deployment module is used to deploy the bare metal servers associated with each data entry that has differences, based on the obtained configuration-related data.

[0091] Optionally, the data acquisition module is further configured to perform the following steps: For each configuration description in the data entry, the configuration description is used as a search keyword to search the preset database; If no data matching the search keywords is found, the steps of adjusting the search keywords according to preset keyword transformation rules and re-searching the preset database according to the adjusted search keywords are performed iteratively until data matching the adjusted search keywords is found, at which point the search for the configuration description information ends; wherein, the preset keyword transformation rules include: replacing or deleting at least one character in the search keywords with similar characters; Retrieve data that matches the search keywords from the preset database.

[0092] Optionally, the data acquisition module is further configured to randomly select a preset keyword transformation strategy from a plurality of preset keyword transformation strategies and execute it to adjust the search keywords; wherein, the plurality of preset keyword transformation strategies include: For the character to be replaced in the search keywords, replace the character with the adjacent character on the keyboard; Swap the positions of two adjacent characters in the search keywords; Delete the first character of the specified side in the search keywords.

[0093] Optionally, the device further includes: an error handling module, configured to terminate the search for the configuration description information, record error information and skip the configuration description information when no data matching the search keyword is found and a preset iteration termination condition is met, and continue to search the preset database using the next configuration description information to be searched as the search keyword, wherein the preset iteration termination condition includes: the length of the search keyword is lower than a preset length threshold.

[0094] Optionally, the different data entries in the configuration list shall at least include system version information and configuration script information for different bare metal servers; The data acquisition module is further configured to, for each data entry in the configuration list that has differences, obtain configuration-related data associated with the system version information and configuration script information in the data entry from the preset database.

[0095] Optionally, the data acquisition module is further configured to, for each data entry of the discrepancy items, if multiple configuration-related data matching the configuration description information are retrieved from the preset database, obtain the latest uploaded configuration-related data from the multiple configuration-related data.

[0096] Optionally, the configuration list is constructed based on the spreadsheet file format associated with the office software.

[0097] As can be seen from the above technical solution, by analyzing the differences between the configuration list and previously received historical configuration lists, the cloud computing platform can determine the bare metal server to be deployed and the configuration description information associated with that bare metal server. The cloud computing platform can then retrieve the associated configuration-related data from a pre-set database based on this configuration description information and deploy the bare metal server accordingly. Therefore, based on this configuration list, the cloud computing platform can automatically deploy a large number of mixed-type bare metal servers with minimal workload, thereby reducing operational complexity and the probability of errors. Furthermore, the user only needs to upload and maintain the configuration list, while the cloud computing platform maintains the configuration-related data, reducing management difficulty and further decreasing the probability of errors.

[0098] The bare metal server deployment device based on the configuration list in this application embodiment can be a device, or a component, integrated circuit, or chip in a terminal. The device can be a mobile electronic device or a non-mobile electronic device. For example, mobile electronic devices can be mobile phones, tablets, laptops, PDAs, in-vehicle electronic devices, wearable devices, ultra-mobile personal computers (UMPCs), netbooks, or personal digital assistants (PDAs), etc., while non-mobile electronic devices can be servers, network-attached storage (NAS), personal computers (PCs), televisions (TVs), ATMs, or self-service machines, etc. This application embodiment does not impose specific limitations.

[0099] The bare metal server deployment device based on a configuration list in this application embodiment can be a device with an operating system. This operating system can be Android, iOS, or other possible operating systems; this application embodiment does not specifically limit it.

[0100] The bare metal server deployment device based on a configuration list provided in this application embodiment can achieve... Figure 1 The various processes implemented in the bare metal server deployment method embodiment based on the configuration list shown will not be repeated here to avoid duplication.

[0101] Optionally, this application embodiment also provides an electronic device, including a processor 110, a memory 109, and a program or instructions stored in the memory 109 and executable on the processor 110. When the program or instructions are executed by the processor 110, they implement the various processes of the above-described bare metal server deployment method embodiment based on the configuration list and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0102] It should be noted that the electronic devices in the embodiments of this application include the mobile electronic devices and non-mobile electronic devices described above.

[0103] Figure 5 A schematic diagram of the hardware structure of an electronic device to implement an embodiment of this application. The electronic device 100 includes, but is not limited to, components such as: radio frequency unit 101, network module 102, audio output unit 103, input unit 104, sensor 105, display unit 106, user input unit 107, interface unit 108, memory 109, and processor 110.

[0104] Those skilled in the art will understand that the electronic device 100 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 110 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 5 The electronic device structure shown does not constitute a limitation on the electronic device. The electronic device may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here. The processor 110 is configured to, in response to receiving a configuration list, compare the configuration list with a previously received historical configuration list to obtain each data entry in the configuration list that has a difference, wherein the different data entries in the configuration list contain configuration description information for different bare metal servers; and to deploy the bare metal servers associated with each data entry of the difference based on the obtained configuration-related data.

[0105] The radio frequency unit 101 is used to retrieve configuration-related data associated with each data entry in the configuration list that has differences from a preset database.

[0106] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described bare metal server deployment method embodiment based on the configuration list and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0107] The processor is the processor in the electronic device described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0108] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface and the processor are coupled. The processor is used to run programs or instructions to implement the various processes of the above-described bare metal server deployment method embodiment based on the configuration list, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0109] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0110] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0111] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0112] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A bare-metal server deployment method based on a configuration list, characterized in that, Applied to a cloud computing platform, the method includes: In response to receiving a configuration list, the configuration list is compared with a previously received historical configuration list to obtain each data entry in the configuration list that has differences. The different data entries in the configuration list contain configuration description information for different bare metal servers. For each data entry in the configuration list that has a difference, retrieve the configuration-related data associated with the data entry from the preset database; Based on the obtained configuration-related data, the bare metal servers associated with each data entry for which there are differences are deployed.

2. The method according to claim 1, characterized in that, The step of retrieving the configuration-related data associated with the data entry from the preset database includes: For each configuration description in the data entry, the configuration description is used as a search keyword to search the preset database; If no data matching the search keywords is found, the steps of adjusting the search keywords according to preset keyword transformation rules and re-searching the preset database according to the adjusted search keywords are performed iteratively until data matching the adjusted search keywords is found, at which point the search for the configuration description information ends; wherein, the preset keyword transformation rules include: replacing or deleting at least one character in the search keywords with similar characters; Retrieve data that matches the search keywords from the preset database.

3. The method according to claim 2, characterized in that, The step of adjusting the search keywords according to preset keyword transformation rules includes: From a plurality of preset keyword transformation strategies, one preset keyword transformation strategy is randomly selected and executed to adjust the search keywords; wherein, the plurality of preset keyword transformation strategies include: For the character to be replaced in the search keywords, replace the character with the adjacent character on the keyboard; Swap the positions of two adjacent characters in the search keywords; Delete the first character of the specified side in the search keywords.

4. The method according to claim 2, characterized in that, If no data matching the search keywords is found, the method further includes: If the preset iteration termination condition is met, the retrieval of the configuration description information ends, the error information is recorded and the configuration description information is skipped, and the next configuration description information to be retrieved is used as the retrieval keyword to search the preset database. The preset iteration termination condition includes: the length of the retrieval keyword is lower than the preset length threshold.

5. The method according to claim 1, characterized in that, The different data entries in the configuration list contain at least system version information and configuration script information for different bare metal servers; for each data entry in the configuration list with differences, the configuration-related data associated with the data entry is retrieved from a preset database, including: For each data entry in the configuration list that has differences, the configuration-related data associated with the system version information and configuration script information in the data entry are obtained from the preset database.

6. The method according to claim 1, characterized in that, For each data entry in the configuration list that has differences, the configuration-related data associated with the data entry is retrieved from a preset database, including: For each configuration description information in each data entry of the aforementioned discrepancy item, if multiple configuration-related data matching the configuration description information are retrieved from the preset database, the latest uploaded configuration-related data among the multiple configuration-related data is obtained from the preset database.

7. The method according to any one of claims 1-6, characterized in that, The configuration list is constructed based on the spreadsheet file format associated with the office software.

8. A bare-metal server deployment apparatus based on a configuration list, characterized in that, The device, applied to a cloud computing platform, includes: The list processing module is used to compare the configuration list with the previously received historical configuration list in response to receiving the configuration list, and obtain each data entry in the configuration list that has differences. The different data entries in the configuration list contain configuration description information for different bare metal servers. The data acquisition module is used to acquire configuration-related data associated with each data entry in the configuration list that has differences from a preset database. The server deployment module is used to deploy the bare metal servers associated with each data entry that has differences, based on the obtained configuration-related data.

9. An electronic device, characterized in that, It includes a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the bare metal server deployment method based on a configuration list as described in any one of claims 1-7.

10. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the bare metal server deployment method based on a configuration list as described in any one of claims 1-7.

Images