CN113342365A - Operating system deployment method, device, equipment and computer-readable storage medium - Google Patents
Operating system deployment method, device, equipment and computer-readable storage medium Download PDFInfo
- Publication number
- CN113342365A CN113342365A CN202110720312.XA CN202110720312A CN113342365A CN 113342365 A CN113342365 A CN 113342365A CN 202110720312 A CN202110720312 A CN 202110720312A CN 113342365 A CN113342365 A CN 113342365A
- Authority
- CN
- China
- Prior art keywords
- client
- deployed
- operating system
- partition
- boot partition
- 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 39
- 238000005192 partition Methods 0.000 claims abstract description 149
- 238000005516 engineering process Methods 0.000 abstract description 8
- 238000010586 diagram Methods 0.000 description 5
- 238000004891 communication Methods 0.000 description 4
- 238000012423 maintenance Methods 0.000 description 4
- 238000013461 design Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 230000014509 gene expression Effects 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 238000013473 artificial intelligence Methods 0.000 description 1
- 230000000295 complement effect Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 239000000284 extract Substances 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 229910044991 metal oxide Inorganic materials 0.000 description 1
- 150000004706 metal oxides Chemical class 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
Images
Classifications
-
- 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/4406—Loading of operating system
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The invention relates to the field of financial science and technology, and discloses an operating system deployment method, device, equipment and a computer readable storage medium, wherein the method comprises the following steps: receiving a system deployment request of a client to be deployed, acquiring equipment parameters of the client to be deployed, and acquiring a corresponding mirror image system according to the equipment parameters; reading a system configuration file in the client to be deployed, determining a partition where the system configuration file is located as a boot partition, clearing data in the boot partition in the client to be deployed, and mounting the boot partition; and deploying the mirror image system to the boot subarea. The automatic batch deployment of the enterprise-level operating system is realized, the system deployment is not required to be carried out manually, the deployment efficiency of the operating system is improved, and the deployment cost is reduced.
Description
Technical Field
The present invention relates to the field of financial technology (Fintech), and in particular, to a method, an apparatus, a device, and a computer-readable storage medium for deploying an operating system.
Background
With the development of computer technology, more and more technologies (big data, distributed, Blockchain, artificial intelligence, etc.) are applied to the financial field, and the traditional financial industry is gradually changing to financial technology (Fintech), but because of the requirements of security and real-time performance of the financial industry, higher requirements are also put forward on operating system deployment technology.
In the traditional operating system deployment, each machine to be deployed needs to be manually operated by professional technicians, a large amount of manual configuration operation is needed, and a large efficiency problem does not exist for the deployment of one or a few personal machines, but if the operating system is deployed for a batch level of an enterprise, because the machines to be deployed are more, different operating systems may be different, and types or specific digits may be different, the same manner cannot be adopted for the operating systems with different enterprise levels, while the manual deployment manner is low in efficiency and easy to make mistakes, the later operation and maintenance cost is high, and the batch deployment of the operating systems is difficult to realize. The operating system deployment mode needs special personnel to perform system deployment operation, so that the system deployment efficiency is low due to manual intervention, and the operating system deployment cost is greatly increased.
Disclosure of Invention
The invention mainly aims to provide an operating system deployment method, an operating system deployment device, operating system deployment equipment and a computer-readable storage medium, and aims to solve the technical problem that the operating system deployment efficiency is low in the prior art.
In order to achieve the above object, the present invention provides an operating system deployment method, including:
receiving a system deployment request of a client to be deployed, acquiring equipment parameters of the client to be deployed, and acquiring a corresponding mirror image system according to the equipment parameters;
reading a system configuration file in the client to be deployed, determining a partition where the system configuration file is located as a boot partition, clearing data in the boot partition in the client to be deployed, and mounting the boot partition;
and deploying the mirror image system to the boot subarea.
Optionally, the device parameters include device CPU architecture information and a device model;
the step of obtaining the device parameters of the client to be deployed comprises:
sending an Iscpu command to the client to be deployed, wherein the Iscpu command is used for indicating the client to be deployed to acquire relevant information of a device CPU;
receiving equipment CPU related information sent by the client to be deployed, and determining CPU architecture information from a preset field of the equipment CPU related information;
and acquiring the equipment identification code of the client to be deployed through the Basic Input Output System (BIOS) of the client to be deployed, and determining the equipment model of the client to be deployed according to the equipment identification code.
Optionally, the system configuration file includes a grub. conf file, and the mounting the boot partition includes:
guiding a kernel to start based on kernel configuration information in the grub.conf file through a grub program corresponding to the grub.conf file;
and determining a driver through the kernel based on the driver configuration information in the grub.conf file, and mounting the boot partition through the driver.
Optionally, after the step of reading the system configuration file in the client to be deployed and determining the partition where the system configuration file is located as a boot partition, the method further includes:
backing up data in other partitions except the boot partition in the client to be deployed to a preset local disk and/or a preset backup server;
after the backup is completed, executing the following steps: and clearing data in the boot partition in the client to be deployed.
Optionally, the step of deploying the mirroring system to the boot partition includes:
releasing the mirror image system to the boot partition, and determining a grub program through a preset guide file in an EFI (extensible firmware interface) guide partition in the client to be deployed;
and guiding the mirror image system to start through the grub program.
Optionally, after the step of reading the system configuration file in the client to be deployed, the method further includes:
if the system configuration file in the client to be deployed is not read, deploying and mounting a boot partition in the client to be deployed, and deploying the mirror image system to the boot partition;
if the system configuration file in the client to be deployed is read, executing the following steps: and determining the partition where the system configuration file is located as a boot partition, clearing data in the boot partition in the client to be deployed, and mounting the boot partition.
Optionally, the step of receiving a system deployment request of a client to be deployed includes:
receiving a system deployment request of a client to be deployed, which is sent by the client to be deployed through a pre-starting execution environment PXE;
or,
and receiving a system deployment request of the client to be deployed, which is sent by the client to be deployed through the universal serial bus interface.
Further, to achieve the above object, the present invention further provides an operating system deployment apparatus, including:
the system comprises a system determining module, a mirror image system and a service module, wherein the system determining module is used for receiving a system deployment request of a client to be deployed, acquiring equipment parameters of the client to be deployed and acquiring the corresponding mirror image system according to the equipment parameters;
the data clearing module is used for reading the system configuration file in the client to be deployed, determining the partition where the system configuration file is located as a boot partition, clearing data in the boot partition in the client to be deployed, and mounting the boot partition;
and the system deployment module is used for deploying the mirror image system to the boot partition.
Further, to achieve the above object, the present invention further provides an operating system deployment device, where the operating system deployment device includes a memory, a processor, and an operating system deployment program stored in the memory and executable on the processor, and the operating system deployment program, when executed by the processor, implements the steps of the operating system deployment method as described above.
Further, to achieve the above object, the present invention also provides a computer readable storage medium, on which an operating system deployment program is stored, which when executed by a processor implements the steps of the operating system deployment method as described above.
The method comprises the steps of obtaining equipment parameters of a client to be deployed by receiving a system deployment request of the client to be deployed, and obtaining a corresponding mirror image system according to the equipment parameters; reading a system configuration file in the client to be deployed, determining a partition where the system configuration file is located as a boot partition, clearing data in the boot partition in the client to be deployed, and mounting the boot partition; and deploying the mirror image system to the boot subarea. The automatic batch deployment of the enterprise-level operating system is realized, the system deployment is not required to be carried out manually, the deployment efficiency of the operating system is improved, and the deployment cost is reduced.
Drawings
FIG. 1 is a schematic structural diagram of a hardware operating environment of a device according to an embodiment of an OS deployment device of the present invention;
FIG. 2 is a flowchart illustrating a first exemplary method of deploying an operating system according to the present invention;
FIG. 3 is a functional block diagram of an operating system deployment device according to a preferred embodiment of the present invention.
The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
It should be noted that, in the conventional operating system deployment, a professional technician needs to manually operate each machine to be deployed, a large amount of manual configuration operations are needed, and for the deployment of one or a small number of personal machines, there is no problem of high efficiency, but if the operating system is deployed in a batch level for an enterprise, because there are many machines to be deployed and different operating systems may be different, and may be different in type or specific digit, the same manner cannot be adopted for the operating systems in different enterprise levels, while the manual one-machine deployment manner has low efficiency and is prone to errors, and the later-stage operation and maintenance cost is high, and the batch deployment of the operating systems is difficult to implement. The operating system deployment mode needs special personnel to perform system deployment operation, so that the system deployment efficiency is low due to manual intervention, and the operating system deployment cost is greatly increased.
Based on the above-mentioned defects, the present invention provides an operating system deployment device, and referring to fig. 1, fig. 1 is a schematic structural diagram of a device hardware operating environment according to an embodiment of the operating system deployment device of the present invention.
As shown in fig. 1, the operating system deployment device may include: a processor 1001, such as a CPU, a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. Wherein a communication bus 1002 is used to enable connective communication between these components. The user interface 1003 may include a Display screen (Display), an input unit such as a Keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface, a wireless interface. The network interface 1004 may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface). The memory 1005 may be a high-speed RAM memory or a non-volatile memory (e.g., a magnetic disk memory). The memory 1005 may alternatively be a memory device separate from the processor 1001 described above.
Those skilled in the art will appreciate that the hardware architecture of the operating system deployment device shown in FIG. 1 does not constitute a limitation of operating system deployment devices, and may include more or fewer components than shown, or some components in combination, or a different arrangement of components.
The invention also provides an operating system deployment method.
Before further detailed description of the embodiments of the present invention, terms and expressions referred to in the embodiments of the present invention are described, and the terms and expressions referred to in the embodiments of the present invention are applicable to the following explanations.
PXE: a Preboot eXecution Environment (PXE), also referred to as a Preboot eXecution Environment, provides a mechanism for booting a computer using a Network Interface (Network Interface). This mechanism allows the computer to boot without relying on a local data storage device (e.g., hard disk) or a locally installed operating system.
Universal serial bus interface: universal Serial Bus (USB), abbreviated as USB, is a Serial Bus standard and a technical specification of input/output interfaces, is widely applied to information communication products such as personal computers and mobile devices, and is extended to other related fields such as video equipment, digital televisions (set top boxes), game machines, and the like.
BIOS: basic Input Output System, Basic Input Output System. The BIOS is a set of programs that are fixed on a ROM (Random Access Memory) chip on a motherboard in a computer, and stores the most important basic input/output programs of the computer, a self-test program after power-on, and a system self-boot program, which can read and write specific information set by the system from a CMOS (Complementary Metal Oxide Semiconductor). Its primary function is to provide the lowest level, most direct hardware setup and control for the computer. In addition, the BIOS provides some system parameters to the operating system.
An ARM framework: historically known as Advanced reduced instruction set machines (RISC machines, earlier known as the Acorn RISC Machine), is a family of Reduced Instruction Set (RISC) processor architectures that are widely used in many embedded system designs. The ARM processor is widely used in embedded system design, and is very suitable for the field of mobile communication due to the characteristic of low power consumption.
The UOS operating system: the operating system based on the Linux kernel developed by the system letter software is divided into a system letter desktop operating system and a system letter server operating system. The letter-making desktop operating system mainly takes a desktop application scene, the letter-making server operating system mainly takes a server supporting service scene, and the letter-making server operating system supports notebooks, desktops, all-in-one machines, workstations and servers of chip platforms such as Loongson, Feiteng, Mega-core, sea lights, spread and the like.
It should be noted that, in the Windows operating system, the physical address is first divided to obtain a partition, and then a directory is established on the partition, in the Windows operating system, all paths start from a drive letter, for example: c: // programfile; in the UOS operating system, however, the directory is first used, and then the physical address is mapped to the directory, and all paths start from the root directory (/).
Referring to fig. 2, fig. 2 is a flow chart illustrating a first embodiment of the operating system deployment method of the present invention.
While a logical order is shown in the flow diagrams, in some cases, steps shown or described may be performed in an order different than presented herein.
In various embodiments of the operating system deployment method, various embodiments are described with the operating system deployment apparatus as the executing subject. The operating system deployment method comprises the following steps:
step S10, receiving a system deployment request of a client to be deployed, acquiring equipment parameters of the client to be deployed, and acquiring a corresponding mirror image system according to the equipment parameters;
in the traditional operating system deployment, each machine to be deployed needs to be manually operated by professional technicians, a large amount of manual configuration operation is needed, and a large efficiency problem does not exist for the deployment of one or a few personal machines, but if the operating system is deployed for a batch level of an enterprise, because the machines to be deployed are more, different operating systems may be different, and types or specific digits may be different, the same manner cannot be adopted for the operating systems with different enterprise levels, while the manual deployment manner is low in efficiency and easy to make mistakes, the later operation and maintenance cost is high, and the batch deployment of the operating systems is difficult to realize. The operating system deployment mode needs special personnel to perform system deployment operation, so that the system deployment efficiency is low due to manual intervention, and the operating system deployment cost is greatly increased.
With the development of internet technology, financial institutions (banks, insurance and securities institutions) have higher and higher requirements on operating system deployment technology, and the operating system deployment mode in the prior art seriously affects the working efficiency of the financial institutions such as banks and the like and increases the deployment cost.
In order to solve the technical problem of low efficiency of deploying an operating system in the prior art, the embodiment provides an automatic deployment scheme for an operating system.
In an embodiment, a system deployment request of a client to be deployed may be triggered at the client by a client user, in which case, the client and an operating system deployment device may be connected through a network, and in this scenario, after the client is powered on, the client user may trigger and send the system deployment request through a pre-boot execution environment interface; the client and the operating system deployment device can also be connected with the operating system deployment device through a universal serial bus interface of the client, and in the scene, the client can trigger and send the system deployment request without being connected with the operating system deployment device through a network.
In another embodiment, the system deployment request of the client to be deployed may also be triggered by a manager in the operating system deployment device, and the embodiment is suitable for a scenario in which the manager needs to collectively perform operating system deployment on batch clients, and in this scenario, the client is connected to the operating system deployment device through a network.
In this implementation, after receiving a system deployment request of a client to be deployed, the device parameter of the client to be deployed needs to be acquired, and the mirror image system corresponding to the device parameter of the client to be deployed is determined according to a preset mapping relationship between the device parameter and the mirror image system.
The device parameters comprise CPU architecture information and device models of the clients to be deployed.
In the step S10, the step of obtaining the device parameter of the client to be deployed includes:
step S11, sending an identification command to the client to be deployed, wherein the identification command is used for indicating the client to be deployed to acquire relevant information of a device CPU;
step S12, receiving the relevant information of the equipment CPU sent by the client to be deployed, and determining the CPU architecture information from the preset field of the relevant information of the equipment CPU;
in this embodiment, the identification command may be an Iscpu command, the operating system deployment device sends the Iscpu command to the client to be deployed, where the Iscpu command is used to instruct the client to be deployed to acquire device CPU-related information, after the client to be deployed acquires the device CPU-related information, the device CPU-related information is returned to the operating system deployment device, and the operating system deployment device returns, according to a preset field "Architecture: # "extracts the corresponding CPU architecture information from the device CPU-related information. For example, if the CPU-related information is "Architecture: # x86 ", the CPU Architecture information is x86 Architecture, and if the CPU related information is" Architecture: # arm ", the CPU architecture information is arm architecture.
Step S13, obtaining the device identification code of the client to be deployed through the BIOS of the client to be deployed, and determining the device model of the client to be deployed according to the device identification code.
In this embodiment, a unique serial number of each computer is stored in a BIOS chip of the computer, where the serial number is an equipment identification code, and a preset machine type determination rule may be combined with the equipment identification code to determine an equipment machine type of the client, where the machine type determination rule may be to determine a corresponding equipment machine type according to a key field of the equipment identification code, or may also be to determine a corresponding relation between the equipment identification code and the machine type, or of course, may also be other ways to determine a machine type according to the equipment identification code, and this embodiment is not particularly limited.
Step S20, reading the system configuration file in the client to be deployed, determining the partition where the system configuration file is located as a boot partition, clearing the data in the boot partition in the client to be deployed, and mounting the boot partition;
the embodiment is directed to a UOS (unified operating system) developed based on Linux, and for a client installed with the UOS, an operating system file of the UOS is installed in a boot partition, so that if a system reinstallation needs to be performed on the client, a system configuration file in the client to be deployed needs to be read first, the boot partition in the client to be deployed is identified according to the system configuration file, and then data in the boot partition is cleared, so as to avoid affecting the use of a new installation system.
Further, the system configuration file includes a grub.conf file, and in this embodiment, the operating system deployment device may traverse a file in the client to be deployed to determine the grub.conf file, where the grub.conf file is a mark of a boot partition, that is, a partition where the grub.conf file is located is the partition where the operating system file is installed.
After the data in the boot partition is cleared, the boot partition needs to be mounted to make the boot partition available, i.e., to make the boot partition available to be written with data.
Further, the step of mounting the boot partition specifically includes: because the grub program is a program for booting the operating system, it boots the kernel to start according to kernel configuration information (kernel information) in its own configuration file (i.e., grub. conf file), loads the kernel to the memory, finds the driver according to the driver configuration information (initrd information) in the grub configuration file, and mounts the boot partition by the driver.
In the embodiment, the boot partition is determined according to the grub. conf file, so that the accurate positioning of the boot partition is realized.
And step S30, deploying the mirror image system to the boot partition.
In this embodiment, after the boot partition is mounted, the mirror image system may be deployed into the boot partition. Specifically, the mirror image system is released to the boot partition, and the mirror image system is booted and started through an EFI boot partition in the client to be deployed, so that the deployment of the mirror image system is completed.
Further, the step of booting the mirror image system by the EFI boot partition in the client to be deployed is specifically: the method comprises the steps of restarting a client, carrying out power-on self-test on a mainboard, loading an EFI partition, reading a preset guide file in the EFI partition, wherein the preset guide file can be EFI \ Boot \ bootaa64.EFI, determining a grub program according to the guide file, and guiding a mirror image system to start through preset configuration information in the grub program.
Wherein, the EFI partition (ESP for short) is a physical partition in the format of FAT16 or FAT32, but the partition identifier is EF (hexadecimal) instead of regular 0E or 0C, therefore, the partition is not visible under the Windows operating system. The partition is used to boot the system.
In the embodiment, the device parameters of the client to be deployed are acquired by receiving the system deployment request of the client to be deployed, and the corresponding mirror image system is acquired according to the device parameters; reading a system configuration file in the client to be deployed, determining a partition where the system configuration file is located as a boot partition, clearing data in the boot partition in the client to be deployed, and mounting the boot partition; and deploying the mirror image system to the boot subarea. The automatic batch deployment of the enterprise-level operating system is realized, the system deployment is not required to be carried out manually, the deployment efficiency of the operating system is improved, and the deployment cost is reduced.
Further, a second embodiment of the operating system deployment method of the present invention is provided, in step S20, after the step of reading the system configuration file in the client to be deployed and determining the partition where the system configuration file is located as the boot partition, the method further includes:
step a1, backing up data in other partitions except the boot partition in the client to be deployed to a preset local disk and/or a preset backup server;
after the backup is completed, executing the following steps: and clearing data in the boot partition in the client to be deployed.
Considering that, when a system is reinstalled, it is generally only necessary to clear data of a boot partition where an original operating system is located, and it is not necessary to clear data of a non-boot partition in the entire client, and considering that there may be a risk of data loss or erroneous deletion when the system is reinstalled, this embodiment determines the boot partition in the client to be deployed, and may correspondingly determine other partitions except the boot partition, that is, the non-boot partition, and backs up data in the non-boot partition to a preset local disk through a serial bus interface of the client, and/or backs up the data to a preset backup server through a network, so as to avoid a situation that data in the non-boot partition cannot be found back after being lost or deleted in the process of reinstalling the system.
It is understood that the data backed up to the preset local disk and/or the preset backup server may be stored in association with the device parameters of the client to be deployed and the current backup time, so as to facilitate maintenance and pulling of the backup data.
Further, if the data loss in the non-boot partition is found after the deployment of the operating system is completed, the backup data of any backup time can be pulled from the preset local disk and/or the preset backup server according to the device parameters of the client.
The embodiment provides a scheme for automatically backing up client data, a client user does not need to manually back up data, the efficiency of data backup is improved, and the intelligence of operating system deployment is also improved.
Further, a third embodiment of the operating system deployment method of the present invention is provided, in the step S20, after the step of reading the system configuration file in the client to be deployed, the method further includes:
b1, if the system configuration file in the client to be deployed is not read, deploying a boot partition in the client to be deployed and mounting, and deploying the mirror image system to the boot partition;
step b2, if the system configuration file in the client to be deployed is read, executing the following steps: and determining the partition where the system configuration file is located as a boot partition, clearing data in the boot partition in the client to be deployed, and mounting the boot partition.
In this embodiment, the operating system deployment device may identify a boot partition in the client to be deployed, and if the boot partition in the client to be deployed cannot be identified, that is, the system configuration file in the client to be deployed is not read, it may be determined that the UOS operating system is not deployed in the client to be deployed, and if the operating system deployment process is to install the UOS operating system for the first time, the boot partition needs to be deployed in the client and mounted, and then the mirror image system is deployed in the deployed boot partition.
Further, when the partitions are deployed in the client, generally, in addition to the boot partition, an EFI partition, a swap partition and a root partition may also be deployed.
When the physical memory of the system is not enough, the swap partition can release a part of space in the hard disk memory for the use of the currently running program. The released space may come from programs which do not have any operation for a long time, the released space is temporarily saved in the Swap partition, and the saved data is restored from the Swap partition to the memory when the programs are to run; the root partition, also called root directory (root directory), refers to the top directory of the logical drive, and is relative to the subdirectories, and in the UOS system, user directory information, software installation area, and the like are placed under the root directory.
Certainly, if the boot partition in the client to be deployed can be identified, it may be determined that the UOS operating system has been deployed in the client to be deployed, and this time the operating system deployment process is to reinstall the UOS operating system, the boot partition does not need to be reinstalled again, and the steps may be performed: and clearing data in the boot partition in the client to be deployed.
The embodiment provides a more complete system deployment scheme, and the corresponding automatic deployment process can be obtained no matter the system is reinstalled or the system is installed for the first time, so that the efficiency of operating system deployment is further improved.
The invention also provides an operating system deployment device.
Referring to fig. 3, fig. 3 is a functional module diagram of a first embodiment of the os deployment apparatus according to the present invention. The operating system deployment device comprises:
the system configuration module 10 is configured to receive a system configuration request of a client to be configured, acquire an equipment parameter of the client to be configured, and acquire a corresponding mirror image system according to the equipment parameter;
a data clearing module 20, configured to read a system configuration file in the client to be deployed, determine a partition where the system configuration file is located as a boot partition, clear data in the boot partition in the client to be deployed, and mount the boot partition;
a system deployment module 30, configured to deploy the mirror system to the boot partition.
Further, the device parameters include device CPU architecture information and device model; the system determination module is further configured to:
sending an identification command to the client to be deployed, wherein the identification command is used for indicating the client to be deployed to acquire relevant information of a device CPU;
receiving equipment CPU related information sent by the client to be deployed, and determining CPU architecture information from a preset field of the equipment CPU related information;
and acquiring the equipment identification code of the client to be deployed through the Basic Input Output System (BIOS) of the client to be deployed, and determining the equipment model of the client to be deployed according to the equipment identification code.
Further, the system configuration file includes a grub. conf file, and the data clearing module is further configured to:
guiding a kernel to start based on kernel configuration information in the grub.conf file through a grub program corresponding to the grub.conf file;
and determining a driver through the kernel based on the driver configuration information in the grub.conf file, and mounting the boot partition through the driver.
Further, the operating system deployment apparatus further includes:
the data backup module is used for backing up data in other partitions except the boot partition in the client to be deployed to a preset local disk and/or a preset backup server;
the data clearing module is further configured to, after the backup is completed, execute the steps of: and clearing data in the boot partition in the client to be deployed.
Further, the system deployment module is further configured to:
releasing the mirror image system to the boot partition, and determining a grub program through a preset guide file in an EFI (extensible firmware interface) guide partition in the client to be deployed;
and guiding the mirror image system to start through the grub program.
Further, the operating system deployment apparatus further includes:
the partition module is used for deploying a boot partition in the client to be deployed and mounting the boot partition if the system configuration file in the client to be deployed is not read, and deploying the mirror image system to the boot partition;
the data clearing module is further configured to, if the system configuration file in the client to be deployed is read, execute the following steps: and determining the partition where the system configuration file is located as a boot partition, clearing data in the boot partition in the client to be deployed, and mounting the boot partition.
Further, the system determination module is further configured to:
receiving a system deployment request of a client to be deployed, which is sent by the client to be deployed through a pre-starting execution environment PXE;
or,
and receiving a system deployment request of the client to be deployed, which is sent by the client to be deployed through the universal serial bus interface.
The specific implementation of the os deployment apparatus of the present invention is substantially the same as that of the above-mentioned os deployment method, and is not described herein again.
In addition, the embodiment of the invention also provides a computer readable storage medium.
The computer readable storage medium has stored thereon an operating system deployment program which, when executed by the processor, implements the steps of the operating system deployment method as described above.
The specific implementation manner of the computer-readable storage medium of the present invention is substantially the same as that of the above-mentioned embodiments of the operating system deployment method, and is not described herein again.
The present invention is described in connection with the accompanying drawings, but the present invention is not limited to the above embodiments, which are only illustrative and not restrictive, and those skilled in the art can make various changes without departing from the spirit and scope of the invention as defined by the appended claims, and all changes that come within the meaning and range of equivalency of the specification and drawings that are obvious from the description and the attached claims are intended to be embraced therein.
Claims (10)
1. An operating system deployment method, characterized by comprising:
receiving a system deployment request of a client to be deployed, acquiring equipment parameters of the client to be deployed, and acquiring a corresponding mirror image system according to the equipment parameters;
reading a system configuration file in the client to be deployed, determining a partition where the system configuration file is located as a boot partition, clearing data in the boot partition in the client to be deployed, and mounting the boot partition;
and deploying the mirror image system to the boot subarea.
2. The operating system deployment method of claim 1, wherein the device parameters include device CPU architecture information and device model;
the step of obtaining the device parameters of the client to be deployed comprises:
sending an identification command to the client to be deployed, wherein the identification command is used for indicating the client to be deployed to acquire relevant information of a device CPU;
receiving equipment CPU related information sent by the client to be deployed, and determining CPU architecture information from a preset field of the equipment CPU related information;
and acquiring the equipment identification code of the client to be deployed through the Basic Input Output System (BIOS) of the client to be deployed, and determining the equipment model of the client to be deployed according to the equipment identification code.
3. The operating system deployment method of claim 1, wherein the system configuration file comprises a grub.
Guiding a kernel to start based on kernel configuration information in the grub.conf file through a grub program corresponding to the grub.conf file;
and determining a driver through the kernel based on the driver configuration information in the grub.conf file, and mounting the boot partition through the driver.
4. The method for deploying an operating system according to claim 1, wherein after the step of reading the system configuration file in the client to be deployed and determining the partition where the system configuration file is located as a boot partition, the method further comprises:
backing up data in other partitions except the boot partition in the client to be deployed to a preset local disk and/or a preset backup server;
after the backup is completed, executing the following steps: and clearing data in the boot partition in the client to be deployed.
5. The method of operating system deployment of claim 1 wherein the step of deploying the mirrored system to the boot partition comprises:
releasing the mirror image system to the boot partition, and determining a grub program through a preset guide file in an EFI (extensible firmware interface) guide partition in the client to be deployed;
and guiding the mirror image system to start through the grub program.
6. The method for deploying an operating system according to claim 1, wherein the step of reading the system configuration file in the client to be deployed further comprises, after the step of reading the system configuration file in the client to be deployed:
if the system configuration file in the client to be deployed is not read, deploying and mounting a boot partition in the client to be deployed, and deploying the mirror image system to the boot partition;
if the system configuration file in the client to be deployed is read, executing the following steps: and determining the partition where the system configuration file is located as a boot partition, clearing data in the boot partition in the client to be deployed, and mounting the boot partition.
7. The operating system deployment method of any one of claims 1 to 6, wherein the step of receiving a system deployment request for a client to be deployed comprises:
receiving a system deployment request of a client to be deployed, which is sent by the client to be deployed through a pre-starting execution environment PXE;
or,
and receiving a system deployment request of the client to be deployed, which is sent by the client to be deployed through the universal serial bus interface.
8. An operating system deployment apparatus, the operating system deployment apparatus comprising:
the system comprises a system determining module, a mirror image system and a service module, wherein the system determining module is used for receiving a system deployment request of a client to be deployed, acquiring equipment parameters of the client to be deployed and acquiring the corresponding mirror image system according to the equipment parameters;
the data clearing module is used for reading the system configuration file in the client to be deployed, determining the partition where the system configuration file is located as a boot partition, clearing data in the boot partition in the client to be deployed, and mounting the boot partition;
and the system deployment module is used for deploying the mirror image system to the boot partition.
9. An operating system deployment device, comprising a memory, a processor, and an operating system deployment program stored on the memory and executable on the processor, the operating system deployment program, when executed by the processor, implementing the steps of the operating system deployment method as claimed in any one of claims 1 to 7.
10. A computer-readable storage medium, having stored thereon an operating system deployment program which, when executed by a processor, implements the steps of the operating system deployment method of any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110720312.XA CN113342365A (en) | 2021-06-28 | 2021-06-28 | Operating system deployment method, device, equipment and computer-readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110720312.XA CN113342365A (en) | 2021-06-28 | 2021-06-28 | Operating system deployment method, device, equipment and computer-readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113342365A true CN113342365A (en) | 2021-09-03 |
Family
ID=77479276
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110720312.XA Pending CN113342365A (en) | 2021-06-28 | 2021-06-28 | Operating system deployment method, device, equipment and computer-readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113342365A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114756247A (en) * | 2022-03-31 | 2022-07-15 | 苏州浪潮智能科技有限公司 | System deployment method, device, equipment and storage medium |
| TWI808713B (en) * | 2022-01-27 | 2023-07-11 | 楊明勳 | Method and system for deploying operating environments |
-
2021
- 2021-06-28 CN CN202110720312.XA patent/CN113342365A/en active Pending
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| TWI808713B (en) * | 2022-01-27 | 2023-07-11 | 楊明勳 | Method and system for deploying operating environments |
| CN114756247A (en) * | 2022-03-31 | 2022-07-15 | 苏州浪潮智能科技有限公司 | System deployment method, device, equipment and storage medium |
| CN114756247B (en) * | 2022-03-31 | 2024-06-21 | 苏州浪潮智能科技有限公司 | System deployment method, device, equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11556325B2 (en) | Software installation onto a client using existing resources | |
| EP2189901B1 (en) | Method and system to enable fast platform restart | |
| US8387045B2 (en) | Cloning image creation using virtual machine environment | |
| US8205194B2 (en) | Updating offline virtual machines or VM images | |
| US7313685B2 (en) | Unattended BIOS recovery | |
| US20040172578A1 (en) | Method and system of operating system recovery | |
| US8838848B2 (en) | Systems and methods for intelligent system profile unique data management | |
| US12001285B2 (en) | System booting method and apparatus, node device, and computer-readable storage medium | |
| CN102591675A (en) | Method and system for management of multiple software images with shared memory blocks | |
| US11030047B2 (en) | Information handling system and method to restore system firmware to a selected restore point | |
| US8335891B2 (en) | Method and system for configuring a storage array | |
| CN113342365A (en) | Operating system deployment method, device, equipment and computer-readable storage medium | |
| US20040221024A1 (en) | Apparatus and method for setting environment of client in client / server system, and program recording medium therefor | |
| US9852029B2 (en) | Managing a computing system crash | |
| US11256519B2 (en) | Using a single process to install a UEFI-supported OS or a non-UEFI supported OS on a hardware platform | |
| US8612737B2 (en) | System and method for supporting multiple hardware platforms with a single disk image | |
| US11675601B2 (en) | Systems and methods to control software version when deploying OS application software from the boot firmware | |
| US20140136777A1 (en) | Method and system for configuring a storage array | |
| CN102681859A (en) | Method for starting Windows operation systems from USB (universal serial bus) mass storage device | |
| KR102423056B1 (en) | Method and system for swapping booting disk | |
| US20230229426A1 (en) | Out-of-band firmware update | |
| US20230350755A1 (en) | Coordinated operating system rollback | |
| KR100947136B1 (en) | Incremental provisioning of software | |
| CN118779070A (en) | Service recovery method and related 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 |