Methods, systems, equipment, and media for automated batch deployment of multiple operating systems

Abstract

This invention discloses a method, system, device, and medium for the batch automatic deployment of multiple operating systems, belonging to the field of operating system deployment technology. The technical problem this invention aims to solve is how to achieve the batch automated deployment of multiple operating system versions, improving the deployment efficiency of data center server rooms and delivery maintenance, and enhancing system stability and security. The technical solution adopted is as follows: High-availability service configuration: Based on keepalived, configure data synchronization services, health monitoring and triggering scripts for the Cobbler service to complete the high-availability configuration of the Cobbler service; Automated deployment of multiple operating systems: Centrally manage the installation and configuration of multiple server operating systems, achieving automated operating system installation and managing operating system-related configurations; Patch configuration update: Configure multiple patch sources on the Cobbler server for storing and managing system patches.

Description

Technical Field

[0001] This invention relates to the field of operating system deployment technology, specifically to a method, system, device, and medium for the batch automatic deployment of multiple operating systems. Background Technology

[0002] With the rapid development of modern information technology and the increasing complexity of IT infrastructure, coupled with the advancements in big data and cloud computing technologies, enterprises are constantly expanding, leading to a corresponding increase in the quantity and complexity of their IT infrastructure. To meet the demands of business growth, enterprises need to deploy a large number of servers and client devices quickly and efficiently. As the core of an enterprise's IT infrastructure, the data center needs to support a massive volume of server demands. Batch deployment of operating systems ensures the efficient operation of the data center and rapid response to business needs.

[0003] Traditionally, operating system automation is achieved by using PXE and Kickstart for automated installation. However, Kickstart offers limited functionality, only allowing the installation of one type of operating system and not supporting the selection of multiple operating systems. In actual delivery and maintenance work, different versions and types of operating systems are encountered.

[0004] Therefore, how to achieve batch automated deployment of multiple operating system versions, improve the deployment efficiency of data center computer rooms and delivery operation and maintenance, and improve system stability and security are technical problems that urgently need to be solved. Summary of the Invention

[0005] The technical objective of this invention is to provide a method, system, device, and medium for the batch automatic deployment of multiple operating systems, in order to solve the problem of how to achieve the batch automatic deployment of multiple versions of operating systems, improve the deployment efficiency of data center computer rooms and delivery and maintenance, and improve system stability and security.

[0006] The technical objective of this invention is achieved as follows: a method for automatically deploying multiple operating systems in batches, the specific details of which are as follows:

[0007] High availability service configuration: Based on keepalived, configure the health monitoring and trigger scripts for the data synchronization service and Cobbler service to complete the high availability configuration of the Cobbler service;

[0008] Automated deployment of multiple operating systems: Centrally manage the installation and configuration of multiple server operating systems, realize automated operating system installation, and manage operating system-related configurations;

[0009] Patch configuration update: Configure multiple patch sources on the Cobbler server to store and manage system patches. After the client machine completes the operating system installation, it will automatically connect to the patch sources provided by the Cobbler server to update and install patches.

[0010] As a preferred option, the data synchronization service is configured as follows: the data synchronization service is configured using rsyn+notify-tools. When a file in the directory is modified, deleted, or added, inotify-tools triggers rsync to perform a synchronization operation, thereby synchronizing the system image file and the cobbler configuration file.

[0011] The health monitoring and triggering scripts for the Cobbler service are written using shell technology. Their purpose is to periodically check the running status of the Cobbler service, including the automatic startup of the Cobbler and HTTP services. If any service abnormalities are detected, the scripts will promptly send alarm emails to the operations and maintenance personnel.

[0012] Even better, centralized management of the installation and configuration of multiple server operating systems is as follows:

[0013] Configure image repositories and installation scripts for multiple operating systems on the Cobbler server;

[0014] Create a separate image repository for each operating system version and store it in a network location accessible to the Cobbler server.

[0015] Ideally, the automated installation of the operating system is as follows:

[0016] The installation is performed automatically when the client server starts, using the pre-configured installation template and configuration file (when automatically installing the operating system, there is a list of operating systems to choose from on the cobbler page), without the need for manual intervention;

[0017] Using PXE booting, the client server can obtain the necessary files and configuration information for installation from the Cobbler server in batches over the network, enabling unattended operating system installation.

[0018] The client accesses the network where the Cobbler server is located and supports loading Kickstart files. The client writes the corresponding Kickstart files to guide the automated installation process of the operating system.

[0019] After the client boots via PXE, it loads the startup file provided by the Cobbler server and executes the Kickstart script to complete the operating system installation.

[0020] More specifically, the management of operating system-related configurations is as follows: The Cobbler server uses Kickstart (%post script segment) technology to complete the configuration files for the management server and defines various configuration files for network configuration, hostname, and user accounts. During the installation process, the network configuration, hostname, and user account configuration files are automatically applied.

[0021] Ideally, the patch source should be configured as a YUM source, which makes it easier for clients to update and install patches using the YUM command, and to periodically synchronize the latest patch packages from the upstream source, ensuring that clients receive the latest security updates and fixes.

[0022] A batch automated deployment system for multiple operating systems, the system comprising:

[0023] The high availability service configuration module is used to configure the health monitoring and trigger scripts of the data synchronization service and Cobbler service based on keepalived, and to complete the high availability configuration of the Cobbler service.

[0024] An automated deployment module for multiple operating systems is used to centrally manage the installation and configuration of multiple server operating systems, enabling automated installation of operating systems and management of related configurations.

[0025] The patch configuration update module is used to configure multiple patch sources on the Cobbler server for storing and managing system patches. After the client machine completes the operating system installation, it automatically connects to the patch sources provided by the Cobbler server to update and install patches.

[0026] As a preferred option, the working process of this system is as follows:

[0027] (1) The Cobbler server adopts a high-availability cluster configuration (to prevent single point of failure) and provides web access services as well as operating system deployment and patch updates to the outside world;

[0028] (2) Ensure the client and Cobbler server are in the same network environment, and check the network status:

[0029] If there is a network anomaly, check the client's network information;

[0030] (3) Check the Cobbler server service configuration information to ensure that the server-side cobbler, DHCP, http, and keepalived services are in normal operating condition;

[0031] (4) Obtain the version information of the operating system or update patch, obtain a list of all available operating system versions for deployment and installation, and determine whether the version information has been obtained:

[0032] If version information is not obtained, check or update the service configuration again;

[0033] (5) Determine whether the required version information is included based on actual needs:

[0034] If the required version information is included, an execution command is sent, and execution begins automatically. After execution, the operating system deployment status or patch installation status is checked, and the installation process is complete.

[0035] (6) After installation, check if the version information matches:

[0036] If the versions are incompatible, you need to check all the server-side configurations, update the service configuration, and restart the client to select the correct version.

[0037] An electronic device, characterized in that it comprises: a memory and at least one processor;

[0038] The memory stores computer-executed instructions;

[0039] The at least one processor executes computer execution instructions stored in the memory, causing the at least one processor to execute the above-described methods for the batch automatic deployment of various operating systems.

[0040] A computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the above-described methods for the batch automatic deployment of various operating systems.

[0041] The multi-operating system batch automatic deployment method, system, device and medium of the present invention have the following advantages:

[0042] (i) This invention realizes automated deployment, patch configuration and update, and high availability configuration of multiple operating systems. The corresponding operating system can be selected according to actual needs, realizing unattended deployment.

[0043] (ii) This invention can realize batch unattended deployment of multiple operating systems, saving manual deployment time and reducing the probability of errors compared with traditional image installation; at the same time, it adopts a high-availability architecture for deployment, improving service reliability; and integrates patch management function to uniformly manage patches and installation package versions.

[0044] (III) This invention is based on cobbler technology. Only the server-side component and its dependent services (DHCP, TFTP, HTTP, etc.) need to be deployed; client machines only need to connect to the network. This enables the installation of multiple operating system versions without manual intervention. It significantly improves the deployment efficiency of data center server rooms and their operation and maintenance, reduces labor costs, lowers the probability of errors, and ensures system security and stability.

[0045] (iv) This invention abandons the traditional ISO image mounting or USB flash drive boot method and uses the cobbler tool technology to deploy the operating system unattended, which improves deployment efficiency and reduces errors in operating system installation.

[0046] (v) The server of the present invention can deploy a variety of common operating system sources to meet different business needs and solve problems such as temporary download of operating system and long customer waiting time.

[0047] (vi) The server of this invention can be updated with patches regularly and provided to the outside world as a YUM source, saving patch download time and allowing unified management of system installation package versions;

[0048] (vii) The present invention is deployed with a high availability architecture, and automatically switches to a backup machine after a service failure, thus avoiding service unavailability caused by the failure.

[0049] (viii) Using this invention, common operating systems can be deployed with one click in the same local area network environment, achieving unattended deployment; it can also upgrade relevant system patches;

[0050] (ix) This invention solves the problems of excessive business reliance on operating system versions, incorrect image versions, inconsistent system installation packages, and long deployment time caused by manually mounting and installing images. It is diverse, practical, and highly available. While providing the main services for deploying the operating system, it also provides related practical services such as NTP updates and patch updates, which can reduce operation and maintenance costs. Attached Figure Description

[0051] The invention will be further described below with reference to the accompanying drawings.

[0052] Appendix Figure 1 A flowchart illustrating a method for automated batch deployment across multiple operating systems;

[0053] Appendix Figure 2 Flowchart for high availability configuration;

[0054] Appendix Figure 3 A flowchart illustrating the process of automatically deploying systems in batches across multiple operating systems. Detailed Implementation

[0055] The following detailed description of the various operating system batch automatic deployment methods, systems, devices, and media of the present invention, with reference to the accompanying drawings and specific embodiments, is provided.

[0056] Example 1:

[0057] As attached Figure 1 As shown in the figure, this embodiment provides a method for batch automatic deployment of multiple operating systems, and the method is as follows:

[0058] S1. High Availability Service Configuration: Based on keepalived, configure the data synchronization service and health monitoring and trigger scripts for the Cobbler service to complete the high availability configuration of the Cobbler service. Keepalived is a lightweight high availability solution for Linux. It is a service software based on the VRRP protocol that ensures high availability of the cluster. Its main functions are to achieve fault isolation of physical machines and failover between load balancers to prevent single points of failure.

[0059] S2. Automated Deployment of Multiple Operating Systems: Centrally manage the installation and configuration of multiple server operating systems, realize automated operating system installation, and manage operating system-related configurations;

[0060] S3. Patch Configuration Update: Configure multiple patch sources on the Cobbler server to store and manage system patches. After the client machine completes the operating system installation, it will automatically connect to the patch sources provided by the Cobbler server to update and install patches.

[0061] As attached Figure 2 As shown, the high availability service configuration in step S1 of this embodiment is as follows:

[0062] S101. Configure data synchronization service: Use rsyn+notify-tools to configure data synchronization service. When a file in the directory is modified, deleted or added, inotify-tools triggers rsync to perform synchronization operation, realizing data synchronization between system image file and cobbler configuration file.

[0063] S102. Health monitoring script and trigger script for the Cobbler service: The health monitoring and trigger script for the Cobbler service is written using shell technology. Its purpose is to periodically check the running status of the Cobbler service, including the automatic startup of the Cobbler and HTTP services. If an abnormality is detected, the trigger script will promptly send an alarm email to the operations and maintenance personnel.

[0064] The specific details of the automated deployment of various operating systems in step S2 of this embodiment are as follows:

[0065] S201, Centralized Management: Centralized management of the installation and configuration of multiple server operating systems; configuring image repositories and installation scripts for multiple operating systems on the Cobbler server; and creating an independent image repository for each operating system version and storing it in a network location accessible by the Cobbler server.

[0066] S202 Automated Operating System Installation: Using pre-configured installation templates and configuration files (a list of operating systems is available on the Cobbler page during automatic installation), the installation process automatically begins when the client server starts, requiring no manual intervention. Utilizing PXE booting, the client server can batch-retriev the necessary files and configuration information from the Cobbler server over the network, enabling unattended operating system installation. Simultaneously, the client accesses the network where the Cobbler server is located and supports loading Kickstart files. A corresponding Kickstart file can be written to guide the automated operating system installation process. After booting via PXE, the client loads the boot file provided by the Cobbler server and executes the Kickstart script to complete the operating system installation.

[0067] S203. Managing Operating System-Related Configurations: The Cobbler server uses Kickstart (%post script segment) technology to manage the server's configuration files and define various configuration files for network configuration, hostname, and user accounts. During the installation process, it automatically applies these configuration files.

[0068] In step S4 of this embodiment, the patch source is configured as a YUM source, which makes it convenient for the client to update and install patches through the YUM command, and to periodically synchronize the latest patch packages from the upstream source to ensure that the client obtains the latest security updates and fixes.

[0069] Example 2:

[0070] This embodiment provides a system for the automatic batch deployment of multiple operating systems, the system comprising:

[0071] The high availability service configuration module is used to configure the health monitoring and trigger scripts of the data synchronization service and Cobbler service based on keepalived, and to complete the high availability configuration of the Cobbler service.

[0072] An automated deployment module for multiple operating systems is used to centrally manage the installation and configuration of multiple server operating systems, enabling automated installation of operating systems and management of related configurations.

[0073] The patch configuration update module is used to configure multiple patch sources on the Cobbler server for storing and managing system patches. After the client machine completes the operating system installation, it automatically connects to the patch sources provided by the Cobbler server to update and install patches.

[0074] As attached Figure 3 As shown, the specific working process of this system is as follows:

[0075] (1) The Cobbler server adopts a high-availability cluster configuration (to prevent single point of failure) and provides web access services as well as operating system deployment and patch updates to the outside world;

[0076] (2) Ensure the client and Cobbler server are in the same network environment, and check the network status:

[0077] If there is a network anomaly, check the client's network information;

[0078] (3) Check the Cobbler server service configuration information to ensure that the server-side cobbler, DHCP, http, and keepalived services are in normal operating condition;

[0079] (4) Obtain the version information of the operating system or update patch, obtain a list of all available operating system versions for deployment and installation, and determine whether the version information has been obtained:

[0080] If version information is not obtained, check or update the service configuration again;

[0081] (5) Determine whether the required version information is included based on actual needs:

[0082] If the required version information is included, an execution command is sent, and execution begins automatically. After execution, the operating system deployment status or patch installation status is checked, and the installation process is complete.

[0083] (6) After installation, check if the version information matches:

[0084] If the versions are incompatible, you need to check all the server-side configurations, update the service configuration, and restart the client to select the correct version.

[0085] Example 3:

[0086] This embodiment also provides an electronic device, including: a memory and at least one processor;

[0087] The memory stores computer-executed instructions;

[0088] The at least one processor executes computer execution instructions stored in the memory, causing the at least one processor to execute the batch automatic deployment method for multiple operating systems as described in any one of the present invention.

[0089] The processor can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), off-the-shelf programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The processor can be a microprocessor or any conventional processor.

[0090] Memory is used to store computer programs and / or modules. The processor implements various functions of the electronic device by running or executing the computer programs and / or modules stored in the memory, and by accessing data stored in the memory. Memory can mainly include a program storage area and a data storage area. The program storage area can store the operating system, at least one application program required for a function, etc.; the data storage area can store data created based on the use of the terminal, etc. In addition, memory can also include high-speed random access memory, and can also include non-volatile memory, such as hard disks, RAM, plug-in hard disks, smart memory cards (SMC), secure digital cards (SD cards), flash memory cards, at least one disk storage device, flash memory devices, or other volatile solid-state storage devices.

[0091] Example 4:

[0092] This embodiment also provides a computer-readable storage medium storing multiple instructions, which are loaded by a processor to cause the processor to execute the various operating system batch automatic deployment methods in any embodiment of the present invention. Specifically, a system or apparatus equipped with a storage medium may be provided, on which software program code implementing the functions of any of the above embodiments is stored, and the computer (or CPU or MPU) of the system or apparatus may read and execute the program code stored in the storage medium.

[0093] In this case, the program code read from the storage medium can itself implement the function of any of the above embodiments, and therefore the program code and the storage medium storing the program code constitute part of the present invention.

[0094] Examples of storage media used to provide program code include floppy disks, hard disks, magneto-optical disks, optical disks (such as CD-ROM, CD-R, CD-RW, DVD-ROM, DVD-RAM, DVD-RW, DVD+RW), magnetic tapes, non-volatile memory cards, and ROMs. Alternatively, program code can be downloaded from a server computer via a communication network.

[0095] Furthermore, it should be clear that not only can the program code read by the computer be executed, but also the operating system or other components operating on the computer can be instructed based on the program code to perform some or all of the actual operations, thereby realizing the function of any of the embodiments described above.

[0096] Furthermore, it is understood that the program code read from the storage medium is written to the memory set in the expansion board inserted into the computer or to the memory set in the expansion unit connected to the computer. Then, based on the instructions of the program code, the CPU or other components installed on the expansion board or expansion unit execute some and all of the actual operations, thereby realizing the function of any of the embodiments described above.

[0097] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for batch automatic deployment of multiple operating systems, characterized in that, The method is as follows: High availability service configuration: Based on keepalived, configure the health monitoring and trigger scripts for the data synchronization service and Cobbler service to complete the high availability configuration of the Cobbler service; Automated deployment of multiple operating systems: Centrally manage the installation and configuration of multiple server operating systems, realize automated operating system installation, and manage operating system-related configurations; Patch configuration update: Configure multiple patch sources on the Cobbler server to store and manage system patches. After the client machine completes the operating system installation, it will automatically connect to the patch sources provided by the Cobbler server to update and install patches. The centralized management of the installation and configuration of multiple server operating systems is detailed below: Configure image repositories and installation scripts for multiple operating systems on the Cobbler server; Create a separate image repository for each operating system version and store it in a network location accessible to the Cobbler server; The automated operating system installation process is detailed below: The installation will be performed automatically when the client server starts, using the pre-configured installation template and configuration file. Using PXE booting, the client server can obtain the necessary files and configuration information for installation from the Cobbler server in batches over the network, enabling unattended operating system installation. The client accesses the network where the Cobbler server is located and supports loading Kickstart files. The client writes the corresponding Kickstart files to guide the automated installation process of the operating system. After the client boots via PXE, it loads the startup file provided by the Cobbler server and executes the Kickstart script to complete the operating system installation; The specific configuration management for the operating system is as follows: The Cobbler server uses Kickstart technology to complete the configuration files for the management server and defines various configuration files for network configuration, hostname, and user accounts. During the installation process, the network configuration, hostname, and user account configuration files are automatically applied.

2. The method for batch automatic deployment of multiple operating systems according to claim 1, characterized in that, The specific configuration of the data synchronization service is as follows: Use rsyn+notify-tools to configure the data synchronization service. When a file in the directory is modified, deleted, or added, inotify-tools triggers rsync to perform a synchronization operation, thereby synchronizing the system image file and the cobbler configuration file. The health monitoring and triggering scripts for the Cobbler service are written using shell technology. Their purpose is to periodically check the running status of the Cobbler service, including the automatic startup of the Cobbler and HTTP services. If any service abnormalities are detected, the scripts will promptly send alarm emails to the operations and maintenance personnel.

3. The method for batch automatic deployment of multiple operating systems according to claim 1, characterized in that, The patch source is configured as a YUM repository, which makes it easy for clients to update and install patches using the YUM command, and regularly synchronizes the latest patch packages from the upstream source to ensure that clients obtain the latest security updates and fixes.

4. A batch automatic deployment system for multiple operating systems, characterized in that, The system includes: The high availability service configuration module is used to configure the health monitoring and trigger scripts of the data synchronization service and Cobbler service based on keepalived, and to complete the high availability configuration of the Cobbler service. An automated deployment module for multiple operating systems is used to centrally manage the installation and configuration of multiple server operating systems, enabling automated installation of operating systems and management of related configurations. The patch configuration update module is used to configure multiple patch sources on the Cobbler server for storing and managing system patches. After the client machine completes the operating system installation, it automatically connects to the patch sources provided by the Cobbler server to update and install patches. The centralized management of the installation and configuration of multiple server operating systems is detailed below: Configure image repositories and installation scripts for multiple operating systems on the Cobbler server; Create a separate image repository for each operating system version and store it in a network location accessible to the Cobbler server; The automated operating system installation process is detailed below: The installation will be performed automatically when the client server starts, using the pre-configured installation template and configuration file. Using PXE booting, the client server can obtain the necessary files and configuration information for installation from the Cobbler server in batches over the network, enabling unattended operating system installation. The client accesses the network where the Cobbler server is located and supports loading Kickstart files. The client writes the corresponding Kickstart files to guide the automated installation process of the operating system. After the client boots via PXE, it loads the startup file provided by the Cobbler server and executes the Kickstart script to complete the operating system installation; The specific configuration management for the operating system is as follows: The Cobbler server uses Kickstart technology to complete the configuration files for the management server and defines various configuration files for network configuration, hostname, and user accounts. During the installation process, the network configuration, hostname, and user account configuration files are automatically applied.

5. The batch automatic deployment system for multiple operating systems according to claim 4, characterized in that, The working process of this system is as follows: (1) The Cobbler server adopts a high-availability cluster configuration to provide web access services as well as operating system deployment and patch updates; (2) Ensure that the client and the Cobbler server are in the same network environment. Check the network status: If there is a network anomaly, check the client's network information; (3) Check the Cobbler server service configuration information to ensure that the server-side cobbler, DHCP, http, and keepalived services are in normal operating condition; (4) Obtain the version information of the operating system or update patch, and obtain a list of all operating system versions that can be deployed and installed, and determine whether the version information has been obtained: If version information is not obtained, check or update the service configuration again; (5) Determine whether the required version information is included based on actual needs: If the required version information is included, an execution command is sent, and execution begins automatically. After execution, the operating system deployment status or patch installation status is checked, and the installation process is complete. (6) After installation, check if the version information matches: If the versions are incompatible, you need to check all the server-side configurations, update the service configuration, and restart the client to select the correct version.

6. An electronic device, characterized in that, include: Memory and at least one processor; The memory stores computer-executed instructions; The at least one processor executes computer execution instructions stored in the memory, causing the at least one processor to perform the batch automatic deployment method of multiple operating systems as described in any one of claims 1 to 3.

7. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by the processor, implement the batch automatic deployment method for multiple operating systems as described in any one of claims 1 to 3.

Images