On Fri, Feb 22, 2013 at 4:55 PM, Vladislav Bogdanov
wrote:
> 04.01.2013 13:56, Andrew Beekhof wrote:
>> On Fri, Jan 4, 2013 at 4:27 PM, Vladislav Bogdanov
>> wrote:
>>> 04.01.2013 06:07, Andrew Beekhof wrote:
On Wed, Dec 19, 2012 at 7:33 PM, Vladislav Bogdanov
wrote:
> Hi all,
>>>
On Fri, Feb 22, 2013 at 4:11 PM, Lars Kellogg-Stedman wrote:
>> > You'd think that would help, but
>> >
>> > https://bugzilla.redhat.com/show_bug.cgi?id=880035 suggests otherwise.
>> > I have one remaining fedora machine where KVM clusters still work, I
>> > don't think I'll ever update it now.
>>
04.01.2013 13:56, Andrew Beekhof wrote:
> On Fri, Jan 4, 2013 at 4:27 PM, Vladislav Bogdanov
> wrote:
>> 04.01.2013 06:07, Andrew Beekhof wrote:
>>> On Wed, Dec 19, 2012 at 7:33 PM, Vladislav Bogdanov
>>> wrote:
Hi all,
I'd like to share my successful attempt to confine pacemaker.
>
> > You'd think that would help, but
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=880035 suggests otherwise.
> > I have one remaining fedora machine where KVM clusters still work, I
> > don't think I'll ever update it now.
> >
Well, that was fascinating read.
Using the udpu transport se
On Fri, Feb 22, 2013 at 2:21 PM, Lars Kellogg-Stedman wrote:
> The "switch" is a standard Linux bridge device, and the two systems are KVM
> virtual machines attached to the same bridge.
You'd think that would help, but
https://bugzilla.redhat.com/show_bug.cgi?id=880035 suggests otherwise.
I have
The "switch" is a standard Linux bridge device, and the two systems are KVM
virtual machines attached to the same bridge. Are there known problems
with this configuration? I' can't get corosync to stay up for more than a
few minutes. I would simply use a vrrp or carp solution, but I need a
servi
On Fri, Feb 22, 2013 at 1:00 PM, Lars Kellogg-Stedman wrote:
>
>> Did you define a recurring monitor action?
>>
>
> You know, upon reflection, probably not. I started with "op monitor
> interval=10s", but because of all the problems I ran into with pcs
> complaining about systemd: services I thin
> Did you define a recurring monitor action?
>
>
You know, upon reflection, probably not. I started with "op monitor
interval=10s", but because of all the problems I ran into with pcs
complaining about systemd: services I think I dropped everything except the
service name and agent in order to sim
On Fri, Feb 22, 2013 at 9:10 AM, Lars Kellogg-Stedman wrote:
> Howdy all,
>
> I'm trying to run Pacemaker 1.1.8 (from
> http://clusterlabs.org/rpm-next/fedora-17/clusterlabs.repo) in a
> two-node configuration under Fedora 17. I'm running into a few
> different problems.
>
> I'm trying to create
On Fri, Feb 22, 2013 at 11:57 AM, Donald Stahl wrote:
>> I'm pretty sure the latter doesn't do anything (bad choice of defaults
>> by the crmsh) because the set isn't colocated with anything.
> It sets sequential=false for the items in that set and it definitely
> behaves differently when I use it
> I'm pretty sure the latter doesn't do anything (bad choice of defaults
> by the crmsh) because the set isn't colocated with anything.
It sets sequential=false for the items in that set and it definitely
behaves differently when I use it.
Without the ()'s if I stop the second service- the first o
On Fri, Feb 22, 2013 at 10:24 AM, pavan tc wrote:
> Hi,
>
> I have installed pacemaker/corosync from the standard yum repositories on my
> CentOS 6.2 box.
> What I get is the following:
>
> pacemaker-cli-1.1.7-6.el6.x86_64
> pacemaker-cluster-libs-1.1.7-6.el6.x86_64
> pacemaker-libs-1.1.7-6.el6.x8
On Fri, Feb 22, 2013 at 5:18 AM, Brian J. Murrell wrote:
> I wonder what happens in the case of two racing "crm" commands that want
> to update the CIB (with non-overlapping/conflicting data). Is there any
> locking to ensure that one crm cannot overwrite the other's change?
> (i.e. second one to
On Fri, Feb 22, 2013 at 11:39 AM, Andrew Beekhof wrote:
> On Fri, Feb 22, 2013 at 1:40 AM, Donald Stahl wrote:
>>> No.
>>>
>>> [quote]
>>> If you say "colocate A with B" and there is nowhere B is allowed to
>>> run, then A wont be allowed to run either.
>>> But once the cluster has figured out wh
On Fri, Feb 22, 2013 at 1:40 AM, Donald Stahl wrote:
>> No.
>>
>> [quote]
>> If you say "colocate A with B" and there is nowhere B is allowed to
>> run, then A wont be allowed to run either.
>> But once the cluster has figured out where they go, it doesn't stop
>> them being started in parallel.
>
Hi,
I have installed pacemaker/corosync from the standard yum repositories on
my CentOS 6.2 box.
What I get is the following:
pacemaker-cli-1.1.7-6.el6.x86_64
pacemaker-cluster-libs-1.1.7-6.el6.x86_64
pacemaker-libs-1.1.7-6.el6.x86_64
pacemaker-1.1.7-6.el6.x86_64
corosynclib-1.4.1-7.el6_3.1.x86_6
So far as I know, crm has not changed. That said, Pacemaker is in "Tech
Preview" on Red Hat, so the usual "nothing changes EVAR!" doesn't apply.
Glad you found the tutorial helpful! Always happy to hear from folks. :)
digimer
On 02/21/2013 05:33 PM, Bob Haxo wrote:
Digimer
Thanks for the inf
Digimer
Thanks for the info. I missed this change, and my codes are now borken.
Huge mistake by me. Hopefully the crm syntax has not changed, or not
changed significantly.
Also, thanks for the "2-Node Red Hat KVM Cluster Tutorial". Extremely
helpful for some of our work.
Bob Haxo
On Thu, 2013
On 02/21/2013 05:16 PM, Bob Haxo wrote:
Greetings,
Anyone know where "crm" is in RHEL 6.4, or in the most recent set of
RHEL 6.3 updates? crm is not included in the latest pacemaker-cli
package: pacemaker-cli-1.1.8-7.el6.x86_64.rpm
Bob Haxo
SGI
If I recall correctly, Red Hat is switching to
Greetings,
Anyone know where "crm" is in RHEL 6.4, or in the most recent set of
RHEL 6.3 updates? crm is not included in the latest pacemaker-cli
package: pacemaker-cli-1.1.8-7.el6.x86_64.rpm
Bob Haxo
SGI
___
Pacemaker mailing list: Pacemaker@oss.clu
Howdy all,
I'm trying to run Pacemaker 1.1.8 (from
http://clusterlabs.org/rpm-next/fedora-17/clusterlabs.repo) in a
two-node configuration under Fedora 17. I'm running into a few
different problems.
I'm trying to create resources using the systemd: manager. If I run
"pcs resource standards" I s
- Original Message -
> From: "Donald Stahl"
> To: "Jake Smith" , "The Pacemaker cluster resource
> manager"
> Sent: Thursday, February 21, 2013 2:24:59 PM
> Subject: Re: [Pacemaker] Dependency Trees
>
> > I think you may have missed a key piece - Sets. Requires more than
> > 2 and as
> I think you may have missed a key piece - Sets. Requires more than 2 and
> assumes at least one will be sequential.
Not exactly. That may have been a poor example but what I was trying
to achieve was the idea that these 2 services must run on the same
host, but that neither one had to be runni
- Original Message -
> From: "Donald Stahl"
> To: "The Pacemaker cluster resource manager"
> Sent: Thursday, February 21, 2013 9:40:06 AM
> Subject: Re: [Pacemaker] Dependency Trees
>
> > No.
> >
> > [quote]
> > If you say "colocate A with B" and there is nowhere B is allowed to
> > run
I wonder what happens in the case of two racing "crm" commands that want
to update the CIB (with non-overlapping/conflicting data). Is there any
locking to ensure that one crm cannot overwrite the other's change?
(i.e. second one to get there has to read in the new CIB before being
able to apply h
> It's of course possible to have that filesystem group and then reference
> the group in dependencies, which can simplify some setups.
True- but then you run into the problem of not being able to have
groups of groups. So if I create a group for my filesystems- I can't
create another group that in
On Wed, 2013-02-20 at 16:26 +0900, Yuichi SEINO wrote:
> Hi Jiaju,
>
> I am testing this patch.
> When a lockfile was removed, it seems that the stop of RA isn't a
> intended behavior.
I'm just curious how the lockfile was removed. Basically the existence
of the lockfile shows one boothd is star
On 2013-02-21T14:43:47, Andrew Beekhof wrote:
> > I'd love to be able to create a group called "filesystem" that
> > includes all of the file system mounts I have- and then be able to
> > create a group that includes the listener, the IP, and the filesystem
> > group- except you can't have a grou
On 2013-02-20T23:06:59, Donald Stahl wrote:
> > On the one hand, you say OraListener1 and OraInstance1 need to be on
> > the same node, but on the other you say they can start/stop
> > individually.
> There are maintenance reasons for some of these requirements- for
> example the listener can onl
> No.
>
> [quote]
> If you say "colocate A with B" and there is nowhere B is allowed to
> run, then A wont be allowed to run either.
> But once the cluster has figured out where they go, it doesn't stop
> them being started in parallel.
> [/quote]
>
> in this case, A = OraListener1 and B = OraBin1
30 matches
Mail list logo
