[Pacemaker] High context switches

2009-11-03 Thread Andreas Zafiris 
Hello,

Please forgive me if this has already been discussed...
I have a pacemaker+openais setup of 2 Debian amd64 machines (IBM x3550, 2 Xeon 
2.5GHz, 6GB Ram) with the following openais.conf:

Kernel: 2.6.26-2-amd64
Pacemaker-openais version: 1.0.5+hg20091012-1~bpo50+1

--- BEGIN openais.conf

otem {
version: 2
token: 3000
token_retransmits_before_loss_const: 10
join: 60
consensus: 1500
vsftype: none
max_messages: 20
clear_node_high_bit: yes
secauth: off
threads: 0
rrp_mode: none
interface {
# The following values need to be set based on your environment
ringnumber: 0
bindnetaddr: 10.10.1.0
mcastaddr: 226.94.1.1
mcastport: 5405
}
}

logging {
to_stderr: yes
debug: off
timestamp: on
to_file: no
to_syslog: yes
syslog_facility: daemon
}

amf {
mode: disabled
}

service {
ver:   0
name:  pacemaker
use_mgmtd: yes
}

aisexec {
user:   root
group:  root
}

--- END openais.conf

Has anyone had high context switches (as seen in vmstat)

procs ---memory-- ---swap-- -io -system-- cpu
 r  b   swpd   free   buff  cache   si   sobibo   in   cs us sy id wa
 1  0  0 3193472 2570928 15659200 1 06   11  0  1 99  0
 0  0  0 3193692 2570928 15659200 020   62 18953  0  1 99  0
 0  0  0 3193628 2570928 15659200 0 0   35 19088  0  1 99  0
 0  0  0 3193184 2570928 15659200 0 0   48 19049  0  1 99  0
 0  0  0 3193792 2570928 15659200 0 0   41 18947  0  1 99  0
 0  0  0 3193828 2570928 15659200 0 0   46 19105  0  1 99  0
 1  0  0 3192480 2570928 15659200 0 0   45 19087  0  1 99  0
 0  0  0 3193196 2570928 15659200 0 0   27 18930  0  1 99  0

This is the behaviour I see while the system is idle. Please note that the 
system with openais-legacy stopped, stays around 500 cs

Is this normal?

Thanks,

Andreas

___
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Re: [Pacemaker] High context switches

2009-11-03 Thread Raoul Bhatia [IPAX] 
On 11/03/2009 09:17 AM, Andreas Zafiris wrote:
> Hello,
> 
> Please forgive me if this has already been discussed...
> I have a pacemaker+openais setup of 2 Debian amd64 machines (IBM x3550, 2 
> Xeon 2.5GHz, 6GB Ram) with the following openais.conf:
> 
> Kernel: 2.6.26-2-amd64
> Pacemaker-openais version: 1.0.5+hg20091012-1~bpo50+1

*SNIP*

> This is the behaviour I see while the system is idle. Please note that the 
> system with openais-legacy stopped, stays around 500 cs
> 
> Is this normal?

might this be related to this thread:
http://www.gossamer-threads.com/lists/linuxha/pacemaker/58296#58296 ?

cheers,
raoul
-- 

DI (FH) Raoul Bhatia M.Sc.  email.  r.bha...@ipax.at
Technischer Leiter

IPAX - Aloy Bhatia Hava OEG web.  http://www.ipax.at
Barawitzkagasse 10/2/2/11   email.off...@ipax.at
1190 Wien   tel.   +43 1 3670030
FN 277995t HG Wien  fax.+43 1 3670030 15


___
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Re: [Pacemaker] enable to run crm line command

2009-11-03 Thread ROUAMBA Halidou 
I tried to install python 2.4 but i faced to a lot of dependencies that i
can't résolve.
I don't have a active suscription on RHN.
I looked towards many Forum and it recommand me to upgrade my OS to RHEL AS
5 because *The dependencies can often be re-written for the older OS. But
you're seriously imperiling your **operating system** doinig this, because a
*lot* of components like Yum rely on Python.*
*See the below url.*
http://linux.derkeiler.com/Newsgroups/linux.redhat/2008-02/msg00085.html




2009/11/2 ROUAMBA Halidou 

> Ok Dejan, i shall try to upgrade my python version to 2.4 and i shall make
> you know the result
>
> thanks
>
> RH
>
>
> Pablo Picasso 
> - "Computers are useless. They can only give you answers."
>
> 2009/11/2 Dejan Muhamedagic 
>
>> Hi,
>>
>> On Mon, Nov 02, 2009 at 03:32:07PM +0100, ROUAMBA Halidou wrote:
>> > Thanks for your help, but another error is generated after adding the
>> > bracket
>> > see the below output.
>> > [*r...@omconi2 packages]# crm*
>> > *Traceback (most recent call last):*
>> > *  File "/usr/sbin/crm", line 24, in ?*
>> > *import subprocess*
>> > *ImportError: No module named subprocess*
>>
>> subprocess is available as of version 2.4. Version 2.3 is really
>> old. Can you upgrade to something more recent?
>>
>> Thanks,
>>
>> Dejan
>>
>> > i look closely in the crm file but this line exist at the line number 24
>> > *import subprocess*
>> > *
>> > *
>> > Thanks.
>> >
>> > 2009/11/2 Dejan Muhamedagic 
>> >
>> > > Hi,
>> > >
>> > > On Mon, Nov 02, 2009 at 01:53:13PM +0100, ROUAMBA Halidou wrote:
>> > > > Marie von Ebner-Eschenbach<
>> > >
>> http://www.brainyquote.com/quotes/authors/m/marie_von_ebnereschenbac.html
>> >
>> > > > - "Even a stopped clock is right twice a day."
>> > > >
>> > > > 2009/11/2 Dejan Muhamedagic 
>> > > >
>> > > > > Hi,
>> > > > >
>> > > > > On Sun, Oct 25, 2009 at 01:07:40PM +0100, ROUAMBA Halidou wrote:
>> > > > > > Hello
>> > > > > >
>> > > > > > I just install the last version of pacemaker and i used hearbeat
>> as
>> > > > > cluster
>> > > > > > stacks.
>> > > > > > The installation has been made on RHEL AS4.6.
>> > > > > > i didn't have any error during the rpm installation.
>> > > > > > The /etc/ha.d/ha.cf et /etc/ha.d/authkeys have been correctly
>> > > > > configured.
>> > > > > > The problem occured when i tried to use crm line command to
>> configure
>> > > the
>> > > > > > CIB file for resource management.
>> > > > > > so this is the outpout of the crm .[
>> > > > > > *r...@omconi2 ~]# crm
>> > > > > >   File "/usr/sbin/crm", line 4576
>> > > > > > for obj in processing_sort_cli(self.obj_list))
>> > > > > >   ^
>> > > > > > SyntaxError: invalid syntax*
>> > > > >
>> > > > > Can't recall seeing this one.
>> > > > >
>> > > > > Which version of pacemaker do you run:
>> > > > >
>> > > > > /usr/lib/heartbeat/crmd version
>> > > > >
>> > > > [*r...@omconi1 packages]# /usr/lib/heartbeat/crmd version*
>> > > > *CRM Version: 1.0.5 (462f1569a43740667daf7b0f6b521742e9eb8fa7)*
>> > > >
>> > > >
>> > > > > And which version of python?
>> > > > >>
>> > > > >> *[r...@omconi1 packages]# python -V*
>> > > > >
>> > > > > *Python 2.3.4*
>> > >
>> > > Don't know, perhaps that is too old. Can you try to replace the
>> > > existing lines:
>> > >
>> > >return '\n'.join(obj.repr_cli() \
>> > > for obj in processing_sort_cli(self.obj_list))
>> > >
>> > > with
>> > >
>> > >return '\n'.join([obj.repr_cli() \
>> > >for obj in processing_sort_cli(self.obj_list)])
>> > >
>> > > Thanks,
>> > >
>> > > Dejan
>> > >
>> > > > >
>> > > > Version of redhat ?
>> > > >
>> > > > > *[r...@omconi1 packages]# cat /etc/redhat-release*
>> > > > > *Red Hat Enterprise Linux AS release 4 (Nahant Update 6)*
>> > > > > *[r...@omconi1 packages]# uname -r*
>> > > > > *2.6.9-67.0.7.ELsmp*
>> > > > >
>> > > > >
>> > > > The rpm have been downloading from this url
>> > > >
>> > >
>> http://download.opensuse.org/repositories/server:/ha-clustering/RHEL_4/i386/
>> > > >
>> > > >
>> > > > >  Thanks,
>> > > > >
>> > > > > Dejan
>> > > > >
>> > > > > > The same error.occurs on both nodes
>> > > > > >
>> > > > > > I see that crm is writed in python language, i'm a newbie in
>> python
>> > > > > >
>> > > > > > if any has faced this problem and could help me,
>> > > > > > I thank him very much.
>> > > > > >
>> > > > > > thanks for  taking a look at my problem
>> > > > > >
>> > > > > > Best regards.
>> > > > > >
>> > > > > > Pablo Picasso<
>> > > > > http://www.brainyquote.com/quotes/authors/p/pablo_picasso.html>
>> > > > > > - "Computers are useless. They can only give you answers."
>> > > > >
>> > > > > > ___
>> > > > > > Pacemaker mailing list
>> > > > > > Pacemaker@oss.clusterlabs.org
>> > > > > > http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>> > > > >
>> > > > >
>> > > > > ___

[Pacemaker] open sorce san

2009-11-03 Thread er krishna 
Dear All,

I have written a article with complete how to which describes following
things :

Making of open source HA SAN :

An article which describes and making of HA SAN with AoE, heartbeat and
DRBD. I mean it contains a complete how to of integration of DRBD, heartbeat
and AoE targets and initiators.


I want to keep it on the clusterlabs website. Can anybody help me to review
it and putting it on clusterlabs site.

PS : Of course pacemaker is the better one and I am trying to add it in my
next how to. Heartbeat is also good and it seves the purpose between two
nodes.


Thanks and Best regards,
Krishna
___
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Re: [Pacemaker] yum update fails

2009-11-03 Thread er krishna 
Dear Andrew,

I have some good how to about SAN and HA. Can you please review my documents
and help me to put it on your site. Please tell if you can find sometime for
its review and help me to help others on FOSS.

Best regards,
Krishna

On Mon, Nov 2, 2009 at 7:17 PM, Andrew Beekhof  wrote:

> Ah, looks like I'm missing an Obsoletes: for pacemaker-libs.
> I'll fix that in while I'm updating the packages (now-ish)
>
> On Sat, Oct 31, 2009 at 12:16 AM, Donna Livingstone
>  wrote:
> > On Oct 19/20th I installed openais on a test RHEL5.4 install
> > successfully(yum install -y "openais = 0.80.5" pacemaker).
> > Today(Oct 30th) I attempted an update and it failed(see below).
> > Looks like libpacemaker3 is in conflict and is now gone from the
> > opensuse repository.
> >
> >
> > [r...@wispoller2 drbd-8.3.5]# yum --disablerepo=rhel-i386-server-5
> update
> > Loaded plugins: rhnplugin, security
> > Skipping security plugin, no data
> > Setting up Update Process
> > Resolving Dependencies
> > Skipping security plugin, no data
> > --> Running transaction check
> > ---> Package cluster-glue.i386 0:1.0-12.1 set to be updated
> > ---> Package cluster-glue-libs.i386 0:1.0-12.1 set to be updated
> > ---> Package heartbeat.i386 0:3.0.0-33.2 set to be updated
> > ---> Package libopenais2.i386 0:0.80.5-15.1 set to be updated
> > ---> Package openais.i386 0:0.80.5-15.1 set to be updated
> > ---> Package pacemaker.i386 0:1.0.5-4.1 set to be updated
> > --> Processing Dependency: pacemaker-libs = 1.0.5-4.1 for package:
> pacemaker
> > ---> Package pacemaker-mgmt.i386 0:1.99.2-6.1 set to be updated
> > ---> Package pacemaker-mgmt-client.i386 0:1.99.2-6.1 set to be updated
> > ---> Package resource-agents.i386 0:1.0-31.4 set to be updated
> > --> Running transaction check
> > ---> Package pacemaker-libs.i386 0:1.0.5-4.1 set to be updated
> > --> Finished Dependency Resolution
> >
> > Dependencies Resolved
> >
> >
> ==
> > Package Arch
> >   Version  Repository
> >Size
> >
> ==
> > Installing:
> > cluster-gluei386
> >   1.0-12.1 server_ha-clustering
> >   1.2 M
> > replacing  heartbeat-common.i386 2.99.2-8.1
> >
> > cluster-glue-libs   i386
> >   1.0-12.1 server_ha-clustering
> >   1.1 M
> > replacing  libheartbeat2.i386 2.99.2-8.1
> >
> > resource-agents i386
> >   1.0-31.4 server_ha-clustering
> >   184 k
> > replacing  heartbeat-resources.i386 2.99.2-8.1
> >
> > Updating:
> > heartbeat   i386
> >   3.0.0-33.2   server_ha-clustering
> >   1.5 M
> > libopenais2 i386
> >   0.80.5-15.1  server_ha-clustering
> >   431 k
> > openais i386
> >   0.80.5-15.1  server_ha-clustering
> >   436 k
> > pacemaker   i386
> >   1.0.5-4.1server_ha-clustering
> >   652 k
> > pacemaker-mgmt  i386
> >   1.99.2-6.1   server_ha-clustering
> >   395 k
> > pacemaker-mgmt-client   i386
> >   1.99.2-6.1   server_ha-clustering
> >   279 k
> > Installing for dependencies:
> > pacemaker-libs  i386
> >   1.0.5-4.1server_ha-clustering
> >   2.7 M
> >
> > Transaction Summary
> >
> ==
> > Install  4 Package(s)
> > Update   6 Package(s)
> > Remove   0 Package(s)
> >
> > Total size: 8.9 M
> > Is this ok [y/N]: y
> > Downloading Packages:
> > Running rpm_check_debug
> > Running Transaction Test
> > Finished Transaction Test
> >
> >
> > Transaction Check Error:
> > file /usr/lib/libcib.so.1.0.1 from install of
> pacemaker-libs-1.0.5-4.1.i386
> > conflicts with file from package libpacemaker3-1.0.3-2.2.i386
> > file /usr/lib/libcrmcluster.so.1.0.0 from install of
> > pacemaker-libs-1.0.5-4.1.i386 conflicts with file from package
> > libpacemaker3-1.0.3-2.2.i386
> > file /usr/lib/libcrmcommon.so.2.0.0 from install of
> > pa

Re: [Pacemaker] yum update fails

2009-11-03 Thread Andrew Beekhof 
sure, post it to the list and i'm sure you'll get some feedback too.

On Tue, Nov 3, 2009 at 11:18 AM, er krishna  wrote:
> Dear Andrew,
>
> I have some good how to about SAN and HA. Can you please review my documents
> and help me to put it on your site. Please tell if you can find sometime for
> its review and help me to help others on FOSS.
>
> Best regards,
> Krishna
>
> On Mon, Nov 2, 2009 at 7:17 PM, Andrew Beekhof  wrote:
>>
>> Ah, looks like I'm missing an Obsoletes: for pacemaker-libs.
>> I'll fix that in while I'm updating the packages (now-ish)
>>
>> On Sat, Oct 31, 2009 at 12:16 AM, Donna Livingstone
>>  wrote:
>> > On Oct 19/20th I installed openais on a test RHEL5.4 install
>> > successfully(yum install -y "openais = 0.80.5" pacemaker).
>> > Today(Oct 30th) I attempted an update and it failed(see below).
>> > Looks like libpacemaker3 is in conflict and is now gone from the
>> > opensuse repository.
>> >
>> >
>> > [r...@wispoller2 drbd-8.3.5]# yum --disablerepo=rhel-i386-server-5
>> > update
>> > Loaded plugins: rhnplugin, security
>> > Skipping security plugin, no data
>> > Setting up Update Process
>> > Resolving Dependencies
>> > Skipping security plugin, no data
>> > --> Running transaction check
>> > ---> Package cluster-glue.i386 0:1.0-12.1 set to be updated
>> > ---> Package cluster-glue-libs.i386 0:1.0-12.1 set to be updated
>> > ---> Package heartbeat.i386 0:3.0.0-33.2 set to be updated
>> > ---> Package libopenais2.i386 0:0.80.5-15.1 set to be updated
>> > ---> Package openais.i386 0:0.80.5-15.1 set to be updated
>> > ---> Package pacemaker.i386 0:1.0.5-4.1 set to be updated
>> > --> Processing Dependency: pacemaker-libs = 1.0.5-4.1 for package:
>> > pacemaker
>> > ---> Package pacemaker-mgmt.i386 0:1.99.2-6.1 set to be updated
>> > ---> Package pacemaker-mgmt-client.i386 0:1.99.2-6.1 set to be updated
>> > ---> Package resource-agents.i386 0:1.0-31.4 set to be updated
>> > --> Running transaction check
>> > ---> Package pacemaker-libs.i386 0:1.0.5-4.1 set to be updated
>> > --> Finished Dependency Resolution
>> >
>> > Dependencies Resolved
>> >
>> >
>> > ==
>> > Package                                         Arch
>> >   Version                                  Repository
>> >                Size
>> >
>> > ==
>> > Installing:
>> > cluster-glue                                    i386
>> >   1.0-12.1                                 server_ha-clustering
>> >               1.2 M
>> > replacing  heartbeat-common.i386 2.99.2-8.1
>> >
>> > cluster-glue-libs                               i386
>> >   1.0-12.1                                 server_ha-clustering
>> >               1.1 M
>> > replacing  libheartbeat2.i386 2.99.2-8.1
>> >
>> > resource-agents                                 i386
>> >   1.0-31.4                                 server_ha-clustering
>> >               184 k
>> > replacing  heartbeat-resources.i386 2.99.2-8.1
>> >
>> > Updating:
>> > heartbeat                                       i386
>> >   3.0.0-33.2                               server_ha-clustering
>> >               1.5 M
>> > libopenais2                                     i386
>> >   0.80.5-15.1                              server_ha-clustering
>> >               431 k
>> > openais                                         i386
>> >   0.80.5-15.1                              server_ha-clustering
>> >               436 k
>> > pacemaker                                       i386
>> >   1.0.5-4.1                                server_ha-clustering
>> >               652 k
>> > pacemaker-mgmt                                  i386
>> >   1.99.2-6.1                               server_ha-clustering
>> >               395 k
>> > pacemaker-mgmt-client                           i386
>> >   1.99.2-6.1                               server_ha-clustering
>> >               279 k
>> > Installing for dependencies:
>> > pacemaker-libs                                  i386
>> >   1.0.5-4.1                                server_ha-clustering
>> >               2.7 M
>> >
>> > Transaction Summary
>> >
>> > ==
>> > Install      4 Package(s)
>> > Update       6 Package(s)
>> > Remove       0 Package(s)
>> >
>> > Total size: 8.9 M
>> > Is this ok [y/N]: y
>> > Downloading Packages:
>> > Running rpm_check_debug
>> > Running Transaction Test
>> > Finished Transaction Test
>> >
>> >
>> > Transaction Check Error:
>> > file /usr/lib/libcib.so.1.0.1 from install of
>> > pacemaker-libs-1.0.5-4.1.i386
>> > conflicts with file from

[Pacemaker] Simple Setup ?

2009-11-03 Thread bards 1888 
Hi,

I have been playing with pacemaker and openais to try and get some sort of
high-availability for the following services;

1. named
2. squid
3. dansguardian


My basic requirements are, a floating virtual IP that can exist on either
node of my 2 node cluster. Users will have a single server setup for DNS and
proxy and that will be the virtual IP. Obviously, the users will then get
directed to the 'master' node and all will be well. However, I want to be
able to run the services on the second node at the same time, so that, for
example, I can point my browser at the second proxy or have the slave DNS
server updated as zone changes are made on the master.

Is there any way I can define just the IP address as the Resource agent and
say "if you get the virtual IP, run this script" which would effectively run
/etc/init.d/service reload for each of the three services ?

Any help/advice would be appreciated.

Cheers
___
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Re: [Pacemaker] Simple Setup ?

2009-11-03 Thread bards 1888 
Sorry I neglected to mention that the main reason I need/want to 'reload'
the services is to ensure that they start listening on the newly acquired
virtual IP.


On Tue, Nov 3, 2009 at 8:30 PM, bards 1888  wrote:

> Hi,
>
> I have been playing with pacemaker and openais to try and get some sort of
> high-availability for the following services;
>
> 1. named
> 2. squid
> 3. dansguardian
>
>
> My basic requirements are, a floating virtual IP that can exist on either
> node of my 2 node cluster. Users will have a single server setup for DNS and
> proxy and that will be the virtual IP. Obviously, the users will then get
> directed to the 'master' node and all will be well. However, I want to be
> able to run the services on the second node at the same time, so that, for
> example, I can point my browser at the second proxy or have the slave DNS
> server updated as zone changes are made on the master.
>
> Is there any way I can define just the IP address as the Resource agent and
> say "if you get the virtual IP, run this script" which would effectively run
> /etc/init.d/service reload for each of the three services ?
>
> Any help/advice would be appreciated.
>
> Cheers
>
___
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Re: [Pacemaker] Simple Setup ?

2009-11-03 Thread Raoul Bhatia [IPAX] 
On 11/03/2009 11:34 AM, bards 1888 wrote:
> Sorry I neglected to mention that the main reason I need/want to
> 'reload' the services is to ensure that they start listening on the
> newly acquired virtual IP.

do you need to *reload* the services, or is *restart* working too?
what about "kill -HUP"?

cheers,
raoul
-- 

DI (FH) Raoul Bhatia M.Sc.  email.  r.bha...@ipax.at
Technischer Leiter

IPAX - Aloy Bhatia Hava OEG web.  http://www.ipax.at
Barawitzkagasse 10/2/2/11   email.off...@ipax.at
1190 Wien   tel.   +43 1 3670030
FN 277995t HG Wien  fax.+43 1 3670030 15


___
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Re: [Pacemaker] Simple Setup ?

2009-11-03 Thread Mailing List User 
Well I suppose what I run is not really the question, I want to be able to run 
a script or as you mention an os command when a node 'gets' the VIP. Can this 
be done ?

As  you rightly point out, 'kill -HUP' would work but then I have to go to the 
trouble of finding PIDs etc. Much easier to run the /etc/init.d script with a 
reload parameter.

Cheers.

- "Raoul Bhatia [IPAX]"  wrote:

> On 11/03/2009 11:34 AM, bards 1888 wrote:
> > Sorry I neglected to mention that the main reason I need/want to
> > 'reload' the services is to ensure that they start listening on the
> > newly acquired virtual IP.
> 
> do you need to *reload* the services, or is *restart* working too?
> what about "kill -HUP"?
> 
> cheers,
> raoul
> -- 
> 
> DI (FH) Raoul Bhatia M.Sc.  email.  r.bha...@ipax.at
> Technischer Leiter
> 
> IPAX - Aloy Bhatia Hava OEG web.  http://www.ipax.at
> Barawitzkagasse 10/2/2/11   email.off...@ipax.at
> 1190 Wien   tel.   +43 1 3670030
> FN 277995t HG Wien  fax.+43 1 3670030 15
> 
> 
> ___
> Pacemaker mailing list
> Pacemaker@oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> -- 
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


___
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Re: [Pacemaker] Resource capacity limit

2009-11-03 Thread Yan Gao 
Hi again,

Yan Gao wrote:
> Hi Lars,
> Thanks for the great suggestions!
> 
> Lars Marowsky-Bree wrote:
>> On 2009-10-30T19:41:35, Yan Gao  wrote:
>>> Configuration example:
>>>
>>> node yingying \
>>> attributes capacity="100"
>>> primitive dummy0 ocf:heartbeat:Dummy \
>>> meta weight="90" priority="2"
>>> primitive dummy1 ocf:heartbeat:Dummy \
>>> meta weight="60" priority="1"
>>> ..
>>> property $id="cib-bootstrap-options" \
>>> limit-capacity="true"
>> First, I would prefer not to contaminate the regular node attribute
>> namespace; the word "capacity" might already be used. Second, the
>> "weight" is just one dimension, which is somewhat difficult.
>>
>> I'd propose to introduce a new XML element, "resource_utilization" (name
>> to be decided ;-) containing a "nvset", and which can be used in a node
>> element or a resource primitive.
>>
>> This creates a new namespace, avoiding clashes, and distinguishes the
>> utilization parameters from the other various attributes.
>>
>> Further, it trivially allows for several user-defined metrics.
> Right, great idea! I'll try to implement it if Andrew is OK with that either:)
> 
Done and attached.

XML sample:
..

  

  
  

  

..

  

  
  

  
  

  
  

  

..

Please kindly review it...
Any suggestions are appreciated!

Thanks,
  Yan
-- 
y...@novell.com
Software Engineer
China Server Team, OPS Engineering

Novell, Inc.
Making IT Work As One™
diff -r c81e55653fba include/crm/msg_xml.h
--- a/include/crm/msg_xml.h	Fri Oct 16 14:26:27 2009 +0200
+++ b/include/crm/msg_xml.h	Tue Nov 03 19:02:22 2009 +0800
@@ -130,6 +130,7 @@
 #define XML_TAG_ATTRS			"attributes"
 #define XML_TAG_PARAMS			"parameters"
 #define XML_TAG_PARAM			"param"
+#define XML_TAG_UTILIZATION		"utilization"
 
 #define XML_TAG_RESOURCE_REF		"resource_ref"
 #define XML_CIB_TAG_RESOURCE	  	"primitive"
diff -r c81e55653fba include/crm/pengine/status.h
--- a/include/crm/pengine/status.h	Fri Oct 16 14:26:27 2009 +0200
+++ b/include/crm/pengine/status.h	Tue Nov 03 19:02:22 2009 +0800
@@ -58,6 +58,8 @@
 #define pe_flag_start_failure_fatal	0x1000ULL
 #define pe_flag_remove_after_stop	0x2000ULL
 
+#define pe_flag_limit_utilization	0x0001ULL
+
 
 typedef struct pe_working_set_s 
 {
@@ -116,6 +118,8 @@
 		
 		GHashTable *attrs;	/* char* => char* */
 		enum node_type type;
+
+		GHashTable *utilization;
 }; 
 
 struct node_s { 
@@ -186,6 +190,7 @@
 
 		GHashTable *meta;	   
 		GHashTable *parameters;
+		GHashTable *utilization;
 
 		GListPtr children;	  /* resource_t* */	
 };
diff -r c81e55653fba lib/pengine/common.c
--- a/lib/pengine/common.c	Fri Oct 16 14:26:27 2009 +0200
+++ b/lib/pengine/common.c	Tue Nov 03 19:02:22 2009 +0800
@@ -147,6 +147,10 @@
 	{ "node-health-red", NULL, "integer", NULL, "-INFINITY", &check_number,
 	  "The score 'red' translates to in rsc_location constraints",
 	  "Only used when node-health-strategy is set to custom or progressive." },
+
+	/*Resource utilization*/
+	{ "limit-utilization", NULL, "boolean", NULL, "false", &check_boolean,
+	  "Limit the resource utilization of nodes to avoid being overloaded", NULL},
 };
 
 void
diff -r c81e55653fba lib/pengine/complex.c
--- a/lib/pengine/complex.c	Fri Oct 16 14:26:27 2009 +0200
+++ b/lib/pengine/complex.c	Tue Nov 03 19:02:22 2009 +0800
@@ -371,6 +371,12 @@
 	if(safe_str_eq(class, "stonith")) {
 	set_bit_inplace(data_set->flags, pe_flag_have_stonith_resource);
 	}
+
+	(*rsc)->utilization = g_hash_table_new_full(
+		g_str_hash, g_str_equal, g_hash_destroy_str, g_hash_destroy_str);
+
+	unpack_instance_attributes(data_set->input, (*rsc)->xml, XML_TAG_UTILIZATION, NULL,
+   (*rsc)->utilization, NULL, FALSE, data_set->now);
 	
 /* 	data_set->resources = g_list_append(data_set->resources, (*rsc)); */
 	return TRUE;
@@ -451,6 +457,9 @@
 	if(rsc->meta != NULL) {
 		g_hash_table_destroy(rsc->meta);
 	}
+	if(rsc->utilization != NULL) {
+		g_hash_table_destroy(rsc->utilization);
+	}
 	if(rsc->parent == NULL && is_set(rsc->flags, pe_rsc_orphan)) {
 		free_xml(rsc->xml);
 	}
diff -r c81e55653fba lib/pengine/status.c
--- a/lib/pengine/status.c	Fri Oct 16 14:26:27 2009 +0200
+++ b/lib/pengine/status.c	Tue Nov 03 19:02:22 2009 +0800
@@ -159,6 +159,9 @@
 			if(details->attrs != NULL) {
 g_hash_table_destroy(details->attrs);
 			}
+			if(details->utilization != NULL) {
+g_hash_table_destroy(details->utilization);
+			}
 			pe_free_shallow_adv(details->running_rsc, FALSE);
 			pe_free_shallow_adv(details->allocated_rsc, FALSE);
 			crm_free(details);
diff -r c81e55653fba lib/pengine/unpack.c
--- a/lib/pengine/unpack.c	Fri Oct 16 14:26:27 2009 +0200
+++ b/lib/pengine/unpack.c	Tue Nov 03 19:02:22 2009 +0800
@@ -165,6 +165,10 @@
 	crm_info("Node scores: 'red' = %s, 'yellow' = %s, 'green' = %s",
 		 score2char(node_score_red),score2char(node_score_yellow),
 		 score2char(node_s

Re: [Pacemaker] enable to run crm line command

2009-11-03 Thread Dejan Muhamedagic 
Hi,

On Tue, Nov 03, 2009 at 10:06:13AM +0100, ROUAMBA Halidou wrote:
> I tried to install python 2.4 but i faced to a lot of dependencies that i
> can't résolve.
> I don't have a active suscription on RHN.
> I looked towards many Forum and it recommand me to upgrade my OS to RHEL AS
> 5 because *The dependencies can often be re-written for the older OS. But
> you're seriously imperiling your **operating system** doinig this, because a
> *lot* of components like Yum rely on Python.*
> *See the below url.*
> http://linux.derkeiler.com/Newsgroups/linux.redhat/2008-02/msg00085.html

I meant upgrading the whole distribution. The module which is not
available with before python 2.3 was introduced in crm because
the newer python versions would issue an ugly warning about using
a soon to be obsolete functions. Sigh. If there is a lot of demand
and the effort reasonably small I may consider supporting the
older version too. So far nobody reported these issues.

Thanks,

Dejan

> 2009/11/2 ROUAMBA Halidou 
> 
> > Ok Dejan, i shall try to upgrade my python version to 2.4 and i shall make
> > you know the result
> >
> > thanks
> >
> > RH
> >
> >
> > Pablo 
> > Picasso - 
> > "Computers are useless. They can only give you answers."
> >
> > 2009/11/2 Dejan Muhamedagic 
> >
> >> Hi,
> >>
> >> On Mon, Nov 02, 2009 at 03:32:07PM +0100, ROUAMBA Halidou wrote:
> >> > Thanks for your help, but another error is generated after adding the
> >> > bracket
> >> > see the below output.
> >> > [*r...@omconi2 packages]# crm*
> >> > *Traceback (most recent call last):*
> >> > *  File "/usr/sbin/crm", line 24, in ?*
> >> > *import subprocess*
> >> > *ImportError: No module named subprocess*
> >>
> >> subprocess is available as of version 2.4. Version 2.3 is really
> >> old. Can you upgrade to something more recent?
> >>
> >> Thanks,
> >>
> >> Dejan
> >>
> >> > i look closely in the crm file but this line exist at the line number 24
> >> > *import subprocess*
> >> > *
> >> > *
> >> > Thanks.
> >> >
> >> > 2009/11/2 Dejan Muhamedagic 
> >> >
> >> > > Hi,
> >> > >
> >> > > On Mon, Nov 02, 2009 at 01:53:13PM +0100, ROUAMBA Halidou wrote:
> >> > > > Marie von Ebner-Eschenbach<
> >> > >
> >> http://www.brainyquote.com/quotes/authors/m/marie_von_ebnereschenbac.html
> >> >
> >> > > > - "Even a stopped clock is right twice a day."
> >> > > >
> >> > > > 2009/11/2 Dejan Muhamedagic 
> >> > > >
> >> > > > > Hi,
> >> > > > >
> >> > > > > On Sun, Oct 25, 2009 at 01:07:40PM +0100, ROUAMBA Halidou wrote:
> >> > > > > > Hello
> >> > > > > >
> >> > > > > > I just install the last version of pacemaker and i used hearbeat
> >> as
> >> > > > > cluster
> >> > > > > > stacks.
> >> > > > > > The installation has been made on RHEL AS4.6.
> >> > > > > > i didn't have any error during the rpm installation.
> >> > > > > > The /etc/ha.d/ha.cf et /etc/ha.d/authkeys have been correctly
> >> > > > > configured.
> >> > > > > > The problem occured when i tried to use crm line command to
> >> configure
> >> > > the
> >> > > > > > CIB file for resource management.
> >> > > > > > so this is the outpout of the crm .[
> >> > > > > > *r...@omconi2 ~]# crm
> >> > > > > >   File "/usr/sbin/crm", line 4576
> >> > > > > > for obj in processing_sort_cli(self.obj_list))
> >> > > > > >   ^
> >> > > > > > SyntaxError: invalid syntax*
> >> > > > >
> >> > > > > Can't recall seeing this one.
> >> > > > >
> >> > > > > Which version of pacemaker do you run:
> >> > > > >
> >> > > > > /usr/lib/heartbeat/crmd version
> >> > > > >
> >> > > > [*r...@omconi1 packages]# /usr/lib/heartbeat/crmd version*
> >> > > > *CRM Version: 1.0.5 (462f1569a43740667daf7b0f6b521742e9eb8fa7)*
> >> > > >
> >> > > >
> >> > > > > And which version of python?
> >> > > > >>
> >> > > > >> *[r...@omconi1 packages]# python -V*
> >> > > > >
> >> > > > > *Python 2.3.4*
> >> > >
> >> > > Don't know, perhaps that is too old. Can you try to replace the
> >> > > existing lines:
> >> > >
> >> > >return '\n'.join(obj.repr_cli() \
> >> > > for obj in processing_sort_cli(self.obj_list))
> >> > >
> >> > > with
> >> > >
> >> > >return '\n'.join([obj.repr_cli() \
> >> > >for obj in processing_sort_cli(self.obj_list)])
> >> > >
> >> > > Thanks,
> >> > >
> >> > > Dejan
> >> > >
> >> > > > >
> >> > > > Version of redhat ?
> >> > > >
> >> > > > > *[r...@omconi1 packages]# cat /etc/redhat-release*
> >> > > > > *Red Hat Enterprise Linux AS release 4 (Nahant Update 6)*
> >> > > > > *[r...@omconi1 packages]# uname -r*
> >> > > > > *2.6.9-67.0.7.ELsmp*
> >> > > > >
> >> > > > >
> >> > > > The rpm have been downloading from this url
> >> > > >
> >> > >
> >> http://download.opensuse.org/repositories/server:/ha-clustering/RHEL_4/i386/
> >> > > >
> >> > > >
> >> > > > >  Thanks,
> >> > > > >
> >> > > > > Dejan
> >> > > > >
> >> > > > > > The same error.occurs on both nodes
> >> > > > > >
> >> > > > > > I see that crm is w

Re: [Pacemaker] Simple Setup ?

2009-11-03 Thread Raoul Bhatia [IPAX] 
On 11/03/2009 11:50 AM, Mailing List User wrote:
> Well I suppose what I run is not really the question, I want to be able to 
> run a script or as you mention an os command when a node 'gets' the VIP. Can 
> this be done ?
> 
> As  you rightly point out, 'kill -HUP' would work but then I have to go to 
> the trouble of finding PIDs etc. Much easier to run the /etc/init.d script 
> with a reload parameter.

hi,

first of all, please read the documents provided at
http://www.clusterlabs.org/wiki/Documentation

second, i would try to

1. use an ipaddr2 resource for the vip
2. use a cloned group for your resources

then i would either

a. put a specially crafted lsb script doing your reload stuff into the
cloned group (2) and use constraints to start the clone *after* the vip
(1)

or b. put a specially crafted lsb script and your vip (1) into another
group and order: 1.ip before 2 before 1.reload-lsb

maybe there is a much simpler way to handle this use case?
one thing that would come to my mind is something like "run
command/script after resource $action".

cheers,
raoul
-- 

DI (FH) Raoul Bhatia M.Sc.  email.  r.bha...@ipax.at
Technischer Leiter

IPAX - Aloy Bhatia Hava OEG web.  http://www.ipax.at
Barawitzkagasse 10/2/2/11   email.off...@ipax.at
1190 Wien   tel.   +43 1 3670030
FN 277995t HG Wien  fax.+43 1 3670030 15


___
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

[Pacemaker] [ANNOUNCEMENT] Debian Packages for Pacemaker 1.0.6, completely revamped

2009-11-03 Thread Martin Gerhard Loschwitz 
Ladies and Gentleman,

i am happy to announce the availability of Pacemaker 1.0.6 packages
for Debian GNU/Linux 5.0 alias Lenny (i386 and amd64).

These packages are a remarkable break, as they have totally and
ruthlessly been revamped. The whole layout has actually changed;
here are the most important things to keep in mind when using them:

* pacemaker-openais and pacemaker-heartbeat are gone; pacemaker now
only comes in one flavour, having support for corosync and heartbeat
built it. This is based on pacemaker's capability to detect by which
messaging framework it has been started and act accordingly.

* openais is gone. pacemaker 1.0.6 uses corosync.

* the new layout allows flawless updates. if you have heartbeat
2.1.4 and do a dist-upgrade, you will automatically get pacemaker.
all you need to do afterwards is converting the xml-file to work
with pacemaker -- you can then start heartbeat, and things are
going to be fine (more on this can be found in the Clusterlabs-
Wiki)

* Now that we finally have a decent layout for pacemaker, we can
easily provide gui packages: welcome pacemaker-mgmt, being in good
condition and shape now, allowing you do administer your cluster
via a GTK tool.

The new packages can as always be found on:

deb http://people.debian.org/~madkiss/ha lenny main
deb-src http://people.debian.org/~madkiss/ha lenny main

-- 
: Martin G. Loschwitz   Tel +43-1-8178292-63  :
: LINBIT Information Technologies GmbH  Fax +43-1-8178292-82  :
: Vivenotgasse 48, 1120 Vienna, Austria http://www.linbit.com :

___
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

[Pacemaker] Stopping multi-state clone

2009-11-03 Thread hj lee 
Hi,

When I stop a multi-state clone resource, first the master becomes slave,
and then it is stopped. This happens also when I do "service openais stop".
But I want the master gets stopped without demoting to slave. Is there any
specific reason for current design? Is there any way to configure to skip
this demotion when multi-state clone is stopped?

I think stopping resource mean only stop, not demote and stop. How do you
think?

Thanks
hj
___
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

[Pacemaker] How to configure the openais.conf

2009-11-03 Thread lepace 

Hi,all
I want to configure a HA cluster which having more than 60 nodes,and I want to 
use N-to-N mode,so every node can potentially be used for failover.which I want 
to know is how to configure the value of parameters in openais.conf，or the 
methods to find the right value of parametres
thanks___
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Re: [Pacemaker] How to configure the openais.conf

2009-11-03 Thread Steven Dake 
We have found through testing the practical limit on cluster size with
the protocol used in openais is ~30 nodes currently.  The default
parameters should work well for these sizes.

Regards
-steve

On Wed, 2009-11-04 at 08:57 +0800, lepace wrote:
> 
> Hi,all
> I want to configure a HA cluster which having more than 60 nodes,and I
> want to use N-to-N mode,so every node can potentially be used for
> failover.which I want to know is how to configure the value of
> parameters in openais.conf，or the methods to find the right value of
> parametres
> thanks
> 
> 
> 
> __
> 09年新晋3D主流网游《天下贰》，网易六年亿资打造
> ___
> Pacemaker mailing list
> Pacemaker@oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker


___
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Re: [Pacemaker] [ANNOUNCEMENT] Debian Packages for Pacemaker 1.0.6, completely revamped

2009-11-03 Thread Luke Bigum 
The OpenAIS project has split into Corosync and OpenAIS. Someone else might be 
able to explain it better, but Corosync now contains the core clustering 
components the openais package used to have (aisexec, etc), while the OpenAIS 
project just contains the SA Forum API stuff.

So, what most people once thought of as "OpenAIS" is now Corosync.

Luke Bigum
Systems Administrator
 (p) 1300 661 668
 (f)  1300 661 540
(e)  lbi...@iseek.com.au
http://www.iseek.com.au
Level 1, 100 Ipswich Road Woolloongabba QLD 4102

[cid:image001.jpg@01CA5D43.C8915480]

This e-mail and any files transmitted with it may contain confidential and 
privileged material for the sole use of the intended recipient. Any review, 
use, distribution or disclosure by others is strictly prohibited. If you are 
not the intended recipient (or authorised to receive for the recipient), please 
contact the sender by reply e-mail and delete all copies of this message.


From: Romain CHANU [mailto:romainch...@gmail.com]
Sent: Wednesday 4 November 2009 11:36 AM
To: pacemaker@oss.clusterlabs.org
Subject: Re: [Pacemaker] [ANNOUNCEMENT] Debian Packages for Pacemaker 1.0.6, 
completely revamped

Hi Martin,

Could you tell us what's the rationale to remove openais and include corosync?

Would it mean that people should use corosync from now on for any HA 
development?

Best Regards,

Romain Chanu

2009/11/3 Martin Gerhard Loschwitz 
mailto:martin.loschw...@linbit.com>>
Ladies and Gentleman,

i am happy to announce the availability of Pacemaker 1.0.6 packages
for Debian GNU/Linux 5.0 alias Lenny (i386 and amd64).

These packages are a remarkable break, as they have totally and
ruthlessly been revamped. The whole layout has actually changed;
here are the most important things to keep in mind when using them:

* pacemaker-openais and pacemaker-heartbeat are gone; pacemaker now
only comes in one flavour, having support for corosync and heartbeat
built it. This is based on pacemaker's capability to detect by which
messaging framework it has been started and act accordingly.

* openais is gone. pacemaker 1.0.6 uses corosync.

* the new layout allows flawless updates. if you have heartbeat
2.1.4 and do a dist-upgrade, you will automatically get pacemaker.
all you need to do afterwards is converting the xml-file to work
with pacemaker -- you can then start heartbeat, and things are
going to be fine (more on this can be found in the Clusterlabs-
Wiki)

* Now that we finally have a decent layout for pacemaker, we can
easily provide gui packages: welcome pacemaker-mgmt, being in good
condition and shape now, allowing you do administer your cluster
via a GTK tool.

The new packages can as always be found on:

deb 
http://people.debian.org/~madkiss/ha 
lenny main
deb-src 
http://people.debian.org/~madkiss/ha 
lenny main

--
: Martin G. Loschwitz   Tel +43-1-8178292-63  :
: LINBIT Information Technologies GmbH  Fax +43-1-8178292-82  :
: Vivenotgasse 48, 1120 Vienna, Austria http://www.linbit.com :

___
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

<>___
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Re: [Pacemaker] cluster doesn't failover - log at the end of msg

2009-11-03 Thread Luke Bigum 
Hi Thomas,

You need to use a location constraint on your NFS resource and a ping/pingd 
resource to monitor network connectivity. Combined together you can make NFS or 
your DRBD Master resource constrained to nodes that have network connectivity. 
See http://www.clusterlabs.org/wiki/Example_configurations#Set_up_pingd. 

Luke Bigum
Systems Administrator
 (p) 1300 661 668
 (f)  1300 661 540
(e)  lbi...@iseek.com.au
http://www.iseek.com.au
Level 1, 100 Ipswich Road Woolloongabba QLD 4102



This e-mail and any files transmitted with it may contain confidential and 
privileged material for the sole use of the intended recipient. Any review, 
use, distribution or disclosure by others is strictly prohibited. If you are 
not the intended recipient (or authorised to receive for the recipient), please 
contact the sender by reply e-mail and delete all copies of this message.


-Original Message-
From: Thomas Schneider [mailto:thomas.schnei...@euskill.com] 
Sent: Wednesday 4 November 2009 8:28 AM
To: pacemaker@oss.clusterlabs.org
Subject: [Pacemaker] cluster doesn't failover - log at the end of msg


Hi

Thanks for your help i solve the problem by replacing this line

location cli-standby-nfs nfs \
rule $id="cli-standby-rule-nfs" -inf: #uname eq
storage02.myriapulse.local

by

location ms_drbd_nfs-master-storage01.myriapulse.local ms_drbd_nfs rule
role=master 100: \#uname storage01.myriapulse.local

but i have an other problem because i have 2 network card

 Eth1: replication link
 --  
 | Server 1   |--| Server 2 |
 --  
  ||
 Eth0 eth0
  ||  
 External Network

The data of the nfs server is accessed via eth0, but if y shutdown eth0 on
the node witch is running the resource, the resource doesn't migrate and is
unreachable, i think it's because of the replication link (who stay up)

node storage01.myriapulse.local \
attributes standby="off"
node storage02.myriapulse.local \
attributes standby="off"
primitive drbd_nfs ocf:linbit:drbd \
params drbd_resource="nfs" \
op monitor interval="15s" \
meta target-role="Started"
primitive fs_nfs ocf:heartbeat:Filesystem \
params device="/dev/drbd/by-res/nfs" directory="/share"
fstype="ext3" \
meta is-managed="true"
primitive ftp-server lsb:proftpd \
op monitor interval="1min"
primitive ip_nfs ocf:heartbeat:IPaddr2 \
params ip="10.1.1.69" nic="eth0"
primitive nfs-kernel-server lsb:nfs-kernel-server \
op monitor interval="1min"
group nfs fs_nfs ip_nfs nfs-kernel-server \
meta target-role="Started"
ms ms_drbd_nfs drbd_nfs \
meta master-max="1" master-node-max="1" clone-max="2"
clone-node-max="1" notify="true"
location drbd-fence-by-handler-ms_drbd_nfs ms_drbd_nfs \
rule $id="drbd-fence-by-handler-rule-ms_drbd_nfs" $role="Master"
-inf: #uname ne storage02.myriapulse.local
location ms_drbd_nfs-master-storage01.myriapulse.local ms_drbd_nfs \
rule $id="ms_drbd_nfs-master-storage01.myriapulse.local-rule"
$role="master" 100: #uname eq storage01.myriapulse.local
colocation ftp_on_nfs inf: ftp-server nfs
colocation nfs_on_drbd inf: nfs ms_drbd_nfs:Master
order ftp_after_nfs inf: nfs ftp-server
order nfs_after_drbd inf: ms_drbd_nfs:promote nfs:start
property $id="cib-bootstrap-options" \
dc-version="1.0.5-unknown" \
cluster-infrastructure="openais" \
expected-quorum-votes="2" \
no-quorum-policy="ignore" \
stonith-enabled="false"

Thanks for your help
Thomas Schneider


-Message d'origine-
De : drbd-user-boun...@lists.linbit.com
[mailto:drbd-user-boun...@lists.linbit.com] De la part de Lars Ellenberg
Envoyé : samedi 31 octobre 2009 10:15
À : drbd-u...@lists.linbit.com
Objet : Re: [DRBD-user] cluster doesn't failover - log at the end of msg

On Sat, Oct 31, 2009 at 02:57:37AM +0100, Thomas Schneider wrote:
> Hello,
> 
> I'm trying to setup a cluster for shared storage with pacemaker, drbd, and
> nfs.
> I use two server and there is two network interface one each server, eth0
> connected to the network, and eth1 direct link betwene the two node for
drbd
> replication,


> I can migrate the resource between the to node, but the problem is when i
> make a hard power-off of server01 ( the server where is running the
> resource) the second server (server02) doesn't make failover. (the
resource
> doesn't start) May you can take a look to my config file in the following


> storage01:~# crm configure show
> node storage01.myriapulse.local \
> attributes standby="off"
> node storage02.myriapulse.local \
> attributes standby="off"
> primitive drbd_nfs ocf:linbit:drbd \
> params drbd_resource="nfs" \
> op monitor interval="15s" \
> meta target-role="Started"
> primitive fs_nfs ocf:heartbeat:Filesystem \
> params devic

Re: [Pacemaker] [ANNOUNCEMENT] Debian Packages for Pacemaker 1.0.6, completely revamped

2009-11-03 Thread Romain CHANU 
Hi Martin,

Could you tell us what's the rationale to remove openais and include
corosync?

Would it mean that people should use corosync from now on for any HA
development?

Best Regards,

Romain Chanu


2009/11/3 Martin Gerhard Loschwitz 

> Ladies and Gentleman,
>
> i am happy to announce the availability of Pacemaker 1.0.6 packages
> for Debian GNU/Linux 5.0 alias Lenny (i386 and amd64).
>
> These packages are a remarkable break, as they have totally and
> ruthlessly been revamped. The whole layout has actually changed;
> here are the most important things to keep in mind when using them:
>
> * pacemaker-openais and pacemaker-heartbeat are gone; pacemaker now
> only comes in one flavour, having support for corosync and heartbeat
> built it. This is based on pacemaker's capability to detect by which
> messaging framework it has been started and act accordingly.
>
> * openais is gone. pacemaker 1.0.6 uses corosync.
>
> * the new layout allows flawless updates. if you have heartbeat
> 2.1.4 and do a dist-upgrade, you will automatically get pacemaker.
> all you need to do afterwards is converting the xml-file to work
> with pacemaker -- you can then start heartbeat, and things are
> going to be fine (more on this can be found in the Clusterlabs-
> Wiki)
>
> * Now that we finally have a decent layout for pacemaker, we can
> easily provide gui packages: welcome pacemaker-mgmt, being in good
> condition and shape now, allowing you do administer your cluster
> via a GTK tool.
>
> The new packages can as always be found on:
>
> deb 
> http://people.debian.org/~madkiss/halenny
>  main
> deb-src 
> http://people.debian.org/~madkiss/halenny
>  main
>
> --
> : Martin G. Loschwitz   Tel +43-1-8178292-63  :
> : LINBIT Information Technologies GmbH  Fax +43-1-8178292-82  :
> : Vivenotgasse 48, 1120 Vienna, Austria http://www.linbit.com :
>
> ___
> Pacemaker mailing list
> Pacemaker@oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
___
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

[Pacemaker] cluster doesn't failover - log at the end of msg

2009-11-03 Thread Thomas Schneider 

Hi

Thanks for your help i solve the problem by replacing this line

location cli-standby-nfs nfs \
rule $id="cli-standby-rule-nfs" -inf: #uname eq
storage02.myriapulse.local

by

location ms_drbd_nfs-master-storage01.myriapulse.local ms_drbd_nfs rule
role=master 100: \#uname storage01.myriapulse.local

but i have an other problem because i have 2 network card

 Eth1: replication link
 --  
 | Server 1   |--| Server 2 |
 --  
  ||
 Eth0 eth0
  ||  
 External Network

The data of the nfs server is accessed via eth0, but if y shutdown eth0 on
the node witch is running the resource, the resource doesn't migrate and is
unreachable, i think it's because of the replication link (who stay up)

node storage01.myriapulse.local \
attributes standby="off"
node storage02.myriapulse.local \
attributes standby="off"
primitive drbd_nfs ocf:linbit:drbd \
params drbd_resource="nfs" \
op monitor interval="15s" \
meta target-role="Started"
primitive fs_nfs ocf:heartbeat:Filesystem \
params device="/dev/drbd/by-res/nfs" directory="/share"
fstype="ext3" \
meta is-managed="true"
primitive ftp-server lsb:proftpd \
op monitor interval="1min"
primitive ip_nfs ocf:heartbeat:IPaddr2 \
params ip="10.1.1.69" nic="eth0"
primitive nfs-kernel-server lsb:nfs-kernel-server \
op monitor interval="1min"
group nfs fs_nfs ip_nfs nfs-kernel-server \
meta target-role="Started"
ms ms_drbd_nfs drbd_nfs \
meta master-max="1" master-node-max="1" clone-max="2"
clone-node-max="1" notify="true"
location drbd-fence-by-handler-ms_drbd_nfs ms_drbd_nfs \
rule $id="drbd-fence-by-handler-rule-ms_drbd_nfs" $role="Master"
-inf: #uname ne storage02.myriapulse.local
location ms_drbd_nfs-master-storage01.myriapulse.local ms_drbd_nfs \
rule $id="ms_drbd_nfs-master-storage01.myriapulse.local-rule"
$role="master" 100: #uname eq storage01.myriapulse.local
colocation ftp_on_nfs inf: ftp-server nfs
colocation nfs_on_drbd inf: nfs ms_drbd_nfs:Master
order ftp_after_nfs inf: nfs ftp-server
order nfs_after_drbd inf: ms_drbd_nfs:promote nfs:start
property $id="cib-bootstrap-options" \
dc-version="1.0.5-unknown" \
cluster-infrastructure="openais" \
expected-quorum-votes="2" \
no-quorum-policy="ignore" \
stonith-enabled="false"

Thanks for your help
Thomas Schneider


-Message d'origine-
De : drbd-user-boun...@lists.linbit.com
[mailto:drbd-user-boun...@lists.linbit.com] De la part de Lars Ellenberg
Envoyé : samedi 31 octobre 2009 10:15
À : drbd-u...@lists.linbit.com
Objet : Re: [DRBD-user] cluster doesn't failover - log at the end of msg

On Sat, Oct 31, 2009 at 02:57:37AM +0100, Thomas Schneider wrote:
> Hello,
> 
> I'm trying to setup a cluster for shared storage with pacemaker, drbd, and
> nfs.
> I use two server and there is two network interface one each server, eth0
> connected to the network, and eth1 direct link betwene the two node for
drbd
> replication,


> I can migrate the resource between the to node, but the problem is when i
> make a hard power-off of server01 ( the server where is running the
> resource) the second server (server02) doesn't make failover. (the
resource
> doesn't start) May you can take a look to my config file in the following


> storage01:~# crm configure show
> node storage01.myriapulse.local \
> attributes standby="off"
> node storage02.myriapulse.local \
> attributes standby="off"
> primitive drbd_nfs ocf:linbit:drbd \
> params drbd_resource="nfs" \
> op monitor interval="15s" \
> meta target-role="Started"
> primitive fs_nfs ocf:heartbeat:Filesystem \
> params device="/dev/drbd/by-res/nfs" directory="/share"
> fstype="ext3" \
> meta is-managed="true"
> primitive ftp-server lsb:proftpd \
> op monitor interval="1min"
> primitive ip_nfs ocf:heartbeat:IPaddr2 \
> params ip="10.1.1.69" nic="eth0"
> primitive nfs-kernel-server lsb:nfs-kernel-server \
> op monitor interval="1min"
> group nfs fs_nfs ip_nfs nfs-kernel-server \
> meta target-role="Started"
> ms ms_drbd_nfs drbd_nfs \
> meta master-max="1" master-node-max="1" clone-max="2"
> clone-node-max="1" notify="true"
> location cli-standby-nfs nfs \
> rule $id="cli-standby-rule-nfs" -inf: #uname eq
> storage02.myriapulse.local colocation ftp_on_nfs inf: ftp-server nfs
> colocation nfs_on_drbd inf: nfs ms_drbd_nfs:Master order ftp_after_nfs
inf:
> nfs ftp-server order nfs_after_drbd inf: ms_drbd_nfs:promote nfs:start

You really should get your line breaks right!

> property $id="cib-bootstrap-options" \
> dc-version="1.0.5-unknown" \
> cluster-infrastructure="openais" \
> expected-quorum-votes="2" \
> no-quorum-policy="ignore" \

Re: [Pacemaker] yum update fails

2009-11-03 Thread er krishna 
Dear Andrew,

Can you please just tell if you like the design doc. I have complete how to
and other document to make this dream in running form & believe me it worked
on my desktop. Just please let me know if you are interested in this and
keeping my all the documents on your site.

Best Regards,
Krishna

On Tue, Nov 3, 2009 at 5:03 PM, er krishna  wrote:

> Dear Andrew,
>
> Thanks a lot for your kind help. I have 4-5 documents with complete design,
> how to and patches. I am sending the very first document to you and all the
> people related with this mailing list. My whole intention is that to help
> OSS and mankind by some means. Please find the very first doc. Tommorow I
> will send the other document. Till then please review it and please put on
> your site.
>
> Best Regards,
> Krishna
>
> On Tue, Nov 3, 2009 at 3:00 PM, Andrew Beekhof  wrote:
>
>> sure, post it to the list and i'm sure you'll get some feedback too.
>>
>> On Tue, Nov 3, 2009 at 11:18 AM, er krishna  wrote:
>> > Dear Andrew,
>> >
>> > I have some good how to about SAN and HA. Can you please review my
>> documents
>> > and help me to put it on your site. Please tell if you can find sometime
>> for
>> > its review and help me to help others on FOSS.
>> >
>> > Best regards,
>> > Krishna
>> >
>> > On Mon, Nov 2, 2009 at 7:17 PM, Andrew Beekhof 
>> wrote:
>> >>
>> >> Ah, looks like I'm missing an Obsoletes: for pacemaker-libs.
>> >> I'll fix that in while I'm updating the packages (now-ish)
>> >>
>> >> On Sat, Oct 31, 2009 at 12:16 AM, Donna Livingstone
>> >>  wrote:
>> >> > On Oct 19/20th I installed openais on a test RHEL5.4 install
>> >> > successfully(yum install -y "openais = 0.80.5" pacemaker).
>> >> > Today(Oct 30th) I attempted an update and it failed(see below).
>> >> > Looks like libpacemaker3 is in conflict and is now gone from the
>> >> > opensuse repository.
>> >> >
>> >> >
>> >> > [r...@wispoller2 drbd-8.3.5]# yum --disablerepo=rhel-i386-server-5
>> >> > update
>> >> > Loaded plugins: rhnplugin, security
>> >> > Skipping security plugin, no data
>> >> > Setting up Update Process
>> >> > Resolving Dependencies
>> >> > Skipping security plugin, no data
>> >> > --> Running transaction check
>> >> > ---> Package cluster-glue.i386 0:1.0-12.1 set to be updated
>> >> > ---> Package cluster-glue-libs.i386 0:1.0-12.1 set to be updated
>> >> > ---> Package heartbeat.i386 0:3.0.0-33.2 set to be updated
>> >> > ---> Package libopenais2.i386 0:0.80.5-15.1 set to be updated
>> >> > ---> Package openais.i386 0:0.80.5-15.1 set to be updated
>> >> > ---> Package pacemaker.i386 0:1.0.5-4.1 set to be updated
>> >> > --> Processing Dependency: pacemaker-libs = 1.0.5-4.1 for package:
>> >> > pacemaker
>> >> > ---> Package pacemaker-mgmt.i386 0:1.99.2-6.1 set to be updated
>> >> > ---> Package pacemaker-mgmt-client.i386 0:1.99.2-6.1 set to be
>> updated
>> >> > ---> Package resource-agents.i386 0:1.0-31.4 set to be updated
>> >> > --> Running transaction check
>> >> > ---> Package pacemaker-libs.i386 0:1.0.5-4.1 set to be updated
>> >> > --> Finished Dependency Resolution
>> >> >
>> >> > Dependencies Resolved
>> >> >
>> >> >
>> >> >
>> ==
>> >> > Package Arch
>> >> >   Version  Repository
>> >> >Size
>> >> >
>> >> >
>> ==
>> >> > Installing:
>> >> > cluster-gluei386
>> >> >   1.0-12.1 server_ha-clustering
>> >> >   1.2 M
>> >> > replacing  heartbeat-common.i386 2.99.2-8.1
>> >> >
>> >> > cluster-glue-libs   i386
>> >> >   1.0-12.1 server_ha-clustering
>> >> >   1.1 M
>> >> > replacing  libheartbeat2.i386 2.99.2-8.1
>> >> >
>> >> > resource-agents i386
>> >> >   1.0-31.4 server_ha-clustering
>> >> >   184 k
>> >> > replacing  heartbeat-resources.i386 2.99.2-8.1
>> >> >
>> >> > Updating:
>> >> > heartbeat   i386
>> >> >   3.0.0-33.2   server_ha-clustering
>> >> >   1.5 M
>> >> > libopenais2 i386
>> >> >   0.80.5-15.1  server_ha-clustering
>> >> >   431 k
>> >> > openais i386
>> >> >   0.80.5-15.1  server_ha-clustering
>> >> >   436 k
>> >> > pacemaker   i386
>> >> >   1.0.5-4.1server_ha-clustering
>> >> >

Re: [Pacemaker] [ANNOUNCEMENT] Debian Packages for Pacemaker 1.0.6, completely revamped

2009-11-03 Thread Steven Dake 
On Wed, 2009-11-04 at 11:41 +1000, Luke Bigum wrote:
> The OpenAIS project has split into Corosync and OpenAIS. Someone else
> might be able to explain it better, but Corosync now contains the core
> clustering components the openais package used to have (aisexec, etc),
> while the OpenAIS project just contains the SA Forum API stuff.
> 
>  

>From the maintainer of both openais and corosync, this is an accurate
description.

All of the features of openais that pacemaker used previously are now
integrated into Corosync.  Those features have been removed by openais
and now openais contains only the SA Forum APIs.

Regards
-steve

> 
> So, what most people once thought of as "OpenAIS" is now Corosync.
> 
>  
> 
> Luke Bigum
> 
> Systems Administrator
> 
>  (p) 1300 661 668
> 
>  (f)  1300 661 540
> 
> (e)  lbi...@iseek.com.au
> 
> http://www.iseek.com.au
> 
> Level 1, 100 Ipswich Road Woolloongabba QLD 4102
> 
>  
> 
> iseekbar.jpg
> 
>  
> 
> This e-mail and any files transmitted with it may contain confidential
> and privileged material for the sole use of the intended recipient.
> Any review, use, distribution or disclosure by others is strictly
> prohibited. If you are not the intended recipient (or authorised to
> receive for the recipient), please contact the sender by reply e-mail
> and delete all copies of this message.
> 
>  
> 
>  
> 
> From: Romain CHANU [mailto:romainch...@gmail.com] 
> Sent: Wednesday 4 November 2009 11:36 AM
> To: pacemaker@oss.clusterlabs.org
> Subject: Re: [Pacemaker] [ANNOUNCEMENT] Debian Packages for Pacemaker
> 1.0.6, completely revamped
> 
> 
>  
> 
> Hi Martin,
> 
> Could you tell us what's the rationale to remove openais and include
> corosync?
> 
> Would it mean that people should use corosync from now on for any HA
> development?
> 
> Best Regards,
> 
> Romain Chanu
> 
> 
> 
> 2009/11/3 Martin Gerhard Loschwitz 
> 
> Ladies and Gentleman,
> 
> i am happy to announce the availability of Pacemaker 1.0.6 packages
> for Debian GNU/Linux 5.0 alias Lenny (i386 and amd64).
> 
> These packages are a remarkable break, as they have totally and
> ruthlessly been revamped. The whole layout has actually changed;
> here are the most important things to keep in mind when using them:
> 
> * pacemaker-openais and pacemaker-heartbeat are gone; pacemaker now
> only comes in one flavour, having support for corosync and heartbeat
> built it. This is based on pacemaker's capability to detect by which
> messaging framework it has been started and act accordingly.
> 
> * openais is gone. pacemaker 1.0.6 uses corosync.
> 
> * the new layout allows flawless updates. if you have heartbeat
> 2.1.4 and do a dist-upgrade, you will automatically get pacemaker.
> all you need to do afterwards is converting the xml-file to work
> with pacemaker -- you can then start heartbeat, and things are
> going to be fine (more on this can be found in the Clusterlabs-
> Wiki)
> 
> * Now that we finally have a decent layout for pacemaker, we can
> easily provide gui packages: welcome pacemaker-mgmt, being in good
> condition and shape now, allowing you do administer your cluster
> via a GTK tool.
> 
> The new packages can as always be found on:
> 
> deb http://people.debian.org/~madkiss/ha lenny main
> deb-src http://people.debian.org/~madkiss/ha lenny main
> 
> --
> : Martin G. Loschwitz   Tel +43-1-8178292-63  :
> : LINBIT Information Technologies GmbH  Fax +43-1-8178292-82  :
> : Vivenotgasse 48, 1120 Vienna, Austria http://www.linbit.com :
> 
> ___
> Pacemaker mailing list
> Pacemaker@oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> 
>  
> 
> 
> ___
> Pacemaker mailing list
> Pacemaker@oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker


___
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Re: [Pacemaker] [ANNOUNCEMENT] Debian Packages for Pacemaker 1.0.6, completely revamped

2009-11-03 Thread Steven Dake 
On Wed, 2009-11-04 at 09:35 +0800, Romain CHANU wrote:
> Hi Martin,
> 
> Could you tell us what's the rationale to remove openais and include
> corosync?
> 
> Would it mean that people should use corosync from now on for any HA
> development?
> 
> Best Regards,
> 
> Romain Chanu
> 

Just a short note I would also recommend making available the latest
openais packages which complement both corosync and pacemaker with sa
forum complaint apis.

Regards
-steve

> 
> 2009/11/3 Martin Gerhard Loschwitz 
> Ladies and Gentleman,
> 
> i am happy to announce the availability of Pacemaker 1.0.6
> packages
> for Debian GNU/Linux 5.0 alias Lenny (i386 and amd64).
> 
> These packages are a remarkable break, as they have totally
> and
> ruthlessly been revamped. The whole layout has actually
> changed;
> here are the most important things to keep in mind when using
> them:
> 
> * pacemaker-openais and pacemaker-heartbeat are gone;
> pacemaker now
> only comes in one flavour, having support for corosync and
> heartbeat
> built it. This is based on pacemaker's capability to detect by
> which
> messaging framework it has been started and act accordingly.
> 
> * openais is gone. pacemaker 1.0.6 uses corosync.
> 
> * the new layout allows flawless updates. if you have
> heartbeat
> 2.1.4 and do a dist-upgrade, you will automatically get
> pacemaker.
> all you need to do afterwards is converting the xml-file to
> work
> with pacemaker -- you can then start heartbeat, and things are
> going to be fine (more on this can be found in the
> Clusterlabs-
> Wiki)
> 
> * Now that we finally have a decent layout for pacemaker, we
> can
> easily provide gui packages: welcome pacemaker-mgmt, being in
> good
> condition and shape now, allowing you do administer your
> cluster
> via a GTK tool.
> 
> The new packages can as always be found on:
> 
> deb http://people.debian.org/~madkiss/ha lenny main
> deb-src http://people.debian.org/~madkiss/ha lenny main
> 
> --
> : Martin G. Loschwitz   Tel +43-1-8178292-63
>  :
> : LINBIT Information Technologies GmbH  Fax +43-1-8178292-82
>  :
> : Vivenotgasse 48, 1120 Vienna, Austria
> http://www.linbit.com :
> 
> ___
> Pacemaker mailing list
> Pacemaker@oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> ___
> Pacemaker mailing list
> Pacemaker@oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker


___
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Re: [Pacemaker] [ANNOUNCEMENT] Debian Packages for Pacemaker 1.0.6, completely revamped

2009-11-03 Thread Romain CHANU 
So what about this:
http://theclusterguy.clusterlabs.org/post/205886990/advisory-dont-use-pacemaker-on-corosync-yet

Is pacemaker 1.0.6 able to run correctly with corosync?

I am still at a stage where I need to decide for the implementation of my HA
solution. For a design with pacemaker / corosync, there is no need to use
openais anymore, right?

Cheers,

Romain Chanu

2009/11/4 Steven Dake 

> On Wed, 2009-11-04 at 09:35 +0800, Romain CHANU wrote:
> > Hi Martin,
> >
> > Could you tell us what's the rationale to remove openais and include
> > corosync?
> >
> > Would it mean that people should use corosync from now on for any HA
> > development?
> >
> > Best Regards,
> >
> > Romain Chanu
> >
>
> Just a short note I would also recommend making available the latest
> openais packages which complement both corosync and pacemaker with sa
> forum complaint apis.
>
> Regards
> -steve
>
> >
> > 2009/11/3 Martin Gerhard Loschwitz 
> > Ladies and Gentleman,
> >
> > i am happy to announce the availability of Pacemaker 1.0.6
> > packages
> > for Debian GNU/Linux 5.0 alias Lenny (i386 and amd64).
> >
> > These packages are a remarkable break, as they have totally
> > and
> > ruthlessly been revamped. The whole layout has actually
> > changed;
> > here are the most important things to keep in mind when using
> > them:
> >
> > * pacemaker-openais and pacemaker-heartbeat are gone;
> > pacemaker now
> > only comes in one flavour, having support for corosync and
> > heartbeat
> > built it. This is based on pacemaker's capability to detect by
> > which
> > messaging framework it has been started and act accordingly.
> >
> > * openais is gone. pacemaker 1.0.6 uses corosync.
> >
> > * the new layout allows flawless updates. if you have
> > heartbeat
> > 2.1.4 and do a dist-upgrade, you will automatically get
> > pacemaker.
> > all you need to do afterwards is converting the xml-file to
> > work
> > with pacemaker -- you can then start heartbeat, and things are
> > going to be fine (more on this can be found in the
> > Clusterlabs-
> > Wiki)
> >
> > * Now that we finally have a decent layout for pacemaker, we
> > can
> > easily provide gui packages: welcome pacemaker-mgmt, being in
> > good
> > condition and shape now, allowing you do administer your
> > cluster
> > via a GTK tool.
> >
> > The new packages can as always be found on:
> >
> > deb 
> > http://people.debian.org/~madkiss/halenny
> >  main
> > deb-src 
> > http://people.debian.org/~madkiss/halenny
> >  main
> >
> > --
> > : Martin G. Loschwitz   Tel +43-1-8178292-63
> >  :
> > : LINBIT Information Technologies GmbH  Fax +43-1-8178292-82
> >  :
> > : Vivenotgasse 48, 1120 Vienna, Austria
> > http://www.linbit.com :
> >
> > ___
> > Pacemaker mailing list
> > Pacemaker@oss.clusterlabs.org
> > http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> >
> > ___
> > Pacemaker mailing list
> > Pacemaker@oss.clusterlabs.org
> > http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
>
> ___
> Pacemaker mailing list
> Pacemaker@oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
___
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Re: [Pacemaker] [ANNOUNCEMENT] Debian Packages for Pacemaker 1.0.6, completely revamped

2009-11-03 Thread Andrew Beekhof 
On Wed, Nov 4, 2009 at 9:09 AM, Romain CHANU  wrote:
> So what about this:
> http://theclusterguy.clusterlabs.org/post/205886990/advisory-dont-use-pacemaker-on-corosync-yet
>
> Is pacemaker 1.0.6 able to run correctly with corosync?

Yes.
I did mention it in the release notes, but I'll also indicate it more
prominently.

The RPM packages will also be built against corosync.

>
> I am still at a stage where I need to decide for the implementation of my HA
> solution. For a design with pacemaker / corosync, there is no need to use
> openais anymore, right?

Not unless one of the services you wish to provide (eg. ocfs2 or clvm) needs it.

___
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker