An identity-based self-discovery bulk remote deployment method and device

Abstract

The application relates to an identification-based self-discovery batch remote deployment method and device, and belongs to the technical field of remote deployment. The method comprises the following steps: starting an OSDP management server to initialize a target node; starting an OSBP image service of the target node to receive identification information of the target node; sending the identification information to the OSDP management server; generating a kickstart file and a grub file of the target node; restarting the target node in response to a restart instruction; sending a dhcp address request instruction to the OSDP management server; sending the kickstart file and a system image installation package to the target node based on the MAC address of the target node; and remotely deploying the target node according to the received kickstart file and the system image installation package. The application can complete batch remote deployment, and improves the stability and reliability of deployment.

Description

TECHNICAL FIELD

[0001] The present application belongs to the technical field of remote deployment, and particularly relates to a self-discovery batch remote deployment method and device based on identification. BACKGROUND

[0002] Remote deployment is a technology that distributes software, operating systems, configuration files, or security patches to multiple devices from a remote location through a network without direct contact with the target devices. The self-discovery batch remote deployment method based on identification is a technology that automatically identifies devices through their unique identification and uses a self-discovery mechanism to perform batch remote configuration and deployment. It is suitable for large-scale device management, such as rapid deployment of enterprise network devices, Internet of Things devices, and data center servers.

[0003] The self-discovery batch remote deployment method based on identification is commonly used in cloud computing and Internet of Things scenarios. It achieves precise identification and batch deployment of devices by automatically identifying their unique identification information (such as MAC addresses, serial numbers, etc.). This method ensures efficient and accurate remote configuration and installation when facing a large number of devices.

[0004] However, in existing remote deployment methods, the deployment system cannot accurately identify the unique identification information of each target device, and devices are easily confused, increasing the risk of configuration errors. When distributing configuration files and setting up networks, administrators need to manually confirm target devices, which cannot automatically match devices and configurations, resulting in low efficiency and high error rate of remote deployment, affecting the stability of the system. SUMMARY

[0005] In view of the above deficiencies of the prior art, in order to solve the technical problems that in existing remote deployment methods, the deployment system cannot accurately identify the unique identification information of each target device, devices are easily confused, increasing the risk of configuration errors, and when distributing configuration files and setting up networks, administrators need to manually confirm target devices, which cannot automatically match devices and configurations, resulting in low efficiency and high error rate of remote deployment, affecting the stability of the system, the present application provides a self-discovery batch remote deployment method and device based on identification.

[0006] In a first aspect of the present application, a self-discovery batch remote deployment method based on identification is provided, the method comprising:

[0007] S1, starting an OSDP management server to initialize a target node;

[0008] S2, starting an OSBP mirror service of the target node, and receiving identification information of the target node, wherein the identification information comprises a target node name and target node hardware information, and the hardware information comprises a MAC address of the target node;

[0009] S3, sending the identification information to an OSDP management service end;

[0010] S4, generating a kickstart file and a grub file of the target node, wherein the kickstart file comprises a to-be-installed operating system version of the target node and network card information based on the MAC address;

[0011] S5, issuing a restart instruction to the target node;

[0012] S6, restarting the target node in response to the restart instruction;

[0013] S7, sending a dhcp address request instruction to the OSDP management service end;

[0014] S8, sending the kickstart file and a system image installation package corresponding to the to-be-installed operating system version to the target node based on the MAC address of the target node in response to the dhcp address request instruction;

[0015] S9, remotely deploying the target node according to the received kickstart file and the system image installation package.

[0016] Further, S1 specifically comprises:

[0017] allocating a default IP address to the target node to complete initialization of the target node.

[0018] Further, S2 specifically comprises:

[0019] S201, generating an identification filling interface through the OSBP mirror service;

[0020] S202, receiving the identification information through the identification filling interface.

[0021] Further, S3 specifically comprises:

[0022] pushing the identification information to the OSDP management service end in a broadcast form at an interval of a preset time length.

[0023] Further, S4 specifically comprises:

[0024] S401, establishing a communication connection between the OSDP management service end and the target node;

[0025] S402, store the identification information into a database of the OSDP management server, and generate a kickstart file and a grub file of the target node based on the identification information.

[0026] Further, the communication connection is a socket communication connection based on TCP protocol.

[0027] The second aspect of the application provides a device for identity-based self-discovery batch remote deployment, which is used for implementing the identity-based self-discovery batch remote deployment method of any one of the first aspect, and the device comprises:

[0028] An initialization module is configured to start the OSDP management server to initialize the target node.

[0029] A starting module is configured to start an OSBP image service of the target node and receive identification information of the target node, wherein the identification information comprises a target node name and hardware information of the target node, and the hardware information comprises a MAC address of the target node.

[0030] A first sending module is configured to send the identification information to the OSDP management server.

[0031] A generating module is configured to generate a kickstart file and a grub file of the target node, wherein the kickstart file comprises a to-be-installed operating system version of the target node and network card information based on the MAC address.

[0032] A delivering module is configured to deliver a restart instruction to the target node.

[0033] A restarting module is configured to restart the target node in response to the restart instruction.

[0034] A second sending module is configured to send a dhcp address request instruction to the OSDP management server.

[0035] A responding module is configured to send the kickstart file and a system image installation package corresponding to the to-be-installed operating system version to the target node based on the MAC address of the target node in response to the dhcp address request instruction.

[0036] A deploying module is configured to remotely deploy the target node according to the received kickstart file and system image installation package.

[0037] Further, the initialization module is specifically configured to:

[0038] allocate a default IP address to the target node, and complete the initialization of the target node.

[0039] Further, the starting module specifically comprises:

[0040] The filling submodule is configured to generate an identification filling interface through the OSBP mirror service;

[0041] The receiving submodule is configured to receive identification information through the identification filling interface.

[0042] Further, the first sending module is specifically configured to:

[0043] The identification information is pushed to the OSDP management server in a broadcast form at intervals of a preset time length.

[0044] Further, the generating module specifically includes:

[0045] The establishing submodule is configured to establish a communication connection between the OSDP management server and the target node.

[0046] The generating submodule is configured to store the identification information into a database of the OSDP management server, and generate a kickstart file and a grub file of the target node based on the identification information.

[0047] Further, the communication connection is a socket communication connection based on a TCP protocol.

[0048] In a third aspect, the present application provides an identification-based self-discovery batch remote deployment system, comprising a memory and one or more processors.

[0049] The memory stores one or more application programs, and the one or more application programs are adapted to be executed by the one or more processors to implement the identification-based self-discovery batch remote deployment method of the first aspect.

[0050] In a fourth aspect, the present application provides a computer readable storage medium, which stores a computer program capable of being loaded and executed by a processor to implement the identification-based self-discovery batch remote deployment method of the first aspect.

[0051] The present application has the following advantages:

[0052] In the embodiment of the present application, the identification information of the target node is automatically received, each target node is accurately identified, the risk of device identification confusion is avoided, the identification information is sent to the OSDP management server, the reliable communication and data exchange between the OSDP management server and the target node are ensured, the data is ensured not to be lost during deployment, the risk of human operation error is reduced through the kickstart file and the system image installation package, the accuracy and consistency of deployment are ensured, the information of the target node is matched with its deployment configuration, the batch operation of a large number of devices is automatically implemented through the automatic issue of the restart instruction and the reception of the dhcp address request instruction, the deployment efficiency of large-scale devices is improved, and the stability and reliability of deployment are enhanced. BRIEF DESCRIPTION OF DRAWINGS

[0053] The accompanying drawings are included to provide a further understanding of the present application, and are incorporated in and constitute a part of this specification. The drawings illustrate embodiments of the present application and, together with the description, serve to explain the principles of the present application. In the drawings:

[0054] Figure 1 is a flow diagram of a self-discovery batch remote deployment method based on identification provided by an embodiment of the present application;

[0055] Figure 2 is a structural diagram of a self-discovery batch remote deployment device based on identification provided by an embodiment of the present application;

[0056] Figure 3 is a structural diagram of a self-discovery batch remote deployment system based on identification provided by an embodiment of the present application. DETAILED DESCRIPTION

[0057] In order to make the personnel in the art better understand the technical solutions in the embodiments of the present application, the technical solutions of the present application will be described clearly and completely below in conjunction with the drawings. Obviously, the described embodiments are a part of the embodiments of the present application, rather than all the embodiments. It should be understood that these descriptions are exemplary, and are not intended to limit the scope of the present application. Based on the embodiments of the present application, all other embodiments obtained by those of ordinary skill in the art without creative work should fall within the scope of the present application.

[0058] In addition, in the following description, the description of well-known structures and techniques is omitted to avoid unnecessary confusion of the concepts disclosed in the present application.

[0059] In the description of the present application, it should be noted that, unless otherwise explicitly specified and limited, the orientation or positional relationship indicated by the terms "center", "upper", "lower", "left", "right", "vertical", "horizontal", "inner", "outer" and the like is based on the orientation or positional relationship shown in the drawings, and is only for the convenience of describing the present application and simplifying the description, and does not indicate or imply that the device or element referred to must have a particular orientation, be constructed and operated in a particular orientation, and therefore cannot be understood as a limitation on the present application. In addition, the terms "first", "second", "third" are only for descriptive purposes and cannot be understood as indicating or implying relative importance. The terms "mounting", "connecting", "connecting" should be broadly understood, for example, it can be fixedly connected, or it can be detachably connected, or integrally connected; it can be mechanically connected, or it can be electrically connected; it can be directly connected, or it can be indirectly connected through an intermediate medium, or it can be the communication between two elements. For those skilled in the art, the specific meaning of the above terms in the present application can be understood according to the specific circumstances.

[0060] The exemplary embodiments will be described in detail herein, with examples shown in the drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Rather, they are merely examples of methods and systems consistent with some aspects of the present application as detailed in the appended claims.

[0061] In order to solve the technical problems that in the prior remote deployment method, the deployment system cannot accurately identify the unique identity information of each target device, the devices are easily confused, the risk of configuration error is increased, the administrator needs to manually confirm the target device when performing configuration file distribution and network setting, the device and the configuration cannot be automatically matched, resulting in low efficiency and high error rate of remote deployment, affecting the stability of the system, the present application provides a self-discovery batch remote deployment method and device based on identification.

[0062] Method embodiment

[0063] Referring to Figure 1 , a flowchart of a self-discovery batch remote deployment method based on identification provided by an embodiment of the present application is shown.

[0064] The self-discovery batch remote deployment method based on identification provided by the embodiment of the present application, the method comprises:

[0065] Specifically, the method comprises steps S1 to S9:

[0066] S1, starting the OSDP management server to initialize the target node.

[0067] The OSDP (Operating System Deployment Platform) management server is a central control system responsible for managing and coordinating the entire operating system deployment process, and can communicate with each target node, distribute configuration files, operating system images, and send control instructions. The target node refers to a server or device that needs to install an operating system or be configured. The target node is connected to the management server through a network and accepts the deployment instructions issued by the management server.

[0068] In a possible implementation, S1 specifically includes:

[0069] The default IP address is assigned to the target node, and the initialization of the target node is completed.

[0070] The default IP address refers to an IP address automatically assigned to a device by a system or a management server when the device is initially configured or accessed in a network. This address enables the device to perform basic communication in the network and is usually used in the device initialization or configuration phase.

[0071] It should be noted that the OSDP management server can automatically complete the initialization configuration of the node, reducing the tedious steps of manually assigning IP addresses. Through the automated process, the system can batch process the initialization work of multiple nodes, improving the deployment efficiency and ensuring the consistency and accuracy of all nodes during initialization.

[0072] S2, starting the OSBP image service of the target node, receiving the identification information of the target node, wherein the identification information includes the target node name and the target node hardware information, and the hardware information includes the MAC address of the target node.

[0073] In a possible implementation, S2 specifically includes:

[0074] S201, generating an identification filling interface through the OSBP image service.

[0075] The identification filling interface is a user interface generated by the OSBP image service for inputting the identification of the device.

[0076] It should be noted that by generating the identification filling interface, the identification information of the target node can be conveniently input or confirmed, ensuring the uniqueness and accuracy of each node. This not only simplifies the device identification process, but also improves the flexibility and reliability of deployment, especially in large-scale deployment, which can quickly provide correct identification information for each node and reduce the risk of incorrect configuration.

[0077] S202, receiving the identification information through the identification filling interface.

[0078] It should be noted that the management server capable of collecting the identification information of the target nodes through automation can accurately identify each device, ensure that the correct operating system image and configuration file are distributed for each node, eliminate the need for manual matching of nodes and configuration, reduce human errors, and improve the efficiency and accuracy of deployment.

[0079] S3, sending the identification information to the OSDP management server.

[0080] The OSDP (Operating System Deployment Platform) management server is the core of the deployment system, which is responsible for receiving the identification information of the nodes, generating configuration files, managing the distribution of operating system images, and coordinating the deployment process.

[0081] In a possible implementation, S3 specifically includes:

[0082] The identification information is pushed to the OSDP management server in the form of broadcast at intervals for a preset duration.

[0083] It should be noted that by sending the identification information to the management server, automatic identification and dynamic management of the nodes are realized, and the OSDP management server can automatically generate a deployment strategy based on the information, ensuring that each node receives an operating system and related software suitable for its hardware configuration and network environment, avoiding identification errors and delays caused by manual operation.

[0084] S4, generating a kickstart file and a grub file of the target node, wherein the kickstart file includes the to-be-installed operating system version of the target node and the network card information based on the MAC address.

[0085] The kickstart file is an automatic configuration file, usually used for installation of Red Hat and its derivative versions of Linux operating system, which defines all parameters required in the operating system installation process, including partition scheme, software package selection, network configuration, etc., thereby realizing unattended installation of operating system. GRUB (Grand Unified Bootloader, Grand Unified Bootloader) is a boot loader, which is used to boot the operating system kernel, and the grub file contains configuration information required in the system startup process, such as boot sequence, kernel parameters, etc.

[0086] In a possible implementation, S4 specifically includes:

[0087] S401, establishing a communication connection between the OSDP management server and the target node.

[0088] The communication connection refers to a two-way communication channel established in the network, so that the OSDP management server and the target node can transmit data, send instructions and receive state information to each other.

[0089] It should be noted that by establishing the communication connection between the management server and the target node, the stability and real-time performance of data transmission during system deployment are ensured. The establishment of the communication connection enables the management server to monitor the node state, send instructions, and distribute the operating system image and configuration file in real time, ensuring the continuity and efficiency of the deployment process.

[0090] S402, store the identification information into the database of the OSDP management server, and generate the kickstart file and the grub file of the target node based on the identification information.

[0091] In a possible implementation, the communication connection is a socket communication connection based on TCP protocol.

[0092] The TCP (Transmission Control Protocol) is a connection-oriented and reliable transport layer protocol that ensures data transmission in an orderly and error-free manner in the network. TCP ensures the integrity and accuracy of data transmission by establishing a connection, confirming data reception, and retransmitting lost data packets. Socket is the endpoint of network communication, used to establish a two-way communication connection between different devices through the network. Socket communication based on TCP protocol is a commonly used communication method that can create a stable and reliable connection between two devices to transmit data.

[0093] It should be noted that the automatic generation of the kickstart file and the grub file completely automates the operating system installation process, and customizes the configuration according to the hardware information and MAC address of each node, ensuring adaptability. This avoids the tediousness and possible errors of manual configuration, improves the efficiency and consistency of large-scale deployment, and ensures that the operating system installation process of all nodes is consistent, accurate and fast.

[0094] S5, issue a restart instruction to the target node.

[0095] It should be noted that issuing a restart instruction can remotely and automatically control the restart process of the target node, avoiding manual intervention and making the batch deployment process more efficient.

[0096] S6, in response to the restart instruction, restart the target node.

[0097] It should be noted that the target node automatically responds to the restart instruction issued by the management service end to complete system restart, greatly reducing manual intervention and improving the efficiency and consistency of batch deployment. Through remote automatic restart, the target node can continue to perform deployment tasks according to the predetermined process, ensuring the smoothness of the deployment process and reducing downtime, and is suitable for rapid deployment and management of large-scale equipment.

[0098] S7, send a dhcp address request instruction to the OSDP management service end.

[0099] Among them, DHCP (Dynamic Host Configuration Protocol) is used to automatically allocate IP addresses, and the target node requests the allocation of IP addresses and other network configuration information (such as gateway, subnet mask, etc.) from the DHCP server by sending a DHCP address request instruction, so that the node can be correctly connected to the network.

[0100] It should be noted that automatically sending the DHCP address request instruction enables the target node to dynamically obtain network configuration, reducing the tediousness and errors of manual IP address configuration. Through the automatic network configuration of DHCP, the deployment process is more efficient, especially in large-scale systems, which enables each node to quickly access the network and ensures the smooth progress of the entire deployment process, improving the flexibility and adaptability of the system.

[0101] S8, in response to the dhcp address request instruction, send a kickstart file and a system image installation package corresponding to the to-be-installed operating system version to the target node based on the MAC address of the target node.

[0102] Among them, MAC (Media Access Control) address is the unique hardware identifier of network equipment, and each network interface card has a unique MAC address, which is used to identify devices in a local area network. MAC address is used for device identification in network communication.

[0103] It should be noted that the target node is accurately identified based on the MAC address, and the kickstart file and operating system image installation package are sent to it, ensuring that each device can obtain the correct operating system and configuration file in large-scale deployment, reducing the error rate and complexity of manual operation, improving the automation and efficiency of batch deployment, and ensuring the accuracy and consistency of system deployment.

[0104] S9, according to the received kickstart file and system image installation package, remotely deploy the target node.

[0105] It should be noted that the target nodes rely on the kickstart file for automatic operating system installation, reducing manual intervention and enabling efficient large-scale batch deployment. By combining the kickstart file and the system image, the configuration and operating system version of all nodes are ensured to be consistent, improving the accuracy and speed of deployment, while significantly reducing the possibility of errors.

[0106] The beneficial effects of this invention are as follows:

[0107] In this embodiment of the invention, by automatically receiving the identification information of the target nodes, each target node is accurately identified, avoiding the risk of device identification confusion. The identification information is sent to the OSDP management server, ensuring reliable communication and data exchange between the OSDP management server and the target nodes, and ensuring that data is not lost during deployment. The kickstart file and system image installation package reduce the risk of human error, ensuring the accuracy and consistency of deployment, and matching the information of the target nodes with their deployment configuration. By automatically issuing restart commands and receiving DHCP address request commands, batch operations on a large number of devices are spontaneously realized, improving the deployment efficiency of large-scale devices and enhancing the stability and reliability of deployment.

[0108] Device Examples

[0109] Reference manual attached Figure 2 The diagram shows a schematic representation of an identifier-based self-discovery batch remote deployment device provided in an embodiment of the present invention.

[0110] Another specific embodiment of the present invention discloses an identifier-based self-discovery batch remote deployment device, used to implement the identifier-based self-discovery batch remote deployment method of any of the method embodiments. The identifier-based self-discovery batch remote deployment device 20 includes:

[0111] Initialization module 201 is used to start the OSDP management server to initialize the target node.

[0112] The startup module 202 is used to start the OSBP image service of the target node and receive the identification information of the target node, wherein the identification information includes the target node name and the target node hardware information, wherein the hardware information includes the target node's MAC address.

[0113] The first sending module 203 is used to send the identification information to the OSDP management server.

[0114] The generation module 204 is used to generate the kickstart file and grub file for the target node. The kickstart file includes the operating system version to be installed on the target node and the network card information based on the MAC address.

[0115] The issuing module 205 is configured to issue the restart instruction to the target node.

[0116] The restart module 206 is configured to restart the target node in response to the restart instruction.

[0117] The second sending module 207 is configured to send a dhcp address request instruction to an OSDP management server.

[0118] The response module 208 is configured to send a kickstart file and a system image installation package corresponding to a to-be-installed operating system version to the target node based on a MAC address of the target node in response to the dhcp address request instruction.

[0119] The deployment module 209 is configured to remotely deploy the target node according to the received kickstart file and the system image installation package.

[0120] In a possible implementation, the initialization module is specifically configured to:

[0121] assign a default IP address to the target node, and complete the initialization of the target node.

[0122] In a possible implementation, the starting module specifically includes:

[0123] The filling submodule is configured to generate an identification filling interface through an OSBP image service.

[0124] The receiving submodule is configured to receive identification information through the identification filling interface.

[0125] In a possible implementation, the first sending module is specifically configured to:

[0126] push the identification information to the OSDP management server in a broadcast form at an interval of a preset time length.

[0127] In a possible implementation, the generating module specifically includes:

[0128] The establishing submodule is configured to establish a communication connection between the OSDP management server and the target node.

[0129] The generating submodule is configured to store the identification information into a database of the OSDP management server, and generate a kickstart file and a grub file of the target node based on the identification information.

[0130] In a possible implementation, the communication connection is a socket communication connection based on a TCP protocol.

[0131] The present application has the following advantages:

[0132] In the embodiment of the present application, each target node is accurately identified by automatically receiving the identification signal of the target node, avoiding the risk of device identification confusion, and sending the identification information to the OSDP management server, thereby guaranteeing reliable communication and data exchange between the OSDP management server and the target node, ensuring that data will not be lost during deployment, reducing the risk of human operation errors through the kickstart file and system image installation package, ensuring the accuracy and consistency of deployment, matching the information of the target node with its deployment configuration, automatically issuing a restart instruction and receiving a dhcp address request instruction to automatically implement batch operation on a large number of devices, improve the deployment efficiency of large-scale devices, and enhance the stability and reliability of deployment.

[0133] System embodiment

[0134] Referring to the accompanying drawings Figure 3 Fig. 1 shows a structural schematic diagram of a self-discovery batch remote deployment system based on identification provided by an embodiment of the present application.

[0135] The present application provides a self-discovery batch remote deployment system based on identification 30, comprising a memory 303 and one or more processors 301.

[0136] The memory 303 stores one or more application programs, and the one or more application programs are adapted to be executed by the one or more processors 301 to implement the self-discovery batch remote deployment method based on identification of the method embodiment.

[0137] The self-discovery batch remote deployment system based on identification 30 comprises a processor 301 and a memory 303. The processor 301 and the memory 303 are connected, such as through a bus 302.

[0138] The structure of the self-discovery batch remote deployment system based on identification 30 does not constitute a limitation on the embodiments of the present application.

[0139] The processor 301 can be a CPU, a general-purpose processor, a DSP, an ASIC, an FPGA or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It can implement or execute various exemplary logical blocks, modules and circuits described in combination with the disclosure. The processor 301 can also be a combination of computing functions, such as a combination of one or more microprocessors, a combination of DSP and microprocessor, etc.

[0140] The bus 302 can include a path for conveying information between the aforementioned components. The bus 302 can be a PCI bus or an EISA bus, etc. The bus 302 can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is shown in the figure, but it does not mean that there is only one bus or only one type of bus.

[0141] The memory 303 can be a ROM or other type of static storage device that can store static information and instructions, a RAM or other type of dynamic storage device that can store information and instructions, an EEPROM, a CD-ROM or other optical disk storage, an optical disk storage (including a compact disk, a laser disk, an optical disk, a digital versatile disk, a Blu-ray disk, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto.

[0142] Computer-readable storage medium embodiment

[0143] The present application provides a computer-readable storage medium, which stores a computer program capable of being loaded and executed by a processor to implement the identity-based self-discovery bulk remote deployment method of the first aspect.

[0144] The applicant of the present application has made a detailed description and explanation of the embodiments of the present application in combination with the drawings of the specification, but those skilled in the art should understand that the above embodiments are only preferred embodiments of the present application, and the detailed description is only to help the reader better understand the spirit of the present application, and is not a limitation on the protection scope of the present application, on the contrary, any improvement or modification based on the spirit of the present application should fall within the protection scope of the present application.

[0145] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the embodiments of the present application, and are not a limitation. Although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that the technical solutions recorded in the foregoing embodiments can be modified, or some technical features can be replaced by equivalent ones; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application, and any changes or replacements that can be easily thought of by those skilled in the art within the technical scope disclosed by the present application should be covered within the protection scope of the present application.

Claims

1. A method for self-discovery batch remote deployment based on identifiers, characterized in that, The identity-based self-discovery batch remote deployment method comprises: S1, starting an OSDP management server to initialize a target node; S2, starting an OSBP image service of the target node to receive identity information of the target node, wherein the identity information comprises a target node name and target node hardware information, and the hardware information comprises a MAC address of the target node; S3, sending the identity information to the OSDP management server; S4, generating a kickstart file and a grub file of the target node, wherein the kickstart file comprises a to-be-installed operating system version of the target node and network card information based on the MAC address; S5, issuing a restart instruction to the target node; S6, restarting the target node in response to the restart instruction; S7, sending a dhcp address request instruction to the OSDP management server; S8, sending the kickstart file and a system image installation package corresponding to the to-be-installed operating system version to the target node based on the MAC address of the target node in response to the dhcp address request instruction; S9, remotely deploying the target node according to the received kickstart file and the system image installation package.

2. The identity based self-discovery bulk remote deployment method of claim 1, wherein, The S1 specifically comprises: allocating a default IP address to the target node to complete the initialization of the target node.

3. The identity based self-discovery bulk remote deployment method of claim 1, wherein, The S2 specifically comprises: S201, generating an identity filling interface through the OSBP image service; S202, receiving the identity information through the identity filling interface.

4. The identity based self-discovery bulk remote deployment method of claim 1, wherein, The S3 specifically comprises: pushing the identity information to the OSDP management server in a broadcast form at an interval of a preset time length.

5. The identity based self-discovery bulk remote deployment method of claim 1, wherein, The S4 specifically comprises: S401, establishing a communication connection between the OSDP management server and the target node; S402, storing the identity information in a database of the OSDP management server, and generating the kickstart file and the grub file of the target node based on the identity information.

6. The identity based self-discovery bulk remote deployment method of claim 5, wherein, The communication connection is a socket communication connection based on a TCP protocol.

7. An identity-based self-discovery bulk remote deployment apparatus, comprising: The identity-based self-discovery batch remote deployment device comprises: an initialization module configured to start an OSDP management server to initialize a target node; a starting module configured to start an OSBP image service of the target node to receive identity information of the target node, wherein the identity information comprises a target node name and target node hardware information, and the hardware information comprises a MAC address of the target node; a first sending module configured to send the identity information to the OSDP management server; a generating module configured to generate a kickstart file and a grub file of the target node, wherein the kickstart file comprises a to-be-installed operating system version of the target node and network card information based on the MAC address; a issuing module configured to issue a restart instruction to the target node; A restarting module, configured to restart the target node in response to the restarting instruction; A second sending module, configured to send a dhcp address request instruction to an OSDP management server; A responding module, configured to send the kickstart file and a system image installation package corresponding to the to-be-installed operating system version to the target node based on a MAC address of the target node in response to the dhcp address request instruction; A deploying module, configured to perform remote deployment of the target node according to the received kickstart file and the system image installation package.

8. The identity-based self-discovery bulk remote-deployment apparatus of claim 7, wherein, The initializing module is specifically configured to: Assign a default IP address to the target node, and complete initialization of the target node.

9. The identity-based self-discovery bulk remote-deployment apparatus of claim 7, wherein, The starting module specifically includes: A filling submodule, configured to generate an identification filling interface through the OSBP image service; A receiving submodule, configured to receive the identification information through the identification filling interface.

10. The identity-based self-discovery bulk remote-deployment apparatus of claim 7, wherein, The first sending module is specifically configured to: Push the identification information to the OSDP management server in a broadcast form at an interval of a preset time length.

Images