One: Experimental environment
node
os
ip
san_ip
VIP
node1
rhel 6.5
192.168.10.11
172.16.1.1
192.168.10.100
node2
Rhel 6.5
192.168.10.12
172.16.1.2
san
rhel 6.5
172.16.1.3
/table>
Note:The concept of 1.corosync and pacemaker is not said here, there is a lot of information on the In
1. Environment IntroductionOS: centos 6.5Kernel: 2.6.32-431.11.2.el6.x86 _ 64Node1: nginxha001 10.0.15.31 MasterNode2: nginxha002 10.0.15.32 SlaveVip: 10.0.15.30Note: drbd is used in this example. For installation of mysql, corosync, and pacemaker programs, see other materials. Both programs must be installed. drbd resources can be copied to the other one after configuration is completed on one platform. Bo
Operation thinking: Through the DRBD to achieve data synchronization, through the Corosync+pacemaker (hereinafter referred to as CP) to detect failures and transfer, only one of the normal state of work, the other only to detect and synchronize data, when there is a failure, Server2 automatically take over all business, and synchronizing the data to another (of course, it doesn't have to sync successfully at this point ...). This is illustrated below:
Tags: pacemaker corosync pcsExperimental purpose: Using Corosync as the cluster message transaction layer (massage layer), pacemaker as the cluster resource Manager (Cluster Resource Management), PCs as a management interface tool for CRM. Requires the implementation of HTTPD's high-availability features.Environment: CentOS 6.9pacemaker:1.1.15corosync:1.47pcs:0.9.155Preparatory work:
Configure SSH
node2
192.168.3.20.node2Modify/etc/ha. d/ha. cf to add the node to the file, and modify the specific configuration node as needed:Keepalive 2Deadtime 20Inittime 120Udpport 694Bcast eth0 (your broadcast Nic, usually eth0)Auto_failback onNode node1Node node2Modify/etc/ha. d/authkeys to modify the encryption mode:Auth 11 crcModify the/etc/ha. d/authkeys attribute to 600.Modify/etc/ha. d/haresources to add an ip address for automatic drift processing:
Node1 Ipaddr: 192.168.3.169/24/eth0 mysql httpd
This article briefly describes how to configure a Fence_vmware_soap type of stonith device (test-only learning) in Rhel 7 pacemaker.Stonith is the abbreviation for Shoot-the-other-node-in-the-head, and it protects the data from corruption due to node anomalies or simultaneous access.A node unresponsive does not mean that it does not have access to data, and if it wants to be sure that the data is secure, it needs to use Stonith to isolate the node to ensure that the data is properly accessed by
managing master-slave DRBD hosts. The main use of drbdadm, because it more in line with the user's habits. Drbdsetup and Drbdmeta are less used as they are closer to the underlying device.DRBD's working features: real-time, transparent, set data synchronization typeThere are three types of data synchronization:A: Asynchronous, good performance, poor reliabilityB: Semi-synchronous performance reliability TradeoffC: Good synchronization reliability, poor performanceResource type for DRBD:Resource
Tags: haproxy mariadb pacemaker CorosyncThe highly available solution keepalived just provides the simplest high-availability features, and the truly advanced features keepalived difficult to complete. Openais specifications provide a complete solution, but a lot of the weight of many features considered comprehensive, very detailed, to understand these we can be more in-depth understanding of the complete system of high availability, when encounterin
First, install the heartbeat.Ha premise: 1, time synchronization; 2, SSH dual-machine mutual trust; 3, host name to be consistent with uname-n, and through/etc/hosts resolution; rpm-ivhepel-release-6-8.noarch.rpm #配置epel的源: yum-yinstallheartbeatcp/usr/share/doc/heartbeat-3.0.4/{ Authkeys,ha.cf,haresources}/etc/ha.d/Three configuration files: 1, key file, 600,/etc/ha.d/authkeys2, heartbeat configuration configuration of the service/etc/ HA.D/HA.CF3, resource management configuration file/etc/ha.
resource management function and cannot form a cluster independently.2, Corosync IntroductionCorosync was originally used only to demonstrate an application of the Openais Cluster Framework interface specification, which can be said to be part of the Openais, but the latter is clearly beyond the official original idea, and more and more vendors are trying to use Corosync as a cluster solution. The RHCs cluster suite, such as Redhat, is based on the Corosync implementation.Corosync only provides
650) This. width = 650; "src =" http://s3.51cto.com/wyfs02/M01/37/C6/wKioL1OvrZKw1D9-AAEDaobD9Aw534.jpg "Title =" 1.jpg" alt = "wKioL1OvrZKw1D9-AAEDaobD9Aw534.jpg"/>
Lab platform:
Centos 1, 6.4
Functions:
Use corosync + pacemaker + drbd to achieve high availability of the lamp platform, and install the discuz forum for testing.
Tutorial steps:
1,
Synchronize the hosts files of both parties and add the parsing of node6 and node7
10.32.9.56 node6
10.3
the system to find out the inconsistency or conflict between the software and the definition of the system.
Differences:
First, their test methods are different:
Unit testing is a white box test;
Integration testing is a gray-box test;
System testing is a black box testing.
Second, they have different scope of study, that is, their testing focuses are different:
Unit testing mainly tests the data structure, logic control, and exception handling within a unit;
The integration test mainly tes
1 Start the Docker service, which causes the running Docker to error if the Docker service stops, without switching2 Prepare the same image file on each node3 pcs resource Create My-docker1 docker image= "Index.alauda.cn/library/tomcat:9" name= "My-docker" run_opts= "-P 8,888:8,080 "4 Setting up PCs constraint colocation add my-docker1 VIP1 INFINITYThis article is from the "old section of the Cultivation of Life" blog, please be sure to keep this source http://031028.blog.51cto.com/9866455/18370
Corosync Introduction:
Corosync can use a simple configuration file to define the way and protocol of information delivery when passing information. It is an emerging software, launched in 2008, but in fact it is not a real sense of the new software, in 2002, there is a project Openais, it is too large, split into two subprojects, which can achieve HA heartbeat information transmission function is Corosync, its code 60% Left or right from Openais. Corosync can provide a complete ha function, bu
Corosync is used to enable multiple machines to communicate with each other (maintaining heartbeats), while pacemaker manages the entire cluster's operations on the Corosync top. Corosync is the future direction of development. In later new projects, the general use of Corosync, and Hb_gui can provide a good ha management functions, can achieve graphical management. In addition, related graphics have RHCs suite Luci+ricci.
Consistency of highly avail
Keepalived Server installation and configuration, keepalived Server0. Keepalived Introduction
Keepalived is a high-availability service solution based on VRRP protocol. It can be used to avoid IP spof. Similar Tools include heartbeat, corosync, and pacemaker. However, it generally does not appear separately, but works with other load balancing technologies (such as lvs, haproxy, and nginx) to achieve high c
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.