On Wed, Feb 13, 2013 at 3:00 PM, Dennis Jacobfeuerborn
wrote:
> On 02/13/2013 01:43 AM, Andrew Beekhof wrote:
>> On Wed, Feb 13, 2013 at 12:52 AM, Dennis Jacobfeuerborn
>> wrote:
>>> On 02/12/2013 03:15 AM, Andrew Beekhof wrote:
On Tue, Feb 12, 2013 at 1:01 PM, Dennis Jacobfeuerborn
wr
On 02/13/2013 01:43 AM, Andrew Beekhof wrote:
> On Wed, Feb 13, 2013 at 12:52 AM, Dennis Jacobfeuerborn
> wrote:
>> On 02/12/2013 03:15 AM, Andrew Beekhof wrote:
>>> On Tue, Feb 12, 2013 at 1:01 PM, Dennis Jacobfeuerborn
>>> wrote:
On 02/12/2013 02:38 AM, Andrew Beekhof wrote:
> On Tue,
On Wed, Feb 13, 2013 at 12:52 AM, Dennis Jacobfeuerborn
wrote:
> On 02/12/2013 03:15 AM, Andrew Beekhof wrote:
>> On Tue, Feb 12, 2013 at 1:01 PM, Dennis Jacobfeuerborn
>> wrote:
>>> On 02/12/2013 02:38 AM, Andrew Beekhof wrote:
On Tue, Feb 12, 2013 at 3:09 AM, Dennis Jacobfeuerborn
wr
On 02/12/2013 03:57 PM, Dejan Muhamedagic wrote:
> Hi,
>
> On Tue, Feb 12, 2013 at 02:52:58PM +0100, Dennis Jacobfeuerborn wrote:
>> On 02/12/2013 03:15 AM, Andrew Beekhof wrote:
>>> On Tue, Feb 12, 2013 at 1:01 PM, Dennis Jacobfeuerborn
>>> wrote:
On 02/12/2013 02:38 AM, Andrew Beekhof wrot
Hi,
On Tue, Feb 12, 2013 at 02:52:58PM +0100, Dennis Jacobfeuerborn wrote:
> On 02/12/2013 03:15 AM, Andrew Beekhof wrote:
> > On Tue, Feb 12, 2013 at 1:01 PM, Dennis Jacobfeuerborn
> > wrote:
> >> On 02/12/2013 02:38 AM, Andrew Beekhof wrote:
> >>> On Tue, Feb 12, 2013 at 3:09 AM, Dennis Jacobfe
On 02/12/2013 03:15 AM, Andrew Beekhof wrote:
> On Tue, Feb 12, 2013 at 1:01 PM, Dennis Jacobfeuerborn
> wrote:
>> On 02/12/2013 02:38 AM, Andrew Beekhof wrote:
>>> On Tue, Feb 12, 2013 at 3:09 AM, Dennis Jacobfeuerborn
>>> wrote:
On 02/11/2013 11:30 AM, Andrew Beekhof wrote:
> On Mon, F
On Tue, Feb 12, 2013 at 1:01 PM, Dennis Jacobfeuerborn
wrote:
> On 02/12/2013 02:38 AM, Andrew Beekhof wrote:
>> On Tue, Feb 12, 2013 at 3:09 AM, Dennis Jacobfeuerborn
>> wrote:
>>> On 02/11/2013 11:30 AM, Andrew Beekhof wrote:
On Mon, Feb 11, 2013 at 9:24 PM, Viacheslav Biriukov
wrote
On 02/12/2013 02:38 AM, Andrew Beekhof wrote:
> On Tue, Feb 12, 2013 at 3:09 AM, Dennis Jacobfeuerborn
> wrote:
>> On 02/11/2013 11:30 AM, Andrew Beekhof wrote:
>>> On Mon, Feb 11, 2013 at 9:24 PM, Viacheslav Biriukov
>>> wrote:
It is VM in the OpenStack. So we can't use static IP.
Righ
On Tue, Feb 12, 2013 at 3:09 AM, Dennis Jacobfeuerborn
wrote:
> On 02/11/2013 11:30 AM, Andrew Beekhof wrote:
>> On Mon, Feb 11, 2013 at 9:24 PM, Viacheslav Biriukov
>> wrote:
>>> It is VM in the OpenStack. So we can't use static IP.
>>> Right now investigating why interface become down.
>>
>> Ev
Yes, you are right.
In our case we got this bug with dnsmasq (
http://markmail.org/message/7kjf4hljszpydsrx#query:+page:1+mid:7kjf4hljszpydsrx+state:results
).
Still investigating.
2013/2/11 Dennis Jacobfeuerborn
> On 02/11/2013 11:30 AM, Andrew Beekhof wrote:
> > On Mon, Feb 11, 2013 at 9:24
On 02/11/2013 11:30 AM, Andrew Beekhof wrote:
> On Mon, Feb 11, 2013 at 9:24 PM, Viacheslav Biriukov
> wrote:
>> It is VM in the OpenStack. So we can't use static IP.
>> Right now investigating why interface become down.
>
> Even if you solve that, dynamic IP addresses are fundamentally
> incompa
We need solution for something like VIP for our MySQL servers (for example)
with auto migration when something go wrong. If you have a better solution
– please suggest.
Talking about dynamic IP addresses: it is not important for us. After boot
(not every day) we reconfigure cluster using maintenanc
On Mon, Feb 11, 2013 at 9:24 PM, Viacheslav Biriukov
wrote:
> It is VM in the OpenStack. So we can't use static IP.
> Right now investigating why interface become down.
Even if you solve that, dynamic IP addresses are fundamentally
incompatible with cluster software.
You're effectively trying to
It is VM in the OpenStack. So we can't use static IP.
Right now investigating why interface become down.
Thank you!
2013/2/11 Viacheslav Biriukov
>
>
>
> 2013/2/11 Dan Frincu
>
>> Hi,
>>
>> On Sun, Feb 10, 2013 at 2:24 PM, Viacheslav Biriukov
>> wrote:
>> > Hi guys,
>> >
>> > Got a tricky iss
2013/2/11 Dan Frincu
> Hi,
>
> On Sun, Feb 10, 2013 at 2:24 PM, Viacheslav Biriukov
> wrote:
> > Hi guys,
> >
> > Got a tricky issue with Corosync and Pacemaker over DHCP IP address using
> > unicast. Corosync craches periodically.
> >
> > Packages are from centos 6 repos:
> > corosync-1.4.1-7.e
Hi,
On Sun, Feb 10, 2013 at 2:24 PM, Viacheslav Biriukov
wrote:
> Hi guys,
>
> Got a tricky issue with Corosync and Pacemaker over DHCP IP address using
> unicast. Corosync craches periodically.
>
> Packages are from centos 6 repos:
> corosync-1.4.1-7.el6_3.1.x86_64
> corosynclib-1.4.1-7.el6_3.1.
Hi guys,
Got a tricky issue with Corosync and Pacemaker over DHCP IP address using
unicast. Corosync craches periodically.
Packages are from centos 6 repos:
corosync-1.4.1-7.el6_3.1.x86_64
corosynclib-1.4.1-7.el6_3.1.x86_64
pacemaker-cluster-libs-1.1.7-6.el6.x86_64
pacemaker-libs-1.1.7-6.el6.x86_
17 matches
Mail list logo