WO2017162173A1

WO2017162173A1 - Method and device for establishing connection of cloud server cluster

Info

Publication number: WO2017162173A1
Application number: PCT/CN2017/077738
Authority: WO
Inventors: 周莉
Original assignee: 中兴通讯股份有限公司
Priority date: 2016-03-22
Filing date: 2017-03-22
Publication date: 2017-09-28
Also published as: CN107222320A

Abstract

A method and device for establishing a connection of a cloud server cluster. The method for establishing a connection of a cloud server cluster comprises: performing host name resolution on a primary virtual machine and a backup virtual machine of a cloud server cluster, and configuring a dual-machine confidence building mechanism; mounting a preset highly available application on the primary virtual machine and the backup virtual machine, and configuring the mounted highly available application; adding a preset monitoring script which is used for describing a service of the preset highly available application; and starting the service of the preset highly available application to execute the preset monitoring script, and setting a floating Internet protocol (IP) address to establish a highly available connection of the cloud server cluster.

Description

Method and device for establishing connection of cloud server cluster

Technical field

The present disclosure relates to the field of cloud server technologies, for example, to a method and apparatus for establishing a connection of a cloud server cluster.

Background technique

Cloud server downtime may bring losses to the enterprise. When the host hosting the service system fails, it needs to switch to the standby machine in a short time. The technology to achieve this application requirement is "high-availability cluster technology", which is a server cluster technology aimed at reducing service interruption time, protecting users' business application systems from providing uninterrupted services to software, hardware or The impact of human-induced failures on the business is minimized.

The virtualization management software only supervises the virtual machine itself. When the virtual machine has a problem, the virtual machine is migrated, and the services on the virtual machine form a cluster, define the order in which the services are started, clone the services on the virtual machine, and define the number of service failures. The functions are not perfect, and the high availability of the cloud server cluster is poor.

Summary of the invention

The present disclosure proposes a method and apparatus for establishing a connection of a cloud server cluster, which can ensure high availability of a cloud server cluster.

This embodiment provides a method for establishing a connection between a cloud server cluster, including: performing host name resolution on the primary virtual machine and the standby virtual machine of the cloud server cluster, and configuring a dual-machine mutual trust mechanism; in the primary virtual machine and the Installing a preset high-availability application on the standby virtual machine, and configuring the installed high-availability application; adding a preset monitoring script, where the preset monitoring script is used to describe the service of the preset high-availability application; Presetting the service of the highly available application to execute the preset monitoring script and setting an Internet Protocol (IP) address interconnected between the floating networks to establish a highly available connection of the cloud server cluster.

This embodiment provides a device for establishing a connection between a cloud server cluster, and includes: a parsing module, configured to perform host name resolution on the primary virtual machine and the standby virtual machine of the cloud server cluster, and configure a dual-machine mutual trust mechanism; the configuration module is set to Installing a preset high-availability application on the primary virtual machine and the standby virtual machine, and configuring the installed high-availability application; adding a module, adding a preset monitoring script, where the preset monitoring script is used Describe the service of the preset high-availability application; the startup module is configured to start the service of the preset high-availability application, execute the preset monitoring script, and set a floating IP address to establish the cloud server cluster Highly available connection.

The embodiment further provides a computer readable storage medium storing computer executable instructions for executing the method for establishing a connection by the cloud server cluster.

The embodiment further provides a cloud server, the cloud server comprising one or more processors, a memory and one or more programs, the one or more programs being stored in the memory when executed by one or more processors The method of establishing a connection by the above cloud server cluster is performed.

The embodiment further provides a computer program product comprising a computer program stored on a non-transitory computer readable storage medium, the computer program comprising program instructions, when the program instructions are executed by a computer a method of causing the computer to perform a connection establishment of the cloud server cluster.

This embodiment provides a method and device for establishing a connection between a cloud server cluster, and configuring a dual-machine mutual trust mechanism of the primary virtual machine and the standby virtual machine of the cloud server cluster to install a preset high-availability application, and installing the highly available application after installation. Configure and add a preset monitoring script. The preset monitoring script is used to describe the service of the preset high-availability application, start the service of the preset high-availability application, execute the preset monitoring script, and set the floating IP to establish the cloud server. The cluster's highly available connections ensure high availability of cloud server clusters.

DRAWINGS

FIG. 1 is a schematic flowchart of a method for establishing a connection of a cloud server cluster according to the embodiment.

2 is a schematic flowchart of a method for establishing a connection of a cloud server cluster according to the embodiment.

FIG. 3 is a schematic structural diagram of an apparatus for establishing a connection of a cloud server cluster according to the embodiment.

FIG. 4 is a schematic structural diagram of an apparatus for establishing a connection of a cloud server cluster according to the embodiment.

FIG. 5 is a schematic structural diagram of a hardware of a cloud server according to this embodiment.

detailed description

The embodiments are described in the following, and the examples of the embodiments are shown in the drawings, and the same or similar reference numerals indicate the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are intended to be illustrative only, and are not to be construed as limiting. The features of the following embodiments and embodiments may be combined with each other without conflict.

This embodiment is exemplified by the method in which the cloud server cluster is connected to establish a connection. The device can be set in a cloud server cluster.

The method in this embodiment can be applied after the virtualization function of the cloud server cluster is started.

Referring to Figure 1, the method can include S110-S140.

In S110, the primary virtual machine and the standby virtual machine of the cloud server cluster are used for host name resolution, and a dual-machine mutual trust mechanism is configured.

Optionally, the host name resolution of the primary virtual machine and the standby virtual machine of the cloud server cluster may be as follows:

For example, on the node of the active virtual machine, edit the path to the /etc/hosts file in the Vi command editing interface, and add the following content to the hosts file:

192.168.56.101 Master.Cluster.com Master;

192.168.56.102 Slave.Cluster.com Slave;

The format of the content added in the hosts file can be the network IP address of the main virtual machine (for example, 192.168.56.101); the host name or domain name of the active virtual machine (for example, Master.Cluster.com); the main virtual The host name alias of the machine (for example, Master). The difference between the host name and the domain name includes: usually using the host name in the LAN, and then through the hosts file, the host name is resolved to the corresponding IP address.

You can also modify /etc/sysconfig/network on the active VM in the Vi command editing interface. File, modify the HOSTNAME in the network file to HOSTNAME=Master. In this way, when you restart the host of the cloud server and log in to the active VM, the host name of the active VM can be changed to Master.

Optionally, the host name of the standby virtual machine may be modified to a slave according to the method of modifying the host name of the active virtual machine to be the master.

Optionally, after the host names of the active virtual machine and the standby virtual machine are parsed, a dual-machine mutual trust mechanism can be configured, that is, a key is created to allow all users who hold the key to log in to the cloud server. Cluster.

Optionally, a first Secure Shell (SSH) passwordless login mode from the primary virtual machine to the standby virtual machine may be established; and a second SSH passwordless login is established from the standby virtual machine to the primary virtual machine. mode.

Optionally, the configuration of the dual-machine mutual trust mechanism can be exemplified as follows.

For example, you can use the ssh-keygen command on the active VM to create an SSH key and activate the SSH key. The ssh-keygen command can be used to generate the ssh login key. You can log in to the active VM remotely. Instead of entering the key of the remote active virtual machine, enter the directory and file name where the public key and key are located, which can be stored in the directory /root/.ssh. Optionally, when the directory and file name are not entered, the primary virtual machine generates a public key and a key in the current directory, and then inputs the ssh login password, enters the password when the key is used, or does not enter the ssh login password. The first SSH passwordless login mode from the primary virtual machine to the standby virtual machine is established, which is convenient to use.

And the public key and key of ssh to the active virtual machine are generated under /root/.ssh of the primary virtual machine. You can also copy the public key file Master_rsa.pub generated on the primary virtual machine to /root/.ssh of the standby virtual machine, and copy the public key file Master_rsa.pub generated on the primary virtual machine to the standby virtual machine. In /root/.ssh/authorized_keys, modify the permissions of authorized_keys to 600. Through the steps in this example, you can establish the first SSH passwordless login mode from the primary virtual machine to the standby virtual machine.

Optionally, the second SSH passwordless login mode from the standby virtual machine to the active virtual machine may also be established according to the above example.

In S120, a preset high availability application is installed on the primary virtual machine and the standby virtual machine, and the installed high availability application is configured.

Optionally, the preset high availability applications may include a Pacemaker application, a Corosync application, a Crmsh application, and a Distributed Replicated Block Device (DRBD) application.

Optionally, the preset high availability application is installed on the primary virtual machine and the standby virtual machine, and the installed high availability application is configured, as exemplified below.

For example, execute the command on the primary virtual machine: yum install-y pacemaker corosync crmsh drbd. After installing the Pacemaker application, the Corosync application, the Crmsh application, and the DRBD application, you can configure the Corosync application. In the path cd/etc/corosync, execute the command scp corosync.conf.example corosync.conf, which copies the configuration of the Corosync application. The file, for example, can be modified by the Vi command editor as follows:

Threads: 1. Among them, threads is the starting thread, the value of threads means to start a preset number of threads to transmit heartbeat information. When there are many nodes in the cloud server cluster and when the host is multi-core, multiple threads can be started to monitor, 0 is the default value. In this embodiment, the thread value can be modified to 1, that is, a thread is started to perform heartbeat information transmission.

Bindnetaddr: 192.168.56.0. Bindnetaddr is the IP address segment monitored by the cloud server cluster. The IP address of the network card is associated with the gateway. The network segment where the active virtual machine communicates can be obtained. The IP address in this embodiment can be 192.168.56.101. For 255.255.255.0, the IP address and the mask are logically ANDed to obtain 192.168.56.0.

To_logfile:yes. Among them, set to_logfile to yes to enable local log storage.

Logfile: /var/log/cluster/corosync.log. You can set the file directory to save the local logfile by setting the logfile. In the actual application scenario, the /var/log/cluster directory already exists. You can create the corosync.log file in the /var/log/cluster directory.

To_syslog: yes. Among them, to_syslog can be set to write to the system log. If to_syslog is set to yes, the system log can be written to /var/log/messages.

The quorum indicates that the voting mechanism is enabled. Assume that the initial voting mechanism requires at least 3 votes. In this embodiment, the cloud server cluster includes the host and standby examples, and only two nodes can change the expected voting number to 2. Two_node: 1, which means that when the cloud server cluster contains two nodes, the host and the standby, only one vote is required, which can be mainly used for the host.

Optionally, the authentication function can be used when the Corosync application is enabled, ie the key can be generated for the Corosync application. For example, you can use the corosync-keygen command on the primary virtual machine to generate a key for the Corosync application. You can save the generated key file in the /etc/corosync/authkey path. Transfer the corosync key files authkey and corosync configuration files to the /etc/corosync directory of the standby virtual machine. You can run the service corosync start to start the corosync application service. After the startup is complete, you can detect whether the corosync starts normally.

Among them, the DRBD application is a storage and replication solution that implements software, has no sharing, and mirrors block device content between servers. For example, the primary virtual machine and the standby virtual machine can all allocate a part of the space to the DRBD management. When the data on the host is modified, the DRBD application automatically synchronizes to the standby standby. When the host fails, the same data can be used on the standby. Read and write operations.

Optionally, the services of the DRBD application may be predefined and created, and the examples are as follows:

Enter the following command in the Vi command editor:

Wherein, protocol C indicates that protocol C is used, and protocol C indicates that the write confirmation is received by the remote host, and then the write completion is considered. Address 192.168.56.101:7898 indicates that the listening port of the DRBD application is set to communicate with another virtual machine. Address 192.168.56.102:7898 indicates that another listening port for the DRBD application is set up to communicate with another virtual machine.

Optionally, the partition required for the DRBD application synchronization data can also be created. The storage space of the host and the backup machine is the same. You can enter the following command in the Vi command editor:

Fdisk/dev/sdc;

Drbdadm create-md mysql;

Service drbd start.

And, you can set the primary virtual machine to be the primary node of the DRBD application. Enter the following command only in the Vi command editor on the primary virtual machine:

Drbdadm - overwrite-data-of-peer primary mysql.

Optionally, you can also create a file system, you can enter the following command in the Vi command editor:

Mkfs-t ext4/dev/drbd0.

In S130, a preset monitoring script is added, and the preset monitoring script is used to describe a service of the preset high-availability application.

The preset monitoring script may include a start function, a stop function, and a monitor function.

Optionally, adding a preset monitoring script can be exemplified as follows.

Services for the Pacemaker application include the Linux Standards Base (LSB) service and the OCF service. The LSB service can be a script in the /etc/init.d directory. Pacemaker application The LSB service can be used to start and stop the service. The OCF service is an extension of the LSB service and adds services such as fault monitoring for high-availability cluster management. High availability guarantees for cloud management system services can be achieved by implementing OCF services.

Optionally, a preset monitoring script may be added, where the preset monitoring script may be an OCF service script, and the OCF service script is an executable file, wherein the preset monitoring script may include a start function, a stop function, and a monitor function.

Optionally, in the start function, start the cloud server cluster and set the timeout period to 20s. In the stop function, you can stop the cloud server cluster and set the timeout period to 20s. In the monitor function, you can monitor the cloud server cluster and set the timeout period to 10s and the interval to 5s.

Optionally, in the OCF service script, the metadata function may be written. After the metadata function is executed, when the meta-data command is input in the Vi command editing interface, the data in the xml format is output, and the data in the xml format may be the OCF service. Meta information. The description, parameter definitions, and command definitions for each OCF service can be described by data in xml format, and then the timeout period for configuring metadata can be 5s.

Optionally, in the OCF service script, you can also define validate-all, that is, the validity of the detected parameter. The timeout of the configured validate-all is 5s.

In S140, the service of the preset high-availability application is started to execute a preset monitoring script, and a floating IP address is set to establish a high-availability connection of the cloud server cluster.

Optionally, starting the service of the preset high-availability application to execute the preset monitoring script and setting the floating IP address to establish a high-availability connection of the cloud server cluster can be exemplified as follows.

For example, the IP address of the primary virtual machine is 192.168.56.101, the IP address of the standby virtual machine is 192.168.56.102, and the virtual IP address is 192.168.56.254.

To switch the Vi command edit mode of the active virtual machine and the standby virtual machine to the crm command line edit mode, use the following command:

Configure primitive vip ocf:heartbeat:IPaddr2\;

Params ip=192.168.56.254\;

Nic=eth0\;

Cidr_netmask=24\;

Op start timeout=20s interval=0s on-fail=stop\;

Op monitor timeout=20s interval=10s on-fail=restart\;

Op stop timeout=20s interval=0s on-fail=block\;

Verify

Commit;

Optionally, you can create a cloud server cluster service and set the timeout period for starting, stopping, and monitoring the cloud server cluster. If the cloud server cluster on the primary virtual machine is abnormal, it can be monitored by the monitor in the OCF service script. According to the operation specified when the user is created, it is decided to switch to the standby machine after the host starts several times, or directly switch to the standby machine.

Optionally, by configuring a dual-machine mutual trust mechanism between the active virtual machine and the standby virtual machine of the cloud server cluster, installing a preset high-availability application, configuring the installed high-availability application, and adding a preset monitoring script, The monitoring script is used to describe the service of the preset high-availability application, start the service of the preset high-availability application, execute the preset monitoring script, and set the floating IP address to establish a high-availability connection of the cloud server cluster, which can effectively ensure the cloud. High availability of server clusters.

The high availability of a cloud server cluster can be measured by the reliability and maintainability of the cluster. The availability of the cluster can usually be measured by Mean Time Between Failures (MTBF), and the maintainability of the cluster is measured by Mean time to repair (MTTR).

Optionally, in order to prevent the cloud server from being down, the service carried by the cloud server cannot be executed, and the primary virtual machine and the standby virtual machine are set in the cloud server cluster, and are used on the primary virtual machine and the standby virtual machine. The high-availability application is running. When the active virtual machine is working normally, the status information can be periodically sent to the standby virtual machine. When the standby virtual machine does not receive the status information sent by the active virtual machine within the preset time, The standby virtual machine can start the high-availability application and take over the current service of the active virtual machine through the floating IP address, thus ensuring high availability of the cloud server cluster. When the primary virtual machine returns to normal, it can send status information to the standby virtual machine, and when the standby virtual machine receives the primary virtual machine. When the status information is available, you can choose to release the floating IP address and take over the current service by the active virtual machine.

Referring to Figure 2, the method includes S210-S280.

In S210, the virtualization function of the cloud server cluster is started.

For example, you can enable the virtualization function of the board or host in the cloud server cluster. For example, enter the BIOS and set the virtualization to enable.

In S220, the first virtual machine is installed on the host of the cloud server cluster as the primary virtual machine, and the second virtual machine is installed as the standby virtual machine on the standby of the cloud server cluster.

Taking the first virtual machine and the second virtual machine as Virtualbox as an example, this step can be exemplified as follows.

You can download the Virtualbox binary installation file corresponding to the host operating system of the cloud server cluster on the Virtualbox website, and then run the Virtualbox binary installation file to open the installation wizard. When installing the Virtualbox virtual machine, you can customize the VirtualBox feature and select any shortcut. Specify the installation directory, you can also install the USB device driver and the VirtualBoxhost-only network adapter.

Optionally, the binary installation file when installing the Virtualbox virtual machine may be a virtual desktop infrastructure (VDI) file, and the VDI file is a virtual disk image file of the VirtualBox.

Optionally, in creating the active virtual machine of the cloud server cluster, you can define the name of the active virtual machine and the operating system type enabled by the virtual machine. For example, the Linux operating system can be selected, and the version can be Linux2.6/3.X ( 64bit), you can also set the memory size of the active virtual machine, for example, set to 2048M, then load the hard disk file VDI of the specified virtual machine, and then create it.

In this step, you can directly load the pre-prepared VDI files without reinstalling the operating system on each virtual machine. As long as the first machine is installed, you need to use the operating system, and then other needs. The virtual machine using this operating system can be directly loaded, which effectively reduces the time for installation and deployment.

Optionally, before creating the standby virtual machine of the cloud server cluster, the VDI file for creating the primary virtual machine may be copied and the copied VDI file may be renamed, or the copied VDI file may be set to be readable and modifiable. Then follow the steps to create a primary virtual machine to recreate an alternate virtual machine.

Optionally, the virtualization of the host and the standby device enables flexible scheduling of physical resources of the cloud server cluster and cross-domain sharing, thereby improving resource utilization.

In S230, a virtual Host-only network is established, and the virtual Host-only network is mounted to the primary virtual machine and the standby virtual machine.

The example of establishing a virtual Host-only network is as follows: Select File-->Preferences-->network-->Host-only Networks operation path in the virtual machine VirtualBox. In the Host-only Networks Details interface, configure the IP address and network mask of the Adapter in the TAB page of the Adapter. In this example, you can configure the IPv4 address as 192.168.56.1 and the mask as 255.255.255.0. Not configured yet, not enabled. It is also possible to configure the IPv6 address when it needs to be enabled. Then select the check box in front of the Enable Server in the interface of the Dynamic Host Configuration Protocol (DHCP) Server of the Host-only Networks Details, indicating that the DCHCP Server is enabled, and can be dynamically allocated by the DHCP server when the VM is created. The IP address of the virtual machine, you can configure the DHCP Server Address, the setting value is 192.168.56.100, Server Mask: 255.255.255.0, Lower Address Bound: 192.168.56.101 (indicating the starting address assigned by the DHCP server), Upper Address Bound: 192.168 .56.254 (represents the termination address assigned by the DHCP server). At this time, the virtual Host-only network vboxnet0 is established.

Optionally, after the virtual host-only network vboxnet0 is established, the active virtual machine can be set.

For example, in the operation path of Setting-->Network-->Adapter1 of the active virtual machine, the network card of the active virtual machine is Attatched to: Host-only Adapter, and the name is vboxnet0, and then the Promiscuous Mode is set to Allow. All mode, click OK, that is, the main virtual machine The virtual NIC is mounted on the host-only network plane. Optionally, the NIC of the standby virtual machine may be mounted to the virtual Host-only network according to the foregoing operation. When the primary virtual machine and the standby virtual machine are mounted to the host-only virtual machine NIC, when the active virtual machine is started, the DHCPServer service on the host-only NIC assigns an IP address to the virtual machine, and the assigned IP address is established. The virtual Host-only network starts with the Lower Address Bound (address 192.168.56.100). When the primary virtual machine is started in the first order, the DHCP server assigns the primary virtual machine an IP address of 192.168.56.101, and then starts the standby virtual machine. The DHCP Server service on the Host-only network card assigns an IP address to the standby virtual machine. The DHCP Server will assign the primary virtual machine an IP address of 192.168.56.102.

In an abnormal state, if the DHCP server fails to obtain the eth0 NIC when the standby VM is started, you can delete the standby VM after deleting /etc/udev/rules.d/70-persistent-net.rules.

In S240, the primary virtual machine and the standby virtual machine of the cloud server cluster are used for host name resolution, and a dual-machine mutual trust mechanism is configured.

192.168.56.101 Master.Cluster.com Master;

192.168.56.102 Slave.Cluster.com Slave;

The format of the content added in the hosts file can be the network IP address of the main virtual machine (for example, 192.168.56.101); the host name or domain name of the active virtual machine (for example, Master.Cluster.com); the main virtual The host name alias of the machine (for example, Master). The difference between a host name and a domain name is that the host name is usually used in the LAN, and then the host file is resolved to the corresponding IP address through the hosts file.

At the same time, you can modify the /etc/sysconfig/network file on the active VM in the Vi command editing interface, and change the HOSTNAME in the network file to HOSTNAME=Master. In this way, restart the cloud server host again and log in. Active virtual When the machine is in use, the host name of the active virtual machine can be changed to Master.

Optionally, a first SSH passwordless login mode from the primary virtual machine to the standby virtual machine may be established; and a second SSH passwordless login mode from the standby virtual machine to the primary virtual machine is established.

For example, you can use the ssh-keygen command on the active VM to create an SSH key and activate the SSH key. The ssh-keygen command can be used to generate the ssh login key. You can log in to the active VM remotely. No need to enter the key of the remote active virtual machine, enter the directory and file name where the public key and key are located, and store it in the directory /root/.ssh. Optionally, when not entering the directory and file name, the main use The virtual machine generates the public key and key in the current directory, then enters the ssh login password, enters the password when using the key, or enters the ssh login password, which can be used to establish the first SSH from the primary virtual machine to the standby virtual machine. No password login mode, easy to use.

Optionally, the second SSH passwordless login mode from the standby virtual machine to the active virtual machine may be established according to the foregoing example, and details are not described herein again.

In S250, set the Network Time Protocol (NTP) time server of the Host-only network, and configure the NTP time client.

The number of NTP time clients is the same as the number of standby virtual machines.

This step can be exemplified as follows: You can install NTP time server by executing yum install-y ntp in the Vi command editor.

When configuring the NTP time server on the intranet, you can use the Vi command to modify the /etc/ntp.conf configuration file and add restrict 192.168.56.1 mask255.255.255.0 nomodify notrap to the /etc/ntp.conf configuration file. Access the IP address segment of the NTP time server, mask, and so on. Enter echo "server 192.168.56.101">>/etc/ntp.conf at the command line to indicate that the primary virtual machine is the NTP time server.

Optionally, an NTP standard time server on the Internet can also be set to select the NTP standard time server closest to the user. This example assumes that the cloud server cluster is implemented in Shanghai. You can configure the three NTP time servers closest to Shanghai in the ntp.conf configuration file:

Server 1.cn.pool.ntp.org;

Server 3.asia.pool.ntp.org;

Server 0.asia.pool.ntp.org.

Then, modify the ntp.conf configuration file to set the local time server as the time server when the external time server is unavailable. You can add the following to the ntp.conf configuration file:

Server 127.127.1.0 #local clock;

Fudge 127.127.1.0 #startnum 10.

After setting the ntp.conf configuration file, you can execute ntpdate-u1.cn.pool.ntp.org to force the time server to synchronize with the standard NTP time server. Then, run the service ntpd start command to restart the ntpd service. .

Optionally, the NTP time client can be configured as an example.

Run the yum install-y ntp command to install the NTP service on the standby VM. Configure the NTP service to be self-starting. Use the Vi command to modify the /etc/ntp.conf configuration file. You can add the following content:

Restrict 192.168.56.101 mask nomodify notrap;

Server 192.168.56.101.

The server 192.168.56.101 can set the IP address of the primary NTP time server. The IP address of the NTP time server of the cloud server cluster is 192.168.56.101. After the setting is completed, Save the ntp.conf configuration file. Finally, after the modification is complete, you can execute ntpdate-u192.168.56.101, that is, the NTP time client is forced to synchronize with the NTP time server through the ntpdate command. When the NTP time client is restarted, the NTP time client starts to synchronize with the NTP time server.

In S260, a preset high availability application is installed on the primary virtual machine and the standby virtual machine, and the installed high availability application is configured.

Alternatively, the preset high availability applications may include a Pacemaker application, a Corosync application, a Crmsh application, and a DRBD application.

For example, execute the command on the main virtual machine: yum install-y pacemaker corosync crmsh drbd; after installing the Pacemaker application, Corosync application, Crmsh application, and DRBD application, you can start to configure the Corosync application first, ie in the path cd/etc /corosync, execute the command scp corosync.conf.example corosync.conf, that is, copy the configuration file of the Corosync application. For example, you can modify the modified content through the Vi command editor as follows:

Threads:1;

Among them, threads is the starting thread, the value of threads means to start a preset number of threads to transmit heartbeat information. When there are many nodes in the cloud server cluster and when the host is multi-core, multiple threads can be started to monitor, 0 is the default value. In this embodiment, the thread value can be modified to 1, that is, a thread is started to perform heartbeat information transmission.

Bindnetaddr: 192.168.56.0. Bindnetaddr is the IP address segment monitored by the cloud server cluster. The IP address of the network card is associated with the gateway. The network segment where the active virtual machine communicates can be obtained. The IP address in this embodiment can be 192.168.56.101. It is 255.255.255.0, then the phase is 192.168.56.0.

To_logfile:yes. Among them, set to_logfile to yes to enable local log storage.

Logfile: /var/log/cluster/corosync.log. You can set the file directory to save the local logfile by setting the logfile. In the actual application scenario, /var/log/cluster The record already exists, you can create the corosync.log file in the /var/log/cluster directory.

Optionally, the authentication function can be used when the Corosync application is enabled, ie the key can be generated for the Corosync application. For example, you can use the corosync-keygen command on the active virtual machine to generate a key for the Corosync application. You can save the generated key file in the /etc/corosync/authkey path, and then configure the corosync key files authkey and corosync. The file is transferred to the /etc/corosync directory of the standby VM. You can then run the service corosync start to start the corosync application service. After the startup is complete, you can check whether the corosync starts normally.

Among them, the DRBD application is a storage and replication solution that implements software, has no sharing, and mirrors block device content between servers. For example, the primary virtual machine and the standby virtual machine can allocate a part of space to the DRBD management. When the data on the host is modified, the DRBD application automatically synchronizes to the standby standby. When the host fails, the same data can be used on the standby. Read and write operations.

Enter the following command in the Vi command editor:

Fdisk/dev/sdc;

Drbdadm create-md mysql;

Service drbd start.

Drbdadm - overwrite-data-of-peer primary mysql.

Mkfs-t ext4/dev/drbd0.

In S270, a preset monitoring script is added, and the preset monitoring script is used to describe the service of the preset high-availability application.

Optionally, adding a preset monitoring script can be exemplified as follows:

Services for Pacemaker applications can include LSB services and OCF services, where the LSB service is a Linux standard service, usually a script in the /etc/init.d directory. The Pacemaker application can use the LSB service to start and stop services. The OCF service is an extension of the LSB service, adding features such as fault monitoring and other services for high-availability cluster management. High availability guarantees for cloud management system services can be achieved by implementing OCF services.

Optionally, a preset monitoring script may be added, where the preset monitoring script may be an OCF service script, and the OCF service script is an executable file, where the preset monitoring script includes a start function, a stop function, and a monitor function.

Optionally, in the OCF service script, the metadata function may be written. After the metadata function is executed, when the meta-data command is input in the Vi command editing interface, the data in the xml format may be output, and the data in the xml format may be the OCF service. Meta information. The description, parameter definition and command definition of each OCF service can be described by the data in xml format, and then the timeout period of the metadata can be configured to be 5s.

In S280, a service of the preset high availability application is started to execute a preset monitoring script, and a floating IP address is set to establish a high availability connection of the cloud server cluster.

Configure primitive vip ocf:heartbeat:IPaddr2\;

Params ip=192.168.56.254\;

Nic=eth0\;

Cidr_netmask=24\;

Op start timeout=20s interval=0s on-fail=stop\;

Op monitor timeout=20s interval=10s on-fail=restart\;

Op stop timeout=20s interval=0s on-fail=block\;

Verify

Commit;

Optionally, you can create a cloud server cluster service and set the timeout period for starting, stopping, and monitoring the cloud server cluster. If the cloud server cluster on the active VM is abnormal, it can be monitored by the monitor in the OCF service script. According to the operation specified when the user is created, it is decided to switch to the standby machine after the host starts several times, or directly switch to Standby machine.

In this embodiment, it is possible to directly load a pre-prepared VDI file without reinstalling the operating system on each virtual machine, as long as the first machine is installed with an operating system to be used, and then other virtual machines that need to use the operating system. Load directly, which reduces the time for installation and deployment. Virtualization of the host and the standby device enables flexible scheduling of physical resources of the cloud server cluster and cross-domain sharing, which improves resource utilization. By establishing a virtual host-only network, you can set up an independent IP address, and you can communicate with the host and other virtual machines. The active virtual machine and the standby virtual machine occupy only one external IP address. The internal network is all configured in DHCP. The network IP address is expanded in the size of the cloud server cluster, which can greatly save the IP address resources. At the same time, only one IP address is used. When the cloud server cluster fails, the user does not need to change the access IP address when the host and the standby switch are switched. User experience. In addition, the preset monitoring script is added, and the preset monitoring script is written by the cloud server cluster administrator. The cloud server cluster can be started, monitored, and stopped by the preset preset monitoring script, and the cloud server cluster can be monitored. Conduct intelligent, efficient and secure control. Install a preset high-availability application by configuring the dual-machine mutual trust mechanism between the active virtual machine and the standby virtual machine of the cloud server cluster, configure the installed high-availability application, and add preset monitoring feet. The preset monitoring script is used to describe the service of the preset high-availability application, start the service of the preset high-availability application, execute the preset monitoring script, and set the floating IP address to establish a high-availability connection of the cloud server cluster. Effectively ensure high availability of cloud server clusters.

FIG. 3 is a schematic structural diagram of an apparatus for establishing a connection of a cloud server cluster according to the embodiment. The device can be set in a cloud server cluster.

Referring to FIG. 3, the apparatus 30 can include a parsing module 301, a configuration module 302, an adding module 303, and a launching module 304.

The parsing module 301 is configured to perform host name resolution on the active virtual machine and the standby virtual machine of the cloud server cluster, and configure a dual-machine mutual trust mechanism.

Optionally, the parsing module 301 is further configured to: establish a first SSH passwordless login mode from the primary virtual machine to the standby virtual machine; and establish a second SSH passwordless login mode from the standby virtual machine to the primary virtual machine. .

The configuration module 302 is configured to install a preset high availability application on the primary virtual machine and the standby virtual machine, and configure the installed high availability application.

The adding module 303 is configured to add a preset monitoring script, and the preset monitoring script is used to describe a service of the preset high-availability application.

Optionally, the preset monitoring script may include a start function, a stop function, and a monitor function.

The startup module 304 is configured to start a service of the preset high availability application to execute a preset monitoring script and set a floating IP address to establish a high availability connection of the cloud server cluster.

Optionally, referring to FIG. 4, the apparatus 30 may further include:

The installation module 305 is configured to install the first virtual machine on the host of the cloud server cluster as the primary virtual machine, and install the second virtual machine as the standby virtual machine on the standby of the cloud server cluster.

The establishing module 306 is configured to establish a virtual Host-only network and mount the virtual Host-only network to the primary virtual machine and the standby virtual machine.

The setting module 307 is configured to set an NTP time server of the Host-only network and configure an NTP time client.

Optionally, the number of NTP time clients is the same as the number of standby virtual machines.

The module 308 is enabled to be set to enable the virtualization function of the cloud server cluster.

In this embodiment, the dual-machine mutual trust mechanism of the active virtual machine and the standby virtual machine of the cloud server cluster is configured to install a preset high-availability application, and the installed high-availability application is configured, and a preset monitoring script is added. The preset monitoring script is used to describe the service of the preset high-availability application, start the service of the preset high-availability application, execute the preset monitoring script, and set the floating IP address to establish a high-availability connection of the cloud server cluster, which can effectively ensure High availability for cloud server clusters.

FIG. 9 is a schematic diagram of a hardware structure of a cloud server according to this embodiment. The cloud server includes a processor 410 and a memory 420; and may further include a communications interface 430 and a bus 440.

The processor 410, the memory 420, and the communication interface 430 can complete communication with each other through the bus 440. Communication interface 430 can be used for information transmission. The processor 410 can invoke the logic instructions in the memory 420 to perform the method of establishing a connection by any one of the cloud server clusters in the above embodiments.

In addition, the logic instructions in the memory 420 described above may be implemented in the form of software functional units and sold or used as separate products, and may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present disclosure may be embodied in the form of a software product stored in a storage medium, including a plurality of instructions for causing a computer device (which may be a personal computer, a server, or a network) The device or the like) performs all or part of the steps of the method described in this embodiment. The foregoing storage medium may be a non-transitory storage medium, including: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. A medium that can store program code, or a transitory storage medium.

In the description of the above embodiments, the terms "first", "second", and the like are used for descriptive purposes only, and are not to be construed as indicating or implying relative importance. Further, "multiple" means two or more unless otherwise stated.

Any process or method description in the flowcharts or otherwise described herein may be understood to represent a module, segment or portion of code that includes one or more executable instructions for implementing the steps of a particular logical function or process. And the scope of the above embodiments includes an additional implementation in which The functions are performed in the order shown or discussed, including in a substantially simultaneous manner or in the reverse order, depending on the functionality involved.

It should be understood that the technical solution of the embodiment may be implemented by hardware, software, firmware, or a combination thereof. In the above-described embodiments, multiple steps or methods may be implemented in software or hardware stored in a memory and executed by a suitable instruction execution system. For example, the hardware can include discrete logic circuits with logic gates for implementing logic functions on data signals, application specific integrated circuits with suitable combinational logic gates, programmable gate arrays (PGAs), field programmable gate arrays (FPGAs) )Wait.

All or part of the steps carried by the method of the above embodiment may also be completed by a program to instruct related hardware, and the program may be stored in a computer readable storage medium, and when executed, the steps of the method embodiment are included. One or a combination thereof.

In addition, the multiple functional units in this embodiment may be integrated into one processing module, or each unit may exist physically separately, or two or more units may be integrated into one module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. The integrated modules, if implemented in the form of software functional modules and sold or used as stand-alone products, may also be stored in a computer readable storage medium.

The description of the terms "one embodiment", "some embodiments", "example", "specific examples", or "some examples" and the like means that the features, structures, materials, or characteristics described in connection with the embodiments or examples are included in At least one embodiment or example. In the embodiments, the schematic representation of the above terms does not necessarily refer to the same embodiment or example. Furthermore, the described features, structures, materials, or characteristics may be combined in a suitable manner in any one or more embodiments or examples.

Industrial applicability

The present disclosure provides a method and apparatus for establishing a connection of a cloud server cluster, which can ensure high availability of a cloud server cluster.

Claims

A method for establishing a connection of a cloud server cluster, comprising:

Perform host name resolution for the primary virtual machine and the standby virtual machine of the cloud server cluster, and configure a dual-machine mutual trust mechanism;

Installing a preset high-availability application on the primary virtual machine and the standby virtual machine, and configuring the installed high-availability application;

Adding a preset monitoring script, the preset monitoring script is used to describe a service of the preset high-availability application;

The service of the preset high-availability application is started to execute the preset monitoring script, and a floating network interconnection protocol IP address is set to establish a high-availability connection of the cloud server cluster.
The method of claim 1, before the host name resolution of the active virtual machine and the standby virtual machine of the cloud server cluster, and the configuration of the dual-machine mutual trust mechanism, the method further includes:

The first virtual machine is installed on the host of the cloud server cluster as the primary virtual machine, and the second virtual machine is installed as the standby virtual machine on the standby of the cloud server cluster.
The method of claim 1 further comprising:

Establishing a virtual Host-only network and mounting the virtual Host-only network to the primary virtual machine and the standby virtual machine.
The method of claim 3 further comprising:

Set the network time protocol NTP time server of the Host-only network, and configure the NTP time client.
The method of claim 4 wherein the number of NTP time clients is the same as the number of the standby virtual machines.
The method of claim 1 wherein said configuring a two-way mutual trust mechanism comprises:

Establishing a first secure shell protocol SSH passwordless login mode from the primary virtual machine to the standby virtual machine;

Establishing a second SSH passwordless login mode from the standby virtual machine to the primary virtual machine.
The method according to claim 2 or 5 or 6, wherein the preset monitoring script includes a start function, a stop function, and a monitor function.
The method according to any one of claims 1 to 7, before the host name resolution of the active virtual machine and the standby virtual machine of the cloud server cluster is configured, and the dual-machine mutual trust mechanism is configured, the method further includes:

Enable the virtualization function of the cloud server cluster.
A device for establishing a connection of a cloud server cluster, comprising:

The parsing module is configured to perform host name resolution on the primary virtual machine and the standby virtual machine of the cloud server cluster, and configure a dual-machine mutual trust mechanism;

a configuration module, configured to install a preset high-availability application on the primary virtual machine and the standby virtual machine, and configure the installed high-availability application;

Adding a module, configured to add a preset monitoring script, the preset monitoring script is used to describe a service of the preset high-availability application;

The startup module is configured to start the service of the preset high-availability application to execute the preset monitoring script, and set a floating network interconnection protocol IP address to establish a high-availability connection of the cloud server cluster.
The apparatus of claim 9 further comprising:

The installation module is configured to install the first virtual machine on the host of the cloud server cluster before the resolution module performs the host name resolution on the primary virtual machine and the standby virtual machine of the cloud server cluster, and configures the dual-machine mutual trust mechanism. And installing, by the primary virtual machine, a second virtual machine on the standby machine of the cloud server cluster as the standby virtual machine.
The apparatus of claim 9 further comprising:

Establishing a module, setting up to establish a virtual Host-only network, and mounting the virtual Host-only network to the primary virtual machine and the standby virtual machine.
The apparatus of claim 11 further comprising:

Set the module to set the network time protocol NTP time server of the Host-only network and configure the NTP time client.
The apparatus of claim 12, wherein the number of the NTP time clients is the same as the number of the standby virtual machines.
The apparatus of claim 9, wherein the parsing module is further configured to:

Establishing a first secure shell protocol SSH passwordless login mode from the primary virtual machine to the standby virtual machine;

Establishing a second SSH passwordless login mode from the standby virtual machine to the primary virtual machine.
The apparatus according to claim 10 or 13 or 14, wherein the preset monitoring script includes a start function, a stop function, and a monitor function.
The apparatus of any of claims 9-15, further comprising:

The module is enabled to be set to enable the virtualization function of the cloud server cluster.
A computer readable storage medium storing computer executable instructions for performing the method of establishing a connection by a cloud server cluster according to any one of claims 1-8.