CN116662078B - Operating system batch recovery method and system based on microkernel implementation - Google Patents

Operating system batch recovery method and system based on microkernel implementation Download PDF

Info

Publication number
CN116662078B
CN116662078B CN202310943665.5A CN202310943665A CN116662078B CN 116662078 B CN116662078 B CN 116662078B CN 202310943665 A CN202310943665 A CN 202310943665A CN 116662078 B CN116662078 B CN 116662078B
Authority
CN
China
Prior art keywords
machine
operating system
recovered
restored
microkernel
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.)
Active
Application number
CN202310943665.5A
Other languages
Chinese (zh)
Other versions
CN116662078A (en
Inventor
花磊
崔骥
温涛
李东航
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Jiangsu Boyun Technology Co ltd
Original Assignee
Jiangsu Boyun Technology Co ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Jiangsu Boyun Technology Co ltd filed Critical Jiangsu Boyun Technology Co ltd
Priority to CN202310943665.5A priority Critical patent/CN116662078B/en
Publication of CN116662078A publication Critical patent/CN116662078A/en
Application granted granted Critical
Publication of CN116662078B publication Critical patent/CN116662078B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1446—Point-in-time backing up or restoration of persistent data
    • G06F11/1458—Management of the backup or restore process
    • G06F11/1469—Backup restoration techniques
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/61—Installation
    • G06F8/63—Image based installation; Cloning; Build to order
    • 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/4416—Network booting; Remote initial program loading [RIPL]
    • 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/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
    • 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/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/45562—Creating, deleting, cloning virtual machine instances
    • 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/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/45595—Network integration; Enabling network access in virtual machine instances
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Computer Security & Cryptography (AREA)
  • Stored Programmes (AREA)
  • Retry When Errors Occur (AREA)

Abstract

The embodiment of the specification provides a method and a system for recovering batch of an operating system based on microkernel implementation, wherein the method comprises the following steps: checking the state of each machine to be restored, and determining the type of an operating system to be restored when the state meets preset conditions; setting the machine to be recovered to be started next time, guiding through a network and restarting; requesting a pXelinux0.cfg file from the PXE service by the machine to be recovered and analyzing the file; acquiring a microkernel operating system, entering into installation, executing a startup script, installing a Docker third party package, pulling a Docker mirror image, and executing a Docker creation command; the method comprises the steps of calling an interface to obtain a snapshot file according to the type of an operating system to be restored, executing snapshot downloading operation, installing a kernel based on decompressed snapshots, and reloading the kernel file; the executor restarts the command and enters the operating system after the recovery is completed, and the method has the advantage of efficiently completing the recovery of the operating system.

Description

Operating system batch recovery method and system based on microkernel implementation
Technical Field
The present disclosure relates to the field of data processing, and in particular, to a method and system for batch recovery of an operating system implemented based on microkernels.
Background
The operating system is used as one of important system software and is responsible for managing software and hardware resources and providing an interface for system software and hardware interaction. The main stream schemes for restoring the machine operating system are as follows: 1. backup recovery at hard disk level; 2. file-level backup recovery. The recovery scheme of the disk level of the main stream is as follows: 1. the disk image is to make the data of the whole hard disk or partition into an image file, and then use a restoration tool to restore. 2. Restoration tools that are self-contained with the operating system, such as windows self-contained system restoration, are used. The file level recovery scheme of the main stream is as follows: 1. and packaging and transmitting the key files to a machine to be restored for decompression. 2. Using common Backup tools, windows Backup, time Machine, etc.
The existing operating system recovery tool or scheme needs manual intervention, cannot execute automatic tasks, cannot meet the use requirements in a large-batch service capacity expansion or migration scene, and is extremely low in efficiency.
Therefore, it is necessary to provide a method and a system for batch recovery of an operating system based on microkernel implementation, which are used for efficiently completing recovery of the operating system.
Disclosure of Invention
One of embodiments of the present disclosure provides a method for batch recovery of an operating system based on microkernel implementation, where the method includes: checking the state of each machine to be restored, and judging whether the state of the machine to be restored meets preset conditions or not; when the state of the machine to be recovered meets a preset condition, determining the type of the corresponding operating system to be recovered of the machine to be recovered; setting the machine to be recovered to be started next time, guiding the machine to be recovered through a network, and restarting the machine to be recovered; the machine to be restored requests a pXelinux0.cfg file from the PXE service, and analyzes the obtained pXelinux0.cfg file; the machine to be recovered acquires a microkernel operating system and enters a microkernel operating system installation flow; after the microkernel system of the machine to be recovered is successfully installed, executing a startup script, installing a Docker third party package, pulling a Docker mirror image, and executing a Docker creation command; the machine to be restored calls an interface to obtain a snapshot file according to the type of the operating system to be restored, performs snapshot downloading operation, and decompresses the snapshot to a target directory after downloading is completed; the machine to be restored installs the kernel based on the decompressed snapshot and reloads the kernel file; and the machine to be recovered executes a machine restarting command and enters the operating system after recovery is completed.
In some embodiments, the machine to be restored requests a pxelinux0.cfg file from a PXE service, including: and the machine to be restored requests the pXelinux0.cfg file from the PXE service through a TFTP protocol.
In some embodiments, the machine to be restored obtains a microkernel operating system, including: and the machine to be recovered acquires the microkernel operating system through an HTTP protocol.
In some embodiments, the machine to be restored calls an interface to obtain a snapshot file according to the type of the operating system to be restored, including: after the container is started, the machine to be restored acquires the snapshot file corresponding to the type of the operating system to be restored through an HTTP protocol calling interface.
In some embodiments, the machine to be restored executes a machine restart command, enters an operating system after restoration is completed, and includes: and the machine to be recovered executes the machine restarting command through the IPMI protocol and enters the operating system after recovery is completed.
In some embodiments, the decompressing the snapshot to the target directory includes: and the machine to be restored switches the root directory to the target directory through a color command, executes decompression operation and decompresses the snapshot to the target directory.
In some embodiments, the machine to be restored installs the kernel based on the decompressed snapshot and reloads the kernel file, including: and the machine to be restored installs the kernel by using a corresponding command based on the starting mode of the BIOS and reloads the kernel file.
In some embodiments, the method further comprises: and after the kernel file is reloaded by the machine to be recovered, before the command is restarted by the execution machine, acquiring the personalized operation executed after recovery through the HTTP protocol, and executing the personalized operation executed after recovery through the command.
In some embodiments, the method further comprises: and the machine to be recovered informs the machine to be recovered that the recovery of the machine to be recovered is completed through an HTTP protocol carrying a machine serial number parameter calling interface of the machine to be recovered.
One embodiment of the present disclosure provides a microkernel-based batch operating system recovery system, including a server and a plurality of machines to be recovered; the server is used for checking the state of each machine to be recovered and judging whether the state of the machine to be recovered meets the preset condition or not; when the state of the machine to be recovered meets a preset condition, determining the type of the corresponding operating system to be recovered of the machine to be recovered; setting the machine to be recovered to be started next time, guiding the machine to be recovered through a network, and restarting the machine to be recovered; the machine to be restored is used for requesting a pXelinux0.cfg file from the PXE service, analyzing the acquired pXelinux0.cfg file, acquiring a microkernel operating system, entering a microkernel operating system installation flow, executing a startup script after the microkernel system is installed successfully, installing a Docker third party package, pulling a Docker mirror image, executing a Docker creation command, calling an interface according to the type of the operating system to be restored to acquire a snapshot file, executing snapshot downloading operation, decompressing the snapshot to a target directory after downloading is completed, installing a kernel based on the decompressed snapshot, reloading the kernel file, executing a machine restarting command, and entering the operating system after restoration is completed.
Drawings
The present specification will be further elucidated by way of example embodiments, which will be described in detail by means of the accompanying drawings. The embodiments are not limiting, in which like numerals represent like structures, wherein:
FIG. 1 is a flow chart of a method of operating system batch recovery based on a microkernel implementation, according to some embodiments of the present description;
FIG. 2 is a block diagram of an operating system batch recovery system based on a microkernel implementation, shown in accordance with some embodiments of the present description;
FIG. 3 is a block diagram of a machine to be restored, shown in accordance with some embodiments of the present description.
Detailed Description
In order to more clearly illustrate the technical solutions of the embodiments of the present specification, the drawings that are required to be used in the description of the embodiments will be briefly described below. It is apparent that the drawings in the following description are only some examples or embodiments of the present specification, and it is possible for those of ordinary skill in the art to apply the present specification to other similar situations according to the drawings without inventive effort. Unless otherwise apparent from the context of the language or otherwise specified, like reference numerals in the figures refer to like structures or operations.
It will be appreciated that "system," "apparatus," "unit" and/or "module" as used herein is one method for distinguishing between different components, elements, parts, portions or assemblies at different levels. However, if other words can achieve the same purpose, the words can be replaced by other expressions.
As used in this specification and the claims, the terms "a," "an," "the," and/or "the" are not specific to a singular, but may include a plurality, unless the context clearly dictates otherwise. In general, the terms "comprises" and "comprising" merely indicate that the steps and elements are explicitly identified, and they do not constitute an exclusive list, as other steps or elements may be included in a method or apparatus.
A flowchart is used in this specification to describe the operations performed by the system according to embodiments of the present specification. It should be appreciated that the preceding or following operations are not necessarily performed in order precisely. Rather, the steps may be processed in reverse order or simultaneously. Also, other operations may be added to or removed from these processes.
The following description will be given of some terms related to the present specification.
The pre-boot execution environment (preboot execute environment, abbreviated as PXE) is an execution environment that is started through a network, and can perform file transfer and boot installation of an operating system through a simple file transfer protocol.
The address resolution protocol (Address Resolution Protocol, abbreviated ARP) is a protocol used to map an IP address to a MAC address, i.e., to interrogate the MAC address corresponding to the target IP.
The simple file transfer protocol (Trivial File Transfer Protocol, abbreviated as TCP) is a protocol in the TCP/IP protocol family for simple file transfer between a client and a server, providing a file transfer service that is not complex and has little overhead.
The internet protocol address (Internet Protocol Address, IP for short) is a series of numbers, also called logical addresses, in the internet protocol that identify the device that sends or receives the datagram.
A medium access control address (Media Access Control Address, abbreviated MAC), which is an address used to identify the location of a network device, is also known as a physical address.
An Operating System (OS) is a computer program that manages computer hardware and software resources.
Out-of-band refers to the use of independent management channels for information communication.
Hypertext transfer protocol (HyperText Transfer Protocol, HTTP) is an application layer protocol for distributed, collaborative, and hypermedia information systems.
The hypertext transfer secure protocol (HyperText Transfer Protocol Secure, HTTPS) is a transport protocol for secure communications over a computer network.
The dynamic host configuration protocol (Dynamic Host Configuration Protocol, DHCP for short) is a network protocol for a local area network. The client can automatically obtain the IP address and the subnet mask allocated by the server when logging in the server by controlling a section of IP address range by the server.
A basic input/output system (Basic Input Output System, simply BIOS) is firmware that performs hardware initialization during a power-on phase and provides runtime services for an operating system.
The unified extensible firmware interface (Unified Extensible Firmware Interface, abbreviated as UEFI) is a standard detailing a completely new type of interface, and is a standard firmware interface suitable for computers, and is intended to replace BIOS.
FIG. 1 is a flow chart of a method of operating system batch recovery based on a microkernel implementation, according to some embodiments of the present description. As shown in FIG. 1, the operating system batch recovery method implemented based on microkernel may include the following steps.
Step 111, checking the state of each machine to be restored, and judging whether the state of the machine to be restored meets the preset condition.
The server can check the machine to be recovered, and can judge the power state, network connectivity, raid configuration, user name and password of the IPMI protocol or the redfish protocol, the starting mode of the BIOS and the like of the machine to be recovered through the API of the IPMI protocol or the redfish protocol.
For example, the server may check whether the network is reachable with the PXE service, and when the machine to be restored is reachable with the PXE service, the status satisfies the preset condition.
And step 112, determining the type of the corresponding operating system to be restored of the machine to be restored when the state of the machine to be restored meets the preset condition.
And 113, setting the machine to be recovered to be started next time, guiding through a network, and restarting the machine to be recovered.
And 114, requesting the PXE service by the machine to be restored for a pxelinux0.cfg file, and analyzing the obtained pxelinux0.cfg file.
Specifically, the machine to be restored requests a pxelinux0.cfg file from the PXE service through TFTP protocol.
And 115, the machine to be recovered acquires the microkernel operating system and enters the microkernel operating system installation flow.
Specifically, the machine to be recovered acquires the microkernel operating system through the HTTP protocol.
And step 116, after the microkernel system is successfully installed on the machine to be recovered, executing a startup script, installing a Docker third party package, pulling a Docker mirror image, and executing a Docker creation command.
And 117, calling an interface to acquire a snapshot file according to the type of the operating system to be restored by the machine to be restored, executing snapshot downloading operation, and decompressing the snapshot to the target directory after the snapshot is downloaded.
Specifically, after the container is started, the machine to be restored acquires the snapshot file from the file server of the server providing the restoration service, the file server supports TFTP, HTTP, NFS protocol, and the machine to be restored can acquire the snapshot file corresponding to the type of the operating system to be restored through the corresponding API acquisition calling interface.
In some embodiments, the machine to be restored switches the root directory to the target directory through a color command, performs a decompression operation, and decompresses the snapshot to the target directory.
And 118, installing the kernel by the machine to be restored based on the decompressed snapshot, and reloading the kernel file.
Specifically, the machine to be restored installs the kernel and reloads the kernel file using the corresponding command based on the boot mode of the BIOS (e.g., UEFI, legacy, etc.).
In some embodiments, the method for batch recovery of operating systems implemented based on micro-kernels may include step 119, where the machine to be recovered acquires the personalized operation performed after recovery through HTTP protocol, and performs the personalized operation performed after recovery through a command.
Specifically, the user can configure the script before the machine to be recovered is recovered, and add the script to the recovery flow, and in the recovery process, the machine to be recovered can acquire the script from the server through the HTTP and HTTPS protocols and execute the script.
In some embodiments, the method for batch recovery of operating systems implemented based on micro-kernels may include step 120, where the machine to be recovered informs the server that the recovery of the machine to be recovered is completed through a machine serial number parameter call interface of the machine to be recovered carried by HTTP protocol, and the server may inform the client that the recovery of the machine to be recovered is completed.
Step 121, the machine to be restored executes the machine restart command, and enters the operating system after the restoration is completed.
It can be understood that the batch recovery method of the operating system based on microkernel realizes batch recovery of bare metal operating systems through microkernel, and in the scene of bare metal service migration or service capacity expansion, the existing backup recovery cannot realize efficient recovery and automation operation, and the recovery of bare metal is more based on flash memory, hard disk cannot realize batch recovery and one-key recovery, and the recovery efficiency of a third party tool is lower, if the backup recovery operation is carried out through microkernel, the recovery operation can be completed in a very short time by the whole process operation; the method has the advantages that under partial service scenes, one-key batch recovery can be carried out through the command/interface, recovery speed is related to the read-write speed of the system disk, recovery efficiency is ensured, and after recovery, subsequent personalized tasks are acquired through the interface, so that the personalized tasks are completed.
FIG. 2 is a block diagram of a microkernel-based implementation of an operating system batch recovery system, according to some embodiments of the present description. In some embodiments, the microkernel-based operating system batch recovery system may be run on a machine to be recovered, and the microkernel-based operating system batch recovery method may be performed by the microkernel-based operating system batch recovery system. As shown in FIG. 2, the operating system batch recovery system implemented based on microkernel may include a server and a plurality of machines to be recovered.
The server is used for checking the state of each machine to be restored and judging whether the state of the machine to be restored meets the preset condition or not; when the state of the machine to be recovered meets the preset condition, determining the type of the corresponding operating system to be recovered of the machine to be recovered; and setting the machine to be recovered to be started next time, guiding through a network, and restarting the machine to be recovered.
The machine to be restored is used for requesting a pXelinux0.cfg file from the PXE service, analyzing the obtained pXelinux0.cfg file, obtaining a microkernel operating system, entering a microkernel operating system installation flow, executing a startup script after the microkernel system is installed successfully, installing a Docker third party package, pulling a Docker mirror image, executing a Docker creation command, calling an interface according to the type of the operating system to be restored to obtain a snapshot file, executing a snapshot downloading operation, decompressing the snapshot to a target directory after the downloading is completed, installing the kernel based on the decompressed snapshot, reloading the kernel file, executing a machine restarting command, and entering the operating system after the restoration is completed.
For more description of a microkernel-based implementation of an operating system batch recovery system, reference may be made to FIG. 1 and its related description. And will not be described in detail herein.
FIG. 3 is a schematic diagram of a machine to be restored, as shown in FIG. 3, which is an example of a hardware device that may be applied to aspects of the present invention, according to some embodiments of the present description. The machine to be restored is intended to represent various forms of digital electronic computer devices, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other suitable computers. The machine to be restored may also represent various forms of mobile devices, such as personal digital processing, cellular telephones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the inventions described and/or claimed herein.
As shown in fig. 3, the machine to be restored includes a computing unit that can perform various appropriate actions and processes according to a computer program stored in a Read Only Memory (ROM) or a computer program loaded from a storage unit into a Random Access Memory (RAM). In the RAM, various programs and data required for the operation of the device may also be stored. The computing unit, ROM and RAM are connected to each other by a bus. An input/output (I/O) interface is also connected to the bus.
A plurality of components in a machine to be restored are connected to an I/O interface, comprising: an input unit, an output unit, a storage unit, and a communication unit. The input unit may be any type of device capable of inputting information to the machine to be restored, and may receive input numeric or character information and generate key signal inputs related to user settings and/or function controls of the machine to be restored. The output unit may be any type of device capable of presenting information and may include, but is not limited to, a display, speakers, video/audio output terminals, vibrators, and/or printers. Storage units may include, but are not limited to, magnetic disks, optical disks. The communication unit allows the machine to be restored to exchange information/data with other devices via a computer network, such as the internet, and/or various telecommunications networks, and may include, but is not limited to, modems, network cards, infrared communication devices, wireless communication transceivers and/or chipsets, such as bluetooth (TM) devices, wiFi devices, wiMax devices, cellular communication devices, and/or the like.
The computing unit may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of computing units include, but are not limited to, central Processing Units (CPUs), graphics Processing Units (GPUs), various specialized Artificial Intelligence (AI) computing chips, various computing units running machine learning model algorithms, digital Signal Processors (DSPs), and any suitable processors, controllers, microcontrollers, and the like. The computing unit performs the various methods and processes described above. For example, in some embodiments, the microkernel-based implementation of the operating system batch recovery method may be implemented as a computer software program tangibly embodied on a machine-readable medium, such as a storage unit. In some embodiments, part or all of the computer program may be loaded and/or installed onto the machine to be restored via the ROM and/or the communication unit. In some embodiments, the computing unit may be configured to perform the microkernel-based implementation of the operating system batch recovery method in any other suitable manner (e.g., by means of firmware).
While the basic concepts have been described above, it will be apparent to those skilled in the art that the foregoing detailed disclosure is by way of example only and is not intended to be limiting. Although not explicitly described herein, various modifications, improvements, and adaptations to the present disclosure may occur to one skilled in the art. Such modifications, improvements, and modifications are intended to be suggested within this specification, and therefore, such modifications, improvements, and modifications are intended to be included within the spirit and scope of the exemplary embodiments of the present invention.
Meanwhile, the specification uses specific words to describe the embodiments of the specification. Reference to "one embodiment," "an embodiment," and/or "some embodiments" means that a particular feature, structure, or characteristic is associated with at least one embodiment of the present description. Thus, it should be emphasized and should be appreciated that two or more references to "an embodiment" or "one embodiment" or "an alternative embodiment" in various positions in this specification are not necessarily referring to the same embodiment. Furthermore, certain features, structures, or characteristics of one or more embodiments of the present description may be combined as suitable.
Furthermore, the order in which the elements and sequences are processed, the use of numerical letters, or other designations in the description are not intended to limit the order in which the processes and methods of the description are performed unless explicitly recited in the claims. While certain presently useful inventive embodiments have been discussed in the foregoing disclosure, by way of various examples, it is to be understood that such details are merely illustrative and that the appended claims are not limited to the disclosed embodiments, but, on the contrary, are intended to cover all modifications and equivalent arrangements included within the spirit and scope of the embodiments of the present disclosure. For example, while the system components described above may be implemented by hardware devices, they may also be implemented solely by software solutions, such as installing the described system on an existing server or mobile device.
Likewise, it should be noted that in order to simplify the presentation disclosed in this specification and thereby aid in understanding one or more inventive embodiments, various features are sometimes grouped together in a single embodiment, figure, or description thereof. This method of disclosure, however, is not intended to imply that more features than are presented in the claims are required for the present description. Indeed, less than all of the features of a single embodiment disclosed above.
Finally, it should be understood that the embodiments described in this specification are merely illustrative of the principles of the embodiments of this specification. Other variations are possible within the scope of this description. Thus, by way of example, and not limitation, alternative configurations of embodiments of the present specification may be considered as consistent with the teachings of the present specification. Accordingly, the embodiments of the present specification are not limited to only the embodiments explicitly described and depicted in the present specification.

Claims (9)

1. The operating system batch recovery method based on microkernel implementation is characterized by comprising the following steps:
checking the state of each machine to be restored, and judging whether the state of the machine to be restored meets preset conditions or not;
when the state of the machine to be recovered meets a preset condition, determining the type of the corresponding operating system to be recovered of the machine to be recovered;
setting the machine to be recovered to be started next time, guiding the machine to be recovered through a network, and restarting the machine to be recovered;
the machine to be restored requests a pXelinux0.cfg file from the PXE service, and analyzes the obtained pXelinux0.cfg file;
the machine to be recovered acquires a microkernel operating system and enters a microkernel operating system installation flow;
after the microkernel system of the machine to be recovered is successfully installed, executing a startup script, installing a Docker third party package, pulling a Docker mirror image, and executing a Docker creation command;
after the container created on the machine to be restored based on the Docker creation command is started, an interface is called according to the type of the operating system to be restored to acquire a snapshot file, snapshot downloading operation is executed, and after the snapshot is downloaded, the snapshot is decompressed to a target directory;
the machine to be restored installs the kernel based on the decompressed snapshot and reloads the kernel file;
the machine to be recovered executes a machine restarting command and enters an operating system after recovery is completed;
the machine to be restored calls an interface to obtain a snapshot file according to the type of the operating system to be restored, and the method comprises the following steps:
after the container is started, the machine to be restored acquires the snapshot file corresponding to the type of the operating system to be restored through an HTTP protocol calling interface.
2. The microkernel-based operating system batch restoration method as in claim 1, wherein the machine to be restored requests a pxelinux0.cfg file from a PXE service, comprising:
and the machine to be restored requests the pXelinux0.cfg file from the PXE service through a TFTP protocol.
3. The method for batch recovery of operating systems based on microkernel implementation of claim 1, wherein the machine to be recovered acquires a microkernel operating system, comprising:
and the machine to be recovered acquires the microkernel operating system through an HTTP protocol.
4. The method for batch recovery of operating systems based on microkernel implementation according to claim 1, wherein the machine to be recovered performs a machine restart command to enter the operating system after recovery is completed, comprising:
and the machine to be recovered executes the machine restarting command through the IPMI protocol and enters the operating system after recovery is completed.
5. The microkernel-based operating system batch recovery method of claim 1, wherein decompressing the snapshot to the target directory comprises:
and the machine to be restored switches the root directory to the target directory through a color command, executes decompression operation and decompresses the snapshot to the target directory.
6. The method for batch recovery of operating systems based on microkernel implementation according to any one of claims 1 to 5, wherein the machine to be recovered installs the kernel based on the decompressed snapshot and reloads the kernel file, comprising:
and the machine to be restored installs the kernel by using a corresponding command based on the starting mode of the BIOS and reloads the kernel file.
7. The microkernel-based operating system batch recovery method as in any one of claims 1-5, further comprising:
and after the kernel file is reloaded by the machine to be recovered, before the command is restarted by the execution machine, acquiring the personalized operation executed after recovery through the HTTP protocol, and executing the personalized operation executed after recovery through the command.
8. The microkernel-based operating system batch recovery method as in any one of claims 1-5, further comprising:
and the machine to be recovered informs the machine to be recovered that the recovery of the machine to be recovered is completed through an HTTP protocol carrying a machine serial number parameter calling interface of the machine to be recovered.
9. The operating system batch recovery system based on microkernel implementation is characterized by comprising a server side and a plurality of machines to be recovered;
the server is used for checking the state of each machine to be recovered and judging whether the state of the machine to be recovered meets the preset condition or not; when the state of the machine to be recovered meets a preset condition, determining the type of the corresponding operating system to be recovered of the machine to be recovered; setting the machine to be recovered to be started next time, guiding the machine to be recovered through a network, and restarting the machine to be recovered;
the machine to be restored is used for requesting a pXelinux0.cfg file from a PXE service, analyzing the acquired pXelinux0.cfg file, acquiring a microkernel operating system, entering a microkernel operating system installation flow, executing a startup script after the microkernel system is successfully installed, installing a Docker third party package, pulling a Docker mirror image, executing a Docker creation command, acquiring a snapshot file according to the type calling interface of the operating system to be restored after the Docker creation command is started, executing snapshot downloading operation, decompressing the snapshot to a target directory after the downloading operation is completed, installing the kernel based on the decompressed snapshot, reloading the kernel file, executing a machine restarting command, and entering the operating system after the restoration is completed;
the machine to be restored calls an interface to obtain a snapshot file according to the type of the operating system to be restored, and the method comprises the following steps:
after the container is started, the machine to be restored acquires the snapshot file corresponding to the type of the operating system to be restored through an HTTP protocol calling interface.
CN202310943665.5A 2023-07-31 2023-07-31 Operating system batch recovery method and system based on microkernel implementation Active CN116662078B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310943665.5A CN116662078B (en) 2023-07-31 2023-07-31 Operating system batch recovery method and system based on microkernel implementation

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310943665.5A CN116662078B (en) 2023-07-31 2023-07-31 Operating system batch recovery method and system based on microkernel implementation

Publications (2)

Publication Number Publication Date
CN116662078A CN116662078A (en) 2023-08-29
CN116662078B true CN116662078B (en) 2023-10-20

Family

ID=87722789

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310943665.5A Active CN116662078B (en) 2023-07-31 2023-07-31 Operating system batch recovery method and system based on microkernel implementation

Country Status (1)

Country Link
CN (1) CN116662078B (en)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104199694A (en) * 2014-08-27 2014-12-10 山东超越数控电子有限公司 Automatic operating system installation and recovery method based on PXE
CN113127077A (en) * 2021-03-29 2021-07-16 中科信安(深圳)信息技术有限公司 Server-based microkernel operating system deployment method and operating system

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101770410B (en) * 2009-01-07 2016-08-17 联想(北京)有限公司 System reducing method based on client operating system, virtual machine manager and system
US9600369B2 (en) * 2013-12-10 2017-03-21 Huawei Technologies Co., Ltd. Operating system recovery method and apparatus, and terminal device

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104199694A (en) * 2014-08-27 2014-12-10 山东超越数控电子有限公司 Automatic operating system installation and recovery method based on PXE
CN113127077A (en) * 2021-03-29 2021-07-16 中科信安(深圳)信息技术有限公司 Server-based microkernel operating system deployment method and operating system

Also Published As

Publication number Publication date
CN116662078A (en) 2023-08-29

Similar Documents

Publication Publication Date Title
US8332490B2 (en) Method, apparatus and program product for provisioning a computer system
US11210132B2 (en) Virtual machine migration in virtualization environment having different virtualization systems
US11418566B2 (en) Adding and removing virtual disks remotely to a streaming machine
US20170337070A1 (en) Computing device for operating a machine session with persistent read cache and non-persistent write cache and related methods
CN108874459B (en) Rapid starting method and device based on virtualization technology
CN111475172B (en) Bare metal deployment method and device
US11860776B2 (en) Concurrent memory recycling for collection of servers
CN111786810A (en) Automatic deployment method and system for large-scale test bed nodes
CN107329802B (en) Virtual machine creating method and electronic equipment
CN114995888A (en) Intelligent network card deployment method, device and medium
CN112948008B (en) Method for managing physical bare machine based on Ironic
CN106557354B (en) Method for setting attribute parameters of private image and computer equipment
CN116662078B (en) Operating system batch recovery method and system based on microkernel implementation
CN111200527B (en) Method for automatically discovering and deploying bare computer based on ironic
CN113821220A (en) Installation method and device of linux operating system
CN113419814B (en) Virtual machine creating method, device, equipment and storage medium in cloud platform
CN113918179A (en) Method and system for automatically installing OS (operating system) by cooperation of host and intelligent network card under Linux
CN114443295A (en) Heterogeneous cloud resource management scheduling method, device and system
CN113360249A (en) Qemu virtual machine operation method based on ARM64
CN106506276A (en) A kind of information detecting method for server
CN115004151A (en) System and method for updating add-on card firmware and collecting hardware information on any server or bare metal server installed with any OS
CN111008043A (en) Server starting method of cloud platform and terminal
US20240036896A1 (en) Generating installation images based upon dpu-specific capabilities
CN117234544B (en) Method and device for recovering system of server equipment
US20230325203A1 (en) Provisioning dpu management operating systems using host and dpu boot coordination

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
GR01 Patent grant
GR01 Patent grant