Dear Steven,
it seems that nova-network breaks the network also on the interface it doesn't
use, I've just done another fresh install using flat_interface eth1, and i get
the issue of packets being sent with the public address.
I think the effects of nova-network should be restricted to some
Il giorno 19/lug/2012, alle ore 00:52, Steven Dake ha scritto:
On 07/18/2012 06:51 AM, Alessandro Tagliapietra wrote:
Hi Steve,
the problem is not that it's not listening on the correct interface, as lsof
shows
corosync 1485 root9u IPv4 14890 0t0 UDP
Il giorno 19/lug/2012, alle ore 09:55, Alessandro Tagliapietra ha scritto:
Il giorno 19/lug/2012, alle ore 09:40, Alessandro Tagliapietra ha scritto:
Il giorno 19/lug/2012, alle ore 00:52, Steven Dake ha scritto:
On 07/18/2012 06:51 AM, Alessandro Tagliapietra wrote:
Hi Steve,
the
Hello,
i've 2 machines, running ubuntu 12.04, i've installed corosync + pacemaker and
it was working fine.
Corosync is using eth1 with 10.8.0.1 and 10.8.0.2 as ip of the hosts, i've got
keystone, glance, nova api-cert-scheduler, mysql, rabbitmq working in HA with
pacemaker.
The problem comes
On 07/18/2012 03:50 AM, Alessandro Tagliapietra wrote:
Hello,
i've 2 machines, running ubuntu 12.04, i've installed corosync +
pacemaker and it was working fine.
Corosync is using eth1 with 10.8.0.1 and 10.8.0.2 as ip of the hosts,
i've got keystone, glance, nova api-cert-scheduler,
Hi Steve,
the problem is not that it's not listening on the correct interface, as lsof
shows
corosync 1485 root9u IPv4 14890 0t0 UDP
226.94.1.1:5405
corosync 1485 root 10u IPv4 14891 0t0 UDP
server1:5404
corosync 1485 root 11u IPv4
6 matches
Mail list logo