CN118740616A - Method, device, electronic device and storage medium for deploying server cluster - Google Patents

Abstract

The embodiment of the present invention provides a deployment server cluster, device, electronic device and storage medium. The method deploys a server operating system to a preset number of devices through a preset pre-start execution environment server, and uses the device for deploying the server operating system as a central node server, and then obtains the device information of the central node server, and determines the number of devices that the central node server allows to be deployed simultaneously when deploying the server operating system to the device to be processed according to the device information of the central node server, and then deploys the server operating system to the device to be processed according to the number of devices that the central node server allows to be deployed simultaneously. This avoids the use of a single pre-start execution environment server to provide network startup services and operating system images for server cluster deployment, and the deployment failure caused by network interruption or instability, thereby improving the stability and efficiency of server cluster deployment.

Description

Method, device, electronic device and storage medium for deploying server cluster

Technical Field

The present invention relates to the field of server technology, and in particular to a method, device, electronic device and storage medium for deploying a server cluster.

Background Art

PXE (Preboot Execution Environment) is a network boot technology that allows a computer to load an operating system from a remote server over the network instead of booting from a local hard disk. PXE is often used to deploy operating systems on a large scale, especially in an enterprise environment, and can greatly simplify the deployment process of new computers or reinstalled systems.

When the existing technology uses PXE to deploy a server cluster, there is only one PXE server to provide network boot services and operating system images. When there are a large number of clients in the network or the network bandwidth is limited, any network interruption or instability may cause deployment failure. This method of deploying a server cluster is not stable and reliable enough.

Summary of the invention

In view of the above problems, embodiments of the present invention are proposed to provide a method, device, electronic device and storage medium for deploying a server cluster that overcome the above problems or at least partially solve the above problems.

In order to solve the above problem, an embodiment of the present invention discloses a method for deploying a server cluster, the method comprising:

Deploy a server operating system to a preset number of devices through a preset pre-start execution environment server, and use the devices where the server operating system is deployed as central node servers;

Obtaining device information of the central node server;

Determine, according to the device information of the central node server, the number of devices that the central node server is allowed to deploy simultaneously when deploying the server operating system on the processed device;

According to the number of devices that the central node server allows to be deployed simultaneously, a server operating system is deployed on the device to be processed.

Optionally, the preset pre-boot execution environment server includes a container image, and the container image includes the server operating system image; and the deploying the server operating system to a preset number of devices through the preset pre-boot execution environment server includes:

Sending the container image of the preset pre-start execution environment server to the preset number of devices respectively;

The container images in the preset number of devices are started, and the server operating system is deployed on the preset number of devices.

Optionally, the device information of the central node server includes at least one of central processing unit performance, memory size, storage speed, current load or network bandwidth; and determining, based on the device information of the central node server, the number of devices that the central node server is allowed to deploy simultaneously when deploying a server operating system on a device to be processed, includes:

The number of devices that are allowed to be deployed simultaneously when the central node server deploys a server operating system on the processed devices is determined based on at least one of the central processing unit performance, memory size, storage speed, current load or network bandwidth of the central node server.

Optionally, the deploying a server operating system on the device to be processed according to the number of devices that the central node server allows to be deployed simultaneously includes:

Determine the total number of devices that all the central node servers are allowed to deploy simultaneously;

Comparing the number of the devices to be processed with the total number;

When the number of the devices to be processed is equal to the total number, deploying a server operating system on the devices to be processed through all the central node servers;

When the number of the devices to be processed is less than the total number, determining a target central node server according to the number of devices that each central node server allows to be deployed simultaneously, and deploying a server operating system to the devices to be processed through the target central node server;

When the number of the devices to be processed is greater than the total number, each of the central node servers simultaneously deploys the server operating system to the corresponding number of devices to be processed according to the number of devices that each of the central node servers is allowed to deploy simultaneously; and whenever the central node server completes the operation of deploying the server operating system to the devices to be processed, the devices to be processed that the central node server needs to process are determined from the remaining devices to be processed, and the server operating system is deployed to the devices to be processed that need to be processed.

Optionally, the central node server and the device to be processed are configured with service discovery, and the deploying of a server operating system to the device to be processed through all the central node servers includes:

For each of the devices to be processed, determining the central node server closest to the device to be processed;

A server operating system is deployed on the device to be processed through the central node server that is closest to the device to be processed.

Optionally, the deploying a server operating system on the device to be processed through the central node server that is closest to the device to be processed includes:

Obtaining a container image from the central node server closest to the device to be processed, and storing it in the device to be processed;

Start the container image in the device to be processed, and deploy a server operating system on the device to be processed.

Optionally, starting the container image in the device to be processed includes:

Obtaining a preset startup script for starting the container image in the device to be processed;

Run the preset startup script to start the container image in the device to be processed.

Accordingly, an embodiment of the present invention discloses a device for deploying a server cluster, the device comprising:

A central node server deployment module, used to deploy a server operating system to a preset number of devices through a preset pre-start execution environment server, and use the devices on which the server operating system is deployed as central node servers;

A device information acquisition module, used to acquire device information of the central node server;

A determination module, configured to determine, based on the device information of the central node server, the number of devices that the central node server is allowed to deploy simultaneously when deploying a server operating system on a device to be processed;

The device deployment module to be processed is used to deploy a server operating system to the device to be processed according to the number of devices that the central node server allows to be deployed simultaneously.

Optionally, the preset pre-start execution environment server includes a container image, and the container image includes the server operating system image; the central node server deployment module includes:

A sending submodule, used for sending the container image of the preset pre-start execution environment server to the preset number of devices respectively;

The startup submodule is used to start the container images in the preset number of devices and deploy the server operating system to the preset number of devices.

Optionally, the device information of the central node server includes at least one of central processing unit performance, memory size, storage speed, current load or network bandwidth; and the determination module includes:

The determination submodule is used to determine the number of devices allowed to be deployed simultaneously when the central node server deploys a server operating system on the processed device based on at least one of the central processing unit performance, memory size, storage speed, current load or network bandwidth of the central node server.

Optionally, the to-be-processed device deployment module includes:

A total number determination submodule, used to determine the total number of devices that all the central node servers are allowed to deploy simultaneously;

A comparison submodule, used for comparing the number of the devices to be processed with the total number;

A first comparison result submodule is used to deploy a server operating system to the devices to be processed through all the central node servers when the number of the devices to be processed is equal to the total number;

A second comparison result submodule is used to determine a target central node server according to the number of devices that each central node server allows to be deployed simultaneously when the number of the devices to be processed is less than the total number, and deploy a server operating system to the devices to be processed through the target central node server;

The third comparison result submodule is used to, when the number of the devices to be processed is greater than the total number, enable each of the central node servers to simultaneously deploy the server operating system to a corresponding number of devices to be processed according to the number of devices that each of the central node servers is allowed to deploy simultaneously; and whenever the central node server completes the operation of deploying the server operating system to the devices to be processed, determine the devices to be processed that the central node server needs to process from the remaining devices to be processed and deploy the server operating system to the devices to be processed.

Optionally, the central node server and the device to be processed are configured with service discovery, and the first comparison result submodule includes:

A distance determination unit, used for determining, for each of the devices to be processed, a central node server closest to the device to be processed;

The deployment unit is used to deploy a server operating system to the device to be processed through the central node server closest to the device to be processed.

Optionally, the deployment unit includes:

A container image acquisition subunit, configured to acquire a container image from a central node server closest to the device to be processed, and store the container image in the device to be processed;

The startup subunit is used to start the container image in the device to be processed and deploy a server operating system to the device to be processed.

Optionally, the promoter unit is specifically used for:

Obtaining a preset startup script for starting the container image in the device to be processed;

Run the preset startup script to start the container image in the device to be processed.

Correspondingly, an embodiment of the present invention discloses an electronic device, comprising: a processor, a memory, and a computer program stored in the memory and capable of running on the processor, wherein the computer program implements the various steps of the above-mentioned model training method embodiment when executed by the processor.

Correspondingly, an embodiment of the present invention discloses a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the various steps of the above-mentioned model training method embodiment are implemented.

The embodiments of the present invention include the following advantages:

A method for deploying a server cluster provided by an embodiment of the present invention deploys a server operating system to a preset number of devices through a preset pre-start execution environment server, and uses the device on which the server operating system is deployed as a central node server, then obtains device information of the central node server, determines the number of devices that the central node server allows to be deployed simultaneously when deploying the server operating system to the device to be processed based on the device information of the central node server, and then deploys the server operating system to the device to be processed based on the number of devices that the central node server allows to be deployed simultaneously. After deploying a preset number of central node servers, the embodiment of the present invention deploys the server operating system to the device to be processed through a preset number of central node servers, thereby avoiding the use of a single pre-start execution environment server to provide network startup services and operating system images for server cluster deployment, which causes deployment failures when the network is interrupted or unstable, thereby improving the stability and efficiency of server cluster deployment.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a flow chart of steps of a method for deploying a server cluster according to an embodiment of the present invention;

FIG2 is a structural block diagram of an apparatus for deploying a server cluster according to an embodiment of the present invention;

FIG3 is a block diagram of an electronic device according to an embodiment of the present invention;

FIG. 4 is a structural block diagram of a computer-readable storage medium according to an embodiment of the present invention.

DETAILED DESCRIPTION

In order to make the above-mentioned objects, features and advantages of the present invention more obvious and easy to understand, the present invention is further described in detail below with reference to the accompanying drawings and specific embodiments.

In actual applications, when the existing technology uses PXE to deploy a server cluster, there is only one PXE server to provide network boot services and operating system images. When there are a large number of clients in the network or the network bandwidth is limited, any network interruption or instability may cause deployment failure. This method of deploying a server cluster is not stable and reliable enough.

One of the core concepts of an embodiment of the present invention is that after deploying a preset number of central node servers, the embodiment of the present invention deploys a server operating system on the processing device through a preset number of central node servers, thereby avoiding the use of a single pre-boot execution environment server to provide network boot services and operating system images for server cluster deployment, and the deployment failure caused by network interruption or instability, thereby improving the stability and efficiency of server cluster deployment.

1 , a flow chart of the steps of a method for deploying a server cluster according to an embodiment of the present invention is shown, which may specifically include the following steps:

Step 101, deploying a server operating system to a preset number of devices through a preset pre-start execution environment server, and using the devices on which the server operating system is deployed as central node servers.

Specifically, using PXE technology to deploy an operating system is an efficient network boot solution that allows a computer to start and install an operating system through a network interface card. The process of using PXE technology to deploy an operating system is as follows:

1. Environment preparation: Before batch deployment of Linux systems, you need to ensure that the network environment meets the requirements. All target machines must be connected to the local area network (LAN), and the network configuration should allow DHCP (Dynamic Host Configuration Protocol) and TFTP (Trivial File Transfer Protocol) communications. This means that network switches and routers need to be correctly set up to allow data packets for these services to pass through. At the same time, you need to prepare one or more servers to run DHCP, TFTP, and HTTP (Hypertext Transfer Protocol)/FTP (File Transfer Protocol) services.

2. Install and configure the DHCP server: The DHCP server is a key component of the PXE network boot process. It is responsible for assigning IP addresses to computers on the network. After installing the DHCP server software, you need to create a new scope that will contain the IP address pool for the PXE client. In addition, you need to configure the DHCP options to specify the IP address of the TFTP server and the name of the PXE boot file so that the client can find and download the boot file.

3. Install and configure the TFTP server: The TFTP server is used to transfer the PXE boot file during the network boot process. Install the TFTP server software and set the TFTP root directory, which is the location on the TFTP server where the PXE boot file is stored. Make sure this directory is accessible to the DHCP server. Then, upload the PXE boot file (such as undivided.kpxe) to the TFTP root directory.

4. Install and configure HTTP/FTP server: HTTP/FTP server is used to store Linux installation images and PXE boot scripts. Install the corresponding server software and set up a shared directory to store the operating system installation media. Upload the operating system installation image file to this directory so that the PXE boot script can download the required installation files from here.

5. Create a PXE boot script: The PXE boot script is a configuration file that instructs the PXE client on how to boot and install the operating system. Use a text editor to create a boot script, such as the pxelinux.cfg/default file, which should contain the HTTP/FTP URL pointing to the Linux kernel and the initial ramdisk (memory disk), as well as any installation parameters that need to be passed to the kernel. After creation, upload this script to the installation directory of the HTTP/FTP server.

6. Configure BIOS (Basic Input/Output System)/UEFI (Unified Extensible Firmware Interface) settings: On the target machine, enter the BIOS/UEFI settings interface and set the network interface card as the preferred boot device. In this way, when the computer starts, it will first try to boot through the network interface card instead of relying on local storage devices.

7. Boot and deploy: After completing the configuration in the BIOS/UEFI settings, reboot the target machines. They will boot over the network, obtain IP addresses from the DHCP server, download PXE boot files from the TFTP server, and finally load the Linux installer from the HTTP/FTP server.

8. Customization and Automation: To achieve unattended automatic installation, you can create automated installation scripts, such as Kickstart files, which automatically complete the installation and configuration of the operating system. At the same time, adjust the PXE startup script and DHCP settings according to the hardware configuration and network environment to ensure a smooth installation process.

9. Security and maintenance: Ensure that all servers use strong passwords and only open corresponding services to trusted clients. Regularly check and update the firmware of BIOS/UEFI and network interface cards to take advantage of the latest security fixes and performance improvements.

10. Monitoring and logging: Configure the server to log all relevant activities during the PXE deployment process. Use network monitoring tools to track the status of the PXE deployment to ensure that all clients can successfully start and install.

11. Verification and testing: Before the official promotion, test the PXE boot and installation process on one or several target machines to ensure that everything works as expected. After the test is successful, gradually promote PXE boot and installation to all target machines.

The above process of using PXE technology to deploy the operating system has the following problems:

Network dependency: PXE deployment requires extremely high network stability because it relies on the network to transfer boot files and operating system images. Any network interruption or instability may cause deployment failure, especially in large-scale deployment, the management of network traffic becomes particularly important. DHCP service compatibility: The DHCP service is responsible for allocating necessary network parameters to the PXE client, including informing the client of the location of the TFTP server. Differences in the configuration of different DHCP servers may cause the PXE client to be unable to obtain the correct boot file path, thus hindering the deployment process. Boot file size limit: PXE transfers boot files through TFTP, and the TFTP protocol has a limit on the size of the transferred file. This means that large operating system images may need to be split or compressed to fit the limitations of network transmission, which increases the complexity of deployment. Security issues: The TFTP protocol does not support data encryption, which makes PXE deployment risky in terms of security. Unencrypted transmission may lead to the leakage of sensitive data, or malicious tampering of boot files, posing a threat to the security of the system. Hardware compatibility: PXE boot requires the network interface card (NIC) to support network boot, but not all hardware provides this function. In addition, different hardware may require specific driver or firmware support, limiting the versatility of PXE deployment. System complexity: PXE deployment involves multiple components, including DHCP, TFTP, HTTP/FTP servers, and BIOS/UEFI settings on the client. These components need to be precisely configured, and misconfiguration of any component may cause the entire deployment process to fail. Maintenance and upgrades: With updates to the operating system and PXE-related software, maintenance and upgrades become necessary. This requires IT administrators to continuously update the PXE environment to ensure the continued effectiveness of the deployment process. Performance bottlenecks: In large-scale deployments, the computing power and network bandwidth of the server may become limiting factors. A large number of PXE clients requesting data at the same time may cause the server to respond slowly, affecting the deployment speed. Error handling and recovery: Errors during the PXE deployment process may be difficult to diagnose, such as the TFTP server being inaccessible or the boot file being damaged. The recovery process may require manual configuration checks, file replacements, or service restarts. Environmental adaptability: PXE deployment needs to adapt to different network environments and hardware configurations. When deployed in different physical locations or network architectures, specific adjustments may be required, such as VLAN settings or different network protocol support. Cross-platform support: PXE deployment needs to work on different hardware and operating system platforms, which may require different boot files and configurations to be prepared for different platforms, increasing the complexity of deployment. User intervention: In some cases, automated PXE deployment may not be able to handle all situations, such as driver issues for specific hardware or custom operating system requirements, which may require manual intervention by the administrator. Hardware failure and replacement: Hardware failure may cause PXE deployment to be interrupted, and after replacing the hardware, the PXE environment may need to be reconfigured to ensure that the new hardware can be successfully started, which increases maintenance costs. Data integrity verification: During the PXE deployment process, it is necessary to ensure that the transmitted data has not been tampered with. The lack of a data integrity verification mechanism may result in deployment failure or the startup of an unsafe system, and additional mechanisms are required to ensure the accuracy of the data. Integration of software stacks: PXE deployment needs to be integrated with existing system management tools and software stacks, such as configuration management tools, monitoring systems, etc. This may require the development of customized integration scripts or the use of third-party solutions, increasing the complexity of deployment.

The embodiment of the present invention deploys the server operating system to a preset number of devices through a preset pre-boot execution environment server, that is, a preset PXE server, and uses the device on which the server operating system is deployed as a central node server. For example, the preset number can be 10. Through 1 preset PXE server, the server operating system is deployed to 10 devices, and 10 deployed servers are obtained, and these 10 deployed servers are used as central servers. Of course, the preset number can be set according to actual needs in actual applications, and the embodiment of the present invention does not limit this.

Step 102: Obtain device information of the central node server.

Exemplarily, if the number of central node servers is 10, the device information of the 10 central node servers is obtained.

Step 103: Determine, based on the device information of the central node server, the number of devices that the central node server is allowed to deploy simultaneously when deploying the server operating system on the devices to be processed.

Specifically, if the number of central node servers is 10, the number of devices allowed to be deployed simultaneously when each central node server deploys the server operating system on the processing device is determined based on the device information of these 10 central node servers. The number of devices allowed to be deployed simultaneously is that the number of devices that are suitable for simultaneous deployment when the central node server has optimal performance. Of course, the number of devices that are suitable for simultaneous deployment when the central node server has optimal performance is less than the maximum number of devices that can be deployed simultaneously by the central node server. For example, the maximum number of devices that can be deployed simultaneously by the central node server A is 200, and the number of devices that are suitable for simultaneous deployment when the processing performance is optimal is 15.

Step 104: deploy a server operating system to the device to be processed according to the number of devices that the central node server allows to be deployed simultaneously.

Specifically, after determining the number of devices that each central node server allows to be deployed simultaneously, the server operating system is deployed on the device to be processed through the central node server according to the number of devices that each central node server allows to be deployed simultaneously.

A method for deploying a server cluster provided by an embodiment of the present invention deploys a server operating system to a preset number of devices through a preset pre-start execution environment server, and uses the device on which the server operating system is deployed as a central node server, then obtains device information of the central node server, determines the number of devices that the central node server allows to be deployed simultaneously when deploying the server operating system to the device to be processed based on the device information of the central node server, and then deploys the server operating system to the device to be processed based on the number of devices that the central node server allows to be deployed simultaneously. After deploying a preset number of central node servers, the embodiment of the present invention deploys the server operating system to the device to be processed through a preset number of central node servers, thereby avoiding the use of a single pre-start execution environment server to provide network startup services and operating system images for server cluster deployment, which causes deployment failures when the network is interrupted or unstable, thereby improving the stability and efficiency of server cluster deployment.

In an embodiment of the present invention, the preset pre-boot execution environment server includes a container image, and the container image includes the server operating system image; the step 101 deploys the server operating system to a preset number of devices through the preset pre-boot execution environment server, which may specifically include the following sub-steps:

Sub-step S11: sending the container image of the preset pre-start execution environment server to the preset number of devices respectively.

Specifically, a basic image of a server operating system is selected, such as an official Ubuntu, CentOS or Debian image. The basic image can be selected according to actual conditions, and the embodiment of the present invention does not limit this.

After determining the base image of the server operating system, write a Dockerfile. By writing a Dockerfile to customize the Docker image of the Linux installer, the Dockerfile will contain all the necessary commands to install the system, configure the network, and install the required software. Dockerfile is a text file that contains a series of instructions and parameters for automatically building Docker container images. Through Dockerfile, developers can define the base operating system of the container image, installed software, environment variables, working directory, exposed ports, commands to be executed when the container is started, etc.

The following is a sample code of a Dockerfile:

#Use the official Ubuntu base image

FROM ubuntu:20.04

#Set maintainer information

LABEL maintainer="yourname@example.com"

#Install necessary packages

RUN apt-get update&&\

apt-get install-y openssh-server curl

#Configure SSH service

RUN mkdir /var/run/sshd

RUN echo'root:password'|chpasswd

RUN sed-i's/#PermitRootLogin prohibit-password/PermitRootLogin yes/'/etc/ssh/sshd_config

#SSH login does not perform strict key checking, which makes it easier to copy files

RUN sed-i's/#StrictHostKeyChecking ask/StrictHostKeyChecking no/'/etc/ssh/ssh_config

#Open SSH port

EXPOSE 22

#Start SSH service

CMD["/usr/sbin/sshd","-D"]

After writing the Dockerfile, build a customized container image through the Dockerfile and push it to the local image repository so that other nodes can pull and use it. Configure the image repository and ensure that all deployment nodes have access rights. The image repository (Docker Registry) is a service for storing and distributing Docker images. It allows users to upload (push) and download (pull) Docker images for deployment and running on different machines or environments.

After building the container image, write a deployment script, use the deployment script to start the Docker container, and configure necessary parameters, such as network settings, storage volumes, etc.

The following is a sample code for running the deployment script:

#!/bin/bash

docker run-d --name linux-installer --privileged\

-v/path/to/ssh_keys:/root/.ssh\

-v/path/to/install/scripts:/install_scripts\

my-linux-installer

In an embodiment of the present invention, the preset pre-start execution environment server includes a container image, which is the container image built by Dockerfile in the above steps, and the container image includes a server operating system image. The container image of the preset pre-start execution environment server is sent to a preset number of devices respectively.

Sub-step S12, starting the container images in the preset number of devices, and deploying the server operating system on the preset number of devices.

Specifically, the deployment script in the preset pre-start execution environment server is obtained, and the container images in the preset number of devices are started through the deployment script, and the server operating system is deployed to the preset number of devices. These containers will run as lightweight Linux installers. Automatic discovery between nodes is achieved by using Docker's built-in service discovery mechanism or in combination with additional tools (such as etcd or Consul), laying the foundation for subsequent P2P (Peer-to-Peer, peer-to-peer) deployment.

By deploying server operating systems through container images, communication between containers can be carried out through encrypted channels, which enhances the security of data transmission. In addition, container images can run on a variety of hardware, reducing dependence on specific hardware. Moreover, containerization simplifies the deployment process, reduces system complexity, and makes deployment and management more intuitive. In addition, containerized deployment facilitates maintenance and upgrades, and container images can be directly replaced without complex system updates.

In an embodiment of the present invention, the device information of the central node server includes at least one of central processing unit performance, memory size, storage speed, current load or network bandwidth; step 103 determines the number of devices that the central node server allows to be deployed simultaneously when deploying a server operating system on a device to be processed according to the device information of the central node server, which may specifically include the following steps:

The number of devices that are allowed to be deployed simultaneously when the central node server deploys a server operating system on the processed devices is determined based on at least one of the central processing unit performance, memory size, storage speed, current load or network bandwidth of the central node server.

Specifically, based on the central processing unit performance, memory size, storage speed, current load or network bandwidth of each central node server, the number of devices allowed to be deployed simultaneously when each central node server deploys the server operating system on the processing device is determined. For example, a central node server with good central processing unit performance, large memory and low load allows more devices to be deployed simultaneously when the server operating system is deployed on the processing device. The number of devices allowed to be deployed simultaneously when the central node server deploys the server operating system on the processing device can also be regarded as the weight of the central node server, and the weight is the number of devices allowed to be deployed simultaneously.

By determining the number of devices allowed to be deployed simultaneously on each central node server through at least one of the central processor performance, memory size, storage speed, current load or network bandwidth of each central node server, each central node server can be reasonably utilized for deployment with higher efficiency.

In the embodiment of the present invention, the step 104 deploys the server operating system on the device to be processed according to the number of devices that the central node server allows to be deployed simultaneously, including:

Sub-step S21, determining the total number of devices that are allowed to be deployed simultaneously on all the central node servers.

Specifically, the following is a sample code for the number of devices that the central node server allows to be deployed simultaneously:

#Assume there are 10 nodes, and their performance weights are as follows:

nodes=['Node1','Node2','Node3','Node4','Node5','Node6','Node7','Node8','Node9','Node10']

weights = [10,1,1,1,1,1,9,1,1,1] # Example weights, the actual situation will be more complicated

Exemplarily, the number of central node servers is 10, and the number of devices that can be deployed simultaneously on all the central node servers is 10+1+1+1+1+1+9+1+1+1=27.

Sub-step S22, comparing the number of the devices to be processed with the total number.

Specifically, the number of pending devices, that is, the number of devices that need to deploy servers, is compared with the total number.

Sub-step S23, when the number of the devices to be processed is equal to the total number, deploying a server operating system to the devices to be processed through all the central node servers.

Specifically, continuing with the previous example, if the number of devices to be processed is 27, then the total number of devices that all central node servers allow to be deployed simultaneously is the same as the number of devices to be processed, allowing 10 central nodes to be deployed simultaneously according to the number of devices allowed to be deployed simultaneously.

Sub-step S24, when the number of the devices to be processed is less than the total number, determine the target central node server according to the number of devices allowed to be deployed simultaneously by each central node server, and deploy the server operating system to the devices to be processed through the target central node server.

Continuing with the previous example, if the number of devices to be processed is 19, then the total number of devices allowed to be deployed simultaneously by all central node servers is greater than the number of devices to be processed. The two central node servers with the highest number of devices allowed to be deployed simultaneously are selected. One of these two central node servers allows 10 devices to be deployed simultaneously, and the other allows 9 devices to be deployed simultaneously. Using these two central node servers, the number of devices to be deployed that can be processed is 19. These two central node servers are determined as the target central node servers, and the server operating system is deployed on the devices to be processed through the target central node servers.

Sub-step S25, when the number of the devices to be processed is greater than the total number, based on the number of devices that each of the central node servers is allowed to deploy simultaneously, each of the central node servers simultaneously deploys the server operating system to the corresponding number of devices to be processed; and whenever the central node server completes the operation of deploying the server operating system to the devices to be processed, the devices to be processed that the central node server needs to process are determined from the remaining devices to be processed and the server operating system is deployed to the devices to be processed that need to be processed.

Specifically, if the number of devices to be processed is 40, then the total number of devices that all central node servers are allowed to deploy simultaneously is less than the number of devices to be processed. According to the number of devices that each central node server is allowed to deploy simultaneously, each central node server deploys the server operating system to the corresponding number of devices to be processed at the same time, that is, 10 central nodes can deploy 27 at the same time. Whenever the central node server completes the operation of deploying the server operating system on the devices to be processed, the central node server determines the devices to be processed that need to be processed from the remaining devices to be processed, and deploys the server operating system to the devices to be processed. For example, after the central node server that allows 10 devices to be deployed simultaneously completes the deployment of 2 devices to be processed, 2 devices to be processed are allocated to this central node server from the remaining devices to be processed.

For example, container orchestration tools such as Docker Swarm or Kubernetes can be used to automatically distribute deployment tasks to different nodes to achieve load balancing and avoid overloading of a single node. By dynamically allocating devices to be processed through the central node server, load balancing can be achieved, overloading of a single node can be avoided, and efficiency and stability can be improved.

In the embodiment of the present invention, the central node server and the device to be processed are configured with service discovery, and the server operating system is deployed on the device to be processed through all the central node servers, including:

For each of the devices to be processed, determine the central node server closest to the device to be processed.

A server operating system is deployed on the device to be processed through the central node server that is closest to the device to be processed.

Specifically, after the central node server is deployed, each central node server is configured as a micro deployment center that can independently provide Docker images of the Linux operating system to other new nodes. Each node is configured with a service discovery mechanism, such as etcd or Consul, so that the deployed nodes can automatically discover each other.

The following is a sample code for configuring service discovery:

1. Install the service discovery tool

2. Install etcd or Consul on all deployment nodes. Taking Consul as an example, you can download and install it through the package manager or directly from the official website.

3.

4.#Install Consul using apt-get (for Debian/Ubuntu systems)

5.sudo apt-get update

6.sudo apt-get install consul

7.

8.#Or use yum to install Consul (applicable to CentOS/RHEL system)

9.sudo yuminstall consul

10. Configure service discovery tools

11.Configure etcd or Consul, which usually involves setting up one or more server nodes as a cluster, and configuring client nodes.

12.

13. Server node configuration:

14. On the server node, configure etcd or Consul to start the service and join the cluster. For example, for Consul, you can use the following command to start the agent and join the cluster:

15.consul agent-server-bootstrap-expect=3-data-dir="/tmp/consul"-node=server-1-bind=127.0.0.1

16. Client node configuration:

17. On the client node, configure etcd or Consul to join the cluster and use the service. For example, for Consul, you can start the client agent with the following command:

18.consul agent-client 0.0.0.0-data-dir="/tmp/consul"-node=client-1-bind=127.0.0.1

19. Registration Services

20. Deployed nodes need to register their services in the service discovery tool. This is usually done through an API or configuration file.

twenty one.

22.API Registration:

23. Use the API provided by etcd or Consul to register the service. For example, use Consul's HTTP API to register a service named my-service:

24.curl-X PUT--data'{"service":{"name":"my-service","tags":["tag1","tag2"],"address":"10.1.2.3", "port":8080}}'http://127.0.0.1:8500/v1/agent/service/register

25. Profile Registration:

26. Define the service in the Consul configuration file and start Consul to automatically register the service.

27. Discovery Service

28. Deployment nodes can query the location and status of other services through service discovery tools.

29.

30. Health Check:

31.

32. Service discovery tools can perform health checks on registered services to ensure that only healthy service instances are returned to requesters.

33. Service Inquiry:

34.

35. Deployment nodes can query available service instances by service name. For example, use Consul's DNS or HTTP API to query my-service:

36.dig@127.0.0.1-p 8600my-service.node.consul

37.

38.#Or use HTTP API

39.curl http://127.0.0.1:8500/v1/health/service/my-service

Specifically, for each device to be processed, determine the central node server closest to the device to be processed, and deploy the server operating system to the device to be processed through the central node server closest to the device to be processed. The device node to be processed can automatically connect to the nearest deployment central node through service discovery.

Assign a central node server to each device to be processed, using a combination of a DHCP server and a load balancer. The DHCP server is responsible for allocating IP addresses and providing the location information of the PXE boot file. Load balancing reduces the performance pressure of a single node and improves the overall deployment performance.

The following is the sample code:

1. Configure the DHCP server: In the DHCP server configuration, specify the IP address of the load balancer as the address of the PXE boot server.

2.DHCP server configuration example:

3.next-server 10.0.0.100; #IP address of the load balancer

4.filename "/pxelinux.0"; #PXE boot file

Through the service discovery mechanism, deployment nodes can automatically discover each other. This self-expanding deployment based on the P2P (peer-to-peer) mechanism avoids the use of a single pre-boot execution environment server to provide network boot services and operating system images for server cluster deployment, which may cause deployment failures when the network is interrupted or unstable, thereby improving the stability and efficiency of server cluster deployment.

In the embodiment of the present invention, the deploying a server operating system on the device to be processed through the central node server closest to the device to be processed includes:

Obtaining a container image from the central node server closest to the device to be processed, and storing it in the device to be processed;

Start the container image in the device to be processed, and deploy a server operating system on the device to be processed.

Specifically, after the device to be processed is connected to the nearest central node server, the central node server deploys the device to be processed as a PXE server, obtains the container image from the central node server closest to the device to be processed, and stores the container image to the device to be processed, and then starts the container image in the device to be processed to deploy the server operating system to the device to be processed.

By obtaining the container image from the central node server, it is possible to avoid using a single pre-start execution environment server to provide the operating system image for server cluster deployment, which may cause deployment failures when the network is interrupted or unstable, thereby improving the stability and efficiency of server cluster deployment.

In an embodiment of the present invention, starting the container image in the device to be processed includes:

Obtaining a preset startup script for starting the container image in the device to be processed;

Run the preset startup script to start the container image in the device to be processed.

Specifically, the preset startup script is obtained from the central node server closest to the device to be processed. The preset startup script is also the deployment script. By running the preset startup script, the container image in the device to be processed is started. By obtaining the startup script from the central node server, the deployment failure caused by network interruption or instability caused by using a single pre-start execution environment server to provide network startup services is avoided, thereby improving the stability and efficiency of server cluster deployment.

In another implementation, deploying a server operating system on the devices to be processed by the central node server also includes: after the central node server deploys a preset number of devices to be processed, determining that the preset number of devices to be processed are newly added central node servers, and deploying a server operating system on the devices to be processed by the central node server and the newly added central node server. In this way, increasing the number of central node servers can improve deployment efficiency.

The decentralized deployment method of the embodiment of the present invention is different from the traditional PXE deployment method that relies on a central server. The present invention adopts a decentralized P2P mechanism to realize the deployment of the software stack through automatic discovery and communication between nodes. Weight-based node selection collects node attributes (such as CPU performance, memory size, etc.) and assigns weights to nodes according to these attributes to select the most suitable node for deployment. This method improves the efficiency and reliability of deployment. Application of Docker containerization technology: By using Docker containerization technology, the present invention can create a lightweight Linux installer, simplify the deployment process, and make the deployed system more flexible and portable. Service discovery and load balancing: Combining service discovery tools (such as etcd or Consul) and container orchestration tools (such as Docker Swarm or Kubernetes), the present invention realizes automatic registration, health check, and load balancing of services, further improving the stability and scalability of the system.

It should be noted that, for the sake of simplicity, the method embodiments are described as a series of action combinations, but those skilled in the art should be aware that the embodiments of the present invention are not limited by the described action sequence, because according to the embodiments of the present invention, certain steps can be performed in other sequences or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions involved are not necessarily required by the embodiments of the present invention.

2, a structural block diagram of a device for deploying a server cluster according to an embodiment of the present invention is shown. The device may specifically include the following modules:

The central node server deployment module 201 is used to deploy the server operating system to a preset number of devices through a preset pre-start execution environment server, and use the devices where the server operating system is deployed as central node servers;

The device information acquisition module 202 is used to acquire the device information of the central node server;

A determination module 203 is used to determine, according to the device information of the central node server, the number of devices that the central node server is allowed to deploy simultaneously when deploying a server operating system on the device to be processed;

The to-be-processed device deployment module 204 is used to deploy a server operating system to the to-be-processed device according to the number of devices that the central node server allows to be deployed simultaneously.

The device of the embodiment of the present invention deploys the server operating system to a preset number of devices through a preset pre-start execution environment server, and uses the device on which the server operating system is deployed as a central node server, then obtains the device information of the central node server, determines the number of devices that the central node server allows to be deployed simultaneously when deploying the server operating system to the device to be processed according to the device information of the central node server, and then deploys the server operating system to the device to be processed according to the number of devices that the central node server allows to be deployed simultaneously. After deploying a preset number of central node servers, the server operating system is deployed to the device to be processed through the preset number of central node servers, thereby avoiding the use of a single pre-start execution environment server to provide network startup services and operating system images for server cluster deployment, which causes deployment failures when the network is interrupted or unstable, thereby improving the stability and efficiency of server cluster deployment.

In an embodiment of the present invention, the preset pre-start execution environment server includes a container image, and the container image includes the server operating system image; the central node server deployment module includes:

A sending submodule, used for sending the container image of the preset pre-start execution environment server to the preset number of devices respectively;

The startup submodule is used to start the container images in the preset number of devices and deploy the server operating system to the preset number of devices.

In an embodiment of the present invention, the device information of the central node server includes at least one of central processing unit performance, memory size, storage speed, current load or network bandwidth; the determination module includes:

The determination submodule is used to determine the number of devices allowed to be deployed simultaneously when the central node server deploys a server operating system on the processed device based on at least one of the central processing unit performance, memory size, storage speed, current load or network bandwidth of the central node server.

In an embodiment of the present invention, the to-be-processed device deployment module includes:

A total number determination submodule, used to determine the total number of devices that all the central node servers are allowed to deploy simultaneously;

A comparison submodule, used for comparing the number of the devices to be processed with the total number;

A first comparison result submodule is used to deploy a server operating system to the devices to be processed through all the central node servers when the number of the devices to be processed is equal to the total number;

A second comparison result submodule is used to determine a target central node server according to the number of devices that each central node server allows to be deployed simultaneously when the number of the devices to be processed is less than the total number, and deploy a server operating system to the devices to be processed through the target central node server;

The third comparison result submodule is used to, when the number of the devices to be processed is greater than the total number, enable each of the central node servers to simultaneously deploy the server operating system to a corresponding number of devices to be processed according to the number of devices that each of the central node servers is allowed to deploy simultaneously; and whenever the central node server completes the operation of deploying the server operating system to the devices to be processed, determine the devices to be processed that the central node server needs to process from the remaining devices to be processed and deploy the server operating system to the devices to be processed.

In the embodiment of the present invention, the central node server and the device to be processed are configured with service discovery, and the first comparison result submodule includes:

A distance determination unit, used for determining, for each of the devices to be processed, a central node server closest to the device to be processed;

The deployment unit is used to deploy a server operating system to the device to be processed through the central node server closest to the device to be processed.

In an embodiment of the present invention, the deployment unit includes:

A container image acquisition subunit, configured to acquire a container image from a central node server closest to the device to be processed, and store the container image in the device to be processed;

The startup subunit is used to start the container image in the device to be processed and deploy a server operating system to the device to be processed.

In an embodiment of the present invention, the promoter unit is specifically used for:

Obtaining a preset startup script for starting the container image in the device to be processed;

Run the preset startup script to start the container image in the device to be processed.

As for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

3, an electronic device according to an embodiment of the present invention is shown, comprising:

It includes a processor, a memory, and a computer program stored in the memory and capable of running on the processor. When the computer program is executed by the processor, the various processes of the above-mentioned model training method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

Referring to Figure 4, a computer-readable storage medium of an embodiment of the present invention is shown. A computer program is stored on the computer-readable storage medium. When the computer program is executed by the processor, the various processes of the above-mentioned model training method embodiment are implemented and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referenced to each other.

Those skilled in the art will appreciate that the embodiments of the embodiments of the present invention may be provided as methods, devices, or computer program products. Therefore, the embodiments of the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the embodiments of the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.

The embodiments of the present invention are described with reference to the flowcharts and/or block diagrams of the methods, terminal devices (systems), and computer program products according to the embodiments of the present invention. It should be understood that each process and/or box in the flowchart and/or block diagram, as well as the combination of the processes and/or boxes in the flowchart and/or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing terminal device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing terminal device generate a device for implementing the functions specified in one process or multiple processes in the flowchart and/or one box or multiple boxes in the block diagram.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing terminal device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device that implements the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.

These computer program instructions can also be loaded onto a computer or other programmable data processing terminal device so that a series of operating steps are executed on the computer or other programmable terminal device to produce computer-implemented processing, so that the instructions executed on the computer or other programmable terminal device provide steps for implementing the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.

Although the preferred embodiments of the present invention have been described, those skilled in the art may make additional changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the embodiments of the present invention.

Finally, it should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or terminal device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or terminal device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or terminal device including the elements.

The above is a detailed introduction to a method, device, electronic device and storage medium for deploying a server cluster provided by the present invention. Specific examples are used in this article to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only used to help understand the method of the present invention and its core idea; at the same time, for general technical personnel in this field, according to the idea of the present invention, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present invention.

Claims (10)

1. A method of deploying a server cluster, the method comprising:

A server operating system is deployed for a preset number of devices through a preset pre-starting execution environment server, and the devices for deploying the server operating system are used as a central node server;

acquiring equipment information of the central node server;

According to the equipment information of the central node server, determining the quantity of equipment which is allowed to be deployed simultaneously when the central node server deploys a server operating system for equipment to be processed;

and deploying a server operating system for the equipment to be processed according to the number of the equipment which is allowed to be deployed simultaneously by the central node server.

2. The method of claim 1, the pre-set pre-boot execution environment server comprising a container image, the container image comprising the server operating system image; the deploying a server operating system for a preset number of devices through a preset pre-start execution environment server comprises:

the container images of the preset pre-starting execution environment server are respectively sent to the preset number of devices;

And starting the container mirror images in the preset number of devices, and deploying a server operating system for the preset number of devices.

3. The method of claim 1, wherein the device information of the central node server includes at least one of central processor performance, memory size, storage speed, current load, or network bandwidth; the determining, according to the device information of the central node server, the number of devices allowed to be deployed simultaneously when the central node server deploys a server operating system for the devices to be processed, includes:

and determining the number of devices which are allowed to be deployed simultaneously when the central node server deploys a server operating system for the devices to be processed according to at least one of the central processor performance, the memory size, the storage speed, the current load or the network bandwidth of the central node server.

4. The method of claim 1, wherein the deploying a server operating system for the device to be processed according to the number of devices that the central node server allows to be deployed simultaneously, comprises:

Determining a total number of the number of devices that all of the central node servers allow to be deployed simultaneously;

Comparing the number of devices to be treated with the total number;

when the number of the to-be-processed devices is equal to the total number, deploying a server operating system for the to-be-processed devices through all the center node servers;

When the number of the to-be-processed devices is smaller than the total number, determining a target center node server according to the number of the devices which are allowed to be deployed simultaneously by the center node servers, and deploying a server operating system for the to-be-processed devices through the target center node server;

When the number of the to-be-processed devices is larger than the total number, according to the number of the devices which are allowed to be deployed simultaneously by each central node server, enabling each central node server to deploy a server operating system for the corresponding number of to-be-processed devices simultaneously; and determining the equipment to be processed required by the central node server from the rest equipment to be processed and deploying the server operating system for the equipment to be processed after the central node server finishes the operation of deploying the server operating system for the equipment to be processed.

5. The method of claim 4, wherein the central node server and the pending devices are configured with service discovery, wherein deploying a server operating system to the pending devices through all of the central node servers comprises:

Determining a center node server nearest to each device to be processed;

And deploying a server operating system for the equipment to be processed through the center node server closest to the equipment to be processed.

6. The method of claim 5, wherein deploying a server operating system to the device to be processed through the closest central node server to the device to be processed comprises:

Obtaining a container mirror image from the center node server closest to the equipment to be processed, and storing the container mirror image to the equipment to be processed;

And starting the container mirror image in the equipment to be processed, and deploying a server operating system for the equipment to be processed.

7. The method of claim 6, wherein said enabling the mirroring of the container in the device to be processed comprises:

acquiring a preset starting script for starting the container mirror image in the equipment to be processed;

And running the preset starting script to start the container mirror image in the equipment to be processed.

8. An apparatus for deploying a server cluster, the apparatus comprising:

the central node server deployment module is used for deploying server operating systems for a preset number of devices through a preset pre-starting execution environment server, and taking the devices deploying the server operating systems as a central node server;

the equipment information acquisition module is used for acquiring the equipment information of the central node server;

the determining module is used for determining the number of the equipment which is allowed to be deployed simultaneously when the central node server deploys a server operating system for the equipment to be processed according to the equipment information of the central node server;

The device to be processed deployment module is used for deploying a server operating system for the device to be processed according to the number of the devices which are allowed to be deployed simultaneously by the central node server.

9. An electronic device, comprising: a processor, a memory and a computer program stored on the memory and capable of running on the processor, which when executed by the processor performs the steps of the method of deploying server clusters according to any one of claims 1-7.

10. A computer readable storage medium, characterized in that it has stored thereon a computer program which, when executed by a processor, implements the steps of the method for deploying server clusters according to any one of claims 1 to 7.