On 25/08/15 04:45 AM, Ulrich Windl wrote:
Digimer schrieb am 24.08.2015 um 18:20 in Nachricht
> <55db4453.10...@alteeve.ca>:
> [...]
>> Using a pair of nodes with a traditional file system exported by NFS and
>> made accessible by a floating (virtual) IP address gives you redundancy
>> withou
On 08/25/2015 05:20 AM, Ferenc Wagner wrote:
> Hi,
>
> Since Corosync is hosted on GitHub, I wonder if it's enough to submit
> pull requests/issues/patch comments there to get the developers'
> attention, or should I also post to develop...@clusterlabs.org?
GitHub is good for patches, and when yo
On 25/08/15 14:14, Streeter, Michelle N wrote:
> I am using pcs but it does nothing with the cluster.conf file. Also, I am
> currently required to use rhel6.6.
>
> I have not been able to find any documentation on what is required in the
> cluster.conf file under the newer versions of pacem
I am using pcs but it does nothing with the cluster.conf file. Also, I am
currently required to use rhel6.6.
I have not been able to find any documentation on what is required in the
cluster.conf file under the newer versions of pacemaker and I have not been
able to reduce my current versi
On 08/24/2015 12:20 PM, Digimer wrote:
> Speaking from a gfs2 background, but assuming it's similar in concept to
> ocfs2...
>
> Cluster locking comes at a performance cost. All locks need to be
> coordinated between the nodes, and that will always be slower that local
> locking only. They are als
Hi,
Since Corosync is hosted on GitHub, I wonder if it's enough to submit
pull requests/issues/patch comments there to get the developers'
attention, or should I also post to develop...@clusterlabs.org?
--
Thanks,
Feri.
___
Users mailing list: Users@cl
>>> "Ulrich Windl" schrieb am 25.08.2015 um
08:59 in Nachricht <55dc2e6602a10001b...@gwsmtp1.uni-regensburg.de>:
Jehan-Guillaume de Rorthais schrieb am 19.08.2015 um
> 10:59 in
> Nachricht <20150819105900.24f85553@erg>:
>
> [...]
[...]
>
> After users have set up their preference, the
>>> Digimer schrieb am 24.08.2015 um 18:20 in Nachricht
<55db4453.10...@alteeve.ca>:
[...]
> Using a pair of nodes with a traditional file system exported by NFS and
> made accessible by a floating (virtual) IP address gives you redundancy
> without incurring the complexity and performance overhea
Why not start with writing a real OCF RA?
>>> Tom Yates schrieb am 24.08.2015 um 11:35 in
>>> Nachricht
:
> I've got a failover firewall pair where the external interface is ADSL;
> that is, PPPoE. i've defined the service thus:
>
> primitive ExternalIP lsb:hb-adsl-helper \
> op moni
>>> Jorge Fábregas schrieb am 23.08.2015 um 20:13
in
Nachricht <55da0d4f.1080...@gmail.com>:
> Hi,
>
> I'm still doing some tests on SLES 11 SP4 & I was trying to run
> "mkfs.ocfs2" against a logical volume (with all infrastructure
> ready: cLVM & DLM & o2cb) but it gives me errors while creating
>>> Jorge Fábregas schrieb am 22.08.2015 um 19:07
in
Nachricht <55d8ac56.4020...@gmail.com>:
> On 08/22/2015 01:38 AM, Andrei Borzenkov wrote:
>> Wrong question :) Of course you can do everything manually. The real
>> question should be - will SUSE support installation done manually. If
>> you d
>>> Jorge Fábregas schrieb am 22.08.2015 um 07:12
in
Nachricht <55d804a4.50...@gmail.com>:
> Hi everyone,
>
> I'm trying out SLES 11 SP4 with the "High-Availability Extension" on two
> virtual machines. I want to keep things simple & I have a question
> regarding the csync2 tool from SUSE. Cons
>>> Kiwamu Okabe schrieb am 20.08.2015 um 18:14 in
>>> Nachricht
:
> Hi,
>
> On Wed, Aug 19, 2015 at 5:03 PM, Kiwamu Okabe wrote:
>> The resource-agents have no ocf-tester command.
>
> I updated pacemaker as 1.1.12-1.el6.
> And run ocf-tester that show following message:
>
> ```
> # ocf-teste
>>> Jehan-Guillaume de Rorthais schrieb am 19.08.2015 um
10:59 in
Nachricht <20150819105900.24f85553@erg>:
[...]
>> Because if both are included, then they will forevermore be answering the
>> question “which one should I use?”.
>
> True.
I think the user base will answer this in terms of how m
14 matches
Mail list logo