A server management method, device, apparatus and storage medium

Abstract

The application discloses a kind of server management method, device, equipment and storage medium, it is related to server technical field, comprising: obtaining the text data for being used to the target server by external application component for the user input management, obtain server management data;Server management data is sent to target server by server management software;Server management data is received by internal application component in target server and is written into shared area in substrate management controller;Server management data is read from shared area, and the target server is managed using the server management data read to it.The external application component created in the server management software, the internal application component created in the server and the shared area, can not depend on in-band network and out-of-band network interface, and not additional increase hardware, so that the user realizes the same server management with in-band network mode only through out-of-band network.

Description

Technical Field

[0001] This application relates to the field of server technology, and in particular to a server management method, apparatus, device and storage medium. Background Technology

[0002] Currently, server management can be achieved in two ways: one is through in-band network access by server administrators, such as accessing the server operating system's interface data via the in-band network interface; the other is through out-of-band network access by server administrators to hardware such as the BMC (Baseboard Management Controller), such as using management software to obtain interface data from the out-of-band network interface connected to the BMC and then using the obtained interface data to manage the server. However, the management software approach cannot achieve data exchange with the server's in-band operating system.

[0003] Currently, some server users also face the need to manage servers. However, due to permission restrictions, users cannot manage servers through in-band networks. When managing servers through out-of-band networks, some practical functions, such as board upgrades, RAID (Redundant Array of Independent Disks) card management, stress testing, and hard drive erasure, are not fully available due to limitations in BMC hardware capabilities.

[0004] In summary, how to enable server users to manage servers without relying on in-band networks is a problem that still needs to be further solved in this field. Summary of the Invention

[0005] In view of this, the purpose of this application is to provide a server management method, apparatus, device, and storage medium that enables data interaction between management software and the server's in-band system without relying on in-band and out-of-band network interfaces or adding additional hardware, allowing users to achieve the same server management as in-band network management only through the out-of-band network. The specific solution is as follows:

[0006] Firstly, this application discloses a server management method, including:

[0007] Server management data is obtained by acquiring text data entered by the user on the client for managing the target server through a pre-created external application component.

[0008] The server management data is sent to the target server via server management software located on the client; wherein the external application component is located within the server management software;

[0009] The server management data is received by an internal application component pre-created in the target server, and the received server management data is written to a shared area in the baseboard management controller located in the target server.

[0010] The server management data is read from the shared area, and the read server management data is used to manage the target server.

[0011] Optionally, writing the received server management data to a shared area in the baseboard management controller of the target server includes:

[0012] The received server management data is written to a shared area in the baseboard management controller located on the target server using the IPMI tool.

[0013] Optionally, the step of using the IPMI tool to write the received server management data to a shared area in the baseboard management controller located in the target server includes:

[0014] The server management data is divided into text segments according to a preset text length to obtain a target number of server management texts.

[0015] Using the IPMI tool, the received target number of server management texts are sequentially written to the shared area of ​​the baseboard management controller located on the target server.

[0016] Optionally, the server management method further includes:

[0017] After each write to the shared area, the written server management text is verified. If the verification passes, the next write of the server management text continues.

[0018] Optionally, before writing the received server management data to the shared area in the baseboard management controller of the target server, the method further includes:

[0019] Use the IPMI tool to initialize all data in the shared area;

[0020] Mount the LiveCD, set the target server to boot from CD, and then restart the target server; wherein the LiveCD is the carrier of the internal application components.

[0021] Optionally, the server management method further includes:

[0022] The initialization, mounting of the LiveCD, startup of the CD and the target server, and writing of server management data into the shared area are monitored in real time based on a preset failure retry mechanism. If any of the execution processes fails, the corresponding execution process will be retried according to the preset number of retries.

[0023] Optionally, the server management method further includes:

[0024] The internal application components are embedded in a memory operating system, and the memory operating system is distributed to the target server via an out-of-band network, and the target server is restarted.

[0025] Secondly, this application discloses a server management device, comprising:

[0026] The text data acquisition module is used to acquire the text data entered by the user on the client for managing the target server through a pre-created external application component, and obtain server management data.

[0027] A data sending module is used to send server management data to the target server through server management software located on the client; wherein the external application component is located in the server management software;

[0028] A data receiving module is used to receive server management data through an internal application component pre-created in the target server;

[0029] The data writing module is used to write the received server management data to a shared area in the baseboard management controller located in the target server;

[0030] The data reading module is used to read the server management data from the shared area;

[0031] The server management module is used to manage the target server using the read server management data.

[0032] Thirdly, this application discloses an electronic device, including a processor and a memory; wherein, when the processor executes a computer program stored in the memory, it implements the aforementioned server management method.

[0033] Fourthly, this application discloses a computer-readable storage medium for storing a computer program; wherein, when the computer program is executed by a processor, it implements the aforementioned server management method.

[0034] As can be seen, this application first obtains the text data input by the user on the client for managing the target server through a pre-created external application component located in the server management software, thus obtaining server management data. Then, the server management software on the client sends the server management data to the target server. Next, an internal application component pre-created in the target server receives the server management data and writes it to a shared area in the baseboard management controller of the target server. Finally, the server management data is read from the shared area and used to manage the target server. This application, through the external application component created in the server management software, the internal application component created in the server, and the shared area, enables data interaction between the management software and the server's in-band system without relying on in-band and out-of-band network interfaces or adding additional hardware. This allows users to achieve the same server management as in-band network management only through the out-of-band network. Attached Figure Description

[0035] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of this application. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0036] Figure 1 This is a flowchart of a server management method disclosed in this application;

[0037] Figure 2 This is a schematic diagram of a specific server management structure disclosed in this application;

[0038] Figure 3 This is a schematic diagram illustrating the operation of a specific failure retry mechanism disclosed in this application;

[0039] Figure 4 This application discloses a specific server management method flowchart;

[0040] Figure 5 This is a schematic diagram illustrating a specific shared area data partitioning rule disclosed in this application;

[0041] Figure 6 This is a schematic diagram of a specific server data transmission disclosed in this application;

[0042] Figure 7 This is a schematic diagram of a specific server data transmission disclosed in this application;

[0043] Figure 8 This is a schematic diagram of the structure of a server management device disclosed in this application;

[0044] Figure 9 This is a structural diagram of an electronic device disclosed in this application. Detailed Implementation

[0045] 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, and 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.

[0046] This application discloses a server management method. See also Figure 1 As shown, the method includes:

[0047] Step S11: Obtain the text data entered by the user on the client for managing the target server through a pre-created external application component to obtain server management data.

[0048] In this embodiment, see Figure 2 As shown, to enable server users to manage the server via out-of-band network, an internal application component is pre-configured in the target server to be managed, and an external application component is pre-configured in the server management software located on the client side. The target server and the server management software communicate wirelessly via a switch. The external application component can run on a Linux system created on the client side. The internal application component is client software written to enable data interaction between the target server and the server management software. The internal application component uses a memory-bootable system image (LiveCD) as its carrier and runs automatically upon server system startup. It can recognize and respond to commands issued by the external application component, thereby completing the data interaction process. Additionally, it should be noted that a shared area is pre-created in the Baseboard Management Controller (BMC) of the target server. This shared area is a small storage space built into the Baseboard Management Controller. Due to the limited storage space of the Baseboard Management Controller, this shared area is small, such as 512 bytes.

[0049] In this embodiment, when it is necessary to manage the target server, the external application component located in the server management software first obtains the text data input by the user on the client for managing the target server, such as the text data to be transmitted selected by the user at the operating system layer, and obtains the corresponding server management data and stores it in memory.

[0050] In this embodiment, when multiple target servers need to be managed, the internal application component can be embedded in a memory operating system (RAM OS), and the RAM OS can be distributed to each of the target servers via an out-of-band network, and the target servers can be restarted. That is, the internal application component is embedded in a memory operating system, then this system is distributed to each target server via an out-of-band network, and the server is automatically restarted, thereby enabling the server to implement the function of the internal application component.

[0051] Step S12: Send the server management data to the target server through the server management software located on the client; wherein the external application component is located in the server management software.

[0052] In this embodiment, after obtaining server management data by acquiring the text data input by the user on the client for managing the target server through a pre-created external application component, the server management software further generates corresponding data transmission commands to send the acquired server management data to the target server via an out-of-band network. It should be noted that the external application component is located within the server management software; for specific location relationships, please refer to [link to relevant documentation]. Figure 2 As shown.

[0053] Step S13: Receive the server management data through an internal application component pre-created in the target server, and write the received server management data to a shared area in the baseboard management controller of the target server.

[0054] In this embodiment, see Figure 2 As shown, after the server management software sends the aforementioned server management data to the target server, the target server can receive the aforementioned server management data through a pre-created internal application component, and then write the received server management data to the shared area located in the baseboard management controller of the target server.

[0055] In one specific implementation, writing the received server management data to a shared area in the baseboard management controller of the target server may specifically include: using the IPMI (Intelligent Platform Management Interface) tool to write the received server management data to the shared area in the baseboard management controller of the target server. In this embodiment, the shared area in the baseboard management controller of the target server supports reading and writing using the IPMI tool (IPMITOOL). When the internal application component receives server management data, it can write it to the shared area of ​​the baseboard management controller using the IPMI tool.

[0056] In this embodiment, before writing the received server management data to the shared area in the baseboard management controller of the target server, the method further includes: initializing all data in the shared area using the IPMI tool; mounting a LiveCD and setting the target server's boot mode to CD boot, then restarting the target server; wherein the LiveCD is the carrier of the internal application components. It should be noted that, in order to achieve data interaction between the target server and the server management software, the data in the shared area needs to be cleared first to eliminate interfering data; then, the LiveCD carrying the internal application components is mounted, allowing the internal application components to run normally; then, the target server's boot mode is set to CD boot, and the target server is restarted, thereby enabling the LiveCD to run normally. In this way, data interaction between the target server and the server management software can be achieved.

[0057] In this embodiment, to ensure that the data interaction function between the target server and the server management software is enabled, it may further include: real-time monitoring of the execution processes of initialization, mounting the LiveCD, starting the CD and the target server, and writing server management data to the shared area based on a preset failure retry mechanism. If any of the execution processes fails, the corresponding execution process will be retried according to a preset number of retries. It should be noted that, see [link to relevant documentation]. Figure 3As shown, to ensure normal data transmission between the target server and the server management software, a retry mechanism is pre-configured. This mechanism is used to monitor in real time the processes of initializing the data, mounting the LiveCD, starting the CD and the target server, and writing the server management data into the shared area. If any of the above processes fails, the corresponding process can be retried according to the preset number of retries. For example, if the LiveCD mounting fails, it will be mounted 3 times again according to the default number of retries. If it still fails after 3 times, the corresponding failure alarm information can be returned. If the LiveCD is successfully mounted after the retry, the step of setting the target server's boot mode to CD boot will continue.

[0058] Furthermore, to ensure the correctness of data transmission, after the received server management data is written to the shared area, the written server management data can be further verified. If the verification passes, it indicates that the transmitted server management data is correct; if the verification fails, it indicates that the transmitted data has an error. At this time, the above-mentioned failure retry mechanism can be automatically activated to retransmit the server management data.

[0059] Step S14: Read the server management data from the shared area and use the read server management data to manage the target server.

[0060] In this embodiment, after the received server management data is written to the shared area in the baseboard management controller of the target server, the server management data can be read from the shared area. That is, the meaning of the text data in the shared area is parsed, and then the target server can be managed accordingly using the read server management data, such as board upgrades, RAID card management, stress testing, and hard drive erasure.

[0061] It should be noted that in this embodiment, data can be sent from the server management software to the target server via the shared area, and data can also be sent from the target server to the server management software via the shared area. In other words, bidirectional data transmission is possible between the server management software and the target server. Furthermore, to prevent simultaneous write operations by external and internal application components during data transmission in the shared area, a heartbeat mechanism can be implemented to monitor the LiveCD's heartbeat. This mechanism can completely distinguish between text data written by external and internal application components using only one byte, thus completing the heartbeat function.

[0062] As can be seen, this embodiment first obtains the text data input by the user on the client for managing the target server through a pre-created external application component located in the server management software, thus obtaining server management data. Then, the server management software on the client sends the server management data to the target server. Next, an internal application component pre-created in the target server receives the server management data and writes it to a shared area in the baseboard management controller of the target server. Finally, the server management data is read from the shared area and used to manage the target server. This embodiment, through the external application component created in the server management software, the internal application component created in the server, and the shared area, enables data interaction between the management software and the server's in-band system without relying on in-band and out-of-band network interfaces or adding additional hardware. This allows users to achieve the same server management as in-band network management only through the out-of-band network.

[0063] This application discloses a specific server management method. See [link to relevant documentation] Figure 4 As shown, the method includes:

[0064] Step S21: Obtain the text data entered by the user on the client for managing the target server through a pre-created external application component to obtain server management data.

[0065] Step S22: Send the server management data to the target server through the server management software located on the client; wherein the external application component is located in the server management software.

[0066] Step S23: Receive the server management data through an internal application component pre-created in the target server, and divide the server management data into text segments according to a preset text length to obtain a target number of server management texts.

[0067] In this embodiment, after the server management data is sent to the target server, the server management data is received by an internal application component pre-created in the target server. Then, the server management data is divided into text segments according to a preset text length to obtain a target number of server management texts. In one specific implementation, the text segmentation rule is described below. Figure 5As shown, T represents the total number of segments; N is the number of segments currently being transmitted; L is the length of the text data in this transmission (the maximum text length for a single transmission is preset to 496); C is the data control bit, where C is FF indicating the current shared area is in its initial state, C is 00 indicating the internal application component is writing data, C is 01 indicating the internal application component has finished writing and is waiting for the external application component to read, C is 02 indicating the external application component is writing, and C is 03 indicating the external application component has finished writing and is waiting for the internal application component to read; D is the direction of data transmission, where D is FF... This indicates that there are currently no data read / write tasks. When D is 00, it means that data is being transferred from an internal application component to an external application component. When D is 01, it means that data is being transferred from an external application component to an internal application component. H is the LiveCD heartbeat. When H is 00, it means that the internal application component is currently writing data. When H is 01, it means that the external application component is currently writing data. M is the checksum. When M is FF, it means that the checksum failed and the data is invalid. When M is any other value, it means that the checksum succeeded and the data is valid. The specific checksum algorithm is the MD5 algorithm, and the checksum bits are in the 05-15 range of the shared area.

[0068] In one specific implementation, after receiving server management data through an internal application component, the total text length L of the server management data is calculated. Then, the server management data of length L is divided according to a preset text length to obtain a corresponding number of server management texts. For example, if the total text length L of the server management data is 1310 and the preset text length is 496, then the total number of divisions T = (1310 / 496) + 1 = 3.

[0069] Step S24: Use the IPMI tool to sequentially write the received target number of server management texts to the shared area in the baseboard management controller of the target server.

[0070] In this embodiment, after dividing the server management data into text according to a preset text length to obtain a target number of server management texts, the IPMI tool can be used to sequentially write the received target number of server management texts into the shared area of ​​the baseboard management controller located in the target server.

[0071] It should be noted that after each write to the shared area, the written server management text can be validated. If the validation passes, the next piece of server management text can be written. For example, when the total text length L of the server management data is 1310 and the preset text length is 496, the total number of entries T = (1310 / 496) + 1 = 3, indicating that the server management data needs to be written to the shared area in three parts. Therefore, before writing the data, the external application component needs to update T = 3, N = 1, and L = 496, indicating that a total of 3 writes are needed, and this is the first write. This write will fill all remaining space, totaling 496 characters. At the same time, if N = 1, the M field is updated to the number of entries written. The data is based on the 16-bit MD5 hash. After the MD5 hash of the first 496 characters written passes verification, C is updated to 02, indicating that the external application component is writing data to the shared area. At this point, D is 01, indicating the writing direction is from the external application component to the internal application component. As the external application component continuously writes 496 characters to the shared area using the IPMI tool, it modifies C to 03, indicating the third data write operation. At this point, the external application component enters a waiting state until C is changed to FF or a timeout occurs. Further details can be found in [link to documentation]. Figure 6 As shown, the internal application component reads data written to the shared area. It's important to note that the internal application component is in real-time monitoring mode after startup. When it detects that D is not equal to FF, it indicates that a transmission task is currently being executed. It then further checks C. If C equals 03, it means that the external application has completed the execution of a certain segment of data written and is waiting for the internal application component to read it. The internal application component reads based on the fact that T indicates a total of 3 transmissions are needed, and this is the first transmission with a length of 496 characters. Therefore, it can directly read 496 bits sequentially from the beginning of the data using the IPMI tool. After the data is read, C is changed to FF, indicating that this segment of data has been read completely. If N == T, it means that all text has been read. At this point, the MD5 value of the text is checked. If they are the same, D is changed to FF, ending the current read. If they are different, a retry mechanism is triggered to read again. Further, as... Figure 7As shown, while the internal application component is reading data, the external application component is also monitoring the C and D fields in real time. If D == FF, it means the second segment of text data can be written. At this point, N is changed to 2, L is changed to the length of the second segment, and C is changed to 02. Then, the data is continuously written to the shared area until all the text is written. At this point, N = T (i.e., 3), thus completing a full text transfer. Similarly, when data needs to be transferred from the internal application component to the external application component, the data to be transferred can be written to the shared area in segments using the same method, and then read by the external application component. The specific process will not be elaborated further.

[0072] Step S25: Read the server management data from the shared area and use the read server management data to manage the target server.

[0073] For more detailed processing procedures of steps S21, S22, and S25, please refer to the corresponding content disclosed in the foregoing embodiments, which will not be repeated here.

[0074] As can be seen, the embodiments of this application, by creating external application components in the server management software, creating internal application components and shared areas in the server, and performing data interaction between the external and internal application components in a segmented manner, can achieve convenient and quick data interaction between the management software and the server's in-band system without relying on in-band and out-of-band network interfaces, without adding additional hardware, and without BMC providing some configurations. It can also ensure the security and effectiveness of the data transmission process, allowing users to achieve the same server management as in-band network management through out-of-band network only.

[0075] Accordingly, this application also discloses a server management device, see [link to relevant documentation]. Figure 8 As shown, the device includes:

[0076] The text data acquisition module 11 is used to acquire the text data input by the user on the client for managing the target server through a pre-created external application component, and obtain server management data.

[0077] The data sending module 12 is used to send server management data to the target server through server management software located on the client; wherein the external application component is located in the server management software;

[0078] Data receiving module 13 is used to receive server management data through an internal application component pre-created in the target server;

[0079] The data writing module 14 is used to write the received server management data to a shared area in the baseboard management controller located in the target server;

[0080] Data reading module 15 is used to read server management data from the shared area;

[0081] Server management module 16 is used to manage the target server using the read server management data.

[0082] The specific workflow of each of the above modules can be found in the relevant content disclosed in the foregoing embodiments, and will not be repeated here.

[0083] As can be seen, in this embodiment, the text data input by the user on the client for managing the target server is first obtained through an external application component pre-created in the server management software, thus obtaining server management data. Then, the server management software on the client sends the server management data to the target server. Next, an internal application component pre-created in the target server receives the server management data and writes it to a shared area in the baseboard management controller of the target server. Finally, the server management data is read from the shared area and used to manage the target server. This embodiment, through the external application component created in the server management software, the internal application component created in the server, and the shared area, enables data interaction between the management software and the server's in-band system without relying on in-band and out-of-band network interfaces or adding additional hardware. This allows users to achieve the same server management as in-band network management only through the out-of-band network.

[0084] In some specific embodiments, the data writing module 14 may specifically include:

[0085] The first data writing unit is used to write the received server management data to a shared area in the baseboard management controller located in the target server using the IPMI tool.

[0086] In some specific embodiments, the first data writing unit may specifically include:

[0087] A text segmentation unit is used to segment the server management data into text according to a preset text length to obtain a target number of server management texts.

[0088] The second data writing unit is used to use the IPMI tool to sequentially write the received target number of server management texts to the shared area of ​​the baseboard management controller located in the target server.

[0089] In some specific embodiments, the server management device may further include:

[0090] A text verification unit is used to verify the server management text written each time it is written to the shared area.

[0091] The text writing unit is used to continue writing the server-managed text if the verification passes.

[0092] In some specific embodiments, the data writing module 14 may be preceded by:

[0093] An initialization unit is used to initialize all data in the shared area using the IPMI tool;

[0094] The LiveCD mounting unit is used to mount a LiveCD; wherein the LiveCD is the carrier of the internal application component.

[0095] The setup and restart unit is used to set the target server's boot mode to CD boot and then restart the target server.

[0096] In some specific embodiments, the server management device may further include:

[0097] The unit is used to monitor in real time the execution process of initialization, mounting of the LiveCD, startup of the CD and the target server, and writing of server management data into the shared area based on a preset failure retry mechanism. If any of the execution processes fails, the corresponding execution process will be retried according to the preset number of retries.

[0098] In some specific embodiments, the server management device may further include:

[0099] The component-embedded unit is used to embed the internal application components into a memory operating system;

[0100] The distribution unit is used to distribute the memory operating system to the target server via an out-of-band network and restart the target server.

[0101] Furthermore, embodiments of this application also disclose an electronic device, Figure 9 This is a structural diagram of an electronic device 20 according to an exemplary embodiment. The content of the diagram should not be construed as limiting the scope of this application.

[0102] Figure 9 This is a schematic diagram of the structure of an electronic device 20 provided in an embodiment of this application. Specifically, the electronic device 20 may include: at least one processor 21, at least one memory 22, a power supply 23, a communication interface 24, an input / output interface 25, and a communication bus 26. The memory 22 stores a computer program, which is loaded and executed by the processor 21 to implement the relevant steps in the server management method disclosed in any of the foregoing embodiments. Furthermore, the electronic device 20 in this embodiment may specifically be an electronic computer.

[0103] In this embodiment, the power supply 23 is used to provide operating voltage for each hardware device on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and external devices, and the communication protocol it follows can be any communication protocol applicable to the technical solution of this application, and is not specifically limited here; the input / output interface 25 is used to acquire external input data or output data to the outside world, and its specific interface type can be selected according to specific application needs, and is not specifically limited here.

[0104] In addition, the memory 22, as a carrier for resource storage, can be a read-only memory, random access memory, disk or optical disk, etc. The resources stored thereon can include operating system 221, computer program 222, etc., and the storage method can be temporary storage or permanent storage.

[0105] The operating system 221 is used to manage and control the various hardware devices on the electronic device 20 and the computer program 222, which may be Windows Server, Netware, Unix, Linux, etc. In addition to including a computer program capable of performing the server management method executed by the electronic device 20 as disclosed in any of the foregoing embodiments, the computer program 222 may further include a computer program capable of performing other specific tasks.

[0106] Furthermore, this application also discloses a computer-readable storage medium for storing a computer program; wherein, when the computer program is executed by a processor, it implements the aforementioned disclosed server management method. Specific steps of this method can be found in the corresponding content disclosed in the foregoing embodiments, and will not be repeated here.

[0107] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the apparatus disclosed in the embodiments, since it corresponds to the method disclosed in the embodiments, the description is relatively simple; relevant parts can be referred to in the method section.

[0108] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0109] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented directly by hardware, a software module executed by a processor, or a combination of both. The software module can be located in random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.

[0110] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, 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 said element.

[0111] The above provides a detailed description of a server management method, apparatus, device, and storage medium provided in this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the method and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A server management method, characterized in that, include: Server management data is obtained by acquiring text data entered by the user on the client for managing the target server through a pre-created external application component. The server management data is sent to the target server via server management software located on the client; wherein the external application component is located within the server management software; The server management data is received by an internal application component pre-created in the target server, and the received server management data is written to a shared area in the baseboard management controller located in the target server. Read the server management data from the shared area, and use the read server management data to manage the target server; The step of writing the received server management data to the shared area in the baseboard management controller located in the target server includes: The server management data is divided into text segments according to a preset text length to obtain a target number of server management texts; the IPMI tool is used to sequentially write the received target number of server management texts into the shared area of ​​the baseboard management controller located in the target server; Before writing the received server management data to the shared area in the baseboard management controller of the target server, the method further includes: The IPMI tool is used to initialize all data in the shared area; a LiveCD is mounted, and the target server is set to boot from CD, and then the target server is restarted; wherein, the LiveCD is the carrier of the internal application components.

2. The server management method according to claim 1, characterized in that, Also includes: After each write to the shared area, the written server management text is verified. If the verification passes, the next write of the server management text continues.

3. The server management method according to claim 1, characterized in that, Also includes: The initialization, mounting of the LiveCD, startup of the CD and the target server, and writing of server management data into the shared area are monitored in real time based on a preset failure retry mechanism. If any of the execution processes fails, the corresponding execution process will be retried according to the preset number of retries.

4. The server management method according to any one of claims 1 to 3, characterized in that, Also includes: The internal application components are embedded in a memory operating system, and the memory operating system is distributed to the target server via an out-of-band network, and the target server is restarted.

5. A server management device, characterized in that, The steps for implementing the server management method as described in any one of claims 1 to 4 include: The text data acquisition module is used to acquire the text data entered by the user on the client for managing the target server through a pre-created external application component, and obtain server management data. A data sending module is used to send server management data to the target server through server management software located on the client; wherein the external application component is located in the server management software; A data receiving module is used to receive server management data through an internal application component pre-created in the target server; The data writing module is used to write the received server management data to a shared area in the baseboard management controller located in the target server; The data reading module is used to read the server management data from the shared area; The server management module is used to manage the target server using the read server management data.

6. An electronic device, characterized in that, It includes a processor and a memory; wherein, when the processor executes a computer program stored in the memory, it implements the server management method as described in any one of claims 1 to 4.

7. A computer-readable storage medium, characterized in that, Used to store computer programs; wherein, when the computer programs are executed by a processor, they implement the server management method as described in any one of claims 1 to 4.

Images