On 26.03.2021 22:18, Reid Wahl wrote:
> On Fri, Mar 26, 2021 at 6:27 AM Andrei Borzenkov
> wrote:
>
>> On Fri, Mar 26, 2021 at 10:17 AM Ulrich Windl
>> wrote:
>>>
>> Andrei Borzenkov schrieb am 26.03.2021 um
>> 06:19 in
>>> Nachricht <534274b3-a6de-5fac-0ae4-d02c305f1...@gmail.com>:
On Fri, Mar 26, 2021 at 2:44 PM Antony Stone
wrote:
> On Friday 26 March 2021 at 18:31:51, Ken Gaillot wrote:
>
> > On Fri, 2021-03-26 at 19:59 +0300, Andrei Borzenkov wrote:
> > > On 26.03.2021 17:28, Antony Stone wrote:
> > > >
> > > > So far all is well and good, my cluster synchronises,
OCF 1.1 is now formally adopted!
https://github.com/ClusterLabs/OCF-spec/blob/master/ra/1.1/resource-agent-api.md
Thanks to everyone who gave feedback.
Now to add support for it ...
On Tue, 2021-03-09 at 17:07 -0600, Ken Gaillot wrote:
> Hi all,
>
> After many false starts over the years, we
On Friday 26 March 2021 at 18:31:51, Ken Gaillot wrote:
> On Fri, 2021-03-26 at 19:59 +0300, Andrei Borzenkov wrote:
> > On 26.03.2021 17:28, Antony Stone wrote:
> > >
> > > So far all is well and good, my cluster synchronises, starts the
> > > resources, and everything's working as expected.
On Friday 26 March 2021 at 17:59:07, Andrei Borzenkov wrote:
> On 26.03.2021 17:28, Antony Stone wrote:
> > # ocf-tester -n Asterisk /usr/lib/ocf/resource.d/heartbeat/asterisk
> > Beginning tests for /usr/lib/ocf/resource.d/heartbeat/asterisk...
> > /usr/sbin/ocf-tester: 226:
If you have an enterprise support agreement, be sure to also explore
whether your vendor supports one and not the other. For example, Red Hat
currently supports pgsql but not PAF (though there is an open BZ to add
support for PAF).
On Fri, Mar 26, 2021 at 9:14 AM Jehan-Guillaume de Rorthais
On Fri, Mar 26, 2021 at 6:27 AM Andrei Borzenkov
wrote:
> On Fri, Mar 26, 2021 at 10:17 AM Ulrich Windl
> wrote:
> >
> > >>> Andrei Borzenkov schrieb am 26.03.2021 um
> 06:19 in
> > Nachricht <534274b3-a6de-5fac-0ae4-d02c305f1...@gmail.com>:
> > > On 25.03.2021 21:45, Reid Wahl wrote:
> > >>
On Fri, Mar 26, 2021 at 4:06 AM Strahil Nikolov
wrote:
> Thanks everyone! I really appreciate your help.
>
> Actually , I found a RH solution (#5423971) that gave me enough ideas /it
> is missing some steps/ to setup the cluster prooperly.
>
Careful. That solution is for Scale-Out. The
On Fri, 2021-03-26 at 19:59 +0300, Andrei Borzenkov wrote:
> On 26.03.2021 17:28, Antony Stone wrote:
> > Hi.
> >
> > I've just signed up to the list. I've been using corosync and
> > pacemaker for
> > several years, mostly under Debian 9, which means:
> >
> > corosync 2.4.2
> >
On 26.03.2021 17:28, Antony Stone wrote:
> Hi.
>
> I've just signed up to the list. I've been using corosync and pacemaker for
> several years, mostly under Debian 9, which means:
>
> corosync 2.4.2
> pacemaker 1.1.16
>
> I've recently upgraded a test cluster to Debian 10, which
Hi,
I'm one of the PAF author, so I'm biased.
On Fri, 26 Mar 2021 14:51:28 +
Isaac Pittman wrote:
> My team has the opportunity to update our PostgreSQL resource agent to either
> PAF (https://github.com/ClusterLabs/PAF) or pgsql
>
Hi All,
My team has the opportunity to update our PostgreSQL resource agent to either
PAF (https://github.com/ClusterLabs/PAF) or pgsql
(https://github.com/ClusterLabs/resource-agents/blob/master/heartbeat/pgsql),
and I've been charged with comparing them.
After searching various mailing
Thanks everyone! I really appreciate your help.
Actually , I found a RH solution (#5423971) that gave me enough ideas /it is
missing some steps/ to setup the cluster prooperly.
So far , I have never used node attributes, order sets and location constraints
based on 'ocf:pacemaker: attribute's
Hi.
I've just signed up to the list. I've been using corosync and pacemaker for
several years, mostly under Debian 9, which means:
corosync 2.4.2
pacemaker 1.1.16
I've recently upgraded a test cluster to Debian 10, which gives me:
corosync 3.0.1
pacemaker
On Fri, Mar 26, 2021 at 10:17 AM Ulrich Windl
wrote:
>
> >>> Andrei Borzenkov schrieb am 26.03.2021 um 06:19 in
> Nachricht <534274b3-a6de-5fac-0ae4-d02c305f1...@gmail.com>:
> > On 25.03.2021 21:45, Reid Wahl wrote:
> >> FWIW we have this KB article (I seem to remember Strahil is a Red Hat
> >>
Just a clarification.
I'm using separate NFS shares for each HANA, so even if someone wipes the NFS
for DC1, the cluster will failover to DC2 (separate NFS) and survive.
Best Regards,Strahil Nikolov___
Manage your subscription:
On Fri, Mar 26, 2021 at 12:17 AM Ulrich Windl <
ulrich.wi...@rz.uni-regensburg.de> wrote:
> >>> Andrei Borzenkov schrieb am 26.03.2021 um 06:19
> in
> Nachricht <534274b3-a6de-5fac-0ae4-d02c305f1...@gmail.com>:
> > On 25.03.2021 21:45, Reid Wahl wrote:
> >> FWIW we have this KB article (I seem
>>> Andrei Borzenkov schrieb am 26.03.2021 um 06:19 in
Nachricht <534274b3-a6de-5fac-0ae4-d02c305f1...@gmail.com>:
> On 25.03.2021 21:45, Reid Wahl wrote:
>> FWIW we have this KB article (I seem to remember Strahil is a Red Hat
>> customer):
>> - How do I configure SAP HANA Scale-Up System
On Thu, Mar 25, 2021 at 11:35 PM Reid Wahl wrote:
>
>
> On Thu, Mar 25, 2021 at 10:20 PM Andrei Borzenkov
> wrote:
>
>> On 25.03.2021 21:45, Reid Wahl wrote:
>> > FWIW we have this KB article (I seem to remember Strahil is a Red Hat
>> > customer):
>> > - How do I configure SAP HANA Scale-Up
On Thu, Mar 25, 2021 at 10:20 PM Andrei Borzenkov
wrote:
> On 25.03.2021 21:45, Reid Wahl wrote:
> > FWIW we have this KB article (I seem to remember Strahil is a Red Hat
> > customer):
> > - How do I configure SAP HANA Scale-Up System Replication in a
> Pacemaker
> > cluster when the HANA
20 matches
Mail list logo
