Re: [Pacemaker] Can I use Pacemaker release 1.1.8 for production clusters?

2013-06-10 Thread Andrew Martin 
- Original Message -
> From: "Florian Crouzat" 
> To: pacemaker@oss.clusterlabs.org
> Sent: Monday, June 10, 2013 10:01:35 AM
> Subject: Re: [Pacemaker] Can I use Pacemaker release 1.1.8 for production 
> clusters?
> 
> Le 10/06/2013 16:46, Michael Furman a écrit :
> > Hi all!
> >
> > According to the Wiki http://clusterlabs.org/wiki/Releases
> 
> 
> This page has not been updated since 10:49, 11 February 2011
> 
> >
> > Even numbered release series (eg. 0.6.x, 1.0.x) are recommended for
> > production clusters.
> >
> > I need to install Pacemaker on Centos 6 machines.
> > Unfortunately, the main Centos repository contains only 1.1.8-7.el6
> > version.
> >
> > Questions:
> > Can I use Pacemaker release 1.1.8 for production clusters (we want
> > to
> > work with the Centos repository)?
> 
> I hope so
> 
> > Do you expect to change existing features in 1.1.8?
> 
> I believe it's not really a tech preview anymore since EL6.4 so I'd
> expect things not to move a lot anymore until RHEL7
> 
> 
> > Do you have uncompleted features in 1.1.8?
> >
> > What repository contains Pacemaker release 1.0.12?
> >
> > Thanks for your help,
> >
> > Michael
> 
> 
> --
> Cheers,
> Florian Crouzat
> 
> ___
> 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
> 
Michael,

I've run into some bugs running Pacemaker 1.1.8 in a production environment.
I am currently waiting for Pacemaker 1.2.0 (the next stable series release)
to be available for use in production clusters. The next development release,
1.1.10, which is due out soon will be very similar to what is released as
1.2.0.

Thanks,

Andrew

___
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] strange error message after vanilla pacemaker / heartbeat install

2013-06-10 Thread Jeffrey Lewis 
Hi folks,

After installing heartbeat & pacemaker on Ubuntu 12.04 LTS, I see the
following in the /var/log/syslog.  Any ideas?  I have no resources
configured at this point, so I'm not sure where to start.

Jun 10 21:06:15 hostname heartbeat: [5033]: ERROR:
api_process_request: bad request [getrsc]
Jun 10 21:06:15 hostname cl_status: [6961]: ERROR: Cannot get cluster
resource status
Jun 10 21:06:15 hostname heartbeat: [5033]: ERROR: MSG: Dumping
message with 5 fields
Jun 10 21:06:15 hostname cl_status: [6961]: ERROR: REASON: Resource is
managed by crm.Use crm tool to query resource
Jun 10 21:06:15 hostname heartbeat: [5033]: ERROR: MSG[0] : [t=hbapi-req]
Jun 10 21:06:15 hostname heartbeat: [5033]: ERROR: MSG[1] : [reqtype=getrsc]
Jun 10 21:06:15 hostname heartbeat: [5033]: ERROR: MSG[2] :
[dest=hostname.example.com]
Jun 10 21:06:15 hostname heartbeat: [5033]: ERROR: MSG[3] : [pid=6961]
Jun 10 21:06:15 hostname heartbeat: [5033]: ERROR: MSG[4] : [from_id=6961]


Looks like I have,

pacemaker-1.1.6-2ubuntu3
heartbeat-3.0.5-3ubuntu2

Thanks,
Jeffrey

___
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] What kind of cluster stack at opensuse-repositories

2013-06-10 Thread Lars Marowsky-Bree 
On 2013-06-10T22:53:54, Andreas Mock  wrote:

> Hi Lars,
> 
> thank you for answering. Could you tell me whether the stack
> is like Option1 or Option3 of this article
> http://blog.clusterlabs.org/blog/2012/pacemaker-and-cluster-filesystems/
> 
> If it's Option1 when do you think SuSE switches to Option3?

Sure. SUSE is using option 1 in SLE HA 11, and will for the lifetime of
that product. It's working quite reliably for us today.

Option 3 is where we'll be headed with the next major release (SLE 12),
but that timeline isn't public ;-) And yes, fixing OCFS2 to handle that
properly (and getting rid of the openais dependency) is pretty high on
the list.

It's my hope that we'll have that in openSUSE 13.1, or latest, a
post-13.1 update.


Regards,
Lars

-- 
Architect Storage/HA
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 
21284 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde


___
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 monitoring user permision denied

2013-06-10 Thread Lars Marowsky-Bree 
On 2013-06-10T18:22:37, Wolfgang Routschka  
wrote:

> After reading Documentation (http://clusterlabs.org/doc/acls.html) I found 
> "All user accounts must be in the haclient group." but all users in haclient 
> group have full access "Note that the root and hacluster users will always 
> have full access."

uid=hacluster != gid=haclient


Regards,
Lars

-- 
Architect Storage/HA
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 
21284 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde


___
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] What kind of cluster stack at opensuse-repositories

2013-06-10 Thread Andreas Mock 
Hi Lars,

thank you for answering. Could you tell me whether the stack
is like Option1 or Option3 of this article
http://blog.clusterlabs.org/blog/2012/pacemaker-and-cluster-filesystems/

If it's Option1 when do you think SuSE switches to Option3?

Best regards
Andreas Mock


-Ursprüngliche Nachricht-
Von: Lars Marowsky-Bree [mailto:l...@suse.com] 
Gesendet: Montag, 10. Juni 2013 19:49
An: The Pacemaker cluster resource manager
Betreff: Re: [Pacemaker] What kind of cluster stack at opensuse-repositories

On 2013-06-10T19:25:38, Andreas Mock  wrote:

> Am I right that these a packages for a RHEL 6.x system but in a 
> corosync-pacemaker-fashion like SuSE uses it over years now?

Yes.

Those packages are scheduled for an update to latest upstream versions as
soon as we wrap up our current project, but we'll not have cman-based
packages available there, I'm pretty sure.

Of course, OBS can build them if someone else maintains them ;-) No policy
against it, just not our primary task.


Regards,
Lars

--
Architect Storage/HA
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer,
HRB 21284 (AG Nürnberg) "Experience is the name everyone gives to their
mistakes." -- Oscar Wilde


___
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

[Pacemaker] pacemaker monitoring user permision denied

2013-06-10 Thread Wolfgang Routschka 
Hi,

one more question about this topic.

I installed pacemaker-1.1.10-1.1622.6ca9c6b.git.el6.x86_64 for testing with acl.

user nagios is configured with crm-shell and role monitor

role monitor \
read cib
user nagios \
role:monitor

After starting crmsh "Attempting connection to the cluster...Could not 
establish cib_ro connection:"

After reading Documentation (http://clusterlabs.org/doc/acls.html) I found "All 
user accounts must be in the haclient group." but all users in haclient group 
have full access "Note that the root and hacluster users will always have full 
access."

How can I configure my nagios user to only running crm_mon for reading cluster 
status.

Greeting Wolfgang

>On 23/04/2013, at 2:56 PM, Andreas Mock web.de> wrote:
>
> Hi Andrew,
>
> is 1.1.10-rc1 a working title or can the package be found somewhere?
>
> Its currently just a tag.
> Grabbing the source tree and running "make TAG=Pacemaker-1.1.10-rc1 rpm" will 
> give you packages.
>
>
> I saw that on http://clusterlabs.org/rpm-next/rhel-6/x86_64/
> there is a new 1.1.9 build.
> Is this a new snapshop build (e.g. having memory leak corrections)?
>
> No, its a rebuild that turns cman support back on.
>
>
> Best regards
> Andreas Mock
>
>
> -Ursprüngliche Nachricht-
> Von: Andrew Beekhof [mailto:andrew at 
> beekhof.net]
> Gesendet: Dienstag, 23. April 2013 01:46
> An: The Pacemaker cluster resource manager
> Betreff: Re: [Pacemaker] pacemaker monitoring user permision denied
>
>
> On 23/04/2013, at 1:45 AM, Wolfgang Routschka
>  drumedar.de> wrote:
>
>> Hi everbody,
>>
>> I want to monitor our pacemaker/cman cluster on scientific linux 6.4 RHEL
> clone with nagios .
>>
>> After reading documentation http://clusterlabs.org/doc/acls.html and
>> configuration my nagios user isn´t able to start crm_mon
>>
>> "Attempting connection to the cluster...Could not establish cib_ro
> connection: Permission denied (13)"
>>
>> User is in haclient group
>>
>> [nagios at xx ~]$ id
>> uid=510(nagios) gid=310(nagios) Gruppen=310(nagios),498(haclient)
>
> This is a known issue that has been fixed in 1.1.10-rc1
>
>>
>> I used Pacemaker 1.1.8-7.el6.x86_64
>>
>> My CIB schema is configured for pacemaker-1.2
>>
>>  validate-with="pacemaker-1.2"
>>
>> enable acl is configured
>>
>> crm configure show
>>
>> property $id="cib-bootstrap-options" \
>>  dc-version="1.1.8-7.el6-394e906" \
>>  cluster-infrastructure="cman" \
>>no-quorum-policy="ignore" \
>>stonith-enabled="false" \
>>enable-acl="true"
>>
>> Greetings
>>
>> ___
>> Pacemaker mailing list: Pacemaker at 
>> 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 at 
> 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 at 
> 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] What kind of cluster stack at opensuse-repositories

2013-06-10 Thread Lars Marowsky-Bree 
On 2013-06-10T19:25:38, Andreas Mock  wrote:

> Am I right that these a packages for a RHEL 6.x system but in a
> corosync-pacemaker-fashion like SuSE uses it over years now?

Yes.

Those packages are scheduled for an update to latest upstream versions
as soon as we wrap up our current project, but we'll not have cman-based
packages available there, I'm pretty sure.

Of course, OBS can build them if someone else maintains them ;-) No
policy against it, just not our primary task.


Regards,
Lars

-- 
Architect Storage/HA
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 
21284 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde


___
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] What kind of cluster stack at opensuse-repositories

2013-06-10 Thread Andreas Mock 
Hi all,

I want to get sure that I do understand it right:

What do I find at 
http://download.opensuse.org/repositories/network:/ha-clustering/RedHat_RHEL
-6/x86_64/

Am I right that I can't use this repository as source for a
more up-to-date-replacement for the RHEL 6.x packages because
these packages are NOT build for a cman-corosync-pacemaker-cluster.

Am I right that these a packages for a RHEL 6.x system but in a
corosync-pacemaker-fashion like SuSE uses it over years now?

Please help to sorting this out.

Best regards
Andreas Mock



___
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] group resource starting parallel

2013-06-10 Thread Dejan Muhamedagic 
On Mon, Jun 10, 2013 at 06:14:27PM +0200, Dejan Muhamedagic wrote:
> On Mon, Jun 10, 2013 at 03:28:56PM +, Wolfgang Routschka wrote:
> > Hi,
> > 
> > thanks for your answer.
> > 
> > Hi,
> > 
> > On Thu, Jun 06, 2013 at 09:01:33AM +0200, Florian Crouzat wrote:
> > > Le 05/06/2013 16:23, Wolfgang Routschka a ?crit :
> > > >Hi Guys,
> > > >
> > > >one question about group  resource for starting parallel configuring 
> > > >with crmshell (Scientific Linux 64 with pacemaker 1.1.8-7, 
> > > >cman-3.0.12.1-49 and crmsh-1.2.5-55).
> > > >
> > > >in my 2 node cluster I?ll configured a group with 40 ip-address 
> > > >resources for easy managing. Now I want that start the resources 
> > > >parallel.
> > > >
> > > >in my crmshell I cannot use the option "meta ordered=false"  - these 
> > > >option is no longer disponse for my information
> > > >
> > > >Afte searching i found "resource sets" so I hope it?s correct for my 
> > > >way  to parallel my resources but I can?t configure resource sets in 
> > > >crmshell in my opinion.
> > > >
> > > >How can I configure my resources to start parallel?
> > > >
> > > >Greetings Wolfgang
> > > 
> > > Well, as one the primary author of pacemaker once said[1] "Unordered 
> > > and/or uncolocated groups are an abomination."
> > > 
> > > I don't know if his position has moved but a group beeing a syntaxic 
> > > shortcut for ordering+collocation, trying to make it behave otherwise 
> > > might not be a good idea, even if I understand your need to address a 
> > > group of 40 resources in a command.
> > > 
> > > Question: the couple seconds (if not a single second) required to 
> > > start synchronously 40 IPaddr2 RA are too long to wait for you ? Why 
> > > do you /must/ start them in parallel ?
> > 
> > I can only start my Web-Application after running all ip-resources so the 
> > first ip-resource is offline in the meantime.
> > 
> > 
> > >That's what a resource set is for. Just define a collocation with those 40 
> > >IP address resources.
> > >Thanks,
> > >
> > >Dejan
> > 
> > I don´t know how can I configure resource sets in crmshell exactly. For my 
> > information a resource set is called if 2 or more resources are in 
> > relationship in a colocation - is it right?
> 
> Yes.
> 
> > crm configure colocation c_parallel inf: (resource1, resource2, resource3, 
> > resource4)
> 
> You should drop commas:
> 
> crm configure colocation c_parallel inf: (resource1 resource2 resource3 
> resource4)
> 
> But anyway, I think that you want to remove the parenthesis:
> 
> crm configure colocation c_parallel inf: resource1 resource2 resource3 
> resource4
> 
> That should keep the resources together, but still allow that
> they start in parallel.

If you want to keep resources running independently of each
other, then I think you should use a score different from "inf".
Probably something greater than resource-stickiness, if you have
that defined too.

Thanks,

Dejan

> Thanks,
> 
> Dejan
> 
> > But in my crm_mon resources all resources successively start
> > 
> > Greetings
> > 
> > Wolfgang

___
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] The main road of the cluster stack evolution

2013-06-10 Thread Lars Marowsky-Bree 
On 2013-06-10T19:26:20, Халезов Иван  wrote:

> 1) The RedHat company is planning to drop corosync support and wants to
> switch to CMAN. (
> http://www.gossamer-threads.com/lists/linuxha/pacemaker/84662 )

To the best of my understanding, this is not correct. Red Hat will
continue to support corosync, and instead it is the cman support that
has a bad life expectancy. (But take this with a grain of salt, as I'm
obviously not privvy to RHT insights ;-)

SUSE will continue to support Pacemaker on top of corosync, as we've
done in SLE HA 11. Our future roadmap will stay with that, so we get to
skip the intermediate effort of cman. Of course, there'll be a major
update in the next major SUSE Linux Enterprise version to base on latest
upstream (corosync 2.x, etc).

> 2) What is the best tool for cluster management: crm, pcs or something else?
> 
> Redhat switches to pcs and drops crm, but SUSE prefers crmsh tool.
> 
> Why? What tool will you advice to use?

This is bound to be one of those emacs versus vi issues. People have
different preferences.

crm shell is currently certainly more mature and does more (including a
history explorer, integration with the policy engine's test mode, or the
mere ability to show the configuration in a non-xml syntax), and better
tested.

SUSE has no interest in abandoning it; and that crm shell is focused
only on managing pacemaker is a bit of a red herring, since there's
nothing that prevents crm shell from growing in that direction. We'll
continue to support crm shell, and will make sure it continues to work
with latest upstream releases.

It remains to be seen if there's common ground that allows some code
sharing between crm shell and pcs. One hopes.

(From an ISV/user/contributor/doc author preference, this must be the
most painful split ever, because it means all documentation has to be
written twice. Sigh. It's so very hard not to rant!)

But in summary, both are viable options.

> 3) What version of pacemaker should I prefer for using on RedHat 6.3 (or
> 6.4) ?
> 
> The version from the vendor (Pacemaker 1.1.7 for RedHat 6.3 and Pacemaker
> 1.1.8 for RedHat 6.4) or the upstream version from Github?
> 
> I usually prefer software versions coming from the distribution, because I
> hope they are well-tested and supported by the vendor.
> But, as I know, Pacemaker is a teсhnology preview in RedHat 6, so they don't
> response for it stability.
> Also, all the same, I have to rebuild Redhat src.rpm package ( for adding
> corosync 2.3 support into pacemaker)

Recompiling major components such as corosync/pacemaker from source will
make your cluster stack unsupported by the vendor - on either RHEL or
SLE HA. So you might as well go with the latest upstream versions on the
basis that that has the most fixes, and is the version you can get
community support for.


Regards,
Lars

-- 
Architect Storage/HA
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 
21284 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde


___
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] Differences in man pages

2013-06-10 Thread Andreas Mock 
Hi all, hi Andrew,

while having your package (pacemaker et. al.) set installed from 
http://clusterlabs.org/rpm-test-next/rhel-6/x86_64/
to (hopefully) help debugging and testing, I mentioned
the following.

The man page of 'crm_resource' doesn't mention
some parameters (like -P) which do work and are
documented by the related man page of the official
RHEL package pacemaker-cli 1.1.8.

Is there a reason that documentation was discarded?

Best regards
Andreas Mock



___
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] uname eq node-name

2013-06-10 Thread Andreas Mock 
Hi all,

I couldn't find a definitive source stating that
a corosync/pacemaker/cman cluster must follow the
rule: uname -n == node-name (== DNS-name of communication-IP)

Can someone give a hint for related documentation?

The question arises when you want to configure a
cman based cluster (cluster.conf) having a uname -n
equal to the DNS-name of the external ip address but
whant to route the cluster communication over
the internal IP-adresse (cluster interconnect).
I couldn't find a solution that doesn't use the
DNS-names of the internal ip-addresses as node-names.

Hints and rules welcome!

Best regards
Andreas Mock



___
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] The main road of the cluster stack evolution

2013-06-10 Thread Digimer 
I will answer to the best of my ability. Please note that Red Hat's 
policy is that nothing is for sure until something is released. So I am 
speaking based on what I see in the community and, of course, things 
might change when RHEL 7 is released.


On 06/10/2013 11:26 AM, Халезов Иван wrote:

Hello everyone!

I would like to ask a few questions about the main road of the cluster
stack evolution.

1) The RedHat company is planning to drop corosync support and wants to
switch to CMAN. (
http://www.gossamer-threads.com/lists/linuxha/pacemaker/84662 )

What do you think the main trend is? What is the most popular and better
supported solution? Corosync, CMAN or something else?
What cluster engine is better for Pacemaker at the moment? And what
could be the best solution in 2-3 years?


The communication and membership layer is and will remain corosync. The 
cman daemon has been removed upstream and will be gone in RHEL 7. 
Likewise, rgmanager will be gone in RHEL 7 as well.


As for "what is better", it depends on your priorities. The only cluster 
stack Red Hat supports at this time is corosync + cman + rgmanager. 
Pacemaker is in "Tech Preview" under RHEL 6, which means it is meant to 
be used in testing and development, not in production.


That said, Pacemaker is the future so there is a strong argument to 
learn it now. If you do though, you should use the repos from 
clusterlabs.org.



2) What is the best tool for cluster management: crm, pcs or something
else?

Redhat switches to pcs and drops crm, but SUSE prefers crmsh tool.

Why? What tool will you advice to use?


Red Hat wants to make life as easy as possible for people migrating from 
their current cluster stack to the planned stack that will ship with 
RHEL 7. The crmsh tool is mature and stable, and a lot of people love 
it, but it is focused on managing pacemaker only.


The pcs tool was created as a more wide-ranging tool. It supports 
corosync as well as pacemaker, and I suspect more features will be added 
as time moves on. That said, it is a very new project so parts are missing.



3) What version of pacemaker should I prefer for using on RedHat 6.3 (or
6.4) ?

The version from the vendor (Pacemaker 1.1.7 for RedHat 6.3 and
Pacemaker 1.1.8 for RedHat 6.4) or the upstream version from Github?

I usually prefer software versions coming from the distribution, because
I hope they are well-tested and supported by the vendor.
But, as I know, Pacemaker is a teсhnology preview in RedHat 6, so they
don't response for it stability.
Also, all the same, I have to rebuild Redhat src.rpm package ( for
adding corosync 2.3 support into pacemaker)


With best regards,
Ivan Khalezov


This is, again, a question of priorities. Personally, I stick to 
corosync + cman + rgmanager as it is very well tested and supported. I 
would personally not put into production something I had to install from 
source. Many people do use pacemaker in production though, so you need 
to decide this.


--
Digimer
Papers and Projects: https://alteeve.ca/w/
What if the cure for cancer is trapped in the mind of a person without 
access to education?


___
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] The main road of the cluster stack evolution

2013-06-10 Thread Andreas Mock 
Hi Ivan,

my advice: Look at 
http://blog.clusterlabs.org/blog/2013/pacemaker-on-rhel6-dot-4/
and at the other blog entries there. It gives some good insight.

Best regards
Andreas Mock


-Ursprüngliche Nachricht-
Von: Халезов Иван [mailto:i.khale...@rts.ru] 
Gesendet: Montag, 10. Juni 2013 17:26
An: The Pacemaker cluster resource manager
Betreff: [Pacemaker] The main road of the cluster stack evolution

Hello everyone!

I would like to ask a few questions about the main road of the cluster 
stack evolution.

1) The RedHat company is planning to drop corosync support and wants to 
switch to CMAN. ( 
http://www.gossamer-threads.com/lists/linuxha/pacemaker/84662 )

What do you think the main trend is? What is the most popular and better 
supported solution? Corosync, CMAN or something else?
What cluster engine is better for Pacemaker at the moment? And what 
could be the best solution in 2-3 years?

2) What is the best tool for cluster management: crm, pcs or something 
else?

Redhat switches to pcs and drops crm, but SUSE prefers crmsh tool.

Why? What tool will you advice to use?

3) What version of pacemaker should I prefer for using on RedHat 6.3 (or 
6.4) ?

The version from the vendor (Pacemaker 1.1.7 for RedHat 6.3 and 
Pacemaker 1.1.8 for RedHat 6.4) or the upstream version from Github?

I usually prefer software versions coming from the distribution, because 
I hope they are well-tested and supported by the vendor.
But, as I know, Pacemaker is a teсhnology preview in RedHat 6, so they 
don't response for it stability.
Also, all the same, I have to rebuild Redhat src.rpm package ( for 
adding corosync 2.3 support into pacemaker)


With best regards,
Ivan Khalezov

___
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] group resource starting parallel

2013-06-10 Thread Dejan Muhamedagic 
On Mon, Jun 10, 2013 at 03:28:56PM +, Wolfgang Routschka wrote:
> Hi,
> 
> thanks for your answer.
> 
> Hi,
> 
> On Thu, Jun 06, 2013 at 09:01:33AM +0200, Florian Crouzat wrote:
> > Le 05/06/2013 16:23, Wolfgang Routschka a ?crit :
> > >Hi Guys,
> > >
> > >one question about group  resource for starting parallel configuring 
> > >with crmshell (Scientific Linux 64 with pacemaker 1.1.8-7, 
> > >cman-3.0.12.1-49 and crmsh-1.2.5-55).
> > >
> > >in my 2 node cluster I?ll configured a group with 40 ip-address 
> > >resources for easy managing. Now I want that start the resources parallel.
> > >
> > >in my crmshell I cannot use the option "meta ordered=false"  - these 
> > >option is no longer disponse for my information
> > >
> > >Afte searching i found "resource sets" so I hope it?s correct for my 
> > >way  to parallel my resources but I can?t configure resource sets in 
> > >crmshell in my opinion.
> > >
> > >How can I configure my resources to start parallel?
> > >
> > >Greetings Wolfgang
> > 
> > Well, as one the primary author of pacemaker once said[1] "Unordered 
> > and/or uncolocated groups are an abomination."
> > 
> > I don't know if his position has moved but a group beeing a syntaxic 
> > shortcut for ordering+collocation, trying to make it behave otherwise 
> > might not be a good idea, even if I understand your need to address a 
> > group of 40 resources in a command.
> > 
> > Question: the couple seconds (if not a single second) required to 
> > start synchronously 40 IPaddr2 RA are too long to wait for you ? Why 
> > do you /must/ start them in parallel ?
> 
> I can only start my Web-Application after running all ip-resources so the 
> first ip-resource is offline in the meantime.
> 
> 
> >That's what a resource set is for. Just define a collocation with those 40 
> >IP address resources.
> >Thanks,
> >
> >Dejan
> 
> I don´t know how can I configure resource sets in crmshell exactly. For my 
> information a resource set is called if 2 or more resources are in 
> relationship in a colocation - is it right?

Yes.

> crm configure colocation c_parallel inf: (resource1, resource2, resource3, 
> resource4)

You should drop commas:

crm configure colocation c_parallel inf: (resource1 resource2 resource3 
resource4)

But anyway, I think that you want to remove the parenthesis:

crm configure colocation c_parallel inf: resource1 resource2 resource3 
resource4

That should keep the resources together, but still allow that
they start in parallel.

Thanks,

Dejan

> But in my crm_mon resources all resources successively start
> 
> Greetings
> 
> Wolfgang
> 
> > [1] - 
> > http://oss.clusterlabs.org/pipermail/pacemaker/2011-January/008969.htm
> > l
> > 
> > 
> > --
> > Cheers,
> > Florian Crouzat
> > 
> > ___
> > 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

___
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] The main road of the cluster stack evolution

2013-06-10 Thread emmanuel segura 
Hello

About tools, i like crmsh so much :)

Thanks


2013/6/10 Халезов Иван 

> Hello everyone!
>
> I would like to ask a few questions about the main road of the cluster
> stack evolution.
>
> 1) The RedHat company is planning to drop corosync support and wants to
> switch to CMAN. ( http://www.gossamer-threads.**
> com/lists/linuxha/pacemaker/**84662)
>
> What do you think the main trend is? What is the most popular and better
> supported solution? Corosync, CMAN or something else?
> What cluster engine is better for Pacemaker at the moment? And what could
> be the best solution in 2-3 years?
>
> 2) What is the best tool for cluster management: crm, pcs or something
> else?
>
> Redhat switches to pcs and drops crm, but SUSE prefers crmsh tool.
>
> Why? What tool will you advice to use?
>
> 3) What version of pacemaker should I prefer for using on RedHat 6.3 (or
> 6.4) ?
>
> The version from the vendor (Pacemaker 1.1.7 for RedHat 6.3 and Pacemaker
> 1.1.8 for RedHat 6.4) or the upstream version from Github?
>
> I usually prefer software versions coming from the distribution, because I
> hope they are well-tested and supported by the vendor.
> But, as I know, Pacemaker is a teсhnology preview in RedHat 6, so they
> don't response for it stability.
> Also, all the same, I have to rebuild Redhat src.rpm package ( for adding
> corosync 2.3 support into pacemaker)
>
>
> With best regards,
> Ivan Khalezov
>
> __**_
> 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
>



-- 
esta es mi vida e me la vivo hasta que dios quiera
___
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] corosync does not start

2013-06-10 Thread andreas graeper 
hi,
i found that uid.gid is hacluster.haclient but /var/log/cluster was owned
by root.root.
corosync refused to start, cause of missing write permission to log file !

another question:
i read in logs, that pacemaker plugin is not supported any longer ?!

i still use
service {
  name:pacemaker
  ver:0
 }
and it seems to work.
in what situation i  have to use ver:1
and if i would use cman, what was its role in the middle of corosync,
pacemaker ? does cman replaces corosync ?
what is cman as corosync-plugin ?

thanks in advance
andreas

2013/6/10 emmanuel segura 

> Hello Andreas
>
> What do you have in /etc/security/limits.conf ?
>
> Thanks
>
>
> 2013/6/10 andreas graeper 
>
>> hi,
>> Jun 10 15:09:06 n1 corosync[2785]:   [MAIN  ] Could not set SCHED_RR at
>> priority 99: Operation not permitted (1)
>> Jun 10 15:09:06 n1 corosync[2785]:   [MAIN  ] Could not lock memory of
>> service to avoid page faults: Cannot allocate memory (12)
>> Jun 10 15:09:06 n1 corosync[2785]:   [MAIN  ] Corosync Cluster Engine
>> ('1.4.1'): started and ready to provide service.
>> Jun 10 15:09:06 n1 corosync[2785]:   [MAIN  ] Corosync built-in features:
>> nss dbus rdma snmp
>> Jun 10 15:09:06 n1 corosync[2785]:   [MAIN  ] Successfully read main
>> configuration file '/etc/corosync/corosync.conf'.
>> Jun 10 15:09:06 n1 corosync[2785]:   [MAIN  ] Corosync Executive couldn't
>> create lock file.
>> Jun 10 15:09:06 n1 corosync[2785]:   [MAIN  ] Corosync Cluster Engine
>> exiting with status 17 at main.c:1794.
>>
>> sestatus : disabled
>> corosync-blackbox :
>>  Failed to initialize the objdb API. Error 6
>>  Failed to initialize the objdb API. Error 6
>>  failed to open /var/lib/corosync/fdata: No such file or directory
>>
>> please help
>> andreas
>>
>>
>> ___
>> 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
>>
>>
>
>
> --
> esta es mi vida e me la vivo hasta que dios quiera
>
> ___
> 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

[Pacemaker] The main road of the cluster stack evolution

2013-06-10 Thread Халезов Иван 

Hello everyone!

I would like to ask a few questions about the main road of the cluster 
stack evolution.


1) The RedHat company is planning to drop corosync support and wants to 
switch to CMAN. ( 
http://www.gossamer-threads.com/lists/linuxha/pacemaker/84662 )


What do you think the main trend is? What is the most popular and better 
supported solution? Corosync, CMAN or something else?
What cluster engine is better for Pacemaker at the moment? And what 
could be the best solution in 2-3 years?


2) What is the best tool for cluster management: crm, pcs or something 
else?


Redhat switches to pcs and drops crm, but SUSE prefers crmsh tool.

Why? What tool will you advice to use?

3) What version of pacemaker should I prefer for using on RedHat 6.3 (or 
6.4) ?


The version from the vendor (Pacemaker 1.1.7 for RedHat 6.3 and 
Pacemaker 1.1.8 for RedHat 6.4) or the upstream version from Github?


I usually prefer software versions coming from the distribution, because 
I hope they are well-tested and supported by the vendor.
But, as I know, Pacemaker is a teсhnology preview in RedHat 6, so they 
don't response for it stability.
Also, all the same, I have to rebuild Redhat src.rpm package ( for 
adding corosync 2.3 support into pacemaker)



With best regards,
Ivan Khalezov

___
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] group resource starting parallel

2013-06-10 Thread Wolfgang Routschka 
Hi,

thanks for your answer.

Hi,

On Thu, Jun 06, 2013 at 09:01:33AM +0200, Florian Crouzat wrote:
> Le 05/06/2013 16:23, Wolfgang Routschka a ?crit :
> >Hi Guys,
> >
> >one question about group  resource for starting parallel configuring 
> >with crmshell (Scientific Linux 64 with pacemaker 1.1.8-7, cman-3.0.12.1-49 
> >and crmsh-1.2.5-55).
> >
> >in my 2 node cluster I?ll configured a group with 40 ip-address 
> >resources for easy managing. Now I want that start the resources parallel.
> >
> >in my crmshell I cannot use the option "meta ordered=false"  - these 
> >option is no longer disponse for my information
> >
> >Afte searching i found "resource sets" so I hope it?s correct for my 
> >way  to parallel my resources but I can?t configure resource sets in 
> >crmshell in my opinion.
> >
> >How can I configure my resources to start parallel?
> >
> >Greetings Wolfgang
> 
> Well, as one the primary author of pacemaker once said[1] "Unordered 
> and/or uncolocated groups are an abomination."
> 
> I don't know if his position has moved but a group beeing a syntaxic 
> shortcut for ordering+collocation, trying to make it behave otherwise 
> might not be a good idea, even if I understand your need to address a 
> group of 40 resources in a command.
> 
> Question: the couple seconds (if not a single second) required to 
> start synchronously 40 IPaddr2 RA are too long to wait for you ? Why 
> do you /must/ start them in parallel ?

I can only start my Web-Application after running all ip-resources so the first 
ip-resource is offline in the meantime.


>That's what a resource set is for. Just define a collocation with those 40 IP 
>address resources.
>Thanks,
>
>Dejan

I don´t know how can I configure resource sets in crmshell exactly. For my 
information a resource set is called if 2 or more resources are in relationship 
in a colocation - is it right?

crm configure colocation c_parallel inf: (resource1, resource2, resource3, 
resource4)

But in my crm_mon resources all resources successively start

Greetings

Wolfgang

> [1] - 
> http://oss.clusterlabs.org/pipermail/pacemaker/2011-January/008969.htm
> l
> 
> 
> --
> Cheers,
> Florian Crouzat
> 
> ___
> 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] corosync does not start

2013-06-10 Thread emmanuel segura 
Hello Andreas

What do you have in /etc/security/limits.conf ?

Thanks


2013/6/10 andreas graeper 

> hi,
> Jun 10 15:09:06 n1 corosync[2785]:   [MAIN  ] Could not set SCHED_RR at
> priority 99: Operation not permitted (1)
> Jun 10 15:09:06 n1 corosync[2785]:   [MAIN  ] Could not lock memory of
> service to avoid page faults: Cannot allocate memory (12)
> Jun 10 15:09:06 n1 corosync[2785]:   [MAIN  ] Corosync Cluster Engine
> ('1.4.1'): started and ready to provide service.
> Jun 10 15:09:06 n1 corosync[2785]:   [MAIN  ] Corosync built-in features:
> nss dbus rdma snmp
> Jun 10 15:09:06 n1 corosync[2785]:   [MAIN  ] Successfully read main
> configuration file '/etc/corosync/corosync.conf'.
> Jun 10 15:09:06 n1 corosync[2785]:   [MAIN  ] Corosync Executive couldn't
> create lock file.
> Jun 10 15:09:06 n1 corosync[2785]:   [MAIN  ] Corosync Cluster Engine
> exiting with status 17 at main.c:1794.
>
> sestatus : disabled
> corosync-blackbox :
>  Failed to initialize the objdb API. Error 6
>  Failed to initialize the objdb API. Error 6
>  failed to open /var/lib/corosync/fdata: No such file or directory
>
> please help
> andreas
>
>
> ___
> 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
>
>


-- 
esta es mi vida e me la vivo hasta que dios quiera
___
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] corosync does not start

2013-06-10 Thread andreas graeper 
hi,

service corosync start  as root


2013/6/10 emmanuel segura 

> Hello Andreas
>
> Ho do you start the cluster ?
>
> Thanks
>
>
> 2013/6/10 andreas graeper 
>
>> hi,
>> Jun 10 15:09:06 n1 corosync[2785]:   [MAIN  ] Could not set SCHED_RR at
>> priority 99: Operation not permitted (1)
>> Jun 10 15:09:06 n1 corosync[2785]:   [MAIN  ] Could not lock memory of
>> service to avoid page faults: Cannot allocate memory (12)
>> Jun 10 15:09:06 n1 corosync[2785]:   [MAIN  ] Corosync Cluster Engine
>> ('1.4.1'): started and ready to provide service.
>> Jun 10 15:09:06 n1 corosync[2785]:   [MAIN  ] Corosync built-in features:
>> nss dbus rdma snmp
>> Jun 10 15:09:06 n1 corosync[2785]:   [MAIN  ] Successfully read main
>> configuration file '/etc/corosync/corosync.conf'.
>> Jun 10 15:09:06 n1 corosync[2785]:   [MAIN  ] Corosync Executive couldn't
>> create lock file.
>> Jun 10 15:09:06 n1 corosync[2785]:   [MAIN  ] Corosync Cluster Engine
>> exiting with status 17 at main.c:1794.
>>
>> sestatus : disabled
>> corosync-blackbox :
>>  Failed to initialize the objdb API. Error 6
>>  Failed to initialize the objdb API. Error 6
>>  failed to open /var/lib/corosync/fdata: No such file or directory
>>
>> please help
>> andreas
>>
>>
>> ___
>> 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
>>
>>
>
>
> --
> esta es mi vida e me la vivo hasta que dios quiera
>
> ___
> 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] Can I use Pacemaker release 1.1.8 for production clusters?

2013-06-10 Thread Florian Crouzat 

Le 10/06/2013 16:46, Michael Furman a écrit :

Hi all!

According to the Wiki http://clusterlabs.org/wiki/Releases



This page has not been updated since 10:49, 11 February 2011



Even numbered release series (eg. 0.6.x, 1.0.x) are recommended for
production clusters.

I need to install Pacemaker on Centos 6 machines.
Unfortunately, the main Centos repository contains only 1.1.8-7.el6 version.

Questions:
Can I use Pacemaker release 1.1.8 for production clusters (we want to
work with the Centos repository)?


I hope so


Do you expect to change existing features in 1.1.8?


I believe it's not really a tech preview anymore since EL6.4 so I'd 
expect things not to move a lot anymore until RHEL7




Do you have uncompleted features in 1.1.8?

What repository contains Pacemaker release 1.0.12?

Thanks for your help,

Michael



--
Cheers,
Florian Crouzat

___
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] Can I use Pacemaker release 1.1.8 for production clusters?

2013-06-10 Thread Michael Furman 


Hi all!

According to the Wiki http://clusterlabs.org/wiki/Releases:

Even numbered release series (eg. 0.6.x, 1.0.x) are
recommended for production clusters.

I need to install Pacemaker
on Centos 6 machines.

Unfortunately, the main Centos repository contains only 1.1.8-7.el6 version.

Questions:

Can I use Pacemaker release 1.1.8 for
production clusters (we want to work with the Centos repository)?

Do you expect to change existing features in 1.1.8?

Do you have uncompleted features in 1.1.8?



What repository contains Pacemaker release
1.0.12?

Thanks for your help,

   Michael

  ___
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] corosync does not start

2013-06-10 Thread emmanuel segura 
Hello Andreas

Ho do you start the cluster ?

Thanks


2013/6/10 andreas graeper 

> hi,
> Jun 10 15:09:06 n1 corosync[2785]:   [MAIN  ] Could not set SCHED_RR at
> priority 99: Operation not permitted (1)
> Jun 10 15:09:06 n1 corosync[2785]:   [MAIN  ] Could not lock memory of
> service to avoid page faults: Cannot allocate memory (12)
> Jun 10 15:09:06 n1 corosync[2785]:   [MAIN  ] Corosync Cluster Engine
> ('1.4.1'): started and ready to provide service.
> Jun 10 15:09:06 n1 corosync[2785]:   [MAIN  ] Corosync built-in features:
> nss dbus rdma snmp
> Jun 10 15:09:06 n1 corosync[2785]:   [MAIN  ] Successfully read main
> configuration file '/etc/corosync/corosync.conf'.
> Jun 10 15:09:06 n1 corosync[2785]:   [MAIN  ] Corosync Executive couldn't
> create lock file.
> Jun 10 15:09:06 n1 corosync[2785]:   [MAIN  ] Corosync Cluster Engine
> exiting with status 17 at main.c:1794.
>
> sestatus : disabled
> corosync-blackbox :
>  Failed to initialize the objdb API. Error 6
>  Failed to initialize the objdb API. Error 6
>  failed to open /var/lib/corosync/fdata: No such file or directory
>
> please help
> andreas
>
>
> ___
> 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
>
>


-- 
esta es mi vida e me la vivo hasta que dios quiera
___
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] corosync does not start

2013-06-10 Thread andreas graeper 
hi,
Jun 10 15:09:06 n1 corosync[2785]:   [MAIN  ] Could not set SCHED_RR at
priority 99: Operation not permitted (1)
Jun 10 15:09:06 n1 corosync[2785]:   [MAIN  ] Could not lock memory of
service to avoid page faults: Cannot allocate memory (12)
Jun 10 15:09:06 n1 corosync[2785]:   [MAIN  ] Corosync Cluster Engine
('1.4.1'): started and ready to provide service.
Jun 10 15:09:06 n1 corosync[2785]:   [MAIN  ] Corosync built-in features:
nss dbus rdma snmp
Jun 10 15:09:06 n1 corosync[2785]:   [MAIN  ] Successfully read main
configuration file '/etc/corosync/corosync.conf'.
Jun 10 15:09:06 n1 corosync[2785]:   [MAIN  ] Corosync Executive couldn't
create lock file.
Jun 10 15:09:06 n1 corosync[2785]:   [MAIN  ] Corosync Cluster Engine
exiting with status 17 at main.c:1794.

sestatus : disabled
corosync-blackbox :
 Failed to initialize the objdb API. Error 6
 Failed to initialize the objdb API. Error 6
 failed to open /var/lib/corosync/fdata: No such file or directory

please help
andreas
___
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] Patrik Rapposch is out of the office

2013-06-10 Thread Digimer 

On 06/10/2013 03:04 AM, patrik.rappo...@knapp.com wrote:


Ich werde ab  10.06.2013 nicht im Büro sein. Ich kehre zurück am
14.06.2013.

Sehr geehrte Damen und Herren,
ich bin bis einschließlich 14.06 nicht verfügbar. Bitte wenden Sie sich für
Netzwerk bezogene Anliegen immer an ksi.netw...@knapp.com. Falls es sich um
Kunden-Betriebssystem Punkte handeln sollte, senden Sie Ihre Mail bitte
immer an ksi...@knapp.com.
Please note, that I am on not available until 14.06.2013. Always use
"ksi.netw...@knapp.com", which ensures that one of our network
adminsitrators takes care of your interest. If you need operating system
support please contact ksi...@knapp-systems.com.


Patrik,

  Can you please set your out of office alerts to not reply to mailing 
list postings?


--
Digimer
Papers and Projects: https://alteeve.ca/w/
What if the cure for cancer is trapped in the mind of a person without 
access to education?


___
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] commandline option to load cib-file like crm(live)configure: load /tmp/cib

2013-06-10 Thread emmanuel segura 
Hello Bauer

crm configure < filename


2013/6/10 Bauer, Stefan (IZLBW Extern) 

>  I was to stupid to read the manpage. Its done like:
>
> ** **
>
> crm configure load replace /tmp/cib
>
> ** **
>
> sorry for the trouble!
>
> ** **
>
> Stefan
>
> ** **
>
> *Von:* Bauer, Stefan (IZLBW Extern) [mailto:stefan.ba...@iz.bwl.de]
> *Gesendet:* Montag, 10. Juni 2013 13:57
> *An:* pacemaker@oss.clusterlabs.org
> *Betreff:* [Pacemaker] commandline option to load cib-file like
> crm(live)configure: load /tmp/cib
>
> ** **
>
> Dear Users,
>
> ** **
>
> we have prepared a tiny cib-file and want to load it into the cluster on
> the commandline.
>
> It works fine if executed in the crm tool with
>
> ** **
>
> crm(live)configure: load /tmp/cib
>
> ** **
>
> How can this be done on the commandline?
>
> ** **
>
> Keep in mind, that our cib-file is not xml but the crm subshell can handle
> it anyway.
>
> ** **
>
> Here is a stanza from /tmp/cib:
>
> ** **
>
> primitive p_eth0 ocf:heartbeat:IPaddr2 \
>
> params ip=”1.2.3.4” cidr_netmask=”24” nic=”eth0” \
>
> and so on….
>
> ** **
>
> Thank you in advance!
>
> ** **
>
> Stefan
>
> ___
> 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
>
>


-- 
esta es mi vida e me la vivo hasta que dios quiera
___
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] commandline option to load cib-file like crm(live)configure: load /tmp/cib

2013-06-10 Thread Bauer, Stefan (IZLBW Extern) 
I was to stupid to read the manpage. Its done like:

crm configure load replace /tmp/cib

sorry for the trouble!

Stefan

Von: Bauer, Stefan (IZLBW Extern) [mailto:stefan.ba...@iz.bwl.de]
Gesendet: Montag, 10. Juni 2013 13:57
An: pacemaker@oss.clusterlabs.org
Betreff: [Pacemaker] commandline option to load cib-file like 
crm(live)configure: load /tmp/cib

Dear Users,

we have prepared a tiny cib-file and want to load it into the cluster on the 
commandline.
It works fine if executed in the crm tool with

crm(live)configure: load /tmp/cib

How can this be done on the commandline?

Keep in mind, that our cib-file is not xml but the crm subshell can handle it 
anyway.

Here is a stanza from /tmp/cib:

primitive p_eth0 ocf:heartbeat:IPaddr2 \
params ip="1.2.3.4" cidr_netmask="24" nic="eth0" \
and so on

Thank you in advance!

Stefan
___
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] commandline option to load cib-file like crm(live)configure: load /tmp/cib

2013-06-10 Thread Bauer, Stefan (IZLBW Extern) 
Dear Users,

we have prepared a tiny cib-file and want to load it into the cluster on the 
commandline.
It works fine if executed in the crm tool with

crm(live)configure: load /tmp/cib

How can this be done on the commandline?

Keep in mind, that our cib-file is not xml but the crm subshell can handle it 
anyway.

Here is a stanza from /tmp/cib:

primitive p_eth0 ocf:heartbeat:IPaddr2 \
params ip="1.2.3.4" cidr_netmask="24" nic="eth0" \
and so on

Thank you in advance!

Stefan
___
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] [PATCH] Low: tools: provide UUID-like string to digest generation

2013-06-10 Thread Vladislav Bogdanov 
This should make "warning: decode_transition_key: Bad UUID (crm_resource.c) in 
sscanf result (4) for 31980:0:0:crm_resource.c"
go away.

---
 tools/crm_resource.c |4 +++-
 1 files changed, 3 insertions(+), 1 deletions(-)

diff --git a/tools/crm_resource.c b/tools/crm_resource.c
index 2aef08b..0fbae4d 100644
--- a/tools/crm_resource.c
+++ b/tools/crm_resource.c
@@ -42,6 +42,8 @@
 #include 
 #include 
 
+#  define FAKE_TE_ID   "----"
+
 bool scope_master = FALSE;
 gboolean do_force = FALSE;
 gboolean BE_QUIET = FALSE;
@@ -669,7 +671,7 @@ send_lrm_rsc_op(crm_ipc_t * crmd_channel, const char *op,
 }
 }
 
-key = generate_transition_key(0, getpid(), 0, __FILE__);
+key = generate_transition_key(0, getpid(), 0, FAKE_TE_ID);
 
 msg_data = create_xml_node(NULL, XML_GRAPH_TAG_RSC_OP);
 crm_xml_add(msg_data, XML_ATTR_TRANSITION_KEY, key);
-- 
1.7.1

___
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] Patrik Rapposch is out of the office

2013-06-10 Thread Patrik . Rapposch 

Ich werde ab  10.06.2013 nicht im Büro sein. Ich kehre zurück am
14.06.2013.

Sehr geehrte Damen und Herren,
ich bin bis einschließlich 14.06 nicht verfügbar. Bitte wenden Sie sich für
Netzwerk bezogene Anliegen immer an ksi.netw...@knapp.com. Falls es sich um
Kunden-Betriebssystem Punkte handeln sollte, senden Sie Ihre Mail bitte
immer an ksi...@knapp.com.
Please note, that I am on not available until 14.06.2013. Always use
"ksi.netw...@knapp.com", which ensures that one of our network
adminsitrators takes care of your interest. If you need operating system
support please contact ksi...@knapp-systems.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://bugs.clusterlabs.org

[Pacemaker] start of pacemaker fails

2013-06-10 Thread Kazunori INOUE 
Hi,
I'm using pacemaker-1.1 (8807e990c7. the latest devel) with corosync-2.3.0.

After this commit, start of pacemaker fails.
https://github.com/ClusterLabs/pacemaker/commit/17237616a12e37e2c073b3bff7dded3d66bc8201

I have not set nodelist{} in corosync.conf.

$ service corosync start
Starting Corosync Cluster Engine (corosync):   [  OK  ]
$ service pacemaker start
Starting Pacemaker Cluster Manager:[FAILED]
$ grep stonith-ng /var/log/ha-log
Jun 10 14:39:54 dev1 pacemakerd[5398]: info: start_child: Forked child 5401 
for process stonith-ng
Jun 10 14:39:55 dev1 stonith-ng[5401]:   notice: crm_add_logfile: Additional 
logging available in /var/log/ha-debug
Jun 10 14:39:55 dev1 stonith-ng[5401]:debug: crm_update_callsites: Enabling 
callsites based on priority=7, files=(null), functions=(null), formats=(null), 
tags=(null)
Jun 10 14:39:55 dev1 stonith-ng[5401]: info: crm_log_init: Changed active 
directory to /var/lib/heartbeat/cores/root
Jun 10 14:39:55 dev1 stonith-ng[5401]: info: get_cluster_type: Verifying 
cluster type: 'corosync'
Jun 10 14:39:55 dev1 stonith-ng[5401]: info: get_cluster_type: Assuming an 
active 'corosync' cluster
Jun 10 14:39:55 dev1 stonith-ng[5401]:   notice: crm_cluster_connect: 
Connecting to cluster infrastructure: corosync
Jun 10 14:39:55 dev1 stonith-ng[5401]: info: crm_get_peer: Created entry 
e96819ac-1936-4332-9d42-089a45d80fbe/0xe004f0 for node (null)/3232261525 (1 
total)
Jun 10 14:39:55 dev1 stonith-ng[5401]: info: crm_get_peer: Node 3232261525 
has uuid 3232261525
Jun 10 14:39:55 dev1 stonith-ng[5401]: info: crm_update_peer_proc: 
init_cpg_connection: Node (null)[3232261525] - corosync-cpg is now online
Jun 10 14:39:55 dev1 stonith-ng[5401]: info: init_cs_connection_once: 
Connection to 'corosync': established
Jun 10 14:39:55 dev1 pacemakerd[5398]:   notice: stop_child: Stopping 
stonith-ng: Sent -15 to process 5401
Jun 10 14:39:55 dev1 stonith-ng[5401]:   notice: corosync_node_name: Unable to 
get node name for nodeid 3232261525
Jun 10 14:39:55 dev1 stonith-ng[5401]:   notice: get_node_name: Could not 
obtain a node name for corosync nodeid 0
Jun 10 14:39:55 dev1 stonith-ng[5401]:error: init_cs_connection_once: Could 
not establish local node name
Jun 10 14:39:55 dev1 stonith-ng[5401]: crit: main: Cannot sign in to the 
cluster... terminating
Jun 10 14:39:55 dev1 stonith-ng[5401]: info: crm_xml_cleanup: Cleaning up 
memory from libxml2
Jun 10 14:39:55 dev1 pacemakerd[5398]:error: pcmk_child_exit: Child process 
stonith-ng (5401) exited: Network is down (100)
Jun 10 14:39:55 dev1 pacemakerd[5398]:  warning: pcmk_child_exit: Pacemaker 
child process stonith-ng no longer wishes to be respawned. Shutting ourselves 
down.

The start was successful when adding the following change.
In the case of corosync, is it specifications not to set TRUE to do_uname?

$ git diff --patch-with-stat
 lib/cluster/cluster.c |1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/lib/cluster/cluster.c b/lib/cluster/cluster.c
index bee991c..efb3b42 100644
--- a/lib/cluster/cluster.c
+++ b/lib/cluster/cluster.c
@@ -318,6 +318,7 @@ get_node_name(uint32_t nodeid)
 #  if SUPPORT_COROSYNC
 case pcmk_cluster_corosync:
 name = corosync_node_name(0, nodeid);
+do_uname = TRUE;
 break;
 #  endif
 #endif
$

Best Regards,
Kazunori INOUE

___
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