Method and system for realizing high availability of tenant cloud server, central controller

Abstract

The application provides a high availability implementation method and system of a tenant cloud server, and a cloud data center controller. The method comprises the following steps: setting a management network address pool; wherein the management network address pool comprises no less than M management network addresses, and the management network addresses are public network IP addresses; allocating the M management network addresses in the management network address pool to M tenant cloud servers one by one; grouping the M tenant cloud servers into a cluster, and setting cluster configuration information of the cluster, wherein the cluster configuration information comprises a virtual IP address; sending the cluster configuration information to each tenant cloud server in the cluster through the management network address allocated to each tenant cloud server; downloading, by each tenant cloud server, a cluster configuration tool from an external network through the allocated management network address; and joining, by each tenant cloud server, the cluster by using the cluster configuration tool and the cluster configuration information. The application can realize high availability of the tenant cloud server.

Description

Technical Field

[0001] One or more embodiments of the present invention relate to cloud computing, and more particularly to a method and system for achieving high availability of tenant cloud servers and a cloud data center controller. Background Technology

[0002] With the rise of cloud computing technology, data center networks have ushered in their second generation of development: cloud service-driven. Cloud services not only require data centers to support massive data storage and transmission, but also emphasize dynamic resource allocation, flexible expansion, and efficient utilization. Against the backdrop of cloud computing, coupled with the support of big data and AI intelligence, highly available and easy-to-operate service models have become the goals pursued by users.

[0003] The tenant's cloud servers currently operate in standalone mode, thus lacking high availability. If a tenant's cloud server fails, services cannot continue to be provided to the tenant, thereby reducing the availability of the tenant's cloud server. Summary of the Invention

[0004] One or more embodiments of the present invention describe a method and system for achieving high availability of tenant cloud servers, and a cloud data center controller, which can improve the availability of tenant cloud servers.

[0005] Based on the first aspect, a method for implementing high availability of a tenant cloud server is provided, the method comprising:

[0006] Set up a management network address pool; wherein the management network address pool includes no less than M management network addresses, which are public IP addresses; M is a positive integer greater than 1;

[0007] The M management network addresses in the management network address pool are assigned one by one to the M tenant cloud servers;

[0008] The M tenant cloud servers are grouped into a cluster, and the cluster configuration information of the cluster is set, which includes virtual IP addresses;

[0009] The cluster configuration information is sent to each tenant cloud server in the cluster by assigning a management network address to each tenant cloud server in the cluster.

[0010] Each tenant cloud server downloads the cluster configuration tool from the external network through the assigned management network address;

[0011] Each tenant cloud server joins the cluster using the cluster configuration tool and cluster configuration information.

[0012] The cluster configuration information for setting the cluster includes at least one of the following:

[0013] Configure the working mode of the cluster as primary / standby mode; assign a corresponding business role to each tenant cloud server in the cluster; assign a corresponding priority to each tenant cloud server in the cluster; and assign the internal network IP address of each tenant cloud server in the cluster to each tenant cloud server.

[0014] The cluster configuration tool is: keepalive software;

[0015] Each tenant cloud server joins the cluster using cluster configuration tools and cluster configuration information, including:

[0016] Each tenant cloud server installs the keepalive software. After installation, the keepalived.conf file is configured to set the virtual IP address, internal IP address, business role, priority, and working mode. The keepalive software is then started, and the keepalive software initiates the cluster selection of the primary tenant cloud server.

[0017] After each tenant cloud server joins the cluster using the cluster configuration tool and cluster configuration information, the method further includes: reclaiming the management network address allocated to each tenant cloud server in the cluster.

[0018] After setting the cluster configuration information for the cluster, the following is further included:

[0019] For each tenant cloud server in the cluster, an available address pair of the virtual IP address is added to the network interface card (NIC) of the tenant cloud server; the available address pair includes the correspondence between the virtual IP address and the MAC address of the tenant cloud server, so that the NIC of the tenant cloud server can receive packets with the destination address being the virtual IP address.

[0020] According to the second aspect, a cloud data center controller is provided, comprising:

[0021] The management network address pool maintenance module is configured to set up a management network address pool; wherein, the management network address pool includes no less than M management network addresses, which are public IP addresses; M is a positive integer greater than 1;

[0022] The management network address distribution module is configured to distribute the M management network addresses in the management network address pool to the M tenant cloud servers one by one.

[0023] The cloud server cluster building module is configured to group the M tenant cloud servers into a cluster, set the cluster configuration information of the cluster, which includes a virtual IP address; and send the cluster configuration information to each tenant cloud server in the cluster through the management network address assigned to each tenant cloud server in the cluster.

[0024] According to the third aspect, a high availability implementation system for tenant cloud servers is provided. This system includes: a cloud data center controller, a configurator, and M tenant cloud servers, wherein...

[0025] A cloud data center controller is used to set up a management network address pool; wherein the management network address pool includes no less than M management network addresses, which are public IP addresses; M is a positive integer greater than 1; the controller assigns the M management network addresses in the management network address pool to M tenant cloud servers; the controller groups the M tenant cloud servers into a cluster and sets the cluster configuration information of the cluster.

[0026] A configurator is used to send cluster configuration information to each tenant cloud server in the cluster by assigning a management network address to each tenant cloud server in the cluster.

[0027] Each tenant cloud server is used to download the cluster configuration tool from the external network via the assigned management network address; and to join the cluster using the cluster configuration tool and cluster configuration information.

[0028] The configurator is a Java-based configurator that connects to each tenant cloud server via SSH port 22. Based on the type of the tenant cloud server, the configurator sends the commands to install keepalive, the commands to configure the conf file, and the cluster configuration information to the tenant cloud server via the management network address.

[0029] The configurator is a device independent of the cloud data center controller, or the configurator is integrated into the cloud data center controller.

[0030] According to a fourth aspect, a computing device is provided, including a memory and a processor, wherein the memory stores executable code, and the processor executes the executable code to implement the method described in any embodiment of the present invention.

[0031] The high availability implementation method and system for tenant cloud servers and the cloud data center controller provided in the various embodiments of the present invention have at least the following beneficial effects:

[0032] 1. Automated establishment of highly available clusters for tenant services based on cloud data center controller.

[0033] 2. By introducing a management network address pool, the cloud data center controller was able to control the tenant's cloud server.

[0034] 3. The cloud data center controller's configurator can use the JAVA architecture to issue Linux commands to the cloud server.

[0035] 4. Establish a high-availability cluster through virtual IP technology and keepalive.

[0036] 5. By leveraging the virtual IP function of the cloud data center controller in conjunction with the management network address pool, the cloud data center controller can control tenant cloud servers, automatically configuring and deploying highly available clusters for tenant cloud servers. This improves the stability and resilience of tenant services, enhances their reliability and high availability, and provides users with a simpler and more reliable cloud data center experience.

[0037] 6. The management network address pool solves the problem that the cloud data center controller cannot operate the tenant cloud server. At the same time, the management network address is automatically reclaimed after the tenant cloud server is configured with a high availability cluster, which can realize the reuse of addresses in the management network address pool and avoid the security risks caused by mounting management network addresses on the tenant cloud server.

[0038] 7. After the cluster is established, the cluster servers can be elastically scaled up or down according to the tenant's business traffic. When operating on the tenant's cloud server, addresses in the management network address pool can be requested and used as needed, and then automatically released after use. The high availability of the tenant's cloud server cluster is achieved through virtual IP + keepalive. The use of the management network address pool enables the cloud data center controller to control the tenant's cloud server. Reclaiming management network addresses allows for the reuse of address pool addresses and also enhances the security of the cloud server. Attached Figure Description

[0039] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0040] Figure 1 This is a schematic diagram of the system architecture used in one embodiment of the present invention.

[0041] Figure 2 This is a flowchart of a method for implementing high availability of a tenant cloud server in one embodiment of the present invention.

[0042] Figure 3 This is a network diagram of a high-availability cluster of tenant cloud servers in one embodiment of the present invention.

[0043] Figure 4 This is a flowchart of a method for implementing high availability of a tenant cloud server in another embodiment of the present invention.

[0044] Figure 5 This is a schematic diagram of the structure of a cloud data center controller in one embodiment of the present invention. Detailed Implementation

[0045] The solution provided by the present invention will now be described with reference to the accompanying drawings.

[0046] First, it should be noted that the terminology used in the embodiments of this invention is for the purpose of describing specific embodiments only and is not intended to limit the invention. The singular forms “a,” “the,” and “the” used in the embodiments of this invention and the appended claims are also intended to include the plural forms, unless the context clearly indicates otherwise.

[0047] It should be understood that the term "and / or" used in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0048] To facilitate understanding of the method provided by this invention, the system architecture involved and applicable to this invention will first be described. For example... Figure 1 As shown, the system includes at least one tenant cloud server, a configurator, and a cloud data center controller.

[0049] It should be understood that Figure 1 The number of tenant cloud servers, configurators, and cloud data center controllers shown is merely illustrative. Any number can be selected and deployed as needed.

[0050] Figure 2 This is a flowchart illustrating a method for implementing high availability of a tenant cloud server in one embodiment of the present invention. See also... Figure 1 and Figure 2 The method includes:

[0051] Step 201: Set up the management network address pool; wherein the management network address pool includes no less than M management network addresses, which are public IP addresses; M is a positive integer greater than 1.

[0052] Step 203: Assign each of the M management network addresses in the management network address pool to one of the M tenant cloud servers.

[0053] Step 205: Group the M tenant cloud servers into a cluster and set the cluster configuration information for the cluster; the cluster configuration information includes virtual IP addresses.

[0054] Step 207: Send the cluster configuration information to each tenant cloud server in the cluster using the management network address assigned to each tenant cloud server in the cluster.

[0055] Step 209: Each tenant cloud server downloads the cluster configuration tool from the external network using the assigned management network address.

[0056] Step 211: Each tenant cloud server joins the cluster using the cluster configuration tool and cluster configuration information.

[0057] according to Figure 2 The method of the embodiment of the present invention shown can enable tenant cloud servers to form a cluster, which operates in a dual-machine or multi-machine mode, thereby supporting high availability and disaster recovery backup, and avoiding business unavailability due to the failure of some tenant cloud servers. The cluster has the following advantages in use: high availability and fault tolerance, when one server fails, other servers can take over to ensure service continuity; strong scalability, cluster servers can be flexibly expanded and scaled down according to business needs, improving resource utilization; high-performance computing, providing high-performance computing and storage capabilities through parallel computing and distributed storage technologies; data backup and recovery, enabling real-time backup and synchronization of data, ensuring data security and reliability, and reducing the risk of data loss; simplified management and maintenance, administrators can monitor and manage the entire cluster through a single console, reducing management complexity and workload.

[0058] Tenant cloud servers are users' private resources, and the cloud data center controller cannot directly control these tenant cloud servers. To solve this problem, in Figure 2 In the method of the embodiment of the present invention shown, a management network address from the management network address pool is allocated to the tenant cloud server. This management network address is a physical address, i.e., a public IP address. Therefore, through this management network address, the cloud data center controller can transmit information with the tenant cloud server, thereby enabling the cloud data center controller to control the tenant cloud server, such as issuing configuration commands and providing external network access to the tenant cloud server. Therefore, in Figure 2In the method of the embodiment of the present invention shown, the cloud data center controller configures the virtual IP address of the cluster and the cluster configuration tool, such as keepalive software, to the tenant cloud server through the management network address, thereby ensuring that the tenant cloud server can join the cluster and achieve high availability and disaster recovery backup.

[0059] The following is combined Figure 2 , Figure 3 as well as Figure 4 The high availability implementation method of the tenant cloud server in the embodiments of the present invention will be described.

[0060] First, execute step 201: Set up the management network address pool; wherein the management network address pool includes no less than M management network addresses, which are public IP addresses; M is a positive integer greater than 1.

[0061] In embodiments of the present invention, the management network address pool is a collection of management network addresses, which are physical layer addresses and public IP addresses configured by the underlying network. The management network addresses enable tenant cloud servers to communicate with the cloud data center controller and the external network.

[0062] The addresses in the management network address pool are shared by all users. When a tenant cloud server establishes a cluster mode, the cloud data center controller allocates and binds the addresses to the tenant cloud server. Each tenant cloud server is allocated a management network address. After the tenant cloud server completes the cluster setup, the management network address of the tenant cloud server will be reclaimed by the cloud data center controller and reserved for use by other tenant cloud servers.

[0063] Step 203: Assign each of the M management network addresses in the management network address pool to one of the M tenant cloud servers.

[0064] In step 203, the cloud data center controller can allocate and bind the management network address to the tenant's cloud server.

[0065] For example, see Figure 3The management network address pool ranges from 100.121.0.3 to 100.121.0.30, configured as a physical network, assigned VLAN numbers, and allows network communication with the cloud data center controller and the external network on the core switch. M is 3, and these three tenant cloud servers will form a cluster. Among the three tenant cloud servers, cloud server 1 is assigned the management network address 100.121.0.3, cloud server 2 is assigned the management network address 100.121.0.4, and cloud server 3 is assigned the management network address 100.121.0.5. The cloud data center controller attaches the three management network cards to the three tenant cloud servers respectively, thus enabling the cloud data center controller to control the tenant cloud servers.

[0066] Next, proceed to step 205: group the M tenant cloud servers into a cluster, and set the cluster configuration information, which includes virtual IP addresses.

[0067] For example, see Figure 3 The assigned virtual IP address is: 192.168.0.10.

[0068] Step 205 involves setting the cluster configuration information, which includes the cluster's virtual IP address. The virtual IP address serves as the unified external service address for the tenant cloud servers. It is also an internal network address within the virtual private network, allowing multiple tenant cloud servers within the cluster to share the same IP address.

[0069] When setting cluster configuration information, step 205 may further include at least one of the following:

[0070] 1. Configure the working mode of the cluster to master-slave mode.

[0071] 2. Assign a corresponding business role to each tenant cloud server in the cluster.

[0072] 3. Assign a corresponding priority to each tenant cloud server in the cluster;

[0073] 4. Configure the internal network IP address of each tenant cloud server in the cluster. For example, see... Figure 3 The internal IP addresses of the three tenant cloud servers are 192.168.0.3, 192.168.0.4, and 192.168.0.5, respectively.

[0074] See Figure 3Select 3 tenant cloud servers and set business roles and priorities for each tenant cloud server. There are two types of business roles: master and slave. A cluster can only have 1 master, and the others are slaves. The priority is an integer from 1 to 100, with higher values ​​indicating higher priority. The priority is consistent with the business role. Generally, the master role has the highest priority, while the slave role is set according to the performance of the tenant cloud server.

[0075] Once the configuration is complete, the cloud data center controller sends this information to the configurator.

[0076] Between steps 205 and 207, the following step can be further performed: Step 206: For each tenant cloud server in the cluster, add an available address pair of the virtual IP address to the network card interface of the tenant cloud server; the available address pair includes the correspondence between the virtual IP address and the MAC address of the tenant cloud server, so that the network card of the tenant cloud server can receive packets with the destination address as the virtual IP address.

[0077] To ensure that traffic accessing virtual IP addresses reaches the actual destination address, the network interface card (NIC) of the tenant cloud server needs to be configured with available address pairs for the virtual IP address. This allows the tenant cloud server's NIC to receive packets destined for the virtual IP address, facilitating a high-availability cluster mode for the tenant cloud server. For example, configure the mapping between the MAC address and virtual IP address for tenant cloud server 1, and configure the mapping between the MAC address and virtual IP address for tenant cloud server 2.

[0078] Next, step 207 is executed: the cluster configuration information is sent to each tenant cloud server in the cluster using the management network address assigned to each tenant cloud server in the cluster.

[0079] In step 207, a configurator can be set up to perform the deployment tasks. This configurator can be integrated into the cloud data center controller or set up independently of the cloud data center controller.

[0080] The cloud data center controller provides a Java-based configurator. This configurator connects to the tenant cloud server via SSH port 22, receives requests from the cloud data center controller to establish a cluster mode, parses the cluster mode type (e.g., master / slave mode), virtual IP address, priority, and business role status (master / slave), and, depending on the tenant cloud server type, adds commands to install keepalive and configure the configuration file. These commands are sent to the tenant cloud server via the management network address. Upon receiving these commands, the tenant cloud server first installs keepalive, then configures the configuration file, and starts keepalive. This automatically establishes the cluster mode using keepalive. The configurator can also convert the cluster configuration information into Linux commands to be used with the keepalive installation commands and then sent to the tenant cloud server.

[0081] The SSH protocol on port 22 of the server is used for remote login and remote management of the server. SSH stands for Secure Shell, an encrypted network protocol that provides a secure way to access the server remotely.

[0082] Next, proceed to step 209: Each tenant cloud server downloads the cluster configuration tool from the external network using the assigned management network address.

[0083] The management network address is a public IP address; therefore, the tenant cloud server can download the cluster configuration tool from the external network using the assigned management network address. In this embodiment of the invention, the cluster configuration tool can be the keepalive software.

[0084] Next, step 211 is performed: Each tenant cloud server joins the cluster using the cluster configuration tool and cluster configuration information.

[0085] In step 211, the process of each tenant cloud server joining the cluster using the cluster configuration tool and cluster configuration information includes:

[0086] Each tenant cloud server installs the keepalive software. After installation, the keepalived.conf file is configured to set the virtual IP address, internal IP address, business role, priority, and working mode. The keepalive software is then started, and the keepalive software initiates the cluster selection of the primary tenant cloud server.

[0087] At this point, the tenant's cloud server has been added to the cluster, and subsequent business operations conducted through the cluster can improve availability.

[0088] After completing step 211, step 213 can be further performed: the management network address allocated to each tenant cloud server in the cluster is reclaimed.

[0089] As can be seen, this embodiment of the invention utilizes virtual IP, keepalive, and management network address pool to establish a high-availability cluster for tenant cloud servers, achieving high availability and disaster recovery backup for tenant services, improving the processing performance of tenant services, and avoiding service interruptions. Controller configuration simplifies complex user operations, enhances user experience, and improves the competitiveness of the cloud data center. The high-availability cluster also supports elastic scaling of cloud servers, allowing for flexible configuration adjustments based on business needs, thereby improving resource utilization.

[0090] One embodiment of the present invention provides a cloud data center controller, see [link to relevant documentation]. Figure 5 ,include:

[0091] The management network address pool maintenance module 501 is configured to set up a management network address pool; wherein, the management network address pool includes no less than M management network addresses, which are public IP addresses; M is a positive integer greater than 1;

[0092] The management network address distribution module 502 is configured to distribute the M management network addresses in the management network address pool to the M tenant cloud servers one by one.

[0093] The cloud server cluster building module 503 is configured to group the M tenant cloud servers into a cluster, set the cluster configuration information of the cluster, which includes a virtual IP address; and send the cluster configuration information to each tenant cloud server in the cluster through the management network address assigned to each tenant cloud server in the cluster.

[0094] In one embodiment of the present invention, when setting the cluster configuration information of the cluster, the cloud server cluster building module 503 is further configured to perform at least one of the following:

[0095] Configure the cluster to operate in master-slave mode;

[0096] Configure a corresponding business role for each tenant cloud server in the cluster;

[0097] Set a corresponding priority for each tenant cloud server in the cluster.

[0098] Configure the internal network IP address of each tenant cloud server in the cluster.

[0099] In one embodiment of the present invention, the management network address pool maintenance module 501 is further configured to perform the following: after each tenant cloud server joins the cluster using the cluster configuration tool and cluster configuration information, the management network address allocated to each tenant cloud server in the cluster is reclaimed.

[0100] In one embodiment of the present invention, after setting the cluster configuration information, the cloud server cluster building module 503 is further configured to execute:

[0101] For each tenant cloud server in the cluster, an available address pair of the virtual IP address is added to the network interface card (NIC) of the tenant cloud server; the available address pair includes the correspondence between the virtual IP address and the MAC address of the tenant cloud server, so that the NIC of the tenant cloud server can receive packets with the destination address being the virtual IP address.

[0102] In one embodiment of the present invention, the management network address distribution module 502 includes a JAVA architecture configurator, which connects to each tenant cloud server via SSH port 22; the configurator sends the command to install keepalive, the command to configure the conf file, and the cluster configuration information to the tenant cloud server via the management network address, according to the type of the tenant cloud server.

[0103] See Figure 1 One embodiment of the present invention proposes a high availability implementation system for tenant cloud servers, the system comprising: a cloud data center controller, a configurator, and M tenant cloud servers, wherein,

[0104] A cloud data center controller is used to set up a management network address pool; wherein the management network address pool includes no less than M management network addresses, which are public IP addresses; M is a positive integer greater than 1; the controller assigns the M management network addresses in the management network address pool to M tenant cloud servers; the controller groups the M tenant cloud servers into a cluster and sets the cluster configuration information of the cluster.

[0105] A configurator is used to send cluster configuration information to each tenant cloud server in the cluster by assigning a management network address to each tenant cloud server in the cluster.

[0106] Each tenant cloud server is used to download the cluster configuration tool from the external network via the assigned management network address; and to join the cluster using the cluster configuration tool and cluster configuration information.

[0107] In one embodiment of the system of the present invention, the configurator is a JAVA architecture configurator, which connects to each tenant cloud server via SSH port 22; the configurator sends the command to install keepalive, the command to configure the conf file, and the virtual IP address to the tenant cloud server via the management network address, according to the type of the tenant cloud server.

[0108] In one embodiment of the system of the present invention, the configurator is a device independent of the cloud data center controller, or the configurator is integrated into the cloud data center controller.

[0109] It should be noted that the above-mentioned devices are typically implemented on the server side. They can be set up on independent servers, or some or all of the devices can be combined and installed on the same server. This server can be a single server or a server cluster consisting of multiple servers. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system. The above-mentioned devices can also be implemented on computer terminals with strong computing capabilities.

[0110] One embodiment of the present invention provides a computer-readable storage medium having a computer program stored thereon, which, when executed in a computer, causes the computer to perform the method in any of the embodiments of the specification.

[0111] One embodiment of the present invention provides a computing device, including a memory and a processor, wherein the memory stores executable code, and when the processor executes the executable code, it implements the method of any embodiment in the specification.

[0112] It is understood that the structures illustrated in the embodiments of the present invention do not constitute a specific limitation on the apparatus of the embodiments of the present invention. In other embodiments of the specification, the above-described apparatus may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0113] The various embodiments in this invention are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the device embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0114] Those skilled in the art will recognize that, in one or more of the examples above, the functions described in this invention can be implemented using hardware, software, widgets, or any combination thereof. When implemented in software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium.

[0115] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of the present invention. It should be understood that the above description is only a specific embodiment of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc., made on the basis of the technical solution of the present invention should be included within the scope of protection of the present invention.

Claims

1. A method for achieving high availability of a tenant cloud server, characterized in that, The method includes: Set up a management network address pool; wherein the management network address pool includes no less than M management network addresses, which are public IP addresses; M is a positive integer greater than 1; The M management network addresses in the management network address pool are assigned one by one to the M tenant cloud servers; The M tenant cloud servers are grouped into a cluster, and the cluster configuration information of the cluster is set, which includes virtual IP addresses; The cluster configuration information is sent to each tenant cloud server in the cluster by assigning a management network address to each tenant cloud server in the cluster. Each tenant cloud server downloads the cluster configuration tool from the external network through the assigned management network address; Each tenant cloud server joins the cluster using the cluster configuration tool and cluster configuration information; For each tenant cloud server in the cluster, add an available address pair of the virtual IP address to the network interface card of the tenant cloud server; the available address pair includes the correspondence between the virtual IP address and the MAC address of the tenant cloud server, so that the network interface card of the tenant cloud server can receive packets with the destination address as the virtual IP address.

2. The method according to claim 1, characterized in that, The cluster configuration information for setting the cluster includes at least one of the following: Configure the cluster to operate in master-slave mode; Configure a corresponding business role for each tenant cloud server in the cluster; Set a corresponding priority for each tenant cloud server in the cluster; Configure the internal network IP address of each tenant cloud server in the cluster.

3. The method according to claim 1, characterized in that, The cluster configuration tool is: keepalive software; Each tenant cloud server joins the cluster using cluster configuration tools and cluster configuration information, including: Each tenant cloud server installs the keepalive software. After installation, the keepalived.conf file is configured to set the virtual IP address, internal IP address, business role, priority, and working mode. The keepalive software is then started, and the keepalive software initiates the cluster selection of the primary tenant cloud server.

4. The method according to claim 1, characterized in that, After each tenant cloud server joins the cluster using the cluster configuration tool and cluster configuration information, the method further includes: reclaiming the management network address allocated to each tenant cloud server in the cluster.

5. The method according to claim 1, characterized in that, After setting the cluster configuration information for the cluster, the following is further included: For each tenant cloud server in the cluster, an available address pair of the virtual IP address is added to the network interface card (NIC) of the tenant cloud server; the available address pair includes the correspondence between the virtual IP address and the MAC address of the tenant cloud server, so that the NIC of the tenant cloud server can receive packets with the destination address being the virtual IP address.

6. A cloud data center controller, characterized in that, include: The management network address pool maintenance module is configured to set up a management network address pool; wherein, the management network address pool includes no less than M management network addresses, which are public IP addresses; M is a positive integer greater than 1; The management network address distribution module is configured to distribute the M management network addresses in the management network address pool to the M tenant cloud servers one by one. The cloud server cluster building module is configured to group the M tenant cloud servers into a cluster, set the cluster configuration information of the cluster, which includes virtual IP addresses; send the cluster configuration information to each tenant cloud server in the cluster through the management network address assigned to each tenant cloud server in the cluster; for each tenant cloud server in the cluster, add an available address pair of the virtual IP address to the network interface card of the tenant cloud server; the available address pair includes the correspondence between the virtual IP address and the MAC address of the tenant cloud server, so that the network interface card of the tenant cloud server can receive packets with the destination address being the virtual IP address.

7. A high availability implementation system for tenant cloud servers, characterized in that, The system includes: a cloud data center controller, a configurator, and M tenant cloud servers, among which, A cloud data center controller is used to set up a management network address pool, wherein the management network address pool includes no fewer than M management network addresses, which are public IP addresses; M is a positive integer greater than 1. The controller assigns each of the M management network addresses in the pool to one of the M tenant cloud servers. The M tenant cloud servers are grouped into a cluster, and the cluster configuration information is set, including virtual IP addresses. For each tenant cloud server in the cluster, an available address pair of the virtual IP address is added to the network interface card (NIC) of that tenant cloud server. This available address pair includes the correspondence between the virtual IP address and the MAC address of the tenant cloud server, thereby enabling the NIC of the tenant cloud server to receive packets destined for the virtual IP address. A configurator is used to send cluster configuration information to each tenant cloud server in the cluster by assigning a management network address to each tenant cloud server in the cluster. Each tenant cloud server is used to download the cluster configuration tool from the external network via the assigned management network address; and to join the cluster using the cluster configuration tool and cluster configuration information.

8. The system according to claim 7, characterized in that, The configurator is a Java-based configurator that connects to each tenant cloud server via SSH port 22. Based on the type of the tenant cloud server, the configurator sends the commands to install keepalive, the commands to configure the conf file, and the cluster configuration information to the tenant cloud server via the management network address.

9. The system according to claim 7, characterized in that, The configurator is a device independent of the cloud data center controller, or the configurator is integrated into the cloud data center controller.

10. A computing device comprising a memory and a processor, wherein the memory stores executable code, and the processor, when executing the executable code, implements the method of any one of claims 1-5.

Images