>>> Cesar Hernandez schrieb am 05.07.2017 um 16:50 in
Nachricht :
>> Not a good idea probably - and the reason for what you are experiencing ;-)
>> If you have problems starting the nodes within a certain time-window
>>
>>> Cesar Hernandez schrieb am 05.07.2017 um 08:50 in
Nachricht :
>> Might be kind of a strange race as well ... but without knowing what the
>> script actually does ...
>>
>
> The script first try to reboot the node
Hi,
I would like to know, why certiticate is created in pacemaker and what will
happen if it expires ?
Thanks and Regards,
*Bhuvanesh Kumar .G*
Linux and Email Administrator
___
Users mailing list: Users@clusterlabs.org
I'm not employed by Red Hat, so I can't speak authoritatively.
My understanding, however, is that they do not distinguish as corosync
on its own doesn't do much. The complexity comes from corosync traffic
though, but it gets more of a concern when you add in pacemaker traffic
and/or the CIB grows
Is RedHat limit node's number, or corosync's code?
At 2017-07-06 11:11:39, "Digimer" wrote:
>On 2017-07-05 09:03 PM, mlb_1 wrote:
>> Hi:
>> I heard corosync-node's number limit to 16? It's true? And Why?
>> Thanks for anyone's answer.
>>
>>
>>
>>
On 2017-07-05 09:03 PM, mlb_1 wrote:
> Hi:
> I heard corosync-node's number limit to 16? It's true? And Why?
> Thanks for anyone's answer.
>
>
>
> https://specs.openstack.org/openstack/fuel-specs/specs/6.0/pacemaker-improvements.html
>
>
>
> * Corosync 2.0 has a lot of
Hi:
I heard corosync-node's number limit to 16? It's true? And Why?
Thanks for anyone's answer.
https://specs.openstack.org/openstack/fuel-specs/specs/6.0/pacemaker-improvements.html
Corosync 2.0 has a lot of improvements that allow to have up to 100
Controllers.
Hi, your suggestion gives me some idea:
I got it working eventually with syntax:
fence_vbox --ip 10.0.2.2 --username=AW23321
--identity-file=/root/.ssh/id_rsa --plug=centos1 --host-os=windows
--action=status --vboxmanage-path="/cygdrive/c/Program\
Files/Oracle/VirtualBox/VBoxManage"
I had to put
>
>
>>>
>>> But you definitely shouldn't have a fencing-agent that claims to have fenced
>>> a node if it is not sure - rather the other way round if in doubt.
>>
>>
>
> True! Which is why I mentioned it to be dangerous.
> But your fencing-agent is even more dangerous ;-)
>
>
Well.. my
On 07/05/2017 04:50 PM, Cesar Hernandez wrote:
>> Not a good idea probably - and the reason for what you are experiencing ;-)
>> If you have problems starting the nodes within a certain time-window
>> disabling startup-fencing might be an option to consider although dangerous.
>> But you
> Not a good idea probably - and the reason for what you are experiencing ;-)
> If you have problems starting the nodes within a certain time-window
> disabling startup-fencing might be an option to consider although dangerous.
> But you definitely shouldn't have a fencing-agent that claims to
On 07/05/2017 04:22 PM, Cesar Hernandez wrote:
>
>> Are you logging which ones went OK and which failed.
>> The script returns negatively if both go wrong?
> The script always returns OK
Not a good idea probably - and the reason for what you are experiencing ;-)
If you have problems starting the
> Are you logging which ones went OK and which failed.
> The script returns negatively if both go wrong?
The script always returns OK
___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users
Project Home:
On 07/05/2017 08:50 AM, Cesar Hernandez wrote:
>> Might be kind of a strange race as well ... but without knowing what the
>> script actually does ...
>>
> The script first try to reboot the node using ssh, something like ssh $NODE
> reboot -f, then runs a remote reboot using AWS api
Are you
Wow! I'm looking forward to the September summit talk.
On 07/05/2017 01:52 AM, Digimer wrote:
> Hi all,
>
> I suspect by now, many of you here have heard me talk about the Anvil!
> intelligent availability platform. Today, I am proud to announce that it
> is ready for general use!
>
>
>>> "Lentes, Bernd" schrieb am 27.06.2017
um
13:00 in Nachricht
<659215068.3650810.1498561202181.javamail.zim...@helmholtz-muenchen.de>:
> Hi,
>
> i configured an order so that a simple virtual machine is started after some
> other resources are started.
>
You might have to use "--host-os windows". You can run it
with -v for more info about why it's failing.
On 05/07/17 10:18 +0200, ArekW wrote:
Hi,
I managed to run the Pacemaker Cluster From Scratch on two CentOS on
VirtualBox. I’m stuck at fence_vbox with similar problem as Durwin’s:
The
Hi!
Could it be that I pointed out this problem about six years ago? At least I
found a locking implementation for OCF RAs dated from 2011. My approach is a
bit different, because I use a global MUTEX lock to create the actual lock
files inside:
---
# Shell functions to support file-based
>>> Dejan Muhamedagic schrieb am 26.06.2017 um 17:05 in
Nachricht <20170626150502.GB4588@tuttle.homenet>:
> Hi,
>
> On Wed, Jun 21, 2017 at 04:40:47PM +0200, Lars Ellenberg wrote:
>>
>> Repost to a wider audience, to raise awareness for this.
>> ocf_take_lock may or may not
Hi,
I managed to run the Pacemaker Cluster From Scratch on two CentOS on
VirtualBox. I’m stuck at fence_vbox with similar problem as Durwin’s:
The script doesn’t accept the plug parameter:
[root@nfsnode1 ~]# fence_vbox --ip 10.0.2.2 --username=AW23321
--identity-file=/root/.ssh/id_rsa
Hi all,
I suspect by now, many of you here have heard me talk about the Anvil!
intelligent availability platform. Today, I am proud to announce that it
is ready for general use!
https://github.com/ClusterLabs/striker/releases/tag/v2.0.0
I started five years ago with an idea of building an
> Might be kind of a strange race as well ... but without knowing what the
> script actually does ...
>
The script first try to reboot the node using ssh, something like ssh $NODE
reboot -f, then runs a remote reboot using AWS api
Thanks
___
22 matches
Mail list logo