Identification-based self-discovery batch remote deployment method and device

Abstract

The invention relates to an identification-based self-discovery batch remote deployment method and device, and belongs to the technical field of remote deployment. Comprising the following steps: starting an OSDP management server to initialize a target node; starting an OSOP mirroring service of the target node, and receiving identification information of the target node; sending the identification information to an OSDP management server; generating a kickstart file and a grub file of the target node; in response to the restart instruction, restarting a target node; sending a dhcp address request instruction to an OSDP management server; sending the kickstart file and the system mirror image installation package to the target node based on the MAC address of the target node; and performing remote deployment of the target node according to the received kickstart file and the system mirror image installation package. According to the invention, remote deployment can be completed in batches, and the stability and reliability of deployment are improved.

Description

Technical Field

[0001] The present invention belongs to the technical field of remote deployment, and in particular relates to a method and device for self-discovery batch remote deployment based on identification. Background Art

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

[0003] The identification-based self-discovery batch remote deployment method is usually used in cloud computing, Internet of Things and other scenarios. The identification-based batch remote deployment method realizes accurate identification and batch deployment of devices by automatically identifying the unique identification information of the device (such as MAC address, serial number, etc.). This method ensures that the system can perform efficient and accurate remote configuration and installation when facing a large number of devices.

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

[0005] In view of the above deficiencies in the prior art, in order to solve the problem that in the existing 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 errors is increased, and when distributing configuration files and setting up the network, the administrator needs to manually confirm the target device, and the device and configuration cannot be automatically matched, resulting in low efficiency and high error rate of remote deployment, which affects the technical problem of system stability, the present invention provides a self-discovery batch remote deployment method and device based on identification.

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

[0007] S1, start the OSDP management server to initialize the target node;

[0008] S2, start the OSOP mirroring service of the target node, and receive 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 MAC address of the target node;

[0009] S3, sending the identification information to the OSDP management server;

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

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

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

[0013] S7, sending a DHCP address request instruction to the OSDP management server;

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

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

[0016] Furthermore, S1 is specifically:

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

[0018] Furthermore, S2 specifically includes:

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

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

[0021] Furthermore, S3 is specifically:

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

[0023] Furthermore, S4 specifically includes:

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

[0025] S402, storing the identification information in a database of the OSDP management server, and generating a kickstart file and a grub file of the target node based on the identification information.

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

[0027] In a second aspect of the present invention, a self-discovery batch remote deployment device based on identification is proposed, which is used to implement the self-discovery batch remote deployment method based on identification according to any one of the first aspects, and the device includes:

[0028] The initialization module is used to start the OSDP management server to initialize the target node;

[0029] A startup module, used to start the OSOP mirroring service of the target node, and receive 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 MAC address of the target node;

[0030] A first sending module, used to send identification information to the OSDP management server;

[0031] A generation module, used to generate a kickstart file and a grub file of a target node, wherein the kickstart file includes the version of the operating system to be installed on the target node and network card information based on the MAC address;

[0032] A sending module is used to send a restart instruction to a target node;

[0033] A restart module, used to restart the target node in response to the restart instruction;

[0034] The second sending module is used to send a DHCP address request instruction to the OSDP management server;

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

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

[0037] Furthermore, the initialization module is specifically used for:

[0038] Assign the default IP address to the target node to complete the initialization of the target node.

[0039] Furthermore, the startup module specifically includes:

[0040] The filling submodule is used to generate the identification filling interface through the OSOP mirror service;

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

[0042] Furthermore, the first sending module is specifically used for:

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

[0044] Furthermore, the generation module specifically includes:

[0045] Establish a submodule for establishing a communication connection between the OSDP management server and the target node;

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

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

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

[0049] One or more application programs are stored in the memory, and the one or more application programs are suitable for being executed by one or more processors to implement the identification-based self-discovery batch remote deployment method of the first aspect.

[0050] A fourth aspect of the present invention provides a computer-readable storage medium having a computer program stored thereon, which can be loaded and executed by a processor to implement the identification-based self-discovery batch remote deployment method of the first aspect.

[0051] The beneficial effects of the present invention are as follows:

[0052] In the embodiment of the present invention, by automatically receiving the identification information of the target node, each target node is accurately identified, the risk of device identification confusion is avoided, and the identification information is sent to the OSDP management server, thereby ensuring reliable communication and data exchange between the OSDP management server and the target node, ensuring that data will not be lost during the deployment process, and reducing the risk of human operational errors through the kickstart file and the system image installation package, ensuring the accuracy and consistency of the deployment, and matching the information of the target node with its deployment configuration, and spontaneously implementing batch operations on a large number of devices by automatically issuing restart instructions and receiving DHCP address request instructions, thereby improving the deployment efficiency of large-scale equipment and enhancing the stability and reliability of the deployment. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] The accompanying drawings are only used to illustrate specific embodiments and are not considered to limit the present invention. In the entire drawings, the same reference symbols represent the same components. Obviously, the drawings described below are only some embodiments recorded in the embodiments of the present invention. For those of ordinary skill in the art, other drawings can also be obtained based on these drawings.

[0054] Figure 1 It is a flow chart of a method for self-discovery and remote batch deployment based on identification provided by an embodiment of the present invention;

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

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

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

[0058] Furthermore, in the following description, descriptions of well-known structures and technologies are omitted to avoid unnecessarily obscuring the concepts disclosed in the present invention.

[0059] In the description of the present invention, it should be noted that, unless otherwise clearly specified and limited, the orientation or position relationship indicated by the terms "center", "upper", "lower", "left", "right", "vertical", "horizontal", "inside", "outside", etc. is based on the orientation or position relationship shown in the drawings, which is only for the convenience of describing the present invention and simplifying the description, and does not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as a limitation of the present invention. In addition, the terms "first", "second", and "third" are only used for descriptive purposes and cannot be understood as indicating or implying relative importance. The terms "installed", "connected", and "connected" should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection, or it can be indirectly connected through an intermediate medium, or it can be a connection between the two elements. For those of ordinary skill in the art, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.

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

[0061] In order to solve the technical problems that in the existing 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 errors is increased, and the administrator needs to manually confirm the target device when distributing configuration files and setting up the network, and the device and configuration cannot be automatically matched, resulting in low efficiency and high error rate of remote deployment, which affects the stability of the system, the present invention provides a self-discovery batch remote deployment method and device based on identification.

[0062] Method Embodiment

[0063] Reference Figure 1 , showing a flow chart of a method for self-discovery batch remote deployment based on identification provided by an embodiment of the present invention.

[0064] An embodiment of the present invention provides a method for self-discovery batch remote deployment based on identification, the method comprising:

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

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

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

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

[0069] Assign the default IP address to the target node to complete the initialization of the target node.

[0070] The default IP address refers to the IP address automatically assigned to the device by the system or management server during initial configuration or device access in the 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 tedious steps such as manual allocation of IP addresses. Through the automated process, the system can batch process the initialization of multiple nodes, improving deployment efficiency while ensuring the consistency and accuracy of all nodes during initialization.

[0072] S2, start the OSOP mirroring service of the target node, and receive 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 MAC address of the target node.

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

[0074] S201, generating an identification filling interface through the OSOP mirror service.

[0075] The identification filling interface is a user interface generated by the OSOP mirror service and is used to input the identification of the device.

[0076] It should be noted that by generating an identification filling interface, the identification information of the target node can be easily entered or confirmed to ensure 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 deployments, it can quickly provide correct identification information for each node and reduce the risk of incorrect configuration.

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

[0078] It should be noted that by automatically collecting the identification information of the target nodes, the management server can accurately identify each device, ensure that the correct operating system image and configuration file are distributed to each node, eliminate the need for manual matching of nodes and configurations, 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. It is responsible for receiving node identification information, generating configuration files, managing the distribution of operating system images, and coordinating the deployment process.

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

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

[0083] It should be noted that by sending identification information to the management server, automatic identification and dynamic management of nodes are achieved. The OSDP management server can automatically generate deployment strategies based on this information to ensure 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 operations.

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

[0085] Among them, the kickstart file is an automated configuration file, usually used for the installation of Red Hat and its derivative versions of the Linux operating system. It defines all the parameters required during the operating system installation process, including partition scheme, software package selection, network configuration, etc., so as to achieve unattended operating system installation. GRUB (Grand Unified Bootloader) is a boot program used to boot the operating system kernel. The grub file contains the configuration information required during the system startup process, such as boot order, 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, which enables the OSDP management server and the target node to transmit data, send instructions and receive status information to each other.

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

[0090] S402, storing the identification information in a database of the OSDP management server, and generating a kickstart file and a 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 the TCP protocol.

[0092] Among them, TCP (Transmission Control Protocol) is a connection-oriented, reliable transport layer protocol that ensures that data is transmitted in an orderly and error-free manner in the network. TCP ensures the integrity and accuracy of data transmission by establishing connections, confirming data reception, and retransmitting lost data packets. Socket is the endpoint of network communication and is used to establish a two-way communication connection between different devices through the network. Socket communication based on the 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 kickstart files and grub files makes the operating system installation process fully automated, and customizes the configuration according to the hardware information and MAC address of each node to ensure adaptability. This not only avoids the tediousness and possible errors of manual configuration, but also improves the efficiency and consistency during large-scale deployment, ensuring that the operating system installation process of all nodes is consistent, accurate and fast.

[0094] S5: Send a restart instruction to the target node.

[0095] It should be noted that issuing a restart command 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. Responding to the restart instruction, restarting the target node.

[0097] It should be noted that the target node automatically responds to the restart command issued by the management server to complete the system restart, which greatly reduces manual intervention and improves 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. It is suitable for the rapid deployment and management of large-scale equipment.

[0098] S7, sending a DHCP address request instruction to the OSDP management server.

[0099] Among them, DHCP (Dynamic Host Configuration Protocol) is used to automatically assign IP addresses. The target node sends a DHCP address request instruction to request the DHCP server to assign an IP address and other network configuration information (such as gateway, subnet mask, etc.), so that the node can correctly connect to the network.

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

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

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

[0103] It should be noted that accurately identifying the target node based on the MAC address and sending it the kickstart file and operating system image installation package ensures that each device can obtain the correct operating system and configuration files in large-scale deployment, reduces the error rate and complexity of manual operations, improves the automation and efficiency of batch deployment, and ensures the accuracy and consistency of system deployment.

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

[0105] It should be noted that the target node relies on the kickstart file to automatically install the operating system, reducing manual intervention and achieving efficient large-scale batch deployment. Through the combination of the kickstart file and the system image, the configuration and operating system version of all nodes are ensured to be consistent, which improves the accuracy and speed of deployment and greatly reduces the possibility of errors.

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

[0107] In the embodiment of the present invention, by automatically receiving the identification information of the target node, each target node is accurately identified, the risk of device identification confusion is avoided, and the identification information is sent to the OSDP management server, thereby ensuring reliable communication and data exchange between the OSDP management server and the target node, ensuring that data will not be lost during the deployment process, and reducing the risk of human operational errors through the kickstart file and the system image installation package, ensuring the accuracy and consistency of the deployment, and matching the information of the target node with its deployment configuration, and spontaneously implementing batch operations on a large number of devices by automatically issuing restart instructions and receiving DHCP address request instructions, thereby improving the deployment efficiency of large-scale equipment and enhancing the stability and reliability of the deployment.

[0108] Device Embodiment

[0109] Reference Manual Attached Figure 2 , showing a schematic structural diagram of an identification-based self-discovery batch remote deployment device provided in an embodiment of the present invention.

[0110] Another specific embodiment of the present invention discloses a self-discovery batch remote deployment device based on identification, which is used to implement any one of the self-discovery batch remote deployment methods based on identification in the method embodiments. The self-discovery batch remote deployment device based on identification 20 includes:

[0111] The 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 OSOP mirroring service of the target node and receive 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 MAC address of the target node.

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

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

[0115] The sending module 205 is used to send the restart instruction to the target node.

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

[0117] The second sending module 207 is used to send a DHCP address request instruction to the OSDP management server.

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

[0119] The deployment module 209 is used to perform remote deployment of the target node according to the received kickstart file and system image installation package.

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

[0121] Assign the default IP address to the target node to complete the initialization of the target node.

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

[0123] The filling submodule is used to generate the identification filling interface through the OSOP mirror service.

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

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

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

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

[0128] A submodule is established to establish a communication connection between the OSDP management server and the target node.

[0129] The generation submodule is used to store the identification information into the database of the OSDP management server and generate the kickstart file and 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 the TCP protocol.

[0131] The beneficial effects of the present invention are as follows:

[0132] In the embodiment of the present invention, by automatically receiving the identification information of the target node, each target node is accurately identified, the risk of device identification confusion is avoided, and the identification information is sent to the OSDP management server, thereby ensuring reliable communication and data exchange between the OSDP management server and the target node, ensuring that data will not be lost during the deployment process, and reducing the risk of human operational errors through the kickstart file and the system image installation package, ensuring the accuracy and consistency of the deployment, and matching the information of the target node with its deployment configuration, and spontaneously implementing batch operations on a large number of devices by automatically issuing restart instructions and receiving DHCP address request instructions, thereby improving the deployment efficiency of large-scale equipment and enhancing the stability and reliability of the deployment.

[0133] System Example

[0134] Reference Manual Attached Figure 3 , showing a structural diagram of an identification-based self-discovery batch remote deployment system provided by an embodiment of the present invention.

[0135] The present invention proposes an identification-based self-discovery batch remote deployment system 30 , comprising: a memory 303 and one or more processors 301 .

[0136] One or more application programs are stored in the memory 303 , and the one or more application programs are suitable for being executed by the one or more processors 301 to implement the identification-based self-discovery batch remote deployment method of the method embodiment.

[0137] The identification-based self-discovery batch remote deployment system 30 includes: a processor 301 and a memory 303. The processor 301 and the memory 303 are connected, for example, through a bus 302.

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

[0139] Processor 301 may be a CPU, a general purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, a transistor logic device, a hardware component or any combination thereof. It may implement or execute various exemplary logic blocks, modules and circuits described in conjunction with the disclosure of the present invention. Processor 301 may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.

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

[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, or an EEPROM, a CD-ROM or other optical disk storage, an optical disk storage (including a compressed optical 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 the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited to these.

[0142] Computer Readable Storage Medium Embodiments

[0143] The present invention provides a computer-readable storage medium on which a computer program is stored. The computer program can be loaded and executed by a processor to implement the identification-based self-discovery batch remote deployment method of the first aspect.

[0144] The applicant of the present invention has made a detailed explanation and description of the implementation examples of the present invention in conjunction with the drawings in the specification. However, those skilled in the art should understand that the above implementation examples are only preferred implementation schemes of the present invention, and the detailed description is only to help readers better understand the spirit of the present invention, but not to limit the scope of protection of the present invention. On the contrary, any improvements or modifications based on the inventive spirit of the present invention should fall within the scope of protection of the present invention.

[0145] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the embodiments of the present invention, rather than to limit them. Although the present invention has been described in detail with reference to the above embodiments, those skilled in the art should understand that they can still modify the technical solutions recorded in the above embodiments, or replace some of the technical features therein by equivalents; 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 invention. Any changes or replacements that can be easily thought of by those skilled in the art within the technical scope disclosed in the present invention should be covered within the protection scope of the present invention.

Claims

1. A self-discovery batch remote deployment method based on identification, characterized in that: The identification-based self-discovery batch remote deployment method includes: S1, start the OSDP management server to initialize the target node; S2, starting the OSOP mirroring service of the target node, receiving identification information of the target node, wherein the identification information includes the target node name and target node hardware information, wherein the hardware information includes the MAC address of the target node; S3, sending the identification information to the OSDP management server; S4, generating a kickstart file and a grub file of the target node, wherein the kickstart file includes the version of the operating system to be installed on the target node and the network card information based on the MAC address; S5, issuing a restart instruction to the target node; S6, in response to the restart instruction, restart the target node; S7, sending a DHCP address request instruction to the OSDP management server; S8, in response to the dhcp address request instruction, sending the kickstart file and the system image installation package corresponding to the operating system version to be installed to the target node based on the MAC address of the target node; S9, performing remote deployment of the target node according to the received kickstart file and the system image installation package.

2. The identification-based self-discovery batch remote deployment method according to claim 1, characterized in that: The S1 is specifically: A default IP address is assigned to the target node to complete the initialization of the target node.

3. The identification-based self-discovery batch remote deployment method according to claim 1, characterized in that: The S2 specifically includes: S201, generating an identification filling interface through the OSOP mirror service; S202: receiving the identification information through the identification filling interface.

4. The identification-based self-discovery batch remote deployment method according to claim 1, characterized in that: The S3 is specifically: The identification information is pushed to the OSDP management server in a broadcasting form at preset time intervals.

5. The identification-based self-discovery batch remote deployment method according to claim 1, characterized in that: The S4 specifically includes: S401, establishing a communication connection between the OSDP management server and the target node; 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.

6. The identification-based self-discovery batch remote deployment method according to claim 5, characterized in that: The communication connection is a socket communication connection based on the TCP protocol.

7. A self-discovery batch remote deployment device based on identification, characterized in that: The identification-based self-discovery batch remote deployment device includes: The initialization module is used to start the OSDP management server to initialize the target node; A startup module, used to start the OSOP mirroring service of the target node, and receive identification information of the target node, wherein the identification information includes a target node name and target node hardware information, wherein the hardware information includes a MAC address of the target node; A first sending module, used to send the identification information to the OSDP management server; A generation module, used to generate a kickstart file and a grub file of the target node, wherein the kickstart file includes the version of the operating system to be installed on the target node and the network card information based on the MAC address; A sending module, used for sending a restart instruction to the target node; A restart module, configured to restart the target node in response to the restart instruction; The second sending module is used to send a DHCP address request instruction to the OSDP management server; A response module, configured to respond to the DHCP address request instruction and send the kickstart file and the system image installation package corresponding to the operating system version to be installed to the target node based on the MAC address of the target node; The deployment module is used to perform remote deployment of the target node according to the received kickstart file and the system image installation package.

8. The identification-based self-discovery batch remote deployment device according to claim 7, characterized in that: The initialization module is specifically used for: A default IP address is assigned to the target node to complete the initialization of the target node.

9. The identification-based self-discovery batch remote deployment device according to claim 7, characterized in that: The startup module specifically includes: A filling submodule is used to generate an identification filling interface through the OSOP mirror service; The receiving submodule is used to receive the identification information through the identification filling interface.

10. The identification-based self-discovery batch remote deployment device according to claim 7, characterized in that: The first sending module is specifically used for: The identification information is pushed to the OSDP management server in a broadcasting form at preset time intervals.

Images