CN111078305A - Information acquisition method and device, server and information management system - Google Patents
Information acquisition method and device, server and information management system Download PDFInfo
- Publication number
- CN111078305A CN111078305A CN201911269914.7A CN201911269914A CN111078305A CN 111078305 A CN111078305 A CN 111078305A CN 201911269914 A CN201911269914 A CN 201911269914A CN 111078305 A CN111078305 A CN 111078305A
- Authority
- CN
- China
- Prior art keywords
- file
- information
- operating system
- memory
- server
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 47
- 230000008569 process Effects 0.000 claims abstract description 11
- 238000004891 communication Methods 0.000 claims description 12
- 238000009434 installation Methods 0.000 claims description 4
- 230000001419 dependent effect Effects 0.000 abstract description 3
- 238000010586 diagram Methods 0.000 description 8
- 230000006870 function Effects 0.000 description 6
- 238000012546 transfer Methods 0.000 description 3
- 238000012545 processing Methods 0.000 description 2
- KKIMDKMETPPURN-UHFFFAOYSA-N 1-(3-(trifluoromethyl)phenyl)piperazine Chemical compound FC(F)(F)C1=CC=CC(N2CCNCC2)=C1 KKIMDKMETPPURN-UHFFFAOYSA-N 0.000 description 1
- 241000282326 Felis catus Species 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000009545 invasion Effects 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000007704 transition Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/4401—Bootstrapping
- G06F9/4411—Configuring for operating with peripheral devices; Loading of device drivers
Abstract
The embodiment of the application provides an information acquisition method, an information acquisition device, a server and an information management system, relates to the technical field of computer equipment, and can receive an operating system kernel and a system file which are sent by a management node in the information management system and load the operating system kernel and the system file into a memory. And starting the memory operating system according to the received operating system kernel, running a pre-configured acquisition task file in the system file in the memory operating system, and executing an acquisition command in the acquisition task file to acquire hardware information of the acquisition task file. Therefore, under the condition that the operating system is not installed on the server or the operating system cannot be loaded to the memory from the hard disk, the memory operating system can be operated through the operating system kernel and the system file issued by the management node, so that the related acquisition command is operated to acquire the hardware information of the server. In addition, the whole process is carried out in the memory, the hard disk is not dependent on, and the hard disk information cannot be invaded.
Description
Technical Field
The application relates to the technical field of computer equipment, in particular to an information acquisition method, an information acquisition device, a server and an information management system.
Background
In daily purchasing and managing computers, users can put demands on hardware configuration of the computers according to requirements of the users on the performances of the computers in various aspects. For example, when a new computer needs to be added to a computer room, after the new computer is purchased, the user needs to know whether the actual hardware configuration of the new computer is consistent with the hardware information parameters of the computer on the purchase list.
In the prior art, to obtain hardware information of a computer, it is necessary to acquire the relevant hardware information of the computer through a relevant acquisition command inside an operating system when the operating system is installed in the computer. If the operating system is not installed in the computer, or the operating system cannot be loaded into the memory from the hard disk of the computer for some reasons, the operating system cannot be successfully operated, and thus the hardware information of the computer cannot be acquired.
Disclosure of Invention
The purpose of the present application includes, for example, providing an information collecting method, apparatus and server, which can successfully collect hardware information of the server.
The embodiment of the application can be realized as follows:
in a first aspect, an embodiment provides an information acquisition method, which is applied to any one of a plurality of servers included in an information management system, where the information management system further includes a management node, and the management node is in communication connection with each of the servers, and the method includes:
receiving an operating system kernel and a system file sent by the management node, and loading the operating system kernel and the system file into a memory;
starting a memory operating system according to the operating system kernel;
and in the internal memory operating system, operating a pre-configured acquisition task file in the system file, and executing an acquisition command in the acquisition task file to acquire hardware information of the acquisition task file.
In an optional embodiment, the step of receiving the operating system kernel and the system file sent by the management node and loading the operating system kernel and the system file into the memory includes:
after power up, starting through a PXE network;
and after starting, receiving an operating system kernel and a system file sent by the management node, and loading the operating system kernel and the system file into a memory through a boot loader.
In an optional embodiment, the step of loading the operating system kernel and the system file into the memory by the boot loader includes:
loading the system file to a memory through a boot loader, and decompressing the system file;
and loading the operating system kernel into the memory through the bootstrap loader, and loading a user-level process in the memory by the operating system kernel so as to switch to a root file system.
In an optional embodiment, the step of operating a pre-configured collection task file in the system file, and executing a collection command in the collection task file to collect hardware information of the collection task file includes:
running a pre-configured collection task file in the system file, and triggering and executing a timing task script in the collection task file at intervals of preset duration;
and acquiring hardware information of the user according to an acquisition command in the timed task script.
In an alternative embodiment, the method further comprises:
and sending the collected hardware information to a remote management system according to a collection command in the collection task file so that the remote management system stores the hardware information.
In an optional embodiment, the system file is also preconfigured with a view task file, and the method further includes:
if the server sends the hardware information to a remote management system, executing a checking command in a checking task file to log in the remote management system by running the checking task file configured in advance in the system file so as to search for and obtain the hardware information from the remote management system;
and if the server does not send the hardware information to a remote management system, executing a viewing command in the viewing task file by operating a viewing task file configured in advance in the system file so as to obtain the hardware information from the local.
In an alternative embodiment, the method further comprises:
after the power-off is restarted, acquiring operating system information selected by a user based on the displayed operating system installation prompt information;
and installing the operating system based on the operating system information.
In a second aspect, an embodiment provides an information acquisition apparatus, which is applied to any one of a plurality of servers included in an information management system, where the information management system further includes a management node, and the management node is in communication connection with each of the servers, and the apparatus includes:
the receiving module is used for receiving the operating system kernel and the system file sent by the management node and loading the operating system kernel and the system file into a memory;
the starting module is used for starting the memory operating system according to the operating system kernel;
and the acquisition module is used for operating a pre-configured acquisition task file in the system file in an internal memory operating system and executing an acquisition command in the acquisition task file to acquire hardware information of the acquisition task file.
In a second aspect, an embodiment provides a server, where the server includes a machine-readable storage medium and a processor, where the machine-readable storage medium stores machine-executable instructions, and when the processor executes the machine-executable instructions, the server implements the information collecting method in any one of the foregoing embodiments.
In a third aspect, an embodiment provides an information management system, including a management node and a plurality of servers in communication with the management node;
the management node is used for sending the stored operating system kernel and the system file to the server after receiving an information loading request sent by the server;
the server is used for receiving the operating system kernel and the system file sent by the management node and loading the operating system kernel and the system file into the memory;
the server is also used for starting a memory operating system according to the operating system kernel;
the server is also used for operating a pre-configured collection task file in the system file in a memory operating system and executing a collection command in the collection task file to collect hardware information of the server.
The beneficial effects of the embodiment of the application include, for example:
the information acquisition method, the information acquisition device, the server and the information management system provided by the embodiment of the application can receive the operating system kernel and the system file which are sent by the management node in the information management system, and load the operating system kernel and the system file into the memory. And starting the memory operating system according to the received operating system kernel, running a pre-configured acquisition task file in the system file in the memory operating system, and executing an acquisition command in the acquisition task file to acquire hardware information of the acquisition task file. Therefore, under the condition that the operating system is not installed on the server or the operating system cannot be loaded to the memory from the hard disk, the memory operating system can be operated through the operating system kernel and the system file issued by the management node, so that the related acquisition command is operated to acquire the hardware information of the server. In addition, the whole process is carried out in the memory, the hard disk is not dependent on, and the hard disk information cannot be invaded.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained from the drawings without inventive effort.
Fig. 1 is a system architecture diagram of an information management system provided in an embodiment of the present application;
fig. 2 is a flowchart of an information acquisition method according to an embodiment of the present application;
FIG. 3 is a flowchart of the substeps of step S230 in FIG. 2;
fig. 4 is another flowchart of an information collecting method according to an embodiment of the present application;
fig. 5 is another flowchart of an information collecting method according to an embodiment of the present application;
fig. 6 is a functional block diagram of an information acquisition apparatus according to an embodiment of the present application;
fig. 7 is a block diagram of a server according to an embodiment of the present disclosure.
Icon: 110-an information acquisition device; 111-a receiving module; 112-a start module; 113-an acquisition module; 120-a processor; 130-a memory; 140-communication module.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. The components of the embodiments of the present application, generally described and illustrated in the figures herein, can be arranged and designed in a wide variety of different configurations.
Thus, the following detailed description of the embodiments of the present application, presented in the accompanying drawings, is not intended to limit the scope of the claimed application, but is merely representative of selected embodiments of the application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures. Furthermore, the appearances of the terms "first," "second," and the like, if any, are used solely to distinguish one from another and are not to be construed as indicating or implying relative importance.
It should be noted that the features of the embodiments of the present application may be combined with each other without conflict.
Referring to fig. 1, a block diagram of an information management system according to an embodiment of the present disclosure is shown, where the information management system includes a management node, a switch, and a plurality of servers, and the management node may be communicatively connected to each server through the switch. The management node itself may also be a single server, or a server cluster composed of a plurality of servers, and any server in the information management system may be used as the management node. In this embodiment, the management node, the switch, and the server in the information management system may be located in the same machine room.
In this embodiment, each server may be a server with an installed operating system or a server without an installed operating system, in some application scenarios, in this embodiment, hardware information of a server that has just been added to the information management system may be acquired, and in other application scenarios, hardware information of a server that has been added to the information management system before but cannot load an operating system from a hard disk to a memory for some reason may also be acquired by the information acquisition method provided in the following embodiment.
It is to be understood that the information management system shown in fig. 1 is only one possible example, and in other possible embodiments, the information management system may include only a part of the components shown in fig. 1 or may also include other components.
In order to successfully acquire the hardware information of the server without intruding the hard disk information, fig. 2 shows a flowchart of the information acquisition method provided in the embodiment of the present application.
It should be understood that, in other embodiments, the order of some steps in the information acquisition method of this embodiment may be interchanged according to actual needs, or some steps may be omitted or deleted. The detailed steps of the information acquisition method are described below.
Step S210, receiving the operating system kernel and the system file sent by the management node, and loading the operating system kernel and the system file into a memory.
Step S220, starting the memory operating system according to the operating system kernel.
Step S230, in the internal operating system, running the pre-configured collection task file in the system file, and executing the collection command in the collection task file to collect the hardware information of the collection task file.
The hardware information of the server includes, for example, motherboard information, CPU (Central Processing Unit) information, memory information, disk information, and the like, where the motherboard information includes, for example, manufacturer, model, serial number, and the like, the CPU information includes, for example, CPU model, number, physical core number, and the like, the memory information includes, for example, memory number, single capacity, and the like, and the disk information includes, for example, disk number, single capacity, disk type, Raid level, and the like.
When a server is newly purchased, after the hand is purchased, the actual hardware information of the server needs to be known, so as to check whether the actual hardware information is consistent with the required information on the equipment parameter list provided by the seller. In an actual scene, the hardware of the server is generally not directly disassembled for checking, and an effective acquisition scheme is required to be provided so that the specific and actual hardware information of the equipment can be known without disassembling the equipment.
In the prior art, the relevant hardware information of the server is collected through commands such as dmidcode, MegaCli64, cat/proc/cpuinfo, fdisk, and the like, generally after the server installs the operating system. However, this method can be performed only after the operating system is installed, and the collection of the server hardware information cannot be effectively realized when the operating system is not installed in the server. In addition, the operating system needs to be loaded to the memory from the hard disk of the server, and if the hard disk of the server fails to be loaded, the scheme cannot effectively acquire hardware information. In addition, the hardware information acquisition mode may cause intrusion on the hard disk information.
In this embodiment, one or more servers in the same network are used as a management node by setting the management node, where the management node is used to store a memory operating system, and can be loaded by other servers in the network to run in a memory of the server.
The network between the management node and the server may be a PXE (Pre-boot Execution Environment) network, where the PXE is a boot method, and a necessary condition for PXE installation is that a computer to be installed includes a PXE-supported network card (NIC). The PXE comprises a PXE client and a PXE server, wherein the computer needing to load the memory operating system corresponds to the PXE client, and the management node storing the memory operating system corresponds to the PXE server. The PXE protocol allows computers to boot over a network.
Among them, the management node may support TFTP (Trivial File Transfer Protocol, simple File Transfer Protocol or small File Transfer Protocol), and DHCP (Dynamic Host Configuration Protocol). The DHCP protocol is a protocol for dynamically allocating an IP address to a computer, and in this embodiment, since computer IP address allocation is performed based on a PXE network, when configuring a management node, a corresponding PXE-specific configuration needs to be added.
When a server is newly added to the network, of course, when the server already added to the network needs to load the memory operating system to collect its own hardware information, the kernel of the operating system and the system file may be obtained from the management node and loaded into the memory.
The system file initramfs is a RAM filesystems, and includes a user program and a driver module required for starting, and is used as a transition before the real root file system rootfs is mounted.
After the server is powered on, the server is started through a PXE network, after the server is started, an operating system kernel and system files are downloaded from a management node, and the operating system kernel and the system files are loaded into a memory through a boot loader.
The network card of the server is provided with a PXE Client, and the PXE Client prompts prompt information of booting through a hard disk or a PXE in a ROM (Read-Only Memory) of the network card after the server is started. In this embodiment, the boot will be over PXE to boot over the PXE network. After entering the PXE network boot interface, the server sends request information to the management node through the PXE Client to request the IP address. And after receiving the request information, the management node feeds back the pre-allocated IP address and the access address of the bootstrap loader to the server. And after receiving the access address of the boot loader, the server loads the operating system kernel and the system file into the memory through the boot loader.
When the server is just powered on and started, the memory controller is not configured, so that the program cannot be run in the memory at all, and the server cannot be in the starting environment of the Linux kernel. In order to initialize the CPU and other peripheral devices, so that the Linux kernel can run in the system main memory, and make the system meet the necessary conditions for the Linux kernel to start, a program which runs before the kernel, namely the boot loader, is required.
The Boot Loader mentioned above is a small program that runs before the operating system kernel runs. Through the small program, hardware equipment can be initialized, a mapping chart of a memory space is established, so that the software and hardware environment of the system is brought to a proper state, a correct environment is prepared for finally calling the memory of the operating system, and finally, a kernel image is loaded from other places (Flash, Ethernet and UART) and is jumped to an entry address.
It should be noted that the boot loader is not required by Linux, and is provided by almost all devices running an operating system.
In this embodiment, after the server starts the memory operating system, a pre-configured collection task file in the system file may be run, where the collection task file includes a related collection command, such as dmidcode, and hardware information of the server, including motherboard information, CPU information, memory information, and disk information, may be collected and obtained through the collection command.
The dmidcode acquisition command can acquire hardware information in a Linux system, can decode information in a DMI (desktop Management interface) database, and conforms to SMBIOS (System Management BIOS)/DMI standard.
DMI is a management system that helps collect computer system information, which must be collected in strict compliance with SMBIOS specifications. SMBIOS is a unified specification that a motherboard or system manufacturer needs to follow to display product management information in a standard format. SMBIOS and DMI are open technical standards drafted by DMTF (Desktop Management Task Force), where DMI design is applicable to any platform and operating system.
The DMI plays the role of the interface between the management tool and the system layer. It establishes standard manageable system, and is more convenient for computer manufacturers and users to know the system. The main component of DMI is the MIF (managementinformation Format) database. This database contains all information about the computer system and accessories. Through DMI, a user can obtain serial numbers, computer manufacturers, serial port information and other system accessory information. The following exemplifies implementation code for hardware information acquisition of the server by dmidcode acquisition commands:
obtaining the model of the server: dmidrede grep 'Product Name'
Acquiring a serial number of a mainboard: dmidrede grep 'Serial Number'
Acquiring a system serial number: dmidreode-s system-serial-number
Acquiring memory information: dmidreode-t memory
Acquiring manufacturer information: dmidrecode-t 11
In this embodiment, the operating system kernel and the system file are downloaded from the management node in a network boot manner, so as to boot the memory operating system. And in the internal memory operating system, operating the acquisition task file in the system file, and executing an acquisition command in the acquisition task file to acquire hardware information of the acquisition task file. The whole process is executed in the memory, hard disk information is not needed, and hardware information of the server can be effectively acquired no matter the server is provided with an operating system or is not provided with the operating system. In addition, the data of the information acquisition mode cannot be written into a hard disk, the data disappear after the server is restarted, the hard disk information of the server cannot be invaded, and the hard disk data of the server cannot be influenced.
In this embodiment, after the system file is loaded to the memory by the boot loader, the system file is decompressed. After the operating system memory is loaded into the memory by the boot loader, the operating system kernel loads a user-level process in the memory, that is, init (the first user-level process after the operating system kernel is started) is switched to root file system rootfs.
Root file system rootfs is a memory-based file system, and all operations are completed in the memory. There is also no actual storage device and so no device driver involvement is required. Based on the reasons, the linux uses the rootfs file system in the starting stage, and when the disk driver and the disk file system are loaded successfully, the linux system can switch the system root directory from the rootfs to the disk file system.
In this embodiment, the collection task file is pre-configured in a system file, and the collection task file may be a crontab file. Referring to fig. 3, the step S230 can be implemented by the following sub-steps:
and S231, operating a preset acquisition task file in the system file, and triggering and executing the timing task script in the acquisition task file at intervals of preset time.
And step S232, acquiring the hardware information of the user according to the acquisition command in the timed task script.
In the crontab file, each row represents a task, and each field of each row represents a setting. In this embodiment, a timed task script is added in the collection task file in advance, and the timed task script may be triggered and executed at a preset time interval at regular intervals, where the preset time interval may be one minute, ten minutes, or the like. The script content of the timed task script is the acquisition command, and the hardware information of the server can be acquired according to the acquisition command in the timed task script.
In this embodiment, the acquired hardware information of the server may be stored locally, or may be uploaded to other systems for storage. The other system may be a remote management system, such as a CMDB (configuration management Data Base) system.
When the data needs to be uploaded to a remote management system for storage, the collection task file can be configured in advance, and a related command for triggering information sending is added in the collection command. Referring to fig. 4, the information collecting method provided in this embodiment further includes the following steps:
step S240, sending the collected hardware information to a remote management system according to the collection command in the collection task file, so that the remote management system stores the hardware information.
In addition, in this embodiment, a view task file, such as an ssh file, is pre-configured in the system file, and the collected hardware information of the server may be viewed based on a view command in the view task file.
Referring to fig. 5, in the present embodiment, the information collecting method further includes the following steps:
step S250, if the server sends the hardware information to a remote management system, executing a check command in the check task file to log in to the remote management system by running a check task file configured in advance in the system file, so as to search for and obtain the hardware information from the remote management system.
Step S260, if the server does not send the hardware information to the remote management system, executing a viewing command in the viewing task file by running a viewing task file configured in advance in the system file to obtain the hardware information from a local place.
In the embodiment, when the user needs to log in the remote management system to check the hardware information, the user can log in through the SSH protocol, the SSH protocol is a safe login protocol, and even if the user intercepts the software in the midway, the password cannot be leaked. SSH is secure because it employs public key encryption. The remote management system receives the login request of the server and sends the public key of the remote management system to the server. The server encrypts the login password using the public key and sends it back. The remote management system decrypts the login password by using the private key of the remote management system, and if the password is correct, the remote management system agrees to login of the server.
In this embodiment, since the whole information collection process is performed in the memory, the data in the memory will disappear after the server is powered off and restarted. After shutdown and restart, the server displays the installation prompt information of the operating system, and a user can select whether to install the memory operating system or other operating systems according to the requirement of the user. And the server installs the operating system according to the operating system information which needs to be installed and is selected by the user.
The information collection scheme provided in this embodiment may perform network boot through the PXE network, and boot the memory operating system based on the operating system kernel and the system file downloaded from the management node. And finally, acquiring the hardware information of the server based on the acquisition command in the system file. The information acquisition scheme can effectively acquire the hardware information of the server no matter the server is provided with the operating system or is not provided with the operating system. In addition, the whole process is operated in the memory, so that data cannot be written into the hard disk, and the invasion of hard disk information is avoided.
Based on the same application concept, please refer to fig. 6, which shows a schematic diagram of functional modules of the information acquisition apparatus 110 provided in the embodiment of the present application, and the embodiment may perform functional module division on the information acquisition apparatus 110 according to the above method embodiment. For example, the functional blocks may be divided for the respective functions, or two or more functions may be integrated into one processing block. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. It should be noted that, in the embodiment of the present application, the division of the module is schematic, and is only one logic function division, and there may be another division manner in actual implementation. For example, in the case of dividing each function module according to each function, the information collecting device 110 shown in fig. 6 is only a schematic device diagram. The information acquisition apparatus 110 may include a receiving module 111, a starting module 112, and an acquisition module 113, and the functions of the functional modules of the information acquisition apparatus 110 are described in detail below.
The receiving module 111 is configured to receive the operating system kernel and the system file sent by the management node, and load the operating system kernel and the system file into the memory. It is understood that the receiving module 111 can be used to execute the step S210, and for the detailed implementation of the receiving module 111, reference can be made to the content related to the step S210.
The starting module 112 is configured to start the memory operating system according to the operating system kernel. It is understood that the starting module 112 can be used to execute the step S220, and for the detailed implementation of the starting module 112, reference can be made to the above-mentioned contents related to the step S220.
And the acquisition module 113 is configured to run an acquisition task file configured in advance in the system file in the memory operating system, and execute an acquisition command in the acquisition task file to acquire hardware information of the acquisition task file. It is understood that the acquiring module 113 may be configured to perform the step S230, and for the detailed implementation of the acquiring module 113, reference may be made to the content related to the step S230.
In one possible implementation, the receiving module 111 may be configured to load the operating system kernel and the system file into the memory by:
after power up, starting through a PXE network;
and after starting, receiving an operating system kernel and a system file sent by the management node, and loading the operating system kernel and the system file into a memory through a boot loader.
In one possible implementation, the receiving module 111 may be configured to load the operating system kernel and the system file into the memory by the bootloader program by:
loading the system file to a memory through a boot loader, and decompressing the system file;
and loading the operating system kernel into the memory through the bootstrap loader, and loading a user-level process in the memory by the operating system kernel so as to switch to a root file system.
In one possible implementation, the collection module 113 may be configured to collect hardware information by:
running a pre-configured collection task file in the system file, and triggering and executing a timing task script in the collection task file at intervals of preset duration;
and acquiring hardware information of the user according to an acquisition command in the timed task script.
In a possible implementation manner, the information collecting apparatus 110 further includes a sending module, and the sending module may be configured to:
and sending the collected hardware information to a remote management system according to a collection command in the collection task file so that the remote management system stores the hardware information.
In a possible implementation manner, the system file intelligence is further configured with a view task file in advance, and the information collection apparatus 110 further includes a view module, where the view module may be configured to:
if the server sends the hardware information to a remote management system, executing a checking command in a checking task file to log in the remote management system by running the checking task file configured in advance in the system file so as to search for and obtain the hardware information from the remote management system;
and if the server does not send the hardware information to a remote management system, executing a viewing command in the viewing task file by operating a viewing task file configured in advance in the system file so as to obtain the hardware information from the local.
Referring to fig. 7, a block diagram of the server shown in fig. 1 according to the embodiment of the present disclosure is provided, where the server includes a memory 130, a processor 120, and a communication module 140. The memory 130, the processor 120, and the communication module 140 are electrically connected to each other directly or indirectly to realize data transmission or interaction. For example, the components may be electrically connected to each other via one or more communication buses or signal lines.
The memory 130 is used to store programs or data. The Memory 130 may be, but is not limited to, a Random Access Memory (RAM), a Read Only Memory (ROM), a Programmable Read-Only Memory (PROM), an erasable Read-Only Memory (EPROM), an electrically erasable Read-Only Memory (EEPROM), and the like.
The processor 120 is used for reading/writing data or programs stored in the memory 130 and executing the information acquisition method provided by any embodiment of the present application.
The communication module 140 is used for establishing a communication connection between the server and another communication terminal through a network, and for transceiving data through the network.
It should be understood that the architecture shown in fig. 7 is merely a schematic diagram of an architecture for a server that may also include more or fewer components than shown in fig. 7, or have a different configuration than shown in fig. 7.
To sum up, the information acquisition method, the information acquisition device, the server and the information management system provided by the embodiment of the application can receive the operating system kernel and the system file sent by the management node in the information management system and load the operating system kernel and the system file into the memory. And starting the memory operating system according to the received operating system kernel, running a pre-configured acquisition task file in the system file in the memory operating system, and executing an acquisition command in the acquisition task file to acquire hardware information of the acquisition task file. Therefore, under the condition that the operating system is not installed on the server or the operating system cannot be loaded to the memory from the hard disk, the memory operating system can be operated through the operating system kernel and the system file issued by the management node, so that the related acquisition command is operated to acquire the hardware information of the server. In addition, the whole process is carried out in the memory, the hard disk is not dependent on, and the hard disk information cannot be invaded.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present application should be covered within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (10)
1. An information acquisition method is applied to any one of a plurality of servers included in an information management system, the information management system further comprises a management node, and the management node is in communication connection with each server, and the method comprises the following steps:
receiving an operating system kernel and a system file sent by the management node, and loading the operating system kernel and the system file into a memory;
starting a memory operating system according to the operating system kernel;
and in the internal memory operating system, operating a pre-configured acquisition task file in the system file, and executing an acquisition command in the acquisition task file to acquire hardware information of the acquisition task file.
2. The information acquisition method according to claim 1, wherein the step of receiving the operating system kernel and the system file sent by the management node and loading the operating system kernel and the system file into the memory comprises:
after power up, starting through a PXE network;
and after starting, receiving an operating system kernel and a system file sent by the management node, and loading the operating system kernel and the system file into a memory through a boot loader.
3. The information acquisition method according to claim 2, wherein the step of loading the operating system kernel and the system file into the memory by the boot loader comprises:
loading the system file to a memory through a boot loader, and decompressing the system file;
and loading the operating system kernel into the memory through the bootstrap loader, and loading a user-level process in the memory by the operating system kernel so as to switch to a root file system.
4. The information acquisition method according to claim 1, wherein the step of operating a pre-configured acquisition task file in the system file, and executing an acquisition command in the acquisition task file to acquire hardware information of the acquisition task file comprises:
running a pre-configured collection task file in the system file, and triggering and executing a timing task script in the collection task file at intervals of preset duration;
and acquiring hardware information of the user according to an acquisition command in the timed task script.
5. The information acquisition method of claim 1, further comprising:
and sending the collected hardware information to a remote management system according to a collection command in the collection task file so that the remote management system stores the hardware information.
6. The information collection method according to claim 5, wherein a view task file is also preconfigured in the system file, and the method further comprises:
if the server sends the hardware information to a remote management system, executing a checking command in a checking task file to log in the remote management system by running the checking task file configured in advance in the system file so as to search for and obtain the hardware information from the remote management system;
and if the server does not send the hardware information to a remote management system, executing a viewing command in the viewing task file by operating a viewing task file configured in advance in the system file so as to obtain the hardware information from the local.
7. The information acquisition method of claim 1, further comprising:
after the power-off is restarted, acquiring operating system information selected by a user based on the displayed operating system installation prompt information;
and installing the operating system based on the operating system information.
8. An information acquisition apparatus, applied to any one of a plurality of servers included in an information management system, the information management system further including a management node, the management node being communicatively connected to each of the servers, the apparatus comprising:
the receiving module is used for receiving the operating system kernel and the system file sent by the management node and loading the operating system kernel and the system file into a memory;
the starting module is used for starting the memory operating system according to the operating system kernel;
and the acquisition module is used for operating a pre-configured acquisition task file in the system file in an internal memory operating system and executing an acquisition command in the acquisition task file to acquire hardware information of the acquisition task file.
9. A server, comprising a machine-readable storage medium having stored thereon machine-executable instructions and a processor, wherein the processor, when executing the machine-executable instructions, implements the information gathering method of any one of claims 1 to 7.
10. An information management system comprising a management node and a plurality of servers in communication with the management node;
the management node is used for sending the stored operating system kernel and the system file to the server after receiving an information loading request sent by the server;
the server is used for receiving the operating system kernel and the system file sent by the management node and loading the operating system kernel and the system file into the memory;
the server is also used for starting a memory operating system according to the operating system kernel;
the server is also used for operating a pre-configured collection task file in the system file in a memory operating system and executing a collection command in the collection task file to collect hardware information of the server.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911269914.7A CN111078305A (en) | 2019-12-11 | 2019-12-11 | Information acquisition method and device, server and information management system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911269914.7A CN111078305A (en) | 2019-12-11 | 2019-12-11 | Information acquisition method and device, server and information management system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111078305A true CN111078305A (en) | 2020-04-28 |
Family
ID=70313923
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911269914.7A Pending CN111078305A (en) | 2019-12-11 | 2019-12-11 | Information acquisition method and device, server and information management system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111078305A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111524053A (en) * | 2020-04-29 | 2020-08-11 | 中科三清科技有限公司 | Information acquisition method, device, equipment and medium for air quality prediction system |
| CN112231092A (en) * | 2020-11-24 | 2021-01-15 | 政采云有限公司 | Timed task management method, device and equipment and readable storage medium |
| CN113076149A (en) * | 2021-04-09 | 2021-07-06 | 北京明略昭辉科技有限公司 | Method and system for building computing cluster, computer equipment and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104636678A (en) * | 2013-11-15 | 2015-05-20 | 中国电信股份有限公司 | Method and system for controlling terminal device under cloud computing environment |
| CN106911729A (en) * | 2015-12-22 | 2017-06-30 | 中电科技（北京）有限公司 | A kind of operating system remote installation method suitable for domestic processor |
| CN108881504A (en) * | 2018-05-30 | 2018-11-23 | 郑州云海信息技术有限公司 | A kind of hardware information automatic acquiring method and device |
| CN109062580A (en) * | 2018-07-12 | 2018-12-21 | 山东汇贸电子口岸有限公司 | A kind of virtualized environment dispositions method and deployment device |
| CN110495136A (en) * | 2017-11-01 | 2019-11-22 | 华为技术有限公司 | The hardware attributes of bare metal server find method and system |
-
2019
- 2019-12-11 CN CN201911269914.7A patent/CN111078305A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104636678A (en) * | 2013-11-15 | 2015-05-20 | 中国电信股份有限公司 | Method and system for controlling terminal device under cloud computing environment |
| CN106911729A (en) * | 2015-12-22 | 2017-06-30 | 中电科技（北京）有限公司 | A kind of operating system remote installation method suitable for domestic processor |
| CN110495136A (en) * | 2017-11-01 | 2019-11-22 | 华为技术有限公司 | The hardware attributes of bare metal server find method and system |
| CN108881504A (en) * | 2018-05-30 | 2018-11-23 | 郑州云海信息技术有限公司 | A kind of hardware information automatic acquiring method and device |
| CN109062580A (en) * | 2018-07-12 | 2018-12-21 | 山东汇贸电子口岸有限公司 | A kind of virtualized environment dispositions method and deployment device |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111524053A (en) * | 2020-04-29 | 2020-08-11 | 中科三清科技有限公司 | Information acquisition method, device, equipment and medium for air quality prediction system |
| CN111524053B (en) * | 2020-04-29 | 2024-04-19 | 中科三清科技有限公司 | Information acquisition method, device, equipment and medium of air quality prediction system |
| CN112231092A (en) * | 2020-11-24 | 2021-01-15 | 政采云有限公司 | Timed task management method, device and equipment and readable storage medium |
| CN113076149A (en) * | 2021-04-09 | 2021-07-06 | 北京明略昭辉科技有限公司 | Method and system for building computing cluster, computer equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7379982B2 (en) | System and method for custom installation of an operating system on a remote client | |
| US9507604B2 (en) | Boot method and boot system | |
| JP4923058B2 (en) | Automated device driver management | |
| US20170228228A1 (en) | Remote launch of deploy utility | |
| US8402123B2 (en) | Systems and methods for inventorying un-provisioned systems in a software provisioning environment | |
| US20060242395A1 (en) | Operating system boot from network location | |
| US8245022B2 (en) | Method and system to support ISCSI boot through management controllers | |
| US20100325410A1 (en) | System and method for management and installation of operating system images for computers | |
| CN111078305A (en) | Information acquisition method and device, server and information management system | |
| EP2973147A1 (en) | Policy-based secure web boot | |
| CN110908753B (en) | Intelligent fusion cloud desktop server, client and system | |
| WO2011038502A1 (en) | Portable desktop device and method of host computer system hardware recognition and configuration | |
| CN110737479A (en) | method for starting operating system without disk, server and readable storage medium | |
| US20190026126A1 (en) | System and Method for Operating System Initiated Firmware Update via UEFI Applications | |
| CN114138283A (en) | Remote automatic deployment method, device, terminal and storage medium for operating system | |
| CN110099095B (en) | Software deployment method and device, electronic equipment and computer-readable storage medium | |
| US11030047B2 (en) | Information handling system and method to restore system firmware to a selected restore point | |
| CN114385251A (en) | Operating system booting method, system, terminal and storage medium based on memory | |
| CN114115917A (en) | Operating system installation method and device | |
| CN109471665B (en) | Method for automatically installing Windows operating system | |
| US20150212866A1 (en) | Management system for service of multiple operating environments, and methods thereof | |
| CN107659621B (en) | RAID control card configuration method and device | |
| CN113064616A (en) | Software updating method and device, storage medium and electronic equipment | |
| CN113419814A (en) | Virtual machine creating method, device, equipment and storage medium in cloud platform | |
| CN113094108B (en) | Starting method and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WD01 | Invention patent application deemed withdrawn after publication | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20200428 |