HeartBeat 3.0.3 Introduction and RPM

This is a reprinted article. Because the source code compiles through, but the shellfunc file is still missing, so I checked it from rpm Package installation, found this article. Combine this link:

http://www.howtoforge.com/high-availability-load- balancer-haproxy-heartbeat-fedora8

The configuration is basically done. One of the problems is that his master and slave are inverted! Try again tomorrow!

It’s not the first time I have introduced Heatbeat. You can easily install it through yum.Heartbeat 2.x, the information on the Internet (including my previous logs) has been introduced in detail< span style="margin:0px; padding:0px; color:black; background-color:rgb(255,255,102)">Heartbeat 2.x deployment method. And since February Heartbeat 3.0.2, released as the first 3.x Final Release version Later, the official website has been revised, and it is recommended to update from 2.x to 3.0.2, which makes it difficult to find links to many old configuration documents and instructions. In addition, I was triggered to consider using Heartbeat3, which is exactly what I used Heartbeat 2.1.3+DRBD+ during Oracle configuration Encountered a lot of bugs, see here. Although the problem is finally resolved, but without official support, future maintenance may encounter difficulties. For long-term consideration, using Heartbeat 3 is imperative.
Fortunately, Heartbeat 3 Comparison Heartbeat The actual difference between 2.x is not big, and you can even put Heartbeat 3 understood as Heartbeat 2.x The version after splitting into modules, and the configuration methods are similar. Therefore, the biggest difficulty encountered during actual deployment is installation. The official information provides the source code. I don’t like to deploy the software on the generation system using source code. This will cause big problems for subsequent maintenance. Through hard work, I finally successfully compiled a set of heartbeat 3.0.3 with GUI management rpm.

1. About Heartbeat 3
1. Version issues
Heartbeat The last official STABLE release 2.x version is 2.1.4.
Although Fedora, OpenSUSE and other projects have provided 2.99, 3.0, etc.rpm version, but in fact the version is based on Heartbeat 3.0 Compiled with 3.0.1 source code. At present, the Heartbeat 3 introduced in most materials on the Internet also uses this version.
Heartbeat 3 Official release The first version is 3.0.2, which is also to distinguish the 2.99 mentioned above. In addition, due to the official release of 3.0.2, the download address originally provided by OpenSUSE has also been deleted.
For more detailed information, please see: Announce: Final Release of Heartbeat 3.0.2, Cluster-Glue 1.0.2, and Resource-Agents 1.0.2.
These principlesHeartbeat 3 and 2.x is basically the same. If you have any questions, please refer to: [Original]heartbeat 2 .x infrastructure.

2, composition
Heartbeat 3 and 2 The biggest difference of .x is that 3 separates the original 2.x into multiple sub-projects by module, and provides a cluster-glue component dedicated to the management of Local ResourceManager. That is heartbeat + cluster-glue +resouce-agent three parts:

through this The three parts can form a complete HA cluster system. However, this is not enough because there are no management tools.
The original GUI tool Cluster Resource Manager (CRM for short) has also been split and taken care of by another independent project, Pacemaker. Pacemaker provides a variety of user interfaces:

more details For introduction, please see: here.
Choose one of the above user management interfaces. It should be noted that in the Cluster Stacks supported by Pacemaker, in addition to Heartbeat, OpenAIS is also supported. However, the content of OpenAIS is beyond the scope of this article and will be introduced later.

2. About rpmpackage
1, Heartbeat rpm
Heartbeat 3 Available on the official websiteHeartbeat 3.0.3, Cluster Glue 1.0.5, Resource Agents 1.0.3 source code. Download, compile and install.
If you, like me, don’t like to use source code to deploy production systems, you can use the spec in the source package to compile. When compiling, pay attention to creating the directory in the corresponding source package, the variable setting in the spec, etc., but the overall problem is not big.
Better yet, in the Install article of Pacemaker, the installation package of EPEL is provided. If your system is Asianux, RHEL, CentOS, etc., you can use the following method Installation: