On 13/03/14 01:29 AM, John Wei wrote:
Currently, management of pacemaker is done through CLI or xml. Any plan to
provide RESTful api to support cloud software?
John
pcsd is REST-like.
--
Digimer
Papers and Projects: https://alteeve.ca/w/
What if the cure for cancer is trapped in the mind of a
Currently, management of pacemaker is done through CLI or xml. Any plan to
provide RESTful api to support cloud software?
John
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Hom
Well I think I have worked it out
# Create ybrp ip address
pcs resource create ybrpip ocf:heartbeat:IPaddr2 params ip=10.172.214.50
cidr_netmask=24 nic=eth0 clusterip_hash=sourceip-sourceport \
op start interval="0s" timeout="60s" \
op monitor interval="5s" timeout="20s" \
op stop
Hi
I sent out an email to help convert an old config. Thought it might better to
start from scratch.
I have 2 nodes, which run an application (sort of a reverse proxy).
Node A
Node B
I would like to use OCF:IPaddr2 so that I can load balance IP
# Create ybrp ip address
pcs resource create yb
> -Original Message-
> From: Andrew Beekhof [mailto:and...@beekhof.net]
> Sent: Thursday, 13 March 2014 1:39 PM
> To: The Pacemaker cluster resource manager
> Subject: Re: [Pacemaker] help migrating over cluster config from pacemaker
> plugin into corosync to pcs
[snip]
> > I was trying
On 13 Mar 2014, at 11:56 am, Alex Samad - Yieldbroker
wrote:
> Hi
>
> So this is what I used to do to setup my cluster
> crm configure property stonith-enabled=false
> crm configure property no-quorum-policy=ignore
> crm configure rsc_defaults resource-stickiness=100
> crm configure primitive
Hi
So this is what I used to do to setup my cluster
crm configure property stonith-enabled=false
crm configure property no-quorum-policy=ignore
crm configure rsc_defaults resource-stickiness=100
crm configure primitive ybrpip ocf:heartbeat:IPaddr2 params ip=10.32.21.30
cidr_netmask=24 op monitor
On 12/03/14 23:18, Alex Samad - Yieldbroker wrote:
> Hi
>
> Just going through my cluster build, seems like
>
> yum install pacemaker
>
> wants to bring in samba, I have recently migrated up to samba4, wondering if
> I can find a pacemaker that is dependant on samba4 ?
>
> Im on centos 6.5, on a
Hi
Just going through my cluster build, seems like
yum install pacemaker
wants to bring in samba, I have recently migrated up to samba4, wondering if I
can find a pacemaker that is dependant on samba4 ?
Im on centos 6.5, on a quick look I am guessing this might not be a pacemaker
issue, migh
On 2014-03-12T16:16:54, Karl Rößmann wrote:
> >>primitive fkflmw ocf:heartbeat:Xen \
> >>meta target-role="Started" is-managed="true" allow-migrate="true" \
> >>op monitor interval="10" timeout="30" \
> >>op migrate_from interval="0" timeout="600" \
> >>op migrate_
On 13 Mar 2014, at 9:29 am, Jay G. Scott wrote:
>
> OS = RHEL 6
>
> because my machines are behind a firewall, i can't install
> via yum. i had to bring down the rpms and install them.
> here are the rpms i installed. yeah, it bothers me that
> they say fc20 but that's what i got when i used
OS = RHEL 6
because my machines are behind a firewall, i can't install
via yum. i had to bring down the rpms and install them.
here are the rpms i installed. yeah, it bothers me that
they say fc20 but that's what i got when i used the
pacemaker.repo file i found online.
corosync-2.3.3-1.fc20.x
> -Original Message-
> From: Jan Friesse [mailto:jfrie...@redhat.com]
> Sent: Wednesday, March 12, 2014 4:31 PM
> To: The Pacemaker cluster resource manager
> Subject: Re: [Pacemaker] Pacemaker/corosync freeze
>
> Attila Megyeri napsal(a):
> >> -Original Message-
> >> From: Jan Fr
Attila Megyeri napsal(a):
>> -Original Message-
>> From: Jan Friesse [mailto:jfrie...@redhat.com]
>> Sent: Wednesday, March 12, 2014 2:27 PM
>> To: The Pacemaker cluster resource manager
>> Subject: Re: [Pacemaker] Pacemaker/corosync freeze
>>
>> Attila Megyeri napsal(a):
>>> Hello Jan,
>>>
Hi.
primitive fkflmw ocf:heartbeat:Xen \
meta target-role="Started" is-managed="true" allow-migrate="true" \
op monitor interval="10" timeout="30" \
op migrate_from interval="0" timeout="600" \
op migrate_to interval="0" timeout="600" \
params xmfile="/etc
On 2014-03-12T15:17:13, Karl Rößmann wrote:
> Hi,
>
> we have a two node HA cluster using SuSE SlES 11 HA Extension SP3,
> latest release value.
> A resource (xen) was manually stopped, the shutdown_timeout is 120s
> but after 60s the node was fenced and shut down by the other node.
>
> should
> -Original Message-
> From: Jan Friesse [mailto:jfrie...@redhat.com]
> Sent: Wednesday, March 12, 2014 2:27 PM
> To: The Pacemaker cluster resource manager
> Subject: Re: [Pacemaker] Pacemaker/corosync freeze
>
> Attila Megyeri napsal(a):
> > Hello Jan,
> >
> > Thank you very much for your
Hi,
we have a two node HA cluster using SuSE SlES 11 HA Extension SP3,
latest release value.
A resource (xen) was manually stopped, the shutdown_timeout is 120s
but after 60s the node was fenced and shut down by the other node.
should I change some timeout value ?
This is a part of our configur
12.03.2014 00:40, Andrew Beekhof wrote:
>
> On 11 Mar 2014, at 6:23 pm, Vladislav Bogdanov wrote:
>
>> 07.03.2014 10:30, Vladislav Bogdanov wrote:
>>> 07.03.2014 05:43, Andrew Beekhof wrote:
On 6 Mar 2014, at 10:39 pm, Vladislav Bogdanov
wrote:
> 18.02.2014 03:49, Andre
Attila Megyeri napsal(a):
> Hello Jan,
>
> Thank you very much for your help so far.
>
>> -Original Message-
>> From: Jan Friesse [mailto:jfrie...@redhat.com]
>> Sent: Wednesday, March 12, 2014 9:51 AM
>> To: The Pacemaker cluster resource manager
>> Subject: Re: [Pacemaker] Pacemaker/cor
Hello Jan,
Thank you very much for your help so far.
> -Original Message-
> From: Jan Friesse [mailto:jfrie...@redhat.com]
> Sent: Wednesday, March 12, 2014 9:51 AM
> To: The Pacemaker cluster resource manager
> Subject: Re: [Pacemaker] Pacemaker/corosync freeze
>
> Attila Megyeri napsal
Attila Megyeri napsal(a):
>
>> -Original Message-
>> From: Andrew Beekhof [mailto:and...@beekhof.net]
>> Sent: Tuesday, March 11, 2014 10:27 PM
>> To: The Pacemaker cluster resource manager
>> Subject: Re: [Pacemaker] Pacemaker/corosync freeze
>>
>>
>> On 12 Mar 2014, at 1:54 am, Attila Me
> -Original Message-
> From: Andrew Beekhof [mailto:and...@beekhof.net]
> Sent: Tuesday, March 11, 2014 10:27 PM
> To: The Pacemaker cluster resource manager
> Subject: Re: [Pacemaker] Pacemaker/corosync freeze
>
>
> On 12 Mar 2014, at 1:54 am, Attila Megyeri
> wrote:
>
> >>
> >> -
23 matches
Mail list logo