Re: [Pacemaker] large cluster - failure recovery
On 04/11/15 18:41, Radoslaw Garbacz wrote: > Details: > OS: CentOS 6 > Pacemaker: Pacemaker 1.1.9-1512.el6 > Corosync: Corosync Cluster Engine, version '2.3.2' yum update Pacemaker is currently 1.1.12 and corosync 1.4.7 on CentOS 6. There were major improvements in speed with later versions of pacemaker. Trevor ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Some questions on the currenct state
On 12/01/15 15:09, Andreas Mock wrote: Hi all, almost allways when I'm forced to do some major upgrades to our core machines in terms of hardware and/or software (OS) I'm forced to have a look at the current state of pacemaker based HA. Things are going on and things change. Projects converge and diverge, tool(s)/chains come and go and distributions marketing strategies change. Therefor I want to ask the following question in the hope list members deeply involved can answer easily. 1) Are there pacemaker packages für RHEL 6.6 and clones? When yes where? In the CentOS (etc) base/updates repos. For RHEL they're in the HA channel. 2) How can I create a pacemaker package 1.1.12 on my own from the git sources? It's already in base/updates. 3) How can I get the current versions of pcs and/or crmsh? Is pcs competitive to crmsh meanwhile? pcs is in el6.6 and now includes pcsd. You can get crmsh from an opensuse build repo for el6. 4) Is the pacemaker HA solution of RHEL 7.x still bound to use of cman? No 5) Where can I find a currenct workable version of the agents for RHEL 6.6 (and clones) and RHEL 7.x? Probably you want the resource-agents package. T ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] pacemaker with CMAN on RHEL 6.5
And you have to manually copy /etc/cluster/cluster.conf from the first node to the others... On 16/06/14 17:10, Digimer wrote: You need to setup a skeleton cluster.conf file. You can use the 'ccs' tool, here is an example (I use for my cluster, adjust the names to suit): ccs -f /etc/cluster/cluster.conf --createcluster an-anvil-04 ccs -f /etc/cluster/cluster.conf --setcman two_node=1 expected_votes=1 ccs -f /etc/cluster/cluster.conf --addnode an-a04n01.alteeve.ca ccs -f /etc/cluster/cluster.conf --addnode an-a04n02.alteeve.ca ccs -f /etc/cluster/cluster.conf --addfencedev pcmk agent=fence_pcmk ccs -f /etc/cluster/cluster.conf --addmethod pcmk-redirect an-a04n01.alteeve.ca ccs -f /etc/cluster/cluster.conf --addmethod pcmk-redirect an-a04n02.alteeve.ca ccs -f /etc/cluster/cluster.conf --addfenceinst pcmk an-a04n01.alteeve.ca pcmk-redirect port=an-a04n01.alteeve.ca ccs -f /etc/cluster/cluster.conf --addfenceinst pcmk an-a04n02.alteeve.ca pcmk-redirect port=an-a04n02.alteeve.ca ccs -f /etc/cluster/cluster.conf --setfencedaemon post_join_delay=30 hth On 16/06/14 07:13 AM, Thanachit Wichianchai wrote: Hello Pacemaker guys, I am doing a proof of concept of active/passive HA cluster on RHEL 6.5 Since the customer who I am working for will finally get support from Red Hat. Therefore, I am trying to comply with Red Hat Documentation. as stated in several places that on RHEL 6.5 - pacemaker is now supported with CMAN stack. I started configuring things by following steps describe in https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Configuring_the_Red_Hat_High_Availability_Add-On_with_Pacemaker/ap-configfile-HAAR.html document. This document provides configuration steps by using pcs command. no ccs or crmsh commands at all. After I have created cluster. I can start cluster services on node1 but cannot start it on node2 - there error is /etc/cluster/cluster.conf is not there on node2 pcs cluster start Starting Cluster... Starting cluster: Checking if cluster has been disabled at boot...[ OK ] Checking Network Manager... [ OK ] Global setup...[ OK ] Loading kernel modules...[ OK ] Mounting configfs... [ OK ] Starting cman... xmlconfig cannot find /etc/cluster/cluster.conf [FAILED] Stopping cluster: Leaving fence domain... [ OK ] Stopping gfs_controld... [ OK ] Stopping dlm_controld... [ OK ] Stopping fenced... [ OK ] Stopping cman... [ OK ] Unloading kernel modules... [ OK ] Unmounting configfs...[ OK ] Error: unable to start cman pcs cluster status command output on node1 shows cman stack pcs cluster status Cluster Status: Last updated: Mon Jun 16 15:31:53 2014 Last change: Mon Jun 16 14:23:04 2014 via crmd on rhcs1.localdomain Stack: cman Current DC: rhcs1.localdomain - partition with quorum Version: 1.1.10-14.el6-368c726 2 Nodes configured 0 Resources configured PCSD Status: Error: no nodes found in corosync.conf but from the aforementioned document from Red Hat. the stack is corosync. [root@z1 ~]#*|pcs cluster status|* Cluster Status: Last updated: Thu Jul 25 13:01:26 2013 Last change: Thu Jul 25 13:04:45 2013 via crmd onz2.example.com http://z2.example.com Stack: corosync Current DC:z2.example.com http://z2.example.com (2) - partition with quorum Version: 1.1.10-5.el7-9abe687 2 Nodes configured 0 Resources configured from the 2 incidents above, I am not sure whether I am on the right path. My PoC objectives are to 1. configure Active/Passive HA cluster on RHEL 6.5 2. Get Full Support from Red Hat on both OS and High Availability Add-on 3. choose HA Cluster software and stacks which has a future. I expect to have more than 5 years support from Red Hat and Community. I found this quick start guide for redhat on cluster labshttp://clusterlabs.org/quickstart-redhat.html I am not sure whether I should use ccs command to create cluster first and use pcs to manage resource. on more question, I see corosync will be supported in RHEL7. Can I use only corosync with pacemaker in RHEL 6.5? Will I get support from Red Hat ? Could you guys please help advise? Thanks a lot. -- Thanachit Wichianchai / IT Specialist - RHCSA, RHCE +66 87 696 5522/ thanachit [at] acm.org mailto:thanachit%20[at]%20acm.org http://hi.im/thanachit Google Plus https://plus.google.com/u/0/102459307371925233265/posts Linkedin http://th.linkedin.com/in/thanachit ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started:
Re: [Pacemaker] pacemaker depdendancy on samba
On 12/03/14 23:18, Alex Samad - Yieldbroker wrote: Hi Just going through my cluster build, seems like yum install pacemaker wants to bring in samba, I have recently migrated up to samba4, wondering if I can find a pacemaker that is dependant on samba4 ? Im on centos 6.5, on a quick look I am guessing this might not be a pacemaker issue, might be a dep of a dep .. Pacemaker wants to install resource-agents, resource-agents has a dependency on /sbin/mount.cifs and then it goes on from there... T ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Announce: Pacemaker 1.1.10 now available
On 30/07/13 02:51, Andrew Beekhof wrote: [k.proskurin@video-build libqb]$ ./autogen.sh autoreconf: Entering directory `.' autoreconf: configure.ac: not using Gettext autoreconf: running: aclocal -I m4 configure.ac:4: error: Autoconf version 2.61 or higher is required autoconf-2.59-12 Dead end. Create the srpm for libqb on rhel6, then pass it to rpmbuild on rhel5 Also the IUS Community repo has autoconf26x-2.63-4.ius.centos5.noarch package that might be useful... T ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Dnsmasq
I'd guess that your replies are going back with the wrong source IP address on them and the Windows clients are being picky about accepting them. Perhaps you need to investigate ocf:heartbeat:IPsrcaddr On 24/03/12 01:35, Gregg Stock wrote: I'm have some interesting behavior with a pacemaker managed DNS server. Here is the basic setup: primitive p_dnsmasq lsb:dnsmasq \ op monitor interval=60s timeout=30s primitive p_ip_dnsmasq ocf:heartbeat:IPaddr2 \ params ip=192.168.1.250 cidr_netmask=24 \ op monitor interval=10s order o_ip_before_dns inf: p_ip_dnsmasq p_dnsmasq The cluster seems to manage the resource ok. If the dnsmasq server is running on the hosts regular ip address, everything is fine. When switching to the cluster managed ip address, I get the following behavior on our network. The behavior was the same for various permutation of the listening addresses in the dnsmasq.conf file. 1. Linux hosts are fine. 2. Windows and Mac hosts can ping the DNS server but don't get DNS service. I was able to verify that the requests were getting to the DNS server but the replies were getting and ICMP destination unreachable on the way back. I was able fine a tidbit of information here http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2010q2/003906.html A destination unreachable ICMP reply is normally generated by the kernel when there is nothing listening on that port. The most likely reason for that is that the dnsmasq process no longer exists. If that's the case the problem changes into find why the dnsmasq daemon is exiting. This doesn't seem to be completely applicable because the dnsmasq daemon is running. Any additional information required? Thanks in advance. Best regards, Gregg Stock ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] MySQL Master-Master replication with Corosync and Pacemaker
Peter Scott wrote: Here's the detail: We have two MySQL comasters (each is a master and a slave of the other). Traffic needs to arrive at only one machine at a time because otherwise conflicting simultaneous updates at each machine would cause a problem. If this is true then your database design needs to be fixed. If all tables have auto_increment columns and you add the parameters auto_increment_increment= and auto_increment_offset= to /etc/my.cnf then simultaneous updates can be made from both machines. -- Voiceflex Tel 0203 301 6000 | Fax 0203 310 6700 http://getsatisfaction.com/voiceflex www.voiceflex.com Information contained in this e-mail is intended for the use of the addressee(s) only and is confidential. If you are not an addressee, note that any disclosure, copying, distribution, or use of the contents of this message is strictly prohibited. If you have received this e-mail in error, please contact the firm at +44 (0) 20 3301 6000 or supp...@voiceflex.com. Any views or opinions expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Frontier Systems Ltd. Frontier Systems Ltd does not accept legal responsibility for this e-mail message due to the insecure nature of internet communications. Frontier Systems, 9 Warwick Street, London W1B 5LY Registered in England and Wales, No. 03544845 ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Syntax highlighting in vim for crm configure edit
Patrick H. wrote:
Sent: Tue Nov 15 2011 02:47:59 GMT-0700 (MST)
From: Raoul Bhatia [IPAX] r.bha...@ipax.at
To: The Pacemaker cluster resource manager
pacemaker@oss.clusterlabs.org
Subject: Re: [Pacemaker] Syntax highlighting in vim for crm configure
edit
hi!
On 2011-08-19 16:28, Dan Frincu wrote:
Hi,
On Thu, Aug 18, 2011 at 5:53 PM, Digimerli...@alteeve.com wrote:
On 08/18/2011 10:39 AM, Trevor Hemsley wrote:
Hi all
I have attached a first stab at a vim syntax highlighting file for
'crm
configure edit'
To activate this, I have added 'filetype plugin on' to my
/root/.vimrc
then created /root/.vim/{ftdetect,ftplugin}/pcmk.vim
In /root/.vim/ftdetect/pcmk.vim I have the following content
au BufNewFile,BufRead /tmp/tmp* set filetype=pcmk
but there may be a better way to make this happen.
/root/.vim/pcmk.vim
is the attached file.
Comments (not too nasty please!) welcome.
I've added a couple of extra keywords to the file, to cover a couple
more use cases. Other than that, great job.
will this addition make it into some package(s)?
would it be right to ship this vim syntax file with crm?
thanks,
raoul
Gave this syntax file a shot and I dont think it should be included in
the standard package. Its very colorful, but it breaks too many
standard highlighting conventions.
* The 'node' keyword doesnt gets highligted with a different color
than 'primitive', 'property', etc
* The names of primitives, clones, etc should be highlighed with
Identifier not Type
* The primitive type (ocf:hearbeat:whatever) should be Normal
* Chars like '=' '\' ':' should not be assigned a color (Normal
or left alone)
* Colors of weights are assigned different colors when used in
location rules and colocation/order rules. These should get the
same color policy, and should also be something other than String.
The color output you get from 'configure show' should be what vim
looks like, or very close to it.
You are welcome to amend it as you see fit and submit your version to
the list!
From my POV, 'colorful' is better than black and white which is the
current alternative.
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] [PATCH] Building on Centos 5.7 fails
Andrew Beekhof wrote: On Sat, Oct 15, 2011 at 1:46 AM, Trevor Hemsley thems...@voiceflex.com wrote: Hi I've just built pacemaker 1.1.6 on CentOS 5.7 with the aid of the attached patches. Not sure if the methods I've used are correct but it does now build and produce a series of RPMs which is more than it did before. Files affected: configure.ac - had to rename PKG_FEATURES - PCMK_FEATURES to avoid an autoconf error. Not sure what changed between 1.1.5 and .6 but this was OK before. doc/Makefile.am - added the -L option to a2x to avoid an error about being unable to fetch the dtd file for crm.8. Am more surprised that it works on other distros since the xmllint that a2x calls specifies --nonet pacemaker.spec diff to pull in the patch and to define other stuff that doesn't exist on el5 like _initddir and override the docdir. Also, ./configure on el5 does not like --docdir= I've applied the rest, but the spec file part looks odd. The original doesn't seem to match what was in Git. That was a diff against the Fedora 15 spec file. Maybe that's different to the one in git. -- Trevor Voiceflex www.voiceflex.com ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
[Pacemaker] [PATCH] Building on Centos 5.7 fails
Hi I've just built pacemaker 1.1.6 on CentOS 5.7 with the aid of the attached patches. Not sure if the methods I've used are correct but it does now build and produce a series of RPMs which is more than it did before. Files affected: configure.ac - had to rename PKG_FEATURES - PCMK_FEATURES to avoid an autoconf error. Not sure what changed between 1.1.5 and .6 but this was OK before. doc/Makefile.am - added the -L option to a2x to avoid an error about being unable to fetch the dtd file for crm.8. Am more surprised that it works on other distros since the xmllint that a2x calls specifies --nonet pacemaker.spec diff to pull in the patch and to define other stuff that doesn't exist on el5 like _initddir and override the docdir. Also, ./configure on el5 does not like --docdir= -- Trevor Voiceflex www.voiceflex.com pcmk116-rhel5.tar.bz2 Description: application/bzip ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
Re: [Pacemaker] using ip route change with pacemaker
ge...@riseup.net wrote: crm ra info ocf:heartbeat:Route man ocf_heartbeat_Route Feel free to also tell the author of that howto. :) Actually I'm using this command already for the extern ip to connect to my provider. I had for days the problem with the internal ip for the phones, these registering on the virtual ip, but getting aswer from the main-ip associated to the nic. Maybe what you want is ocf:heartbeat:IPsrcaddr -- Voiceflex www.voiceflex.com ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
Re: [Pacemaker] Reloading a resource after a failover
Max Williams wrote:
Hi,
I have a pair of clustered DNS servers with a virtual IP (VIP) configured. The
problem is that when the VIP fails over, named on the new host of the VIP will
not listen on port 53/UDP of the VIP until it is reloaded (I think this is
because this daemon uses UDP, not TCP).
So I'd like to be able to reload named after a failover of the VIP address. Is
this possible?
I could do it by configuring named as a cloned resource and then configuring an
order so that it is restarted when the VIP fails over or moves but I would much
rather have named reload instead of restart.
Any ideas? I'd rather not have to resort to a wrapper script or anything like
that.
This seems to be a design decision on the part of the bind authors.
There is a parameter
options { interface-interval 1; };
that can be set (in minutes, lowest is 1 minute because 0 disables it)
to have bind rescan for new interfaces on the machine.
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
Re: [Pacemaker] migration fix for ocf:heartbeat:Xen
Daugherity, Andrew W wrote: Message: 7 Date: Thu, 11 Aug 2011 21:07:00 + From: Daugherity, Andrew W adaugher...@tamu.edu To: pacemaker@oss.clusterlabs.org pacemaker@oss.clusterlabs.org Subject: [Pacemaker] migration fix for ocf:heartbeat:Xen Message-ID: 93b5e618-ad19-4993-8066-cb4f8e4ef...@tamu.edu Content-Type: text/plain; charset=us-ascii I have discovered that sometimes when migrating a VM, the migration itself will succeed, but the migrate_from call on the target node will fail, as apparently the status hasn't settled down yet. This is more likely to happen when stopping pacemaker on a node, causing all its VMs to migrate away. Migration succeeds, but then (sometimes) the status call in migrate_from fails, and the VM is unnecessarily stopped and started. Note that it is NOT a timeout problem, as the migrate_from operation (which only checks status) takes less than a second. I noticed the VirtualDomain RA does a loop rather than just checking the status once as the Xen RA does, so I patched a similar thing into the Xen RA, and that solved my problem. (patch/logs snipped) No comments? What does it take to get this patch accepted? I'd much rather use the mainline version than have to reapply my patch after every HAE update. I guess I could open an SR with Novell but this is ultimately an upstream issue. I don't know about getting the patch accepted but since I've seen issues like the one you describe on my systems, I have applied your patch (Thanks!) and will see how it behaves. -- Voiceflex Tel 0203 301 6000 | Fax 0203 310 6700 http://getsatisfaction.com/voiceflex www.voiceflex.com Information contained in this e-mail is intended for the use of the addressee(s) only and is confidential. If you are not an addressee, note that any disclosure, copying, distribution, or use of the contents of this message is strictly prohibited. If you have received this e-mail in error, please contact the firm at +44 (0) 20 3301 6000 or supp...@voiceflex.com. Any views or opinions expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Frontier Systems Ltd. Frontier Systems Ltd does not accept legal responsibility for this e-mail message due to the insecure nature of internet communications. Frontier Systems, 9 Warwick Street, London W1B 5LY Registered in England and Wales, No. 03544845 ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
[Pacemaker] Syntax highlighting in vim for crm configure edit
Hi all
I have attached a first stab at a vim syntax highlighting file for 'crm
configure edit'
To activate this, I have added 'filetype plugin on' to my /root/.vimrc
then created /root/.vim/{ftdetect,ftplugin}/pcmk.vim
In /root/.vim/ftdetect/pcmk.vim I have the following content
au BufNewFile,BufRead /tmp/tmp* set filetype=pcmk
but there may be a better way to make this happen. /root/.vim/pcmk.vim
is the attached file.
Comments (not too nasty please!) welcome.
--
Voiceflex
Tel 0203 301 6000 | Fax 0203 310 6700
http://getsatisfaction.com/voiceflex
www.voiceflex.com
Information contained in this e-mail is intended for the use of the
addressee(s) only and is confidential. If you are not an addressee, note that
any disclosure, copying, distribution, or use of the contents of this message
is strictly prohibited. If you have received this e-mail in error, please
contact the firm at +44 (0) 20 3301 6000 or supp...@voiceflex.com. Any views
or opinions expressed in this message are those of the individual sender,
except where the sender specifically states them to be the views of Frontier
Systems Ltd. Frontier Systems Ltd does not accept legal responsibility for this
e-mail message due to the insecure nature of internet communications. Frontier
Systems, 9 Warwick Street, London W1B 5LY Registered in England and Wales, No.
03544845
Vim syntax file
Language: pcmk
Filenames:*.pcmk
For version 5.x: Clear all syntax items
For version 6.x: Quit when a syntax file was already loaded
if version 600
syntax clear
elseif exists(b:current_syntax)
finish
endif
setlocal iskeyword+=-
Errors
syn matchpcmkParErr )
syn matchpcmkBrackErr ]
syn matchpcmkBraceErr }
Enclosing delimiters
syn region pcmkEncl transparent matchgroup=pcmkParEncl start=(
matchgroup=pcmkParEncl end=) contains=ALLBUT,pcmkParErr
syn region pcmkEncl transparent matchgroup=pcmkBrackEncl start=\[
matchgroup=pcmkBrackEncl end=\] contains=ALLBUT,pcmkBrackErr
syn region pcmkEncl transparent matchgroup=pcmkBraceEncl start={
matchgroup=pcmkBraceEncl end=} contains=ALLBUT,pcmkBraceErr
Comments
syn region pcmkComment start=// end=$ contains=pcmkComment,pcmkTodo
syn region pcmkComment start=/\* end=\*/ contains=pcmkComment,pcmkTodo
syn keyword pcmkTodo contained TODO FIXME XXX
Strings
syn region pcmkStringstart=++ skip=+\|\\+ end=++
General keywords
syn keyword pcmkKeyword node primitive property nextgroup=pcmkName skipwhite
syn keyword pcmkKey2 location nextgroup=pcmkResource skipwhite
syn keyword pcmkKey3 colocation order nextgroup=pcmkName3 skipwhite
syn match pcmkResource /\\f\+\/ nextgroup=pcmkName2 skipwhite
syn match pcmkName /\\f\+\/
syn match pcmkName2 /\\f\+\/ nextgroup=pcmkPrio skipwhite
syn match pcmkName3 /\\f\+\/ nextgroup=pcmkPrio skipwhite
syn match pcmkPrio /\\w\+\/
Graph attributes
syn keyword pcmkType attributes params op meta
syn keyword pcmkTag monitor start stop
Special chars
syn matchpcmkKeyChar =
syn matchpcmkKeyChar ;
syn matchpcmkKeyChar -
Identifier
syn matchpcmkIdentifier /\\w\+\/
syn matchpcmkKeyword ^ms\s* nextgroup=pcmkName skipwhite
Synchronization
syn sync minlines=50
syn sync maxlines=500
Define the default highlighting.
For version 5.7 and earlier: only when not done already
For version 5.8 and later: only when an item doesn't have highlighting yet
if version = 508 || !exists(did_pcmk_syntax_inits)
if version 508
let did_pcmk_syntax_inits = 1
command -nargs=+ HiLink hi link args
else
command -nargs=+ HiLink hi def link args
endif
HiLink pcmkParErr Error
HiLink pcmkBraceErrError
HiLink pcmkBrackErrError
HiLink pcmkComment Comment
HiLink pcmkTodoTodo
HiLink pcmkParEncl Keyword
HiLink pcmkBrackEncl Keyword
HiLink pcmkBraceEncl Keyword
HiLink pcmkKeyword Keyword
HiLink pcmkKey2Keyword
HiLink pcmkKey3Keyword
HiLink pcmkTypeKeyword
HiLink pcmkKeyChar Keyword
HiLink pcmkString String
HiLink pcmkIdentifier Identifier
HiLink pcmkTag Tag
HiLink pcmkName Type
HiLink pcmkName2 Tag
HiLink pcmkName3 Type
HiLink pcmkResource Type
HiLink pcmkPrio Number
delcommand HiLink
endif
let b:current_syntax = pcmk
vim: ts=8
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
