Open Stack

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, mysql, rabbitmq
> working in HA with pacemaker.
> 
> The problem comes after installing nova-network and nova-compute, i've
> used this nova.conf:
> 
> http://pastie.org/private/ddwva8kvaypqrxk7rifvba
> 
> and after nova-compute started and hosts rebooted i can't get to work
> corosync,
> 
> the problem seems that when hosts send packets in eth1 to multicast
> address, the source ip is the public one, not the 10.8.0.x one. After
> disabling nova-network on boot everything works.
> 
> I've also tried to create a virtual eth2 device and set flat_interface
> to eth2, but it seems that still nova-network break the configuration as
> corosync still uses public ip for private lan.
> 
> Any idea?
> 

Corosync goes to great pains to route packets across the interface
identified in the corosync.conf file.  If you are using a subnet
definition ie:
bindnetaddr: 10.8.0.0, it may be that the interface's netmask is causing
a rebind to the new interface when nova network starts.

One way to force binding to a specific interface when your network is
not configured in a typical fashion is to identify the bindnetaddr exactly:

ie: bindnetaddr: 10.8.0.1

Regards
-steve

> Best Regards
> 
> -- 
> Alessandro Tagliapietra | VISup srl
> piazza 4 novembre 7
> 20124 Milano
> 
> http://www.visup.it
> 
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack at lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>