At the OSI layer, there are too many protocols to be supported on Ethernet. If we need to allow Xray (a) net to support so many protocols, there is no better way to implement the plug-in. Therefore, I have considered a method to configure the plug-in through XML. The following is the description of the Protocol under Ethernet frame under my Xray @ net, the extension class of
css| Filter Xray is the meaning of x-rays.
The Xray property, as the name suggests, produces an effect that makes an object look like an X-ray. Its expression is simple:
Filter:xray
Let's take a look at a page first (figure below):
If you add the Xray attribute to the above page, that is, in
Filter:xray
If you look at this page again, it will be another
Corosync + Pacemaker build highly available Clusters
I. Overview:1.1 Introduction to AIS and OpenAISAIS application interface specification is a set of open specifications used to define application interface (API). These applications provide an open and highly portable application interface for application services as middleware. It is urgently needed to implement high-availability applications. The Service Availability Forum (SA Forum) is an open Fo
) = joinedRuntime.totem.pg.mrp.srp.members.167772173.config_version (U64) = 0Runtime.totem.pg.mrp.srp.members.167772173.ip (str) = R (0) IP (10.0.0.13)Runtime.totem.pg.mrp.srp.members.167772173.join_count (U32) = 2Runtime.totem.pg.mrp.srp.members.167772173.status (str) = joined167772172 is the member ID, its IP is 10.0.0.12, the state is joined;167772173 is the member ID, its IP is 10.0.0.13, the state is joined;Corosync Service status is correct.Start the P
Corosync: It belongs to the Openais (Open Application Interface Specification) in a project Corosync a version of itself does not have the voting function, after Corosync 2.0 introduced Votequorum subsystem also has the voting function, if we use the 1 version of the , but also need to use the votes to make the decision of how to be good, of course, in Red Hat Cman + Corosync combined with, but early cman and pacemaker can not combine, if want to use
The following commands are implemented using crm and pcs.
1. Install corosync and pacemaker with the rpm package in CentOS6.5.Yum-y install corosync pacemaker2. Configure pacemaker to run as the corosync plug-in:Add the following configuration in/etc/corosync. conf:Secauth: on # enable security authentication for communications between cluster nodesInterface {Bindnetaddr: 192.168.0.0 # specify the network a
:/etc/2, install the following RPM package:Cluster-glue,cluster-glue-libsCorosync,corosynclibHeartbeat,heartbeat-libsLibesmtpPacemaker,pacemaker-cts,pacemaker-libsResource-agents# yum Install Cluster-glue# yum Install--nogpgcheck *.rpm (copy heartbeat-3.0.4-2.el6.i686.rpm and heartbeat-libs-3.0.4-2.el6.i686.rpm to the home directory)# yum Install Corosync# yum-y Install LIBESMTP# Yum Install
First, the concept of pacemaker(1) Pacemaker (pacemaker), is a highly available cluster resource manager. It achieves maximum availability of resource management for node and resource level fault detection and recovery by using the message and member capabilities provided by the preferred cluster infrastructure (Corosync or heartbeat). It monitors and recovers no
0. IntroductionAs a member management layer (membership layer) in Ha scheme, Corosync is responsible for the functions of cluster member management, communication mode (unicast, broadcast, multicast), pacemaker as the CRM layer. In the practice of using Corosync +pacemaker, the problemof brain fissure is encountered. What is brain fissure: in HA cluster, the network communication between nodes through the h
commercial or open-source clusters. Currently Corosync is divided into 1 versions and 2 versions, 1 does not have a voting function, and the 2 version has a voting function.Pacemaker OverviewPacemaker OverviewPacemaker is a cluster resource manager that leverages the message and member capabilities provided by the preferred cluster infrastructure (OpenAIS or heartbeat) for fault detection and recycling by secondary nodes and systems, enabling high availability of clustered services (also known
Linux Corosync + Pacemaker
Complete HA structure:
Install and configure a high-availability cluster:1. node name: the names of each node in the cluster must be resolved to each other./Etc/hostsIn hosts, the forward and reverse resolution results of the host name must be consistent with those of "uname-n;2. Time must be synchronizedUse Network Time Server synchronization time3. Not required: each node can communicate with each other through ssh key au
The version of the Pacemaker cluster configuration. About the version of the Pacemaker cluster configuration, CIB in Pacemaker has a version composed of admin_epoch, epoch, and num_updates. when a node is added to the cluster, the version number is used, obtain the version of the Pacemaker cluster.
In
Pacemaker: Pacemaker, is a cluster resource manager. It achieves maximum availability for Cluster service node and resource level failure detection and recovery using the messaging and membership capabilities of the preferred cluster infrastructure.Pacemaker is a resource manager and does not provide heartbeat information.heartbeat3.0 components after splitting:Heartbeat: The original message communication
resource or master resource;
Master-max: the maximum number of clone resources that can be defined as primary resources. The default value is 1;
Master-node-max: Maximum number of clone resources on each node can be promoted to the master resource. The default value is 1;
Check whether corosync, pacemaker, crmsh, and pssh are installed in node1 and node2.
[Root @ node1 ~] # Rpm-q corosync pacemaker crmsh p
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
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.