CN104731632A - Method and system for deploying operating system - Google Patents

Abstract

The present invention proposes an operating system deployment method and system. The operating system deployment method includes storing the operating system in the system disk of the device that needs to deploy the operating system, and the system disk is specially used for storing the operating system; After that, start the operating system stored in the system disk. This method can be realized simply and can reduce the cost.

Description

Operating system deployment method and system

technical field

The present invention relates to the field of information technology, in particular to an operating system deployment method and system.

Background technique

The deployment of large-scale operating systems (Operation System, OS) is one of the basic constructions of large-scale Internet companies' operation and maintenance automation. The current batch OS deployment method is based on the NIC Preboot ExecuteEnvironment (PXE) technology, the implementation process is relatively complicated, and the hardware cost is high.

Contents of the invention

The present invention aims to solve one of the technical problems in the related art at least to a certain extent.

Therefore, an object of the present invention is to propose a method for deploying an operating system, which can be implemented simply and with reduced costs.

Another object of the present invention is to provide an operating system deployment system.

In order to achieve the above purpose, the operating system deployment method proposed in the first aspect of the present invention includes: storing the operating system in the system disk of the device that needs to deploy the operating system, and the system disk is specially used to store the operating system; After the device is powered on, the operating system stored in the system disk is started.

The operating system deployment method proposed in the embodiment of the first aspect of the present invention can reduce the cost of the system disk by using the system disk to store the operating system specially, and realize the simple implementation by starting the operating system from the system disk.

In order to achieve the above-mentioned purpose, the operating system deployment system proposed in the second aspect of the present invention includes: a system disk, which is used to specially store the operating system; a device that needs to deploy the operating system, and is used to start the device stored in the The operating system on the system disk.

The operating system deployment system proposed by the embodiment of the second aspect of the present invention can reduce the cost of the system disk by using the system disk to store the operating system specially, and the operating system can be started from the system disk, which is simple to implement.

Additional aspects and advantages of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention.

Description of drawings

The above and/or additional aspects and advantages of the present invention will become apparent and easy to understand from the following description of the embodiments in conjunction with the accompanying drawings, wherein:

FIG. 1 is a schematic flowchart of an operating system deployment method proposed by an embodiment of the present invention;

FIG. 2 is a schematic flowchart of an operating system deployment method proposed in another embodiment of the present invention;

FIG. 3 is a schematic flowchart of an operating system deployment method proposed in another embodiment of the present invention;

FIG. 4 is a schematic structural diagram of an operating system deployment system proposed in another embodiment of the present invention;

FIG. 5 is a schematic structural diagram of an operating system deployment system proposed by another embodiment of the present invention.

Detailed ways

Embodiments of the present invention are described in detail below, examples of which are shown in the drawings, wherein the same or similar reference numerals denote the same or similar modules or modules having the same or similar functions throughout. The embodiments described below by referring to the figures are exemplary only for explaining the present invention and should not be construed as limiting the present invention. On the contrary, the embodiments of the present invention include all changes, modifications and equivalents coming within the spirit and scope of the appended claims.

Fig. 1 is a schematic flowchart of an operating system deployment method proposed by an embodiment of the present invention, the method comprising:

S11: Store the operating system in the system disk of the device on which the operating system needs to be deployed, where the system disk is specially used for storing the operating system.

Wherein, storage may also be referred to as installation or curing.

Taking a server as an example where the device to be deployed with an operating system is used, in the prior art, the OS is installed in a fixed mechanical hard disk in the server. Generally, the storage capacity of the mechanical hard disk is large. In order to utilize the storage space of the mechanical hard disk, not only the OS but also data are stored in the mechanical hard disk. And because the data needs to be read and written frequently, the input and output (IO) operations of the mechanical hard disk are more frequent, which is easy to damage the mechanical hard disk. The price of the mechanical hard disk itself is relatively high. If the mechanical hard disk is often damaged, the cost will be further increased.

However, in this embodiment, the system disk and the data disk will be distinguished, and the system disk is dedicated to storing the OS instead of data. Since the storage space required by the OS is small, a small-capacity storage medium can be used. In addition, The IO operation of the OS is relatively small, which reduces the damage rate of the storage medium, thereby effectively reducing the cost.

Optionally, the system disk is set independently from the device.

In the prior art, the mechanical hard disk is fixedly installed in the server, which will occupy a large space of the server. However, in this embodiment, the system disk and the server can be independent devices to reduce the occupation of the server space.

Optionally, the system disk is a U disk.

Since the capacity of the USB flash drive is sufficient to store the OS, and the price of the USB flash drive is relatively low, costs can be saved.

Optionally, the U disk communicates with the device through a USB3.0 protocol interface.

Since the protocol rate of the USB3.0 protocol can be as high as 5Gbps (400MB/s), it can completely withstand the impact of high IO and avoid loading the OS from the U disk to become the bottleneck of the overall system performance.

In addition, the application of USB3.0 is relatively common and can be used conveniently. For example, the haswell platform has basically popularized the interface of USB3.0 protocol.

It can be understood that, in this embodiment, the system disk is taken as an example of a USB flash disk, and it may also be other storage media dedicated to storing the OS, such as a solid-state hard disk. Of course, considering factors such as cost, a storage medium with a lower cost and sufficient capacity for storing the OS may be preferred.

For example, if the system disk is a USB flash drive and the device on which the OS needs to be deployed is a server, the OS in the USB flash drives of different servers can be uniformly obtained from the master disk.

Wherein, the master disk may be a prefabricated USB disk storing an OS. It is understandable that since different enterprises may require different OSs, different master disks can be produced for different enterprises, and then the content in the master disks can be copied to the corresponding system disks of the respective enterprises.

Referring to FIG. 2, in another embodiment, the method for deploying an OS may further include:

S10: The operating system in the master disk is copied to the system disk of each device by means of batch deployment.

Wherein, the method of batch deployment means that the OS in the master disk can be copied to each sub-disk at the same time in a parallel manner, and each sub-disk refers to a U disk corresponding to each server. For example, the master disk and each sub-disk can be connected to the same controller, and the General Hardware Oriented System Transfer (ghost) method is adopted on the controller to copy all the contents of the master disk to the Each initially blank subdisk.

S12: Start the operating system stored in the system disk after the device is powered on.

For example, after the OS is installed on the USB flash drive connected to the server, the server can load the OS from the USB flash drive and run the OS after the server is powered on. Specifically, the server can be set in advance, and the OS can be imported from the USB flash drive first.

In addition, in order to ensure the reliability, stability and high performance of OS operation, it is recommended to conduct necessary reliability (high temperature, vibration test), stability (IO stress test) and performance tests before introducing this technology.

It can be understood that initially, the method of installing the OS on a USB flash drive can be applied to some pilot devices, and when the system test meets the expected results, it can be applied on a large scale.

The specific content of the system test and the corresponding expected results can be set according to actual needs.

In another embodiment, referring to Fig. 3, the method further includes:

S13: Obtain and record the asset information of the device.

Taking the device as a server as an example, when a new server arrives, in the prior art, asset information such as the serial number (Serial Number, SN) of the server on the shelf will be manually recorded.

However, in this embodiment, the asset information of the equipment is obtained automatically. For example, an initialization script can be configured in the server. After the server is powered on and starts the OS, the script can be run. The script is used to obtain the asset information of the server itself and send the resource information to the automation platform. After that, the automation platform can asset information of each newly-launched server, and record it.

Asset information includes, for example, the rack information of the computer room where the machine is located, the SN of the machine itself, the MAC address of the data network port, the MAC of the BMC lan controller, CPU, memory, hard disk, and pcie equipment.

In addition, in order to maintain compatibility with previous products and replace the OS in large quantities, it is possible to maintain the coexistence of new technologies and old technologies.

In this embodiment, the cost of the system disk can be reduced by using the system disk to store the operating system exclusively, and the implementation is simple by starting the operating system from the system disk. Taking the system disk as an example of a USB flash drive, the OS can be solidified in the USB flash drive, which saves the traditional OS deployment of complex platform construction and human investment in the operation and maintenance of long basic service links, and improves the efficiency of operation and maintenance; smaller storage space , cheaper storage media, which greatly reduces the cost of hardware investment; taking the server that needs to deploy the OS as an example, the server automatically captures the server asset information when it goes online, and writes it back into the remote management system RMS (Remote Manager System), eliminating the need for Outsourcing on-site SN verification, asset information entry, etc., shields the manual process and reduces potential problems; online machine operation and maintenance can realize emergency OS replacement from traditional step-by-step installation to outsourced direct insertion and removal of U disk operations , The operation and maintenance efficiency has a qualitative leap.

FIG. 4 is a schematic structural diagram of an operating system deployment system proposed by another embodiment of the present invention. The system 40 includes a system disk 41 and a device 42 that needs to deploy an operating system.

The system disk 41 is used for specially storing the operating system;

Wherein, storage may also be referred to as installation or curing.

Taking a server as an example where the device to be deployed with an operating system is used, in the prior art, the OS is installed in a fixed mechanical hard disk in the server. Generally, the storage capacity of the mechanical hard disk is large. In order to utilize the storage space of the mechanical hard disk, not only the OS but also data are stored in the mechanical hard disk. And because the data needs to be read and written frequently, the input and output (IO) operations of the mechanical hard disk are more frequent, which is easy to damage the mechanical hard disk. The price of the mechanical hard disk itself is relatively high. If the mechanical hard disk is often damaged, the cost will be further increased.

However, in this embodiment, the system disk and the data disk will be distinguished, and the system disk is dedicated to storing the OS instead of data. Since the storage space required by the OS is small, a small-capacity storage medium can be used. In addition, The IO operation of the OS is relatively small, which reduces the damage rate of the storage medium, thereby effectively reducing the cost.

Optionally, the system disk is set independently from the device.

In the prior art, the mechanical hard disk is fixedly installed in the server, which will occupy a large space of the server. However, in this embodiment, the system disk and the server can be independent devices to reduce the occupation of the server space.

Optionally, the system disk is a U disk.

Since the capacity of the USB flash drive is sufficient to store the OS, and the price of the USB flash drive is relatively low, costs can be saved.

Optionally, the U disk communicates with the device through a USB3.0 protocol interface.

Since the protocol rate of the USB3.0 protocol can be as high as 5Gbps (400MB/s), it can completely withstand the impact of high IO and avoid loading the OS from the U disk to become the bottleneck of the overall system performance.

In addition, the application of USB3.0 is relatively common and can be used conveniently. For example, the haswell platform has basically popularized the interface of USB3.0 protocol.

It can be understood that, in this embodiment, the system disk is taken as an example of a USB flash disk, and it may also be other storage media dedicated to storing the OS, such as a solid-state hard disk. Of course, considering factors such as cost, a storage medium with a lower cost and sufficient capacity for storing the OS may be preferred.

For example, if the system disk is a USB flash drive and the device on which the OS needs to be deployed is a server, the OS in the USB flash drives of different servers can be uniformly obtained from the master disk.

Wherein, the master disk may be a prefabricated USB disk storing an OS. It is understandable that since different enterprises may require different OSs, different master disks can be produced for different enterprises, and then the content in the master disks can be copied to the corresponding system disks of the respective enterprises.

Referring to Fig. 5, the system 40 may also include:

The master disk 43 is used to copy the operating system stored in itself to the system disk of each device in a batch deployment manner.

Wherein, the method of batch deployment means that the OS in the master disk can be copied to each sub-disk at the same time in a parallel manner, and each sub-disk refers to a U disk corresponding to each server. For example, the master disk and each sub-disk can be connected to the same controller, and the General Hardware Oriented System Transfer (ghost) method is adopted on the controller to copy all the contents of the master disk to the Each initially blank subdisk.

The device 42 that needs to deploy the operating system is used to start the operating system stored in the system disk after being powered on.

For example, after the OS is installed on the USB flash drive connected to the server, the server can load the OS from the USB flash drive and run the OS after the server is powered on. Specifically, the server can be set in advance, and the OS can be imported from the USB flash drive first.

In addition, in order to ensure the reliability, stability and high performance of OS operation, it is recommended to conduct necessary reliability (high temperature, vibration test), stability (IO stress test) and performance tests before introducing this technology.

It can be understood that initially, the method of installing the OS on a USB flash drive can be applied to some pilot devices, and when the system test meets the expected results, it can be applied on a large scale.

The specific content of the system test and the corresponding expected results can be set according to actual needs.

Referring to Figure 5, the system 40 also includes:

The obtaining device 44 is used to obtain the asset information of the device and record it.

Taking the device as a server as an example, when a new server arrives, in the prior art, asset information such as the serial number (Serial Number, SN) of the server on the shelf will be manually recorded.

However, in this embodiment, the asset information of the equipment is obtained automatically. The acquisition device is, for example, an automation platform. For example, an initialization script can be configured in the server. After the server is powered on and the OS is started, the script can be run. The script is used to obtain the asset information of the server itself and send the resource information to the automation platform. , and then the automation platform can count and record the asset information of each newly-launched server.

Asset information includes, for example, the rack information of the computer room where the machine is located, the SN of the machine itself, the MAC address of the data network port, the MAC of the BMC lan controller, CPU, memory, hard disk, and pcie equipment.

In addition, in order to maintain compatibility with previous products and replace the OS in large quantities, it is possible to maintain the coexistence of new technologies and old technologies.

In this embodiment, the cost of the system disk can be reduced by using the system disk to store the operating system exclusively, and the implementation is simple by starting the operating system from the system disk. Taking the system disk as an example of a USB flash drive, the OS can be solidified in the USB flash drive, which saves the traditional OS deployment of complex platform construction and human investment in the operation and maintenance of long basic service links, and improves the efficiency of operation and maintenance; smaller storage space , cheaper storage media, greatly reducing the cost of hardware investment; taking the server that needs to deploy the OS as an example, the server automatically captures the server asset information when it goes online, and writes it back into the RMS, eliminating the need for SN checks and Links such as asset information input shield the human processing link and reduce potential problems; online machine operation and maintenance can realize emergency OS replacement from traditional step installation to outsourced direct insertion and removal of U disk operation, and the operation and maintenance efficiency is qualitative. fly over.

It should be noted that, in the description of the present invention, the terms "first", "second" and so on are only used for description purposes, and should not be understood as indicating or implying relative importance. In addition, in the description of the present invention, unless otherwise specified, the meaning of "plurality" means at least two.

Any process or method descriptions in flowcharts or otherwise described herein may be understood to represent modules, segments or portions of code comprising one or more executable instructions for implementing specific logical functions or steps of the process , and the scope of preferred embodiments of the invention includes alternative implementations in which functions may be performed out of the order shown or discussed, including substantially concurrently or in reverse order depending on the functions involved, which shall It is understood by those skilled in the art to which the embodiments of the present invention pertain.

It should be understood that various parts of the present invention can be realized by hardware, software, firmware or their combination. In the embodiments described above, various steps or methods may be implemented by software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented by any one or combination of the following techniques known in the art: Discrete logic circuits, ASICs with suitable combinational logic gates, programmable gate arrays (PGAs), field programmable gate arrays (FPGAs), etc.

Those of ordinary skill in the art can understand that all or part of the steps carried by the methods of the above embodiments can be completed by instructing related hardware through a program, and the program can be stored in a computer-readable storage medium. During execution, one or a combination of the steps of the method embodiments is included.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing module, each unit may exist separately physically, or two or more units may be integrated into one module. The above-mentioned integrated modules can be implemented in the form of hardware or in the form of software function modules. If the integrated modules are realized in the form of software function modules and sold or used as independent products, they can also be stored in a computer-readable storage medium.

The storage medium mentioned above may be a read-only memory, a magnetic disk or an optical disk, and the like.

In the description of this specification, descriptions with reference to the terms "one embodiment", "some embodiments", "example", "specific examples", or "some examples" mean that specific features described in connection with the embodiment or example , structure, material or characteristic is included in at least one embodiment or example of the present invention. In this specification, schematic representations of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.

Although the embodiments of the present invention have been shown and described above, it can be understood that the above embodiments are exemplary and should not be construed as limiting the present invention, those skilled in the art can make the above-mentioned The embodiments are subject to changes, modifications, substitutions and variations.

Claims (12)

1. A method for deploying an operating system, comprising: storing the operating system in the system disk of the device on which the operating system needs to be deployed, and the system disk is specially used for storing the operating system; After the device is powered on, start the operating system stored in the system disk. 2. The method according to claim 1, wherein the system disk is set independently from the device. 3. The method according to claim 2, wherein the system disk is a U disk. 4. The method according to claim 3, wherein the U disk communicates with the device through a USB3.0 protocol interface. 5. The method according to claim 1, wherein when there are at least two devices on which operating systems need to be deployed, the method further comprises: In batch deployment, the operating system in the master disk is copied to the system disk of each device. 6. The method according to claim 1, further comprising: Obtain the asset information of the equipment and record it. 7. An operating system deployment system, comprising: The system disk is used to specially store the operating system; The device that needs to deploy the operating system is used to start the operating system stored in the system disk after being powered on. 8. The system according to claim 7, wherein the system disk is set independently from the device. 9. The system according to claim 8, wherein the system disk is a USB disk. 10. The system according to claim 9, wherein the U disk communicates with the device through a USB3.0 protocol interface. 11. The system according to claim 7, wherein when there are at least two devices on which operating systems need to be deployed, the system further comprises: The master disk is used to copy the operating system stored in itself to the system disk of each device in batch deployment. 12. The system according to claim 7, further comprising: Obtaining the equipment is used to acquire the asset information of the equipment and record it.